Transactional=Yes

Hi

I have TS6.5,OD6.0.0,Windows 2003.

Please see the attached file. I want to know if the deplyoment from source to target of Definition QA fails then will the same fail for definition Prod ,as transactional=yes?

Find more posts tagged with

Comments

Adam Stoller

Hi

I have TS6.5,OD6.0.0,Windows 2003.

Please see the attached file. I want to know if the deplyoment from source to target of Definition QA fails then will the same fail for definition Prod ,as transactional=yes?

Since the entire deployment is transactional - then if either QA or PROD encounters a failure condition - they both will be considered as failing and will both be rolled back.

wild123

Since the entire deployment is transactional - then if either QA or PROD encounters a failure condition - they both will be considered as failing and will both be rolled back.

My requirement is :

Run the attched deployment script from an ipl with the following dummy code :

if($condition)
{
deploy to QA
}else
{
deploy to Prod
}

How can I achive this from the attached deployment script?

Adam Stoller

My requirement is :

Run the attched deployment script from an ipl with the following dummy code :

if($condition)
{
deploy to QA
}else
{
deploy to Prod
}

How can I achive this from the attached deployment script?

change:[html]

[/html]to:

<deployment transactional="yes">
  <execDeploymentTask useDefinition="$def^"/>
</deployment>

and pass in a value for def on the command line - e.g.:

... -k def="QA" ...

... -k def="Prod" ...

wild123

Thanks a lot Ghoti

Smiley Happy

Condition is altered a little ,in the below fashion ::

if(deploy to QA)
{
def_WAS = "QAWAS";
def_IIS = "QAIIS";
}elseif(deploy to Prod)
{
def_WAS = "ProdWAS";
def_IIS = "ProdIIS";
}elseif(deploy to QAWAS,QAIIS, ProdWAS and ProdIIS) # can I do this in a different way than below ? Please check the file attached here.
{
open the deployment configuration xml,
search for

< execDeploymentTask useDefinition="$def_WAS^" / >
< execDeploymentTask useDefinition="$def_IIS^" / >

replace with

< execDeploymentTask useDefinition="QAWAS" / >
< execDeploymentTask useDefinition="QAIIS" / >
< execDeploymentTask useDefinition="ProdWAS" / >
< execDeploymentTask useDefinition="ProdIIS" / >

}

Adam Stoller

Condition is altered a little ,in the below fashion

Your original question was how to run one of two possible deployments with a single deployment configuration file. Your current post appears to have followed the advice given - and then ignored it and went back to your original problem.

Why are you doing a literal replacement instead of parameter substitution?

wild123

Your original question was how to run one of two possible deployments with a single deployment configuration file. Your current post appears to have followed the advice given - and then ignored it and went back to your original problem.

Why are you doing a literal replacement instead of parameter substitution?

Hey already implemented that. And I completely went by you Smiley Happy

.For the last condition ,instead of literal replacement, I ran the script two times ,ie., once for each set of WAS and IIS servers.

Thanks!!

Adam Stoller

Hey already implemented that. And I completely went by you .For the last condition ,instead of literal replacement, I ran the script two times ,ie., once for each set of WAS and IIS servers.

Thanks!!

Oh - okay - that's not what your previous post sounded like you did.
So - this is a closed issue then?
If so - please close the thread.

ISCBorisB

Hey already implemented that. And I completely went by you .For the last condition ,instead of literal replacement, I ran the script two times ,ie., once for each set of WAS and IIS servers.

Thanks!!

That implementation is wrong. OD configuration you've attached before indicates transactional Deployment.

In your "run it twice!" schema you Deploy certain related components to Web Servers (IIS) AND Application
Servers (WAS) individually. If the first OD fails you may(should?) catch it and not run the second. If however the
first run succeeds and the second one fails you'll have the first deployment already commited which violates overall
Deployment Integrity.

In the true spirit of Ghoti proposal it would be much cleaner to have four definitions
(you seem to have them already): QAIIS, QAWAS, PRODIIS, PRODWAS.

Then you'll execute a pair in a single transactional bracket. Like that:
<deployment transactional="yes">
<execDeploymentTask useDefinition="$def^WAS"/>
<execDeploymentTask useDefinition="$def^IIS"/>
</deployment>

-k def in this schema may take either QA or PROD value