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

DD with WFM ?

nipper

I am finally working WFM. I have my external task working fine. However I have a Q with the Deploy Task. To invoke the DD I run this:

iwodcmd start DD/DD.xml -k iwdd=NAV -k areavpath=/default/main/branch/workarea/content -k filelist=/interwoven/iw-home/tmp/filelist.txt

So how do I put this into WFM ? I made the deployment DD/DD.xml, easy enough. I see a way to set -k flags, but it is prepended with odSubst_

So I can change my filelist variable to odSubst_filelist (same with areavpath) but what about iwdd ? There is no variable called iwdd in my deployment. Also is there a standard way that the deployment task creates a filelist ? I figure I can create on on the fly but I would have thought it was handled already.

TIA

Andy

Find more posts tagged with

Comments

moonkhanna

I am finally working WFM. I have my external task working fine. However I have a Q with the Deploy Task. To invoke the DD I run this:

iwodcmd start DD/DD.xml -k iwdd=NAV -k areavpath=/default/main/branch/workarea/content -k filelist=/interwoven/iw-home/tmp/filelist.txt

So how do I put this into WFM ? I made the deployment DD/DD.xml, easy enough. I see a way to set -k flags, but it is prepended with odSubst_

So I can change my filelist variable to odSubst_filelist (same with areavpath) but what about iwdd ? There is no variable called iwdd in my deployment. Also is there a standard way that the deployment task creates a filelist ? I figure I can create on on the fly but I would have thought it was handled already.

TIA

Andy

Hi Andy,

I believe you will have to call an IPL from WFM and run your DD initialisation from the perl script.. Did you try that?

Faizi

If you are using Deploy Task in WFM then you can pass DD Config file as well as variable.

Just click on Variables in Task properties pane than a pop-up will come there is a drop down which is name value pair. Only put the "odDeploymentName" value which deployment file like if your deployment file name is deploy.xml then put "deploy" (without ext) only, rest of the variables are optional.

If you want to pass some variable, which is mentioned in DD Config file then click on OD Variables in properties pane and add variables with name and its value, Which must be same as DD file.

nipper

Munish, I was trying to see if the deploy task is usable, I certainly can write a perl script, but I am trying to follow the IWOV direction. Heck I could have done this easier in WFT. :-)

If you want to pass some variable, which is mentioned in DD Config file then click on OD Variables in properties pane and add variables with name and its value, Which must be same as DD file.

Yea, that was what I was doing, but in setting the variables, WFM tells me that it will prepend odSubst_ to the variable name. I can do that for filelist, but to run DD you must use -k iwdd=something

If I understand the deployment task, WFM will change that to odSubst_iwdd which will not work.

Faizi

but to run DD you must use -k iwdd=something
If I understand the deployment task, WFM will change that to odSubst_iwdd which will not work.

I have checked OD Variables and it is not prefix odSubst_ with the variable on windows environment.

I have passed OD Variable iwdd=value and it appears same iwdd=value.

Although it is mentioned WFM guide. But i can assure you that it is not prefixed on my side and works fine.

nipper

I have checked OD Variables and it is not prefix odSubst_ with the variable on windows environment.

I have passed OD Variable iwdd=value and it appears same iwdd=value.

Although it is mentioned WFM guide. But i can assure you that it is not prefixed on my side and works fine.

Yea, I was kind of figuring that out too. I am not certain what the heck the prefix is for, but it does nto seem to be used. Of course the documentation is lacking to say the least.

13adam13

I am not certain what the heck the prefix is for, but it does not seem to be used. Of course the documentation is lacking to say the least.

If you look at the details on the task, the task variables are prefixed with odSubst_, however the task then attaches those variables to the deploment without the prefix. I assume this is so that the external task knows which tasks variables need to be passed through as deployment variables.
this is important to know if you are going to change the task variables dynamically before it calls OpenDeploy.