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 in DD

tuac

Hi All,

Thanks in advance. I wanted to know the exact place where I could place the dnr script in my DD config file. Any help would be greatly appreciated.

[html]

options = "wide,full"
area = "$area">

[/html]

Thanks!

OD 6.2 Windows EE

Find more posts tagged with

Comments

Adam Stoller

Hi All,

Thanks in advance. I wanted to know the exact place where I could place the dnr script in my DD config file. Any help would be greatly appreciated.
[...]
Thanks!

OD 6.2 Windows EE

I don't believe that DD has DNR scripts - OD does though.
What are you trying to accomplish?

Serialbygroup.pdf

test.pdf

tuac

I don't believe that DD has DNR scripts - OD does though.
What are you trying to accomplish?

Ok. Here is my requirement. I want to trigger DD 2 on the success of DD1. But in the case of any single script failure, i want to roll back the content and nothing should be deployed. Is there any other way you could suggest me?

Thanks very much for the reply.

Query1.txt

nipper

One of the reasons for DNR is that on the receiver you want to run some code. However for DD, the receiver is a DB and access is through ODBC/JDBC and not on the DB server itself. So DNR is not appropriate for this.

You need to write a deployment script that will run DD1, check the return value and on success run DD2, or on failure rollback the previous OD.

Note, I recall there are some examples of synchronized, transactional OD/DD combinations in the OD/DD admin manuals so you should start there first and script anything else you need.

tuac

One of the reasons for DNR is that on the receiver you want to run some code. However for DD, the receiver is a DB and access is through ODBC/JDBC and not on the DB server itself. So DNR is not appropriate for this.

You need to write a deployment script that will run DD1, check the return value and on success run DD2, or on failure rollback the previous OD.

Note, I recall there are some examples of synchronized, transactional OD/DD combinations in the OD/DD admin manuals so you should start there first and script anything else you need.

Thanks for the reply Nipper.

I had gone through the mannual. Yes for the OD/DD combinations, synchronized deploymnets can be followed.

You had specified that we need to run the DD1 script and on success, can inturn trigger the DD2 script. How could I achieve this?

A possible solution can be using a perl script that triggers DD1, gets result and based on the return value, the perl script would trigger the DD2 script.

But the problem with this approach is that when DD2 fails, how could we rollback the contents deployed by DD1 script.

Is there any other simple way or a snippet you could share?

All what I need is execute DD1 , which inturn invoke DD2. In case of any failure in any one of the scripts, all the deployments should be rooled back.

Thanks!

Migrateduser

what about using dbLoader in OD?

something like:

[html]

databaseXmlFile="/opt/OpenDeployNG/conf/databases.xml">

<script cmd="/opt/custom/somescript.sh $area^ $envname^" as="tscontent" where="/opt/iw-home/" async="no" />

[/html]

tuac

databaseXmlFile="/opt/OpenDeployNG/conf/databases.xml"> <script cmd="/opt/custom/somescript.sh $area^ $envname^" as="tscontent" where="/opt/iw-home/" async="no" /> [/html]
what about using dbLoader in OD?

something like:

[html]

Thanks for the reply.

My situation is only related to DD1 triggering DD2. No involvement of OD.

Thanks

Migrateduser

Thanks for the reply.

My situation is only related to DD1 triggering DD2. No involvement of OD.

Thanks

what about using 2 dbLoader's, and making the depolyment transactional? I know your only using DD, but I would think the OD with multiple dbLoaders should do what you need. you can also add a DNR to DB_DEPLOY1 that does some error checking (sql query, whatever) too (if needed) and can report back response code='-2'

[html]

[/html]

Migrateduser

or another thought is use OD dbLoader for the first deployment and give it a DNR to call your 2nd DD on success

[html]

<script cmd="iwodcmd start OpenDeploy_configuration -k iwdd=internal-deployment-name" as="root"/>

[/html]

Adam Stoller

Ok. Here is my requirement. I want to trigger DD 2 on the success of DD1. But in the case of any single script failure, i want to roll back the content and nothing should be deployed. Is there any other way you could suggest me?

Thanks very much for the reply.

Are the two DD deployment definitions within the same DD config file?
If so - you should be able to create a third definition whose sole purpose is to exec each of the other definitions - I believe that will provide the kind of transactional association you're looking for.

tuac

Are the two DD deployment definitions within the same DD config file?
If so - you should be able to create a third definition whose sole purpose is to exec each of the other definitions - I believe that will provide the kind of transactional association you're looking for.

Guys,

Thanks for the replies. But I am still confused. Where can I specify the execdeploymenttask tag in my dd config file?

Thanks!

Migrateduser

Guys,

Thanks for the replies. But I am still confused. Where can I specify the execdeploymenttask tag in my dd config file?

Thanks!

[html]

[/html]

then you call the wrapper-deploy in your odcmd instead of the individual ones.

tuac

[html]

[/html]

then you call the wrapper-deploy in your odcmd instead of the individual ones.

Thanks a lot for you continued assistance.

Did you mean in this way?
[html]

[/html]

Migrateduser

Thanks a lot for you continued assistance.

Did you mean in this way?
[html]

[/html]

yes, so when before you called dd1, you instead call wrapper-deploy, which will itself call dd1 & then dd2..

I am unsure (have not actually tested) if dd1 fails that it stops and does not call dd2, but that should be easy enough for you to test out.. I personally still think I would lean towards using OD with dbLoader and a DNR to call the 2nd deployment on success, but that might not be an option for you and there are always a few ways to acomplish the same thing..

tuac

Thanks a lot for the help. Yes it worked fine. Even if any one script fails, the deployment is rolled back.

-Thanks again!