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 for the Animator process, which is responsible for triggering the SDM events.
Service Desk Manager 17.3
Conventional Architecture (Primary server only or Primary and Secondary servers)
All Supported Operating Systems
1. Login to the SDM Primary server.
2. Click the Administration tab and expand System -> Configurations
3. If running SDM with Primary server only, create a new configuration in SDM:
4. If running SDM with Primary and Secondary servers, edit the existing configuration.
In the example below, web_dom is the existing configuration on a Primary/Secondary installation:
5. Create a new DOMSRVR process. In the example, it is named "domsrvr_for_animator".
Important: take note of the Communication Server Name. In the above example, it is named: domsrvr:02
5. Run pdm_configure. Leave "Load default data" unchecked:
For Config options, select the appropriate configuration and leave "Start SDM services" unchecked:
6. To configure Animator to the newly added dedicated DOMSRVR:
Locate the following two files under NX_ROOT\pdmconf
Open both files with a text editor and search for #define ANIMATOR_NXD(_TAG) and edit the command to:
command = "$NX_ROOT/bin/animator_nxd -d 'domsrvr:02'"
Here domsrvr:02 is the name of the domsrvr created in step #4.
7. Start the SDM service
8. To validate that the DOMSRVR process created is running, run the following command in a command prompt:
slstat | findstr "dom"