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

iwodcmd and callback

iwTech

My work flow uses an external task. [font=Book Antiqua][size=2]The external task calls an ipl file .

[/size][/font]

[font=Book Antiqua][size=2]The ipl file execute the iwodcmd ,

If iwodcmd cmmd fails ,
I have to send an email notification

[/size][/font]

What logic I use for the following command

[HTML]
`C:/Interwoven/OpenDeployNG/bin/iwodcmd start XXXX/xxx123 -k area=$areapath -k file=$filepath `;
[/HTML]

for passing the callback values

Callback (“0”, success) /Callback (“1”, failure)

[font=Book Antiqua]Thanks

-Vin

[/font]

Find more posts tagged with

Comments

Adam Stoller

My work flow uses an external task. [font=Book Antiqua][size=2]The external task calls an ipl file .
[/size][/font]
[font=Book Antiqua][size=2]The ipl file execute the iwodcmd ,
If iwodcmd cmmd fails ,
I have to send an email notification
[/size][/font]
What logic I use for the following command
[HTML]
`C:/Interwoven/OpenDeployNG/bin/iwodcmd start XXXX/xxx123 -k area=$areapath -k file=$filepath `;
[/HTML]
for passing the callback values
Callback (“0”, success) /Callback (“1”, failure)

[font=Book Antiqua]Thanks

-Vin
[/font]

my $cmd = qq($odhome/bin/iwodcmd start ****/xxx123 -k area=$areapath -k file=$filepath);
my $results = qx($cmd 2>&1);
my ($callback, $msg) = ($?) ? (1, "Error") : (0, "Success");
$task->CallBack($callback, $msg);

Personally, I usually check the actual exit status to determine the type of failure and provide a more useful callback message, but I'll leave that up to you.

kaalraa

my $cmd = qq($odhome/bin/iwodcmd start ****/xxx123 -k area=$areapath -k file=$filepath);
my $results = qx($cmd 2>&1);
my ($callback, $msg) = ($?) ? (1, "Error") : (0, "Success");
$task->CallBack($callback, $msg);
Personally, I usually check the actual exit status to determine the type of failure and provide a more useful callback message, but I'll leave that up to you.

Hey Adam.

Could you please provide more info, as how you determine the type of failure? Generally, OD provide the error code as 512 in case of an error occurance.

Jcse

My work flow uses an external task. [font=Book Antiqua][size=2]The external task calls an ipl file .
[/size][/font]
[font=Book Antiqua][size=2]The ipl file execute the iwodcmd ,
If iwodcmd cmmd fails ,
I have to send an email notification
[/size][/font]
What logic I use for the following command
[HTML]
`C:/Interwoven/OpenDeployNG/bin/iwodcmd start XXXX/xxx123 -k area=$areapath -k file=$filepath `;
[/HTML]
for passing the callback values
Callback (“0”, success) /Callback (“1”, failure)

[font=Book Antiqua]Thanks

-Vin
[/font]

Hi

I have done similar thing using a java code,just as ghoti said check for deployment status returned to you by the CLT,based on that place your CallBack.you can also set the error msg as transition comment.

For determine the next level transition link,check for your final job specification file if required(i means to say to determine which should be 0 or 1).

Adam Stoller

Hey Adam.

Could you please provide more info, as how you determine the type of failure? Generally, OD provide the error code as 512 in case of an error occurance.

...
my $result = qx($cmd 2>&1);
my $status = $? >> 8;
my ($callback, $msg) = ($status == 0) ? (0, "Success")
                     : ($status == 1) ? (1, "Failed to start")
                     : ($status == 2) ? (1, "Ran and failed")
                     : ($status == 9) ? (1, "Completed with errors")
                     :                ? (1, "Unknown ($status)");
...

You need to shift the exit status code because it gets padded by the shell processes it gets run through. Usually you only have to shift it once, if you're worried about it you could do something like:

$status = $?;
while ($status > 155) {
    $status >>= 8;
}

iwTech

Hi Adam.

Thank you very much for the answers and detailed explanations .
-Vin