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

Deployments to multiple location on same target server

Aaki

Hi All,

I have a situation where I have to deploy contents from one source to multiple targets and mutiple locations on each target.

Suppose I have servers A,B,C

A has the target locations -> A1,A2 and A3
B's targets - > B4, B5 and B6
same for server C.

My question is: - Do I need to create Multiple ReplicateFarmsets and Defination for ecah target location in Deployment Descriptor file.??

Let Say for Server A the target locations are A1,A2,A3 so here Do I need to create three ReplicateFeamSets and Three Definations that will leads to different targets locations on same target server??

Please give me suggestion.

Thanks & Regards,
Aaki
TS6.7.1SP1
OD 6.1.1

Find more posts tagged with

Comments

ISCBorisB

Hi All,

I have a situation where I have to deploy contents from one source to multiple targets and mutiple locations on each target.

Suppose I have servers A,B,C

A has the target locations -> A1,A2 and A3
B's targets - > B4, B5 and B6
same for server C.

My question is: - Do I need to create Multiple ReplicateFarmsets and Defination for ecah target location in Deployment Descriptor file.??

Let Say for Server A the target locations are A1,A2,A3 so here Do I need to create three ReplicateFeamSets and Three Definations that will leads to different targets locations on same target server??

Please give me suggestion.

Thanks & Regards,
Aaki
TS6.7.1SP1
OD 6.1.1

There are quite a few Configurations that *may* cover your requirements - or at least a portion you've described.
Which one to chose depends on what you really need. Two extremes are "replicationFarm" (not "replicationFarmSet"!)
per Node and single "replicationFarm" for all Nodes.

For what it's worth, my personal rule of thumb in a situation like that is a "replicationFarm" per OD Receiver.
The reason is that I find it a reasonable compromise between Configuration flexibility, code size, ease of maintenance
and ease of changes. Once again, beware! There are various Deployment scenarios that may affect this approach.
So, other things being equal[php]

...

...

...

...

[/php]Comprende?

Aaki

Hi Boris,

I hv tried the way you suggested . but It is not working for me. I hv configured different file locations paths under server A like
<replicationFarmSet>
<replicationFarm name="test" quorum="">
<nodeRef useNode="A">
Target1
Tarhet2
</nodeRef>
</replicationFarm>
</replicationFarmSet>

but it only deploying the to the location given in the corresponding defination.

One thing more i wud like to tell u again that all my tagtets location on same server or another server are different thats why I cant use the multiple nodes in one ReplicateFarm.

more suggestions??

Thanks
Aaki

ISCBorisB

Attach (do not paste into post, attach!) your complete Deployment configuration. Explain what worked and what did not, I'll take a look

cesarecastro

This is incorrect

<replicationFarmSet>
<replicationFarm name="test" quorum="">
<nodeRef useNode="A">
Target1
Tarhet2
</nodeRef>
</replicationFarm>
</replicationFarmSet>

This is correct

<replicationFarmSet>
<replicationFarm name="test" quorum="">
<nodeRef useNode="A">
Target1
</nodeRef>
<nodeRef useNode="A">
Target2
</nodeRef>
</replicationFarm>
</replicationFarmSet>

Read the documentation. It has an example you can follow. Boris' post is also correct.

So here is an entry in the our odnodes file.

<node name="QA1" host="myserver" port="20014"/>

<replicationFarm name="QA_mysite">
<nodeRef useNode="QA1">
<targetRules area="D:/Inetpub/mysite-1/Content/" />
</nodeRef>
<nodeRef useNode="QA1">
<targetRules area="D:/Inetpub/mysite-2/Content/" />
</nodeRef>
<nodeRef useNode="QA1">
<targetRules area="D:/Inetpub/mysite-3/Content/" />
</nodeRef>
</replicationFarm>

Aaki

Yes that is working fine.Thanks you all.