Specifying the dispatchers to host the JMX proxy server
Administrators can create a list of one or more dispatchers as candidates to host the Java Management Extensions (JMX) proxy server. This helps reduce the number of threads required to collect JMX metrics and increases the number of threads that are available for content manager.
The JMX Proxy server communicates with dispatchers and collects their JMX metrics. This communication requires approximately four threads per dispatcher. A distributed install with a large number of dispatchers requires a large volume of threads, which impacts the performance of content manager. To resolve this issue and enhance the performance of content manager, administrators can choose one or more dispatchers as candidates to host the Java Management Extensions (JMX) proxy server.
Choosing dispatchers
Since IBM Cognos Administration uses the presentation service and has a connection to the proxy server, choose dispatchers that are running the presentation service. This provides local calls to the proxy server.
Use IBM Cognos Administration to create a list of one or more dispatchers to host the Java Management Extensions (JMX) proxy server. The dispatcher that is at the top of the list and is currently running is the dispatcher that is chosen to host the JMX proxy service.
If none of the dispatchers in the preferred list are running then any random available dispatcher is chosen to host the JMX proxy server. Note that this is the default behaviour if you do not create a list of dispatchers.