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

DNR related problem - Urgent

Richu

Hi,
PFA the open deploy config file. It contains two DNR call to two perl files - Deploy_metadata.ipl and Invoke_BatchScript.ipl.
If Deploy_metadata.ipl fails then it does not invoke the other perl file which is correct and as per my requirement also. But..... if the Invoke_BatchScript.ipl fails then the Deploy_metadata.ipl is success and metadata deploys successfully. As per my requirements, if the Invoke_BatchScript fails then the metadata deployment should rollback.
Is there any way to achieve this.
Please help!!. Its vey urgent.

Thanks,
Richa

Find more posts tagged with

Comments

Adam Stoller

Hi,
PFA the open deploy config file. It contains two DNR call to two perl files - Deploy_metadata.ipl and Invoke_BatchScript.ipl.
If Deploy_metadata.ipl fails then it does not invoke the other perl file which is correct and as per my requirement also. But..... if the Invoke_BatchScript.ipl fails then the Deploy_metadata.ipl is success and metadata deploys successfully. As per my requirements, if the Invoke_BatchScript fails then the metadata deployment should rollback.
Is there any way to achieve this.
Please help!!. Its vey urgent.

Thanks,
Richa

The only way to achieve this is to have yet-another DNR called, on failure, after rollback - to again perform the DD deployment. I believe this should work, but cannot state so categorically as I've never had to do this.

I suggest you [re-]read [carefully] the entire section of the OD manual that deals with Deploy and Run (that's chapter 4 in the OD_621_deploy_V03_EN.pdf -- not sure what version you're using)

ISCBorisB

Hi,
PFA the open deploy config file. It contains two DNR call to two perl files - Deploy_metadata.ipl and Invoke_BatchScript.ipl.
If Deploy_metadata.ipl fails then it does not invoke the other perl file which is correct and as per my requirement also. But..... if the Invoke_BatchScript.ipl fails then the Deploy_metadata.ipl is success and metadata deploys successfully. As per my requirements, if the Invoke_BatchScript fails then the metadata deployment should rollback.
Is there any way to achieve this.
Please help!!. Its vey urgent.

Thanks,
Richa

What you are trying to do boils down to the File Deployment A running nested Data Deployment B "before". The fact that
you have another depending script is mostly irrelevant.

It is trivial to fail/roll-back A if B fails. All you have to do is [thread=30311]issue "return code -2"[/thread] from the failed component wrapper
and propagate it up if needed ( B to A or Batch to A )

However, within this schema it's impossible to roll-back B if it has been already committed and A (the outer one) Fails.
Ghoti's proposal to run yet another "Fix it!" Deployment(s) on A's failure is a reasonable workaround

Richu

Thanks for reply.
I alreadt tried the same soln, having another DNR on failure.
Problem: Lets say my previous DNR for database deployment deployed 5 files. and I want to rollback the database deployment. I have another DNR on failure which will take data from previous edition and deploy. Now my previous edition has only 4 files. On failure, it will deploy the 4 files but the 5th extra file is not getting deleted from database.
How to achieve that?

Thanks,
Richa

Adam Stoller

Thanks for reply.
I alreadt tried the same soln, having another DNR on failure.
Problem: Lets say my previous DNR for database deployment deployed 5 files. and I want to rollback the database deployment. I have another DNR on failure which will take data from previous edition and deploy. Now my previous edition has only 4 files. On failure, it will deploy the 4 files but the 5th extra file is not getting deleted from database.
How to achieve that?

Thanks,
Richa

If the deployments are filelist based - then listing the files that were associated with the initial deployment should work (assuming you have doDeletes enabled) since if the file does not exist in the source area (previous edition) then it should trigger a delete event for the deployment process.

Note however, that my suggestion about having a failure DNR to run after rollback (which therefore probably needs to be classified as "success" for "rollback" rather than "failure" for the initial deployment) should be able to process all the rolled-back files as part of the DNR process.