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 command line deployment

JeanIns

When running iwodstart from a command prompt from the server, it returns the following information:

>>>>-- Deployment prodmaildeploy finished:
ID: XX Start time: Mon Mar 01
Status: Completed

I need to display this information when invoking iwodstart from a script ????????

This is my code on windows 2000 that's not working:

cmd = "$OdHome\\bin\\iwodstart agentsite_prod";
$return = `$cmd 2>&1`;
print "\n";
print "\n\n";

Thanks

Edited by JeanIns on 03/02/04 08:41 AM (server time).

Find more posts tagged with

Comments

JonathonG

Not sure if this is just a cut-n-paste issue, but you're missing a $ in the code you posted:

cmd = "$OdHome\\bin\\iwodstart agentsite_prod";

should be:

$cmd = "$OdHome\\bin\\iwodstart agentsite_prod";

Assuming that isn't the problem, what do you get printed to your screen when you run this code?

Jonathon
Independent Interwoven Contractor

JeanIns

Nothing is returned, but the content is deployed. (The missing $ was a cut and paste issue). Thanks.

Sunil Mugalavally

Hi,
Try just this

$cmd = "$OdHome\\bin\\iwodstart agentsite_prod";
$return = `$cmd`;
print "\n";
print "\n\n";

Adam Stoller

Two possibilities come to mind:

Change
```
$return = `$cmd 2>&1`;
```
to either:
```
@return = `$cmd 2>&1`;
```
or:
```
{
    local $/;
    $return = `$cmd 2>&1`;
}
```
The hypothesis being that using a simple scalar the way you are, you may only be getting the first line of output which might just happen to be a blank line.
Try using something like this instead:
```
open(PIPE, "$cmd 2>&1 |") || die "[pipe] '$cmd' ($!)";
$return .= $_ while();
close(PIPE);
```
The hypothesis being that backticks mignt not support the redirection of stderr to stdout the way you are trying to do it (note: I cannot remember whether it's 2>&1| or |2>&1)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rodigz

Hi All,

What's wrong with my command line deployment??

$res=system("/usr/Interwoven/OpenDeployNG/bin/iwodstart -fs /usr/Interwoven/OpenDeployNG/conf/Verticals.xml $deployment >>/dev/null");

No errors but the no files transfer.

regards,
Rod

rodigz

Correct one..

$res=system("/usr/Interwoven/OpenDeployNG/bin/iwodstart Verticals");

Adam Stoller

The first one you posted looked like it was based on OD 4.x rather than 5.x - and you were redirecting everything to /dev/null so you wouldn't see any error messages.

The second one you posted looks correct - is this *not* working for you?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

lhdavis

This may be a stupid question, but does your Verticals.xml file reside under the /usr/Interwoven/OpenDeployNG/conf directory? Do any of your deployments work or is it just this one in particular that you are having problems with? Check /usr/Interwoven/OpenDeployNG/log to see if any log files are being generated for this deployment.

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

rodigz

thanks..it's working now.

lhdavis

Can you share with the group what was wrong?

Luke Davis
Open Technology Group, Inc.
luke.davis@med.va.gov

rodigz

This is the correct command to run the Open Deploy 5.6.

$res=system("/usr/Interwoven/OpenDeployNG/bin/iwodstart Verticals");

Adam Stoller

If you have 5.6 SP1 (or higher) you could alternatively use:

$res = system("/usr/Interwoven/OpenDeployNG/bin/iwodcmd start Verticals");

iwodcmd start - does not initiate a new JVM each time it's run. Whereas iwodstart does.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rodigz

Hi,

I have a long list of Definition let say 1, 2, 3. But with this one to 1,2,3. Users can select one only.. Let say the user select one. What will be the command line?

In O.D. 4.2

$res=system("/home/teamsite/iw-home/opendeploy/bin/iwdeploy -fs /home/teamsite/iw-home/opendeploy/conf/sample.cfg 1 >>/dev/null");

How about in od. 5.6? What the command line?
$res = system("/usr/Interwoven/OpenDeployNG/bin/iwodcmd start Sample ");

regards,

Adam Stoller

n O.D. 4.2

$res=system("/home/teamsite/iw-home/opendeploy/bin/iwdeploy -fs /home/teamsite/iw-home/opendeploy/conf/sample.cfg 1 >>/dev/null");

How about in od. 5.6? What the command line?
$res = system("/usr/Interwoven/OpenDeployNG/bin/iwodcmd start Sample ");

Close. In your 4.2 example the deployment configuration file was named "sample.cfg" for 5.x and beyond it would need to be named "sample.xml", and the contents would be structured significantly different (there is a tool in the 5.x distribution called iwodcfg2xml that can be used to assist you in converting 4.x config files to 5.x XML config files - this tool does not appear to be part of the recently released OD 6.x distribution).

Given the filename "sample.xml" the basic 5.x config line would be:

    iwodcmd start sample

not

    iwodcmd start Sample

(the latter would be correct if the config file were named with an uppercase 'S').

As for the other part of your question - if you have N different definitions specified within this config file but you only want one of them to be executed at any particular point in time - you would set this up within the deployment configuration file with something like this: <deployment>
<execDeploymentTask useDefinition="$def^"/>
</deployment>This now means that you have to pass the value of "def" in on the command line, which is done with the -k flag like this (using your 4.x command line as an example of definition names):

   iwodcmd start sample -k def="1"

    iwodcmd start sample -k def="2"

etc.

Okay?

In general, you only want multiple definitions within a single deployment configuration file if:

they are all to be executed in parallel (multiple execDeploymentTask elements), or
they are all related but only one should be executed at a time.

This differs from the 4.x style of configuration where you tended to stick everything into one large monolithic configuration file. You can still do that, but it's not really a "best practice"

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rodigz

Hi Fish,

In the xml defintion I use varible in the useDefintion.
<deployment> <execDeploymentTask useDefinition="$def^"/> </deployment>

How will I define the deploy and run of each defintion.? For instance the value of the variable $def is test and will run deploy and run sample.ipl.

thanks..

Adam Stoller

I'd need to see the entire deployment configuration file and be informed of exactly what you're trying to accomplish in order to answer your question.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rodigz

Hi Fish,

Here's what I'm trying to do.. My useDenifition is base on the variable. Now I want to execute certain deploy n run script base on the usedefintion variable.

<deployment transactional="no">
<execDeploymentTask useDefinition="$dep^">
<deployNRun>
<dnrDeployment location="target" when="after" state="success" mask="corporate$">
<script cmd="/home/teamsite/dbengine/testmailcorp.pl" as="" where="" async="no" />
</dnrDeployment>
<dnrDeployment location="target" when="after" state="success" mask="CP$">
<script cmd="/home/teamsite/dbengine/testmail.pl" as="" where="" async="no" />
</dnrDeployment>
</deployNRun>
</execDeploymentTask>
</deployment>

thanks!

Adam Stoller

You're not really clarifying things too much here.

Are you saying you have multiple defintions - and depending on which definition your exec'ing you want to use a different DNR?

You might be able to do this with a bunch of different variables - but frankly if it gets that complicated I think you'd be better off creating distinct configuration files and then you won't have to pass as many variables around on the command line...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rodigz

Hi Fish,

Basically deploy and run will execute base on the value usedefinition variable.
Let say the value of $dep is CP then it will only execute CP deploy and run.

<deployment transactional="no">
<execDeploymentTask useDefinition="$dep^">
<deployNRun>
<dnrDeployment location="target" when="after" state="success" mask="corporate$">
<script cmd="/home/teamsite/dbengine/testmailcorp.pl" as="" where="" async="no" />
</dnrDeployment>
<dnrDeployment location="target" when="after" state="success" mask="CP$">
<script cmd="/home/teamsite/dbengine/testmail.pl" as="" where="" async="no" />
</dnrDeployment>
</deployNRun>
</execDeploymentTask>
</deployment>

Due to my old setup that's why I'm trying the configuration like this. I might consider your suggestion if things will not work.

thanks!

Adam Stoller

There's no conditional logic within the deployNRun clause - so, as written, regardless of the value of $dep - both dnrDeployment scripts will run (note: dnrDeployment does NOT use 'mask' - that's only for dnrFile and dnrDir) - If you are always going to have a dnrDeployment script run and you want to control the script that is run based on the deployment definition name you might be able to do something like this:<deployment transactional="no">
<execDeploymentTask useDefinition="$dep^">
<deployNRun>
<dnrDeployment location="target" when="after" state="success">
<script cmd="/home/teamsite/dbengine/testmail$dep^.pl"/>
</dnrDeployment>
</deployNRun>
</execDeploymentTask>
</deployment>If you cannot tie the name of the script directly to the name of the definition being run, then you need two parameters - one for the useDefinition="$dep^" and one for the <script cmd="..."/> place.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

rodigz

thanks..for showing me the way..

rodigz

Hi Fish,

How to pass two key/value substitution with "key=value" as arg.??

$res=system("/usr/Interwoven/OpenDeployNG/bin/iwodstart cs_htm -k dep=$deployment; -k script=$scriptfile");

thanks!

Adam Stoller

Yes - that will work - I wasn't sure if you wanted to use the same key/value for both parts of the config file. If the values are going to be the same, you might as well use the same key. If the values may be different, then by all means use different keys.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com