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; } } }

Interwoven workflows to production

desamgopi

Can anyone give me some ideas on moving interwoven workflows to production and want that process to be an automated process?

Thanks in advance.

Find more posts tagged with

Comments

kumar123

Can anyone give me some ideas on moving interwoven workflows to production and want that process to be an automated process?

Thanks in advance.

Moving Interwoven workflows to production? . can you more specific on this.

trace.txt

desamgopi

I want the workflows on the dev server to be moved on to the prod server.

bittu

In my thinking workflow is for within Teamsite environment not for production server.

SolutionPage.pdf

birt_engine.java

SolutionPage.rptdesign

desamgopi

I mean to the prod teamsite server

kumar123

I want the workflows on the dev server to be moved on to the prod server.

If this is the case. you can do "scp" (secure copy)command to copy from one box to another.
or
download those workflows from DEV box to your local desktop using filezilla or some other interface and then upload it back to Prod teamsite box.

desamgopi

I want that to be an automated process.

Can we use opendeploy and make it scheduled? How feasible is this process?

nipper

Can it be automated ? Possibly. Scheduled with OD ? Again possibly. Is it a good idea ? Doubtful.

Now 1st are you using WFT or WFM ? That make a big difference.

When I set up servers, I put all my changes on a config branch. I use a OOTB workflow to push everything to iw-home. You can also use that to push from your dev server to the prod server. That works great with WFT and external scripts.

That means you MUST have everything perfectly portable. No hard coded servers anywhere.

Also one other point. Per IWOV's license agreement that is a violation of the license of the Dev server OD and you must purchase a server license of OD for the Dev server to push config files from Dev to Prod.

I had long discussions with IWOV about that.

kumar123

I want that to be an automated process.

Can we use opendeploy and make it scheduled? How feasible is this process?

how often are you going to change your workflow code?

Adam Stoller

...
When I set up servers, I put all my changes on a config branch. I use a OOTB workflow to push everything to iw-home. You can also use that to push from your dev server to the prod server. That works great with WFT and external scripts.

An OOTB workflow? Which one? I usually create a simple custom wft and deployment script for this, though the deployment process usually uses a custom DNR script to manage distinctions between DEV and PROD versions of config files (shouldn't apply to WFTs, but does apply to things like templating.cfg, available_templates.cfg, etc.)

sbServiceSummaryReport.xls.zip