Missing variables in NX.env after running pdm_configure
search cancel

Missing variables in NX.env after running pdm_configure

book

Article ID: 45297

calendar_today

Updated On:

Products

CA IT Asset Manager CA IT Asset Manager Asset Portfolio Management CA Service Management - Asset Portfolio Management ASSET PORTFOLIO MGMT- SERVER CA Service Desk Manager CA Service Management - Service Desk Manager CA Service Catalog Process Automation Manager CA Process Automation Base

Issue/Introduction

After running pdm_configure, most NX variables are missing from the end of the NX_ROOT\NX.env file that were there prior to running pdm_configure
 
The NX.env template file NX_ROOT\pdmconf\NX.env_nt.tpl was unchanged.
 
At the end of the NX.env file it ends with something like the following or maybe a few lines more:
@NX_CMDB=NOTSTANDALONE

@NX_SA_SERVER_ON_PRIMARY=YES

@NX_SERVER_TYPE=1

@NX_BACKGROUND_SERVERS=BACKGROUND1,BACKGROUND2

@NX_RF=1

! @NX_RF_OVERRIDE_LINKED= Deinstalled

Environment

Service Desk Manager 17.2 and higher
 
Advanced Availability

Cause

pdm_configure uses version control to help create the NX.env. One of the files that is important for this to work correctly is the NX_ROOT\site\client_nx.env file located in the site folder of the Service Desk install directory. pdm_configure will pull from the client_nx.env of the active background server and because of this, if the client_nx.env file is incorrect on the active background server, the NX.env file is not created correctly.

Resolution

To create the nx.env file with all of the expected options:
  1. Navigate to the NX_ROOT\site folder on each Background and Standby server.
  2. Backup each client_nx.env file and open them to compare them.
  3. Take the largest client_nx.env file and copy it and overwrite the other client_nx.env files.
  4. Run pdm_configure on all affected servers and verify the NX.env is now complete.