iwodstart -k

I'm using iwodstart -k to invoke Opendeploy DNR deployment which deploys some static files to webserver and some DCRs to the database. I also invoke an e-mail script in the DNR configuration file which sends e-mail notification to the Content Owner with some Workflow Log information. I want to pass this Workflow Log information to the DNR Configuration file as a parameter. The command looks something like this:
iwodstart -k filelist=/tmp/xyz -k history=$history dcr=/templatedata/XYZ/123.dcr workarea = /default/main/xyz/wa..
But when i try to pass a long string as history parameter Opendeploy ignores the whole string. Is there any limitation on the length of the Parameter for iwodstart -k?
I can get the workflow history information from the database by only passing the history-id as parameter to iwodstart. But i dont want to query the database.
Any help in this regard is highly appreciated.

Find more posts tagged with

Comments

Bubas_IWOV

Hi,

Try to put the variable $hisotry between " " because you may have spaces in the midle of the string and that will be enought for OD to not pick it up.

Bruno

Adam Stoller

iwodstart -k filelist=/tmp/xyz -k history=$history dcr=/templatedata/XYZ/123.dcr workarea = /default/main/xyz/wa..

Not entirely sure what you're doing here - since I don't know what $history is and nor do I know what parameters are being used within your deployment configuration file so I have to guess that there are some typos in your post and that what the command line should look like is this:

iwodstart -k filelist=/tmp/xyz -k "history=$history" -k dcr=/templatedata/XYZ/123.dcr -k workarea=/default/main/xyz/wa...

If any of the other values for the parameters contain spaces - then those too should be placed within double quotes. If any of the parameters (including $history) contain double-quotes within them, you will probably have to escape those double-quotes or substitute something in their place before issuing the command line.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

The history parameter is a string of workflow task transition comments and other details. So it can be upto 3000 characters long. I even tried passing the parameter in double quotes.

Migrateduser

I think there was a problem long ago in OD 5.0.0 regarding length of args, but that was corrected as of 5.0.1.

A thought... Perhaps there's a character, like a semicolon, in your parm that's prematurely terminating your command string? I guess if things are quoted properly this shouldn't matter, though.

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

Adam Stoller

at 3000 characters - you are likely to exceed the max length for a command line / command line argument with the OS / shell.

Where is this information being used within the configuration? Is it a DNR? source-side or target-side? If it's source-side, I'd suggest creating a file with the contents of $history, and pass the full path of the file on the command line rather than the contents. If it's target-side, then it's pretty much the same thing, except you're going to probably have to create the file on the source side and then deploy it to the target side so it can be read by the DNR.

--fish
(Interwoven Senior Technical Consultant)