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

need advise in OD configuration file

Evani20

Hi all, I have kinda similar requirement here, but I wonder is there anyway I can write two or more #deployment> in configuration file #deploymentConfiguration> ? What I mean can I declare one deployment as a transactional and another one as a non-transactional.

Thanks in advance,

Find more posts tagged with

Comments

moonkhanna

yes you can.. what is your issue here? That is how it is supposed to work..

Evani20

Thanks for your reply, let me explain the situation; i have to deploy to to 3 different servers, 2 of them as a transactional and the other one as a non-transactional. So, is there any way, I can modify the deployment configuration file with two #deployment> element.

Thanks in advance,

ISCBorisB

Thanks for your reply, let me explain the situation; i have to deploy to to 3 different servers, 2 of them as a transactional and the other one as a non-transactional. So, is there any way, I can modify the deployment configuration file with two #deployment> element.

Thanks in advance,

According to "oddeployment.dtd" the answer is "No". 'deploymentConfiguration' may contain multiple 'definition' Tags and
only one Deployment Tag, either 'deployment' or 'routedDeployment'.

Note that either Deployment flavor may contain numerous 'execDeploymentTask' Legs. All of them will be running in the same
transactional mode though as defined by Deployment (parent) Tag

moonkhanna

According to "oddeployment.dtd" the answer is "No". 'deploymentConfiguration' may contain multiple 'definition' Tags and
only one Deployment Tag, either 'deployment' or 'routedDeployment'.

Note that either Deployment flavor may contain numerous 'execDeploymentTask' Legs. All of them will be running in the same
transactional mode though as defined by Deployment (parent) Tag

My apologies on the wrong advise... was not very clear about the question.. Thanks for clarifying Bo!

Gogz

Yes, you cannot have more than one deployment element in config file. But for requirement 2 to be transactional & 1 to be non-transactional can be implemented by using the DnRDeploymentJob element. Check in the docs for complete details about DnRDeploymentJob.

Agarwal

You can configure in this way :-

.......

.......

<script cmd="/usr/iw-home/OpenDeployNG/bin/iwodstart Third.xml" />

curiousmaverick

which way????????????

Agarwal

Thanks for your reply, let me explain the situation; i have to deploy to to 3 different servers, 2 of them as a transactional and the other one as a non-transactional. So, is there any way, I can modify the deployment configuration file with two #deployment> element.

Thanks in advance,

You can configure the xml as :-

[deploymentConfiguration nodeSetFile="/usr/iw-home/OpenDeployNG/etc/odnodes.xml"]
[localNode host="abc" timeout="3600"/]
[replicationFarmSet]
[replicationFarm name="MYFARMNAME"]
[nodeRef useNode="First" /]
[nodeRef useNode="Second" /]
[/replicationFarm]

[/replicationFarmSet]
[definition name="deploy"]
[source]
.......
[/source]
[target useReplicationFarm="MYFARMNAME" ]
.......
[/target]
[/definition]
[deployment transactional="yes"]
[execDeploymentTask useDefinition="deploy"]
[/execDeploymentTask]
[dnrDeploymentJob location="source" when="after" state="always"]
[script cmd="/usr/iw-home/OpenDeployNG/bin/iwodstart Third.xml as="" async=""" /]
[/dnrDeploymentJob]
[/deployment]
[logRules maxBytes="5mb" level="normal"/]
[/deploymentConfiguration]

LooseKannon

Hi there,
I have tried to do it the same way:

< dnrDeploymentJob location="source" when="after" >
< script cmd="D:\Interwoven\OpenDeployNG\bin\iwodstart ADI\FileList2 -inst REPLACEME -k host=NWD2IWQA5 -k fileList=D:\Interwoven\TeamSite\ADI\temp\filelist.txt -k farmSet=DrServer -k sourceArea=Y:/default/main/ADI/WORKAREA/common -k targetArea=E:\InetPub\wwwroot"
where="D:\Interwoven\OpenDeployNG\bin" async="no"/>
< /dnrDeploymentJob >

The script does not get called when i run the deployment in command prompt. But when i run the cmd by itself in command prompt it works fine.

Please let me know what im doing wrong. Who does it run as when i run a cmd from command line?

ISCBorisB

Yes, you cannot have more than one deployment element in config file. But for requirement 2 to be transactional & 1 to be non-transactional can be implemented by using the DnRDeploymentJob element. Check in the docs for complete details about DnRDeploymentJob.

It *may* be easier to achieve with multi-tiered deployments or perhaps routed Deployments. The better approach IMO is not to bundle
transactional and non-transactional Deployments at all, not on OD Configuration level anyway. Configure them separately and if needed
encapsulate multiple OD calls within single Script

Natasha

Hi there,

The script does not get called when i run the deployment in command prompt. But when i run the cmd by itself in command prompt it works fine.

Please let me know what im doing wrong. Who does it run as when i run a cmd from command line?

Hi,

How are you trying to run the main deployment in which you have your DNR script? Are you running it as root?
And when you run the cmd written in the script tag, it runs fine, are you logged in as root or the owner?

Thanks,
Natasha.

ISCBorisB

Hi,

How are you trying to run the main deployment in which you have your DNR script? Are you running it as root?
And when you run the cmd written in the script tag, it runs fine, are you logged in as root or the owner?

Thanks,
Natasha.

From Kannon's code fragment it is clear that the platform is Windows, so no 'root' and the like...

Adam Stoller

Hi there,
I have tried to do it the same way:

< dnrDeploymentJob location="source" when="after" >
< script cmd="D:\Interwoven\OpenDeployNG\bin\iwodstart ADI\FileList2 -inst REPLACEME -k host=NWD2IWQA5 -k fileList=D:\Interwoven\TeamSite\ADI\temp\filelist.txt -k farmSet=DrServer -k sourceArea=Y:/default/main/ADI/WORKAREA/common -k targetArea=E:\InetPub\wwwroot"
where="D:\Interwoven\OpenDeployNG\bin" async="no"/>
< /dnrDeploymentJob >

The script does not get called when i run the deployment in command prompt. But when i run the cmd by itself in command prompt it works fine.

Please let me know what im doing wrong. Who does it run as when i run a cmd from command line?

Try changing "iwodstart" to "iwodcmd start" in your command string - it is quite possible that the old iwodstart script is looking for some environment variables that do not exist when it is executed as a DNR script.

yogesh_agrawal

you are missing ".bat" in the dnr script cmd. put the ".bat" for iwodstart in script cmd. it will work.

Agarwal

Hi,

Have a look at this - http://devnet.interwoven.com/forums_vb/showthread.php?t=25383&forumid=12

Thanks and regards
Akshat