Multiple OpenDeploy DNR scripts, failure and rollback

A couple of questions on OpenDeploy 6.1.0 behaviour when multiple DNR scripts are used with transactional deployments.

If you have 2 <dnrDeployment location="source" when="after" triggerpoint="transfer" state="success"> DNR scripts, the OD Admin guide says they are executed in the order they appear in the config. If the first DNR script returns an error, is the second DNR still executed or is it skipped as OD is now in a rollback state ?

Also what is the behaviour if your first DNR script is on the 'source' and the second DNR is on the 'target' ? Are the DNR scripts still executed in the order they appear in the config and is the second DNR executed if the first DNR returns an error.

Many thanks

Find more posts tagged with

Comments

debus

Does anyone have any clues on how OpenDeploy may behave in the scenario described ? I expect OD will behave the same for OD 6.0.x and 6.1, is this a fair assumption ?

Many thanks.

Siddharth

I have a similar question. How do we get back a handle from a DNR shell sctript on the failure of the script so as then next DNR is not executed.

In our scenario we call a BEA Bulk loader script..Once that script is executed I delete the files on the target system, since i dont need them.....

Currently even when my BEA Bulkloader script fails the next script deletes the files..which i want to avoid...

Any idea on this..How to get back a handle from the script and break the flow and return with an Error.

Thx

Sid

Adam Stoller

I have a similar question. How do we get back a handle from a DNR shell sctript on the failure of the script so as then next DNR is not executed.

In our scenario we call a BEA Bulk loader script..Once that script is executed I delete the files on the target system, since i dont need them.....

Currently even when my BEA Bulkloader script fails the next script deletes the files..which i want to avoid...

Any idea on this..How to get back a handle from the script and break the flow and return with an Error.

Thx

Sid

Are you talking about <response code="-2"/>? (see OD Admin manual for more details)

John742

Seems like I would go with Fish's Idea on this. But you will need to break your OD calls into mutiple OD deployments and callback to the script that invoked OD to get the OD return, Unless OD6.1 has greatly changed this.