Maximum Number of Processes and Connections

Maximum Number of Connections

There is a maximum of one of each of these services per dispatcher: agent, Content Manager, data movement, delivery, job, report data. Connections handle one request from one service at a time.

You can specify the maximum number of connections for each service during peak periods and non-peak periods using the following settings:

• Maximum connections for <service_name> service during non-peak period
• Maximum connections for <service_name> service during peak period

The default number of connections is four.

Maximum Number of Processes

There can be multiple report service, batch report service, and data movement processes on each dispatcher. You can specify the maximum number of processes during peak periods using the following settings:

• Maximum number of processes for the <service_name> during peak period
• Maximum number of processes for the <service_name> during non-peak period

The default number of processes for each service is two.

Affinity Connections

In addition, report servers accept low and high affinity connections to process requests from the batch report and report services. Servers also accept low and high affinity connections to process requests from the data movement service.

Low affinity requests can be handled by any report server. Typically, low affinity requests are used when a report or data movement run is initially requested.

High affinity requests are ideally handled by a specific report server. Typically, high affinity requests are for reports that were already requested and may include actions, such as going to the next page in a report. If the specific report server is not available or busy, then the report is rerun (low affinity request) on any report server and the next page (high affinity request) is directed to that server.

Affinity settings take precedence over balance request settings and advanced routing settings. For more information, see Balancing requests among dispatchers and Advanced Dispatcher Routing.

If affinity settings are changed for a service while entries are running, the number of server processes could double. The number of processes may temporarily exceed the maximum setting while the change takes effect. This may cause problems if your system does not have enough memory for the interim period.

For more information about affinity connections, see the IBM® Cognos® Business Intelligence Architecture and Deployment Guide.

You can specify the number of low and high affinity connections for the report service, the batch report service, and the data movement service using the following settings:

• Number of high affinity connections for the <service_name> during peak period
• Number of high affinity connections for the <service_name> during non-peak period

For batch report service, the default number of low affinity connections is two. For the data movement service and report service, the default number of low affinity connections is four. The default number of high affinity connections for all services is one.