nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD5.6 Problem

fyyap

Current practice in my company is, user will submit list of files that he/she has edited to Staging. From Staging, he/she will manually select those files and deploy to production servers. all these action being done in Teamsite 5.0.1.

I'm now in the process of upgrading OD to OD 5.6. The problem is, how can I retain the same practice after installing OD5.6?? Thanks.

Find more posts tagged with

Comments

Migrateduser

I think things should continue to work, since presumably you have a way to auto-generate the filelist and then kick off iwodstart. In OD 5.0.1 and 5.6 this process is the same.

You may need to alter your deployment configs for OD 5.6, depending upon which features you are using.

Note also that OD 5.6 SP1 introduced a new lighter weight CLT. So instead of...

iwodstart foo

you may want to change your invocation to...

iwodcmd start foo

Or you can use the wrapper script to replace the original iwodstart in <od-home>/bin. (This is explained in the SP1 Release Notes.)

Cheers,

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

fyyap

Hi,
Thanks for your quick reply. Just to let you know that, my current OD is 4.5 and those deployment script is in .cfg while the new scrips in OD5.6 is in .xml

So, how can I do so??

regards.

Migrateduser

There is a command line tool that can help get you started with the conversion from 4.5 to 5.6 syntax: iwodcfg2xml

Depending upon how complex your deployment configs are, you'll likely have to modify the new deployment configs by hand after running through the conversion tool.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Adam Stoller

Recommended usage of the iwodcfg2xml utiltility:

Clean up your 4.x configs by removing commented-out code and any extraneous comments (possibly all comments, but that's optional)
If you have multiple non-directly-related deployment definitions in a single deployment configuration file, break them up into separate deployment configuration files
Run the iwodcfg2xml tool as such (assumes iwodcfg2xml is on your PATH:)
- PROMPT> cd dir-with-*.cfg-files
- PROMPT> iwodcfg2xml -dir .
Examine and massage generated *.xml files
Test configurations by running iwodstart config-name -sim or, with 5.6 SP1: iwodcmd start config-name -sim (double-check on the usage of iwodcmd, I haven't had a chance to use it yet, so I might be slightly wrong on it's usage)

Note: prior to 5.6, 5.x versions require that you leave off the .xml extension of the config name (iwodstart configname) 5.6 allows (but does not require) you to include the extension (iwodstart configname.xml)
I think that's about it...

--fish
(Interwoven Senior Technical Consultant)

StreamShare.pdf