Configure a Dedicated Domsrvr for SOAP Web Service - Advanced Availability

In CA SDM Advanced Availability, there is no option for webservice_domsrvr.  This option webservice_domsrvr is only present in the CA SDM Conventional Installation.
casm171
In CA SDM Advanced Availability, there is no option for 
webservice_domsrvr
.  This option 
webservice_domsrvr
 is only present in the CA SDM Conventional Installation.
As a result, all SOAP web service calls use the domsrvr on the CA SDM Background Server. This can impact performance in both the web service application and the CA SDM application itself. This article explains how a dedicated DOMSRVR can be configured to handle the SOAP web service calls.
  1. Create an additional DOMSRVR (for example: 
    domsrvr:03
    ). 
    This DOMSRVR could be on any CA SDM server, depending where the SOAP web service calls. For more information on how to add a domsrvr, see How to Configure Processes for CA SDM Servers.
  2. On the CA SDM server that the newly created DOMSRVR (
    domsrvr:03
    ) resides, edit the 
    NX.env
     file with the 
    PDM_OPTIONS_MGR
     command line utility to add or change content within the NX.ENV configuration file. As a best practice use it to avoid this file from becoming corrupted by a text editor.
    pdm_options_mgr -c -s webservice_domsrvr -v domsrvr:03 -a pdm_option.inst -t pdm_options_mgr -c -s webservice_domsrvr -v domsrvr:03 -a pdm_option.inst
  3. Restart the CA SDM service. 
    If this is not your Background server, only the CA SDM service on this particular server needs to be restarted. 
    If it is the CA SDM Background server, promote the CA SDM Standby server to be the new CA SDM Background server, recycle the CA SDM service and promote it back to the CA SDM Background server.