Deployment through Workflow

hi,
My workflow is doing the 2 tasks.
1. Submitting the contents (DCRS and other assets) to the staging area and 2. If the content is dcr then deploying to the database.

In the second task I am calling a perl script which in turn invokes a deployment config say Product.xml Inside the the Product.xml the dnrDeployment job is invoking Product_dd.xml which is deploying the dcr content to DB.
Here I want to know the the return code of the iwodcmd.exe which returns 0 on success. but on success or failure the command is retuning 0 only.

The flow is as follows:

WF-->Perl script --> Product.xml --> Product_dd.xml
[catching the [calling _dd [ Deploying data
return status] config ] to DB]

I am trying to catch the return status of `$cmd`
where $cmd=Path of iwodcmd.exe "Product.xml"

Here it is not possible to call the Product_dd.xml in the perl script as per the project requirement. the interaction to _dd should be through Product.xml only.
Can anybody please suggest me how and where I can catch the return status on failure of deploying data?

thanks
-Parag

Find more posts tagged with

Comments

Ambuj

Can you please post your perl script code from where you are trying to call the Product.xml?

Also tell us whether you are using transcational deployment or file list deployment?

Parag

--------------------------------------------------

Where my $iwodcmd="D:\\Programs\\Interwoven\\TeamSite\\iw-perl\\bin\\iwperl \\Programs\\Interwoven\\TeamSite\\local\\config\\wft\\Herbalife\\Submit_and_Deploy.ipl";

-----------------------------------------
The perl snippet:
$cmd=$opendeploy_cmd."$category\\Product.xml ";

Where: my $opendeploy_cmd="D:\\Programs\\Interwoven\\OpenDeployNG\\bin\\iwodcmd start content\\";

and $category is getting dynamically.
-------------------------------------------------------------------
The Product.xml:

Ambuj

<externaltask

name="DataDeployTask"

owner="__TAG__('iw_user');"

description="Initiating deployment">

<areavpath v="__TAG__('iw_workarea');"/>

<successors>

<successorset description="Data Deployment">

<succ v="End"/>



</successorset>

</successors>

<command v="__INSERT__($iwodcmd);"/>

<activation>

<pred v="Submit" />

</activation>

</externaltask>
--------------------------------------------------
Where my $iwodcmd="D:\\Programs\\Interwoven\\TeamSite\\iw-perl\\bin\\iwperl \\Programs\\Interwoven\\TeamSite\\local\\config\\wft\\Herbalife\\Submit_and_Deploy.ipl";
-----------------------------------------
The perl snippet:
$cmd=$opendeploy_cmd."$category\\Product.xml ";

Where: my $opendeploy_cmd="D:\\Programs\\Interwoven\\OpenDeployNG\\bin\\iwodcmd start content\\";

and $category is getting dynamically.
-------------------------------------------------------------------
The Product.xml:
<deployment transactional="no">

<execDeploymentTask useDefinition="DummyTask"/>

<dnrDeploymentJob location="source" when="before" state="always">

<script cmd="D:\Programs\Interwoven\OpenDeployNG\bin\iwodcmd.exe start core/Product_dd

where="D:\Programs\Interwoven\OpenDeployNG"

async="no" />

</dnrDeploymentJob>

Try to use below perl code and check if it works for you..

[html]

my $cmd=$opendeploy_cmd."$category\\Product.xml ";

my $resultfile = "D:\....\results."

my $results = `$deploy_cmd > $resultsfile`;

open (RESULTS, "<$resultsfile");
while ()
{

}
close RESULTS;

[/html]

Parag

I came to conclusion that though the second deployment descriptor Product_dd.xml fails the first deployment Product_dd.xml works successfully and wont return the any failure error code.

As in perl script I am calling Product.xml the return code I am getting is obviously of "iwocmd Product.xml" not of Product_dd.xml.
where Product_dd,xml called in dnr of Product.xml

I want to catch the return code of second deployment i.e. Product_dd.xml,

Any pointers towards this?

Thanks
-Parag

Ambuj

I came to conclusion that though the second deployment descriptor Product_dd.xml fails the first deployment Product_dd.xml works successfully and wont return the any failure error code.

As in perl script I am calling Product.xml the return code I am getting is obviously of "iwocmd Product.xml" not of Product_dd.xml.
where Product_dd,xml called in dnr of Product.xml

I want to catch the return code of second deployment i.e. Product_dd.xml,

Any pointers towards this?

Thanks
-Parag

If you are using different deployments through single config then why don't you use transactional deployment.

It will ensure that each deployment is done correctly or the entire deployment cycle will be rolled back.

Check the documentation of Database Deployment through Oped Deploy.

Cheers,
Ambuj Smiley Happy

Adam Stoller

Try to use below perl code and check if it works for you..

[html]
my $cmd=$opendeploy_cmd."$category\\Product.xml ";
my $resultfile = "D:\....\results."
my $results = `$deploy_cmd > $resultsfile`;

open (RESULTS, "<$resultsfile");
while () {

}
close RESULTS;
[/html]

I think the above could be better written as:

...
my $cmd = qq($odhome/bin/iwodcmd start $cfg $k_params $inst_param);
my $results = qx($cmd 2>&1);
my $status = $? >> 8;
if ($status) {
    # error occurred
}
else {
    # success
}
...

Note:

If the DD is being run from a DNR - it should be run from a wrapper script from an OD deployment - the DNR script should check the results of the DD run, and if an error occurred ($status != 0) then it should print to STDOUT the XML snippet that will signify to OD that the DNR failed (<response code="-2"/>) otherwise OD will assume the DNR succeeded and won't respond properly.DD should never be run directly - it should be run within a script that can detect the exit status and do the "correct" thing in response (be it printing out the XML snippet indicated above, or calling back to the workflow with a transition to an error handler, etc.)

Ambuj

[QUOTE=ghoti]I think the above could be better written as:

...
my $cmd = qq($odhome/bin/iwodcmd start $cfg $k_params $inst_param);
my $results = qx($cmd 2>&1);
my $status = $? >> 8;
if ($status) {
    # error occurred
}
else {
    # success
}
...

Note:

Thanks a lot for such a nice explanation..