Deployment scripts in workflows

Hi
I have a problem in invoking the deployment script from workflow.

I am using TS 5.5.2 (recently upgraded from TS 5.5.1) and OD 5.5.1. The operating system I am using is Windows 2000.

The deployment works fine (checked the logs) but it is not returning any return code / console output when invoked from workflow.

The deployment works fine (checked the logs) and also returning any return code / console output when invoked from command prompt / TeamSite menus.

I have used iwodstart.bat which is in (/ODHOME/bin directory) and iwodstart.ipl (/ODHOME/solutions/perl directory).

Can you have any bug-fix (patch) available for this scenario.

It would be great if someone shares about any information in this regard.

Thanks in advance.

With Regards
Ashok Kumar N.

Find more posts tagged with

Comments

Bubas_IWOV

Hi,

Can you be more explicit in what you are looking for?

Bruno

ashokk

Hi Bruno

Thanks for your message.

I am invoking iwodstart.bat / iwodstart.ipl file from teamsite gui /command prompt. These scripts return the output into console. I am storing this output in a variable and parses the variable for any error reported. But this is not true in case when invoked from workflow. There is no output returned into console. I am unable to detect whether deployment is successful / failure. Can this information sufficient. Or do you need more information.

Regards
Ashok.

Bubas_IWOV

Hi,

what i did before, is to start the OD i used an external task.

my $command = "$iwhome/opendeploy/OpenDeployNG/bin/iwodstart portal_hourly_Documents";
print LOG "OD Command -> $command\n";

my $result = `$command`;

print LOG "OD Result -> $result\n";

if ($result=~ /Status: Failed/)
{

$callback_result = 1;

return $callback_result;

}elsif ($result=~ /Status: Completed/)
{

$callback_result = 0;

}

what i would add to this as well is if you dont get anything back then the od should fail as well.

Hope this helps
Bruno

ashokk

Hi Bruno

The problem is $result is empty after the deployment is done. I dont know why this is empty. Note the deployment went fine.

Anyway thanks for your inputs

Regards
Ashok.

Bubas_IWOV

Then we must be doing different things, because when i did this i used to get the log of the deploy as you see when you run it from the command line and then is just a question of searching for key words that identify if it failed or not.

ashokk

Hi Bruno

This problem never used to occur before upgrade of 5.5.2. The output of the command is not stored in the result. This is the actual problem. What I need to do for command returning result in a variable.

Regards
Ashok.

Adam Stoller

Can you please post the *exact* code you are using to initiate your deployment and [attempting] to capture the result / exit status?

--fish
(Interwoven Senior Technical Consultant)

SMTP_MIME_Runtime_Settings.JPG

ashokk

Hi Fish

Attached is the script i am using in the workflow

Regards
Ashok.

DCPackage.zip

Adam Stoller

 my $cmd = "$IWHOME/opendeploy/OpenDeployNG/bin/iwodstart $edc -inst ${country_name}_${lasted} -k edition=$lasted -k branch=$branch_substr -k target=$target -k argument=$countryToLang{$country_name} -k dtype=$dtype";

my $res = `$cmd 2>&1`;
# Checks whether any error reported from running the script
if (($res =~ m|.*ERROR.*|) || ($res =~ m|.*Failed.*|)) {
# Report error
$logText .= "Problem in deployment of $edc.xml -- $res ";
}

Try the following:my $cmd = "...";
my $res;
{
local $/; # ignore newlines
$res = `$cmd 2>&1`;
}
my $stauts = $?;
if ($status || ($res =~ m|(ERROR|Failed)|s)){
# Report error
$logText .= "Problem in deployment of $edc.xml -- $res ";
}

--fish
(Interwoven Senior Technical Consultant)

ashokk

Hi Fish

Thanks for your help.

I have fixed this problem now. Here is how I fixed the same.

Changed invocation of deployment as
my $cmd = "$IWHOME/opendeploy/OpenDeployNG/solutions/perl/iwodstart.ipl $edc -inst ${country_name}_${lasted} -k edition=$lasted -k branch=$branch_substr -k target=$target -k argument=$countryToLang{$country_name} -k dtype=$dtype";
instead of
my $cmd = "$IWHOME/opendeploy/OpenDeployNG/bin/iwodstart $edc -inst ${country_name}_${lasted} -k edition=$lasted -k branch=$branch_substr -k target=$target -k argument=$countryToLang{$country_name} -k dtype=$dtype";

Incorporated the bug-fix in iwodstart.ipl for throwing console output to the calling program as below:

# Commented this code segment by Ashok
# Date: 16.09.2003
# ---- RUN OD AGENT API CLIENT
#open(PIPE, "$DEPLOYAPI_CLIENT_CMD 2>&1 |");
#while(<PIPE>){
# print $_;
#}
#close(PIPE);
#`$DEPLOYAPI_CLIENT_CMD`;
#my($status) = $?;
#print "STATUS: $status\n";
#die "OpenDeploy Failed" if ($status != 0);
#exit(0);

# Inserted by Ashok to return console output to a variable
# and corresponded to calling program.
# Date: 16.09.2003
my $res = `$DEPLOYAPI_CLIENT_CMD`;
die "$res";

Regards
Ashok.

Edited by ashokk on 09/16/03 04:32 AM (server time).

Adam Stoller

my $res = `$DEPLOYAPI_CLIENT_CMD`;
die "$res";

The above looks suspiciously wrong. As regardless of whether the $DEPLOYAPI_CLIENT_CMD succeeds or fails - you are always initiating a 'die' (which causes a non-zero exit status) - instead I'd suggest something like:

my $res = `$DEPLOYAPI_CLIENT_CMD 2>&1`;
my $status = $?;
print $res;
exit($status);

However, I think the reason for the pipe was to allow printing things as they happened (or near-to) - the problem with it is probably that it's doing a 'print $_;' and not a 'print STDERR $_;' -- the former will be buffered and thus you lose anything that you might have gained by doing the pipe.

--fish
(Interwoven Senior Technical Consultant)