Alternative for doing callback from OpenDeploy

eddie1

How many ways are there to do a callback from an IPL file after an OpenDeploy command is issued. Are there any other ways to get the deployment status from OpenDeploy and make the callnback accordingly besides the default way inwhich we store the output from the opendeploy command in the $result variable ?
The Problem im facing is that using the default way,quite often the opendeploy command from my IPL doesnt get called and my $results variable contains nothing causing the callback saying that OpenDeploy command failed when it actually never got called. The reason im certain that it never gets called is that there is no log created by OpenDeploy.

Any help and esecially any work arounds for an immediate solution would be a life saver !!! Please note ..... i have to do this thru the IPL file as it is collecting workflow variables from the workflow and passing them to the OpenDeploy command.

Thanks for your help.

Adam Stoller

I just responded to this in a different thread, but essentially the recommended way to facilitate this depends on the version of the software you are running, the version of the OS you are running it on, and the method you are using for invoking the command.If you are using back-ticks (`...`) - you generally should be able to test the value of the $? variable after the command has run, where a value of zero is success and non-zero is failure.If you are using system() - you should be capturing the return code yourself (my $ret = system(...);) and then perform the same test on the value within $ret. If you are running on Windows2000 - with OpenDeploy 5.5.1 SP2 - you should be able to get reasonably reliable results using either IWODHOME/bin/iwodstart.bat or IWODHOME/solutions/perl/iwodstart.iplIf you are using an earlier version than OpenDeploy 5.5.1 SP2 or you are running on Windows NT - you will need to use IWODHOME/solutions/perl/iwodstart.ipl since batch scripts on NT apparently do not correctly return exit status results.If you are running on Unix - I believe you should be able to use the IWODHOME/bin/iwodstart shell script.NOTE: if you find a situation where, using the above approaches, the exit status is zero, but there are failures in the deployment, please contact Interwoven Support to report the problem and provide them the config files and log files and the screen output, etc.

--fish
(Interwoven Senior Technical Consultant)