Additional domsrvr has been correctly added on secondary server and NX_WEBSERVICES_DOMSRVR correctly defined in NX.env file as well as in NX.env.tpl file ; but SOAP Webservices still using the default domsrvr.
Observed that when starting the CA Service Desk Manager services, the value for NX_WEBSERVICES_DOMSRVR in the NX.env file on the Secondary server gets overwritten with the value for the default domsrvr.
When starting the CA Service Desk Manager services, the value for NX_WEBSERVICES_DOMSRVR in the NX.env file on the Secondary server gets overwritten by version control and the variable on the Secondary server is assigned with the value specified on the Primary server.
Version control processing takes the values from NX_ROOT\site\client_nx.env on the Primary server and updates the NX.env file on the secondary server.
To avoid having the variable overwritten in Secondaries, delete the line referencing WEBSERVICES_DOMSRVR in the client_nx.env file that exists on the Primary server.
Install , client , WEBSERVICES_DOMSRVR , domsrvr
Refer to the following document to configure a dedicated domsrvr process for web services integrations for SDM in Advanced Availability:
TEC1364225 - How to configure a dedicated DOMSRVR for SOAP Web Service in Advanced Availability CA Service Desk Manager (CA SDM)configuration
Was this information helpful?