Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 System Design (Configuration) Guide


B.1 Limits on the number of JP1/AJS3 product connections

The following table shows the number of JP1/AJS3 - Agents, JP1/AJS3 - Views and JP1/AJS3 - Web Consoles that can be connected to JP1/AJS3 - Manager.

Table B‒1: Limits of JP1/AJS3 - Agents, JP1/AJS3 - Views and JP1/AJS3 - Web Consoles that can be connected to JP1/AJS3 - Manager

Definition

Maximum

Number of JP1/AJS3 - Agents that can be connected to a single JP1/AJS3 - Manager (or single logical host in a cluster configuration)

1,024#1

Number of JP1/AJS3 - Views that can be connected to a single JP1/AJS3 - Manager (or single logical host in a cluster configuration)

50#2

Number of JP1/AJS3 - Web Console that can be connected to a single JP1/AJS3 - Manager (or single logical host in a cluster configuration)

32#3,#4

#1

For the agents specified as destination agents for any of the following jobs, you can increase the maximum number of agents that can be connected to 2,048 by specifying a setting for the AGENTLIMITEXTEND environment setting parameter.

  • PC, UNIX, or action job for which Standard is specified for Exec. Service

  • Event job

  • Custom Job

  • HTTP Connection Job

  • Flexible Job

#2

You can increase the maximum number of connections to 128 by specifying a setting for the MAXSESSION environment setting parameter. Connecting 64 or more JP1/AJS3 - Views will greatly increase the load on JP1/AJS3 - Manager and the network. Therefore, if you want to connect 64 or more JP1/AJS3 - Views, prohibit JP1/AJS3 - Views from automatically refreshing their screens or set the automatic refresh interval to 600 seconds or longer. Also, do not use JP1/AJS3 - Manager and the Monthly Schedule window simultaneously, since the window transfers a large amount of data.

#3

You can increase the maximum number of connections to 100 by specifying a setting for the CDMAXSESSION environment setting parameter.

#4

For details about the maximum number of units that can be monitored using JP1/AJS3 - Web Console, see 6.5 Features of and differences between jobnet monitoring programs in the manual JP1/Automatic Job Management System 3 Overview.

The following table shows the maximum number of JP1/AJS3 - Managers that can be connected to JP1/AJS3 - Agent.

Table B‒2: Limit of JP1/AJS3 - Managers that can be connected to JP1/AJS3 - Agent

Definition

Maximum

Number of JP1/AJS3 - Managers that can be connected to a single JP1/AJS3 - Agent

16#

#

The maximum value assumes an environment in which the agent and all managers can communicate smoothly with each other. If there is a manager for which name resolution by the agent takes time or a manager for which a timeout occurs during a connection, operation might be affected even when the number of managers is fewer than the maximum. For example, execution of a job from another manager might be delayed. Also, the number of jobs concurrently processed by the agent might affect operation. Make sure that you consider the load on the system during peak times and configure the system accordingly. Note that for a queueless-job execution environment, the number of JP1/AJS3 - Managers that can be connected is not limited.