The Documentation states:
The services file must contain two entries for each repository running on a host. On UNIX and Linux,manually create the service name entries in the services file before you install the Content Server.The repository does not have default service names or default port numbers. The service name youput in the services file must be the same name you provide during repository configuration, whichis then used to create the server.ini file. The service name for the repository can be the same asthe repository name, but this is not required.
However, does this mean that it makes no difference what is used so long as the same value is used when creating the content repository? The documentation is unclear.
The reason I ask is that I'm configuring some Documentum servers that are VMs and will be cloned. I'd like to pre-configure the services using a generic name for the services and then use that same value for every content server install. There will only ever be one content repository installed on each VM. Documentum Content Server will be installed prior to the cloning but the repositories will not be created until after the cloning operation.
I'd like to use something like:
# Documentum Services Configurationdctm 1491/tcp # Documentum native connectiondctm_s 1492/tcp # Documentum secure connection
But I need to know that the identical service values will not cause any issues with repositories that are using the same docbroker and part of the same federation. In the past I've always used the repository name for the service value but that doesn't seem to be as flexible as I'd like since I don't yet even know what the name of the repository will be.
Thanks,
-Mark
