Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
DeployNRun Return Code?
rwinterpacht
We have a PERL script, which calls OD 5.5 with arguments. The config file is setup to execute a dnr script on the target after successful deployment, but would like to somehow get that status back to the calling perl script. The documentation shows playing around with parsing log files, and writing to some temporary log files, but how would that be done if the script is running on the target, and the PERL script needs to know on the source server?
Thanks,
Raf Winterpacht
Find more posts tagged with
Comments
sunil_j
What kind of DNR scripts are you trying to execute ? Do give some more details on the script which calls the OD 5.5 and also the DNR script ?
Regards
Sunil
Interwoven TeamSite Consultant
rwinterpacht
The DNR scripts are running on the app server to explode a deployed EAR file for Websphere. The perl script on TeamSite calling the deployment needs to wait for that to succesfully take place, before deploying the zip file to the web server(s). Then, on the web servers, a DNR script explodes the zip file. We're not as concerned about that script, but would like to know if the EAR file on the app server was successfully installed before running the web server deployment.
Thanks,
Raf Winterpacht
marcussteiner
in the called .*ipl file you'll have to print the following if you want to give an error back to the opendeploy script:
print "<response code=\"-2\" />"; #failure
Print to stdout and make sure you take the exact syntax as above. one blank more or less will not work (at least not on windows)
if our perl script should return a success we use the following.
print "<response code=\"0\" />"; #success
In transactional mode this will all your assets (file and database) to be rolled back.
hope this helps
m
rwinterpacht
Thanks for the help...we'll try this out and see if the whole thing works. Lots of moving parts (thus points of failure), but more solid than it was.
Thanks,
Raf Winterpacht
Adam Stoller
print "<response code=\"-2\" />"; #failure
If recollection serves correct - I think you also need to make sure that there's a newline at the end of that string - something like:
print qq(<response code="-2"/>
\n
); # failure
You don't really need to send the code="0" one as far as I know, if the exec'd program exits without spitting something like the above to STDOUT, it assumes success and proceeds.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
DM Sender (SAPConnect 5.6.1).docx