replicationFarmSet

shahzamaj

whats the purpose of using "replicationFarmSet" over directly mentioning node names in the "target" tag ?

If I mention node names in "replicationFarmSet", then the replicationFarmSet is used in "target", instead of that I can directly mention node names in target and avoid extra entry replicationFarmSet in the file.Which makes file simpler.

Only advantage of using replicationFarmSet I can see is, if I have to use thie replicationFarmSet more than one time. In this case I can avoid using node names multiple times. But this is rare. I have not used replicationFarm more than once.

Pls explain.

Adam Stoller

whats the purpose of using "replicationFarmSet" over directly mentioning node names in the "target" tag ? If I mention node names in "replicationFarmSet", then the replicationFarmSet is used in "target", instead of that I can directly mention node names in target and avoid extra entry replicationFarmSet in the file.Which makes file simpler. Only advantage of using replicationFarmSet I can see is, if I have to use thie replicationFarmSet more than one time. In this case I can avoid using node names multiple times. But this is rare. I have not used replicationFarm more than once. Pls explain.

This is more a question of design of the software. The software was designed to utilize replicationFarmSets to identify the target receivers for a deployment - not to directly use receiver nodes.

If you only use the target node, or set of nodes, for one deployment - such is life - but if you create additional deployments to those same nodes, then the concept of the replicationFarmSet makes sense.

In your case - you might define the replicationFarmSet in the deployment configuration file itself.

Most of my customers have at least a DEV and PROD instance of TeamSite as well as at least a DEV and PROD web environment to target for deployments respectively. In such cases, defining the replicationFarmSet within the odnodes.xml (rather than in the deployment configuration file) allows me to use the exact same deployment configuration file in both DEV and PROD - and have distinct odnodes.xml files for those environments such that the replicationFarmSet is defined differently for them. This helps improve the correctness of testing something in DEV and then promoting it to PROD. If something goes wrong in PROD it is most likely due to the environment-specific server configuration files than to the environment-generic deployment configuration files.