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

next deployment

System

Can anybody pls tell me whether we can have parameters on next deployment in multi tier?

Thanks

Find more posts tagged with

Comments

Adam Stoller

I believe the answer is "no" - If you're using OD6 - you might want to take a look at the documentation for routed deployments - though depending on your needs it might seem like a bit of overkill. The alternative is to use a DNR script to launch the next deployment - and have the DNR script pass in the parameters.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Fish, I read the documents already they never mentioned about this. I liked your idea. Good one.

Thank U Very Much

Migrateduser

Fyi, feature request for parms in next deployment is #36630.

Please let me know your company name if you want it attached. Or let Tech Support know.

Thanks.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

sriram

Hi,

Even I have similar kind of situation where I want to pass the parameters to next deployment and also i want to make it transactional. Like if a next deployment whch is called through dnr script fails I want to rollback even the parent deployment. Is it possible. Any ideas? suggestions?

Thanks in advance.

Edited by sriram on 11/15/04 11:57 AM (server time).

Adam Stoller

If you use the DNR script idea I posted before - you should be able to do what you want -- as long as the DNR script that starts the "next" deployment is *not* run asynchronously - and you trap for errors in the "child" deployment - you should be able to accomplish a rollback the way you normally would with a DNR script.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Multi-tiered deployments can be configured as transactional, as of OD 5.6 I believe. If any deployment leg at any tier fails, then all legs at all tiers are rolled back.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

sriram

Thanks Fish for your immediate response. Please can you explain more on this.. i donno exactly how to do this.

"you trap for errors in the "child" deployment - you should be able to accomplish a rollback the way you normally would with a DNR script."

thanks

sriram

Thanks Todd. But I want to set the prameters for my next deployment which is not possible using Muti -tiered right? so i am looking for a workaround.

Edited by sriram on 11/15/04 12:46 PM (server time).

Adam Stoller

Well, before I go into a lengthy description - perhaps you can provide some information first.

For instance
- What version of OD are you running?
- Have you ever written a DNR script before?
- Do you understand how a DNR script signals failure to OD?

I don't know if there's any definitive documentation on writing a DNR script - there are bits and pieces about such within the documentation, but nothing concentrated on it (as far as I know) - however, if you look in ODHOME/solutions/perl/ you should see several scripts which you could perhaps use as a model for what you want to do.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

sriram

Ok Here is the information

1) Version is 5.6 on WIN2000.
2) Yes i have written few dnr scripts which are executing sell scripts not the deployments.
3) What I understand from document is that on Failure of the DNR script, script returns response code -2. May be i can use ths response code in shell scripts to roll back the parent deployment .. am i right? If so, how to rollback from script

If possible can you share with me sample deploymeny with dnr script.

Thanks a lot

Adam Stoller

The DNR script would take whatever arguments you supply on the command line within the 'parent' deployment config and would then invoke OD using those parameters - it would check the return status of that 'child' deployment and if the deployment failed, would print to STDOUT (not 'return') the XML snippet to indicate failure, otherwise it just exits and the 'parent' workflow finishes.

Start by writing a script that takes a deployment configuration file and parameters (key=value) pairs on the command line, and which then puts those into order to make a command line to invoke OpenDeploy.
Make sure your script checks the return value from iwodstart or iwodcmd start and does 'the right thing' if the exit status is non-zero.
Then take that script - put it on your target server (which is also a Base Server, otherwise you wouldn't be able to fire off a 'next deployment')
Take the command line you used and put that into your 'parent' deployment config as a DNR script line.

As long as the script does the response code -2 on failure of the 'child' OD process - it will cause the 'parent' OD process to perform a rollback as well.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

sriram

Thanks Fish!!! Its working now. So we need to print XML snippet <response code="-2"/> in case of failure to STDOUT in the script to make parent deployment rollback. Interesting!!!