Creating a dedicated Domsrvr to the Animator Process for CA Service Desk Manager (SDM) r12.9 r14.1 and r17.x in Advanced Availability (AA) Mode

Document ID : KB000035701
Last Modified Date : 24/07/2018
Show Technical Document Details
When it is observed a great number of simultaneous events being triggered by SDM, it is usual to notice an overall performance degradation.
To resolve this problem, it is necessary to add a dedicated domsrvr to the Animator process - which is responsible for triggering the SDM events.




Service Desk Manager 12.9 / 14.x / 17.x running on Advanced Availability (AA) mode.
As the Animator process runs on the Background server only, it is indicated that there is a process defined for both the Background and Standby servers.

The steps below show how to do it:

1. Login to the SDM Primary server.

2.  Click the Administration tab and expand System -> Configurations:


Configuration page


3. Create a new Configuration for the Background Server:


New Configuration for the Background Server

4. Create a new domsrvr process for the Background server:

Add a new Domsrvr

5. Now, create a new Configuration for the Stand By server.

New configuration for the Stand By server

6. And create a new domsrvr process for the Stand by server.

New domsrvr in the Stand By server


7. Now, we need to run fail-over on the environment, as it will be necessary to reconfigure the servers.

For this, login on the Stand by server and run:

  • Start the SDM process - or recycle it if started: 

    net start pdm_daemon_manager 

  • Run the fail-over step:

    pdm_server_control -b


8. Now, login to the Background server and run pdm_configure.

In the last form, choose the Animator_back configuration and uncheck "Start services when completed":

Choose the correct configuration

9. Next, point the Animator to the newly added dedicated domsrvr:

Locate the following two files under C:\Program Files (x86)\CA\Service Desk\pdmconf


In both of these files, search for #define ANIMATOR_NXD(_TAG) and edit the command to:

User-added image


Here domsrvr:02 is the name of the domsrvr created in step 4.


10. Now, validate the changes done:


  • Start the SDM services on the Background server: 

    net start pdm_daemon_manager

  • Make it the Background server again:

    pdm_server_control -b

  • And verify the domsrvr process created:

    slstat | findstr "dom"

New domsrvr:02 running


11. Next, it is necessary to complete the configuration on the Stand by server.

Logon to the Background server and run pdm_configure (as done in step 8) and choose the appropriate Configuration:


Run configure on Standby


12. Repeat step 9 for the Stand by server as well.

13. To validate all settings are correct for the Stand by server as well, repeat the instructions from step 10.

After you have verified all is correctly configured, you should run fail over again on the original Background server.

Additional Information:
The proceeding for r12.9 and 14.1 in Conventional Mode is available in the following tecdoc: