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

iwodstart.ipl and spaces

System

Has anyone successfully used the iwodstart.ipl script in Windows to start a deployment where the deployment configuration file contains spaces in the name (i.e., "Generic - 2 node.xml")? I seems to think the -, 2 and node.xml are separate parameters.

Sebouh

Find more posts tagged with

Comments

Adam Stoller

(1) I recommend strongly against having spaces in paths and/or filenames - they cause problems all over the place.
(2) Which version of OpenDeploy are you using (including service pack and patches)?
(3) How are you trying to invoke the deployment?

Have you tried:
iwodstart "Generic -2 node.xml"

As near as I can tell - iwodstart.ipl does try to quote the parameters passed to it, so if you pass the argument with spaces within quotes it *should* be preserved, but I haven't verified that.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

1) We use spaces in the names of all of our deployment names and have had no problems up to now.
2) OD 5.5.1 SP2 w/patches running on Windows 2000
3) We tried invoking through workflow and directly from the command line. Seems like the java class that processes things in iwodstart.ipl gags on the quotes... For example:

c:\iw-home\iw-perl\bin\iwperl c:/iw-od/OpenDeployNG/solutions/perl/iwodstart.ipl "Generic - 1 Node" -k "defname=ALG_Intranet" -k "node1=WEBS1" -k "srcpath=." -k "srcarea=Y:\default\main\ALG_Intranet\WORKAREA\Prod_Content" -k "flist=c:\iw-home\tmp\filelists\alg45499.txt" -k "trgarea=d:\web\ALG"

Returns the following:

***WARNING - Ignoring unrecognized argument: '-'.
***WARNING - Ignoring unrecognized argument: '1'.
***WARNING - Ignoring unrecognized argument: 'Node'.

Locating OpenDeploy service.
OpenDeploy server host: localhost, RMI registry port: 9173
Got OpenDeploy service.
>>>>>-- Start deployment Generic.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
***ERROR - Starting deployment.
Reason from server: DEPLOY_CONFIG_FILE
Details : Deployment config file not found (C:\iw-od\OPENDE~1\conf\Generic.xml)

nipper

Two points, if you are putting this in a WF, then it needs to be double quoted (since it the quotes may themselves be a special character).

Also, you do not put the .xml on the commandline for iwodstart. It will append it (and error out in 5.51)

Andy

Adam Stoller

OpenDeploy 5.6 accepts the .xml on the end of the config file - but it doesn't require it.

--fish
(Interwoven Senior Technical Consultant)

Adam Stoller

Since iwodstart.ipl is a perl script - you can easily run it in debug mode to see what is going on (I don't have time right now) - I know there is code in there (at least in the version I have) to try and ensure that all arguments are quoted - but perhaps either (a) that was added after 5.5.1 SP2, or (b) it may not be working as intended.

The code I'm referring to starts on line 96 of the version of the script I'm using:

foreach $myargv (@ARGV) {
    push(@MYARGS, "\"$myargv\"");
    if ($myargv eq "-h" || $myargv eq "-v") {
        $nostatus = 1;
    }
}


# ---- CMD TO RUN OD AGENT API CLIENT
my($DEPLOYAPI_CLIENT_CMD) = join(" ",
                                 "$JAVA_EXE",
                                 "-classpath \"$JAVA_CLASSPATH\"",
                                 "-Dinterwoven.deployapi.locator=\"$DEPLOYAPI_SERVICE_LOCATOR\"",
                                 "\"$CLT_CLASS\"",
                                 "\"$DEPLOY_SERVICE\"",
                                 "\"$OD_DIR\"",
@MYARGS);

Either the quoting into MYARGS is not working - *or* - the use of @MYARGS below it isn't working - if you run the command through the debugger, these are the places I would look for the problem.

If you *do* have the code above in your version of iwodstart.ipl and you *do* track it down - please contact Interwoven Support to file a specific bug report so it can be fixed. (I'd do it myself, but as I said, I don't have time right now, sorry)

--fish
(Interwoven Senior Technical Consultant)