We are in the process of planning our upgrade to Harvest/SCM 13. 0 As part of that process we want to eliminate the need to use have the SCM broker name and ip address included in each user's C:\WINDOWS\system32\drivers\etc\hosts file. - which is our current practice.
Is there something we can do as part of the application configuration / setup that will allow us to discontinue doing this?
CA Harvest SCM all versions and platforms
To answer this question, let’s start at the beginning. By default, SCM will use for its “brokername” the hostname of the computer it’s running on. You can override this and choose a different name as your “brokername” by setting the “RT_FORCE_NODE_NAME” environment variable to be the new “brokername” and by configuring your network so that when a computer uses the new “brokername” it finds the ip address associated with the machine the broker is running on. The network configuration could either take the form of entering an “alias” in your network’s DNS directory associating the new “brokername” with the correct IP address, or putting the new “brokername” and ip address in the “hosts” file of the broker computer and all client computers.
If you’re using the configuration of the “brokername” and ip address in the hosts file, this most likely means you have chosen to not use the hostname of the broker computer as the “brokername”. There are 2 choices for a solution, depending on what you would like to do:
- One solution is to remove the “RT_FORCE_NODE_NAME” environment variable, restart the broker and rtserver, and have your users change and start using the hostname of the broker computer as the “brokername”.
- The other solution, if you’d rather continue with the “brokername” you’re using now is to instruct your network administrators to add an “alias” to your company’s DNS directory to associate your “brokername” with the correct ip address..
More information on the RT_FORCE_NODE_NAME environment variable can be found in the Implementation Guide.
As always, please contact CA Technologies support for CA Datacom if you have further questions.