Can we Suppress version control for specific NX Variables?

Document ID : KB000008613
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

In some environments, the need may arise to control a specific NX.env variable on an individual server, setting it to a different value on a given server, and not having it the same globally across all servers.    For example, if you have Support Automation configured on all of your APP servers, but one of those servers is installed in a localized language to meet the needs of some folks in a certain location, you would want anyone accessing that server to ONLY hit the Support Automation URL on that server specifically and not hit the global URL that is set in options manager. The issue here is that when you set it in the NX.env on that one specific server, and then recycle services, version control pushes the value again from the nx.env on the background or primary server, overwriting that value on that specific localized server.

Environment:
CA Service Desk Manager (ALL VERSIONS)
Cause:

The value in the nx.env on the localized APP server is being overwritten by version control pushing the global value (from options manager) from the Background or Primary server to all APP servers.

Resolution:

There is a workaround for this.  Follow these steps to configure a specific NX.env variable to be set for a specific server, and not changed by Version Control.

On the specific server that needs the specific nx.env variable:

1. create a text file - name it as nx.env and place it in the root of your C:\ drive 

2. edit the file and add only the following (For this example we will use the Support Automation URL, but this can be any NX.env variable that is specific to a server): 

@NX_SUPPORTAUTOMATION_URL= {put your URL here that you want to use} 

then save the file. **Make sure the file extension is .env and not .env.txt**

3. recycle CA Service Desk services on that specific server

4. once the services are back up - on that server, run the command nx_env > nx.txt - then open the nx.txt file and search for "supportautomation" - you should see the proper URL in the variable that is in-play now. 

NOTE:  the NX_ROOT\nx.env file will still have the global value from options manager set in it, however, the system will always read that nx.env file from the root of the C:\ drive first upon startup, and any value in it will override the value that is set in the NX_ROOT\nx.env file.

IMPORTANT NOTE:  We recommend using this ONLY in specific situations, and possibly reaching out to CA Support via Chat, Communities, or a Support Case to inquire first as to whether or not there could be any disadvantages or problems when doing this for certain variables.