4.6.2 Environment settings for JP1/AJS3 - Manager connected with a Web Console server
This subsection explains JP1/AJS3 - Manager environment settings that influence connections to and operations of the Web Console server. Consider changing the settings if necessary.
- Organization of this subsection
(1) Maximum number of concurrent sessions on the Web Console server
When JP1/AJS3 - Manager communicates with the Web Console server, the Web Console server creates a communication object used to connect with the scheduler service of JP1/AJS3 - Manager. For each object, the Web Console server and JP1/AJS3 - Manager connect with the scheduler service and establish a session. The maximum number of sessions that can be established at the same time can be set for each manager host. The default maximum number of concurrent sessions is 32.
Many sessions involve many processes, which can place a heavy load on JP1/AJS3 - Manager. To restrict such loads, determine the maximum number of concurrent sessions.
For details, see 20.4.2(21) CDMAXSESSION in the JP1/Automatic Job Management System 3 Configuration Guide.
(2) Timeout period for Web Console server connections
You can specify a certain period of time after the last communication at which the connection between JP1/AJS3 - Manager and the Web Console server times out. The default period is 3 minutes.
For example, if a user cannot log out from the server due to problems such as a communication failure, the session will be kept even if there is no communication. In such a case, the connection is automatically disconnected and the session is released if a timeout period has been specified.
Note that a long timeout period causes a non-active session to remain for a long time, and might cause the maximum number of concurrent sessions to exceed the limit. Determine the timeout period in view of the maximum number of concurrent sessions.
For details, see 20.4.2(104) CDSESSIONTIMEOUT in the JP1/Automatic Job Management System 3 Configuration Guide.
(3) Reusing logon information and the number of sessions that share the logon information when desktop heap shortages occur
The desktop heap area might be insufficient if there are many sessions on the manager host that are executed after being mapped to the same OS user. In this case, reusing the logon information for each session can reduce the desktop heap usage.
If desktop heap shortages occur, change the settings so that the logon information is reused. Also consider the number of shared sessions, if you reuse the logon information.
For details, see 20.4.2(12) REUSELOGON in the JP1/Automatic Job Management System 3 Configuration Guide and 20.4.2(13) LOGONSHMAX in the JP1/Automatic Job Management System 3 Configuration Guide.
- Cautionary note
-
Changing this setting will also change how session processes are started in operations such as connecting to JP1/AJS3 - View and remotely executing a command.
(4) Output from the scheduler log
You can specify whether to output, to the scheduler log of JP1/AJS3 - Manager, the start and end messages for connections from the Web Console server to the scheduler service. By default, the messages are not output to the scheduler log. Specify the setting that suits your operations.
For details, see 20.4.2(16) MONLOG in the JP1/Automatic Job Management System 3 Configuration Guide.
- Cautionary note
-
Changing this setting will also change the settings of whether to output connection-start messages and connection-end messages for connections with JP1/AJS3 - View.
(5) Outputting start and end messages
You can specify whether to output, to the following logs in JP1/AJS3 - Manager, the start and end messages for services that accept connections from the Web Console server.
- In Windows:
-
-
Windows event log
-
Integrated trace log
-
- In UNIX:
-
-
syslog
-
Integrated trace log
-
By default, the messages are output to the logs. We recommend that you keep this default setting because you need this log data to track down the cause of a failure.
The following table lists the process for which messages are output and their timings.
|
No. |
Process |
Output timing |
|---|---|---|
|
1 |
ajscdinetd |
Start |
|
2 |
End |
For details, see 20.4.2(17) MONSYSLOG in the JP1/Automatic Job Management System 3 Configuration Guide.
- Cautionary note
-
Changing this setting will also change the settings of whether to output connection-start messages and connection-end messages for the ajsinetd process, the ajscdinetd process, and JP1/AJS3 - View.
(6) Size of the internal log
You can specify the size of the internal log messages of JP1/AJS3 - Manager.
The following table lists the types of processes for which internal log data is output, and the default size of the log messages.
|
No. |
Type of process that outputs messages to the internal log messages |
Default size |
|---|---|---|
|
1 |
ajscdinetd |
128 kilobytes |
|
2 |
ajsmonsvr |
4,096 kilobytes |
For details about the log size of the ajscdinetd internal log, see 20.4.2(22) AJSCDINETDLOGSIZE in the JP1/Automatic Job Management System 3 Configuration Guide. For details about the log size of the ajsmonsvr internal log see 20.4.2(105) CDMONSVRLOGSIZE in the JP1/Automatic Job Management System 3 Configuration Guide.
(7) The range of generation information
When you use the Web Console server to obtain the generation information of a unit, select one of the following date ranges for which information is obtained. The default value is all.
-
all
Specifies that information is to be obtained from generations that are executed or scheduled to be executed, on all dates.
-
today
Specifies that information is to be obtained from generations to be executed, on that day in the range of the base time.
If the valid range of the root jobnet schedule is set to 48 hours, the range of the generation information cannot be set to today.
For details, see 20.4.2(70) VIEWSTATUSRANGE in the JP1/Automatic Job Management System 3 Configuration Guide.
- Cautionary note
-
Changing this setting will also change the range of the generation information that is obtained by JP1/AJS3 - View.
(8) Issuing JP1 events
You can specify whether to issue a JP1 event when a unit is manipulated by the Web Console server. By default, a JP1 event is not issued. Change the setting according to your operation.
For details, see 20.4.2(85) COMMANDEVENT in the JP1/Automatic Job Management System 3 Configuration Guide.
- Cautionary note
-
Changing this setting will also change the settings of whether a JP1 event is to be issued when a unit is manipulated from JP1/AJS3 - View.
(9) Executing a jobnet whose scheduled execution start time has passed
You can use options for planned execution registration to specify how a jobnet is to be executed if the scheduled execution start time for the jobnet has already passed when the service starts or when the jobnet is registered for execution.