4.6.1 Environment settings for the Web Console server

This subsection explains Web Console server environment settings that need to be considered in advance.

Organization of this subsection

(1) Log sizes and the number of log files output by the Web Console server
(2) Time zone of the Web Console server
(3) Changing display colors for the Web GUI (Job Portal)
(4) Settings for restricting the operations that Web GUI (Job Portal) users can perform
(5) Settings on manager hosts to which the Web Console server can connect
(6) Restricting execution of API functions from user applications
(7) Setting whether to display information about the connection-destination manager host
(8) Setting the session timeout period for the Web GUI
(9) Setting the port number for connection to JP1/AJS3 - Manager when using the Web GUI (Management Portal)

(1) Log sizes and the number of log files output by the Web Console server

The Web Console server outputs the following three types of log data:

Command log

Outputs log data about command operations.
Application server log

Outputs log data about Web GUI operations or API calls from user applications.
Application server common log

Outputs log data about the starting and stopping of the web application server.

The following table lists the default sizes and the number of files for each type of log.

Table 4‒14: Default sizes and the number of files of the log data output by the Web Console server
No.	Log type	Default size	Default number of files
1	Command log	128 kilobytes	2
2	Application server log	8,192 kilobytes	2
3	Application server common log	8,192 kilobytes	2

For the command log and application server log, you can change the size and the number of files of the log data. The size and the number of files for the application server common log cannot be changed.

The log size and the number of files for the command log and application server log are specified in the environment-settings file (ajs3web.conf). For details about the environment-settings file (ajs3web.conf), see the section corresponding to the OS. For Windows, see 3.4.3 Details on the settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For Linux, see 13.3.3 Details on settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top

(2) Time zone of the Web Console server

The date and time information on the Web GUI or a user application is displayed according to the manager host time zone regardless of the client host time zone. Therefore, if the Web Console server and the manager host have different time zones, you need to specify the manager host time zone in the environment-settings file (ajs3web.conf) on the Web Console server.

The following figure shows example time zones of the Web Console server and manager hosts.

Figure 4‒12: Example time zones of the Web Console server and manager hosts

In this example, the time zone of the Web Console server is JST, time zones of the manager hosts from A to C are JST, Asia/Shanghai, America/New_York, respectively. The time displayed on the Web GUI is the time zone of the corresponding destination manager host.

If you connect to the manager host A, setting the environment-settings file (ajs3web.conf) is not required. If you connect to the manager host B or manager host C, you need to set the time zone in the environment-settings file (ajs3web.conf). This is because the time zone of the manager host and that of the Web Console server do not match.

By using the ajswebtz.bat command (in Windows) or the ajswebtz command (in Linux), you can obtain a list of time zones that can be specified in the environment-settings file (ajs3web.conf). For details, see ajswebtz.bat (Windows only) in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference or ajswebtz (Linux only) in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about the environment-settings file (ajs3web.conf), see the section corresponding to the OS. For Windows, see 3.4.3 Details on the settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For Linux, see 13.3.3 Details on settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top

(3) Changing display colors for the Web GUI (Job Portal)

The following discusses the colors that indicate the statuses of units displayed in the windows and dialog boxes of the Web GUI (Job Portal). You can change the display colors by changing settings in the display color settings file (ajs3web_color.conf) on the Web Console server.

For details about the display color settings file (ajs3web_color.conf), see the section corresponding to the OS. For Windows, see 3.4.7 Details on the settings in the display color settings file (ajs3web_color.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For Linux, see 13.3.7 Details on the settings in the display color settings file (ajs3web_color.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.

Changing the display colors that indicate unit statuses

You can change the colors that indicate the statuses of units displayed in the windows and dialog boxes of the Web GUI (Job Portal). The following table lists the windows and dialog boxes in which display colors can be changed, and the items whose display colors can be changed. Note that, for icons, you can change the background color only.

Table 4‒15: Items whose display colors can be changed by editing the display color settings file (`ajs3web_color.conf`)
No.	Screen and Dialog box			Items whose display colors can be changed
1	Dashboard screen	Status of Root Jobnet area		Execution progress (for individual root jobnets)
2				Root jobnet status icons
3				Execution progress (for the whole units)
4				Unit status icons
5		Detail Information area	List tab	Icons in the Status column
6				Icon for the Hold-On button
7				Icon for the Hold-Off button
8			Chart tab	Execution schedule
9	List screen	List area		Icons in the Status column
10	List screen	List area		Icons in the Result column
11	Monitor dialog box, Monitor screen	Map area		Icons for the Unit
12		Top of the screen and dialog box		Icon for the Hold-On button
13				Icon for the Hold-Off button
14				Icon for the Interrupt button
15				Icon for the Kill button
16				Icon for the Rerun button
17	Generation Selection dialog box			Icons in the Status column
18	Monthly Schedule screen	Schedule area		Execution schedule
19		List area		Icons in the Status column
20		Top of the screen		Icon for the Hold-On button
21		Top of the screen		Icon for the Hold-Off button
22	Wait Conditions Statuses dialog box	List area of units with wait conditions		Icons in the Status column
23	Wait Conditions Statuses dialog box	List area of units whose end is being waited for		Icons in the Status column

Setting to use the same display colors for the Web GUI and JP1/AJS3 - View

By using the model file ajs3web_color_view.conf.model, you can set the display colors for the Web GUI to the default display colors for JP1/AJS3 - View. If display colors for JP1/AJS3 - View were changed from the defaults, those colors can be also set for the Web GUI. To do this, change definitions in the display color settings file (ajs3web_color.conf).

Display color for the delay

For units in the Delay status, you can specify whether to have the status displayed as the color for its icon, status, or result.

You can also use the DELAY_COLOR_PRIORITY parameter in the display color settings file (ajs3web_color.conf) to specify which status color to display for a unit if the status of the unit is simultaneously Abend, Warning, or Delay. You can specify the following values:

A-W-D

The priority for the displayed color is Abend > Warning > Delay.
A-D-W

The priority for the displayed color is Abend > Delay > Warning.
D-A-W

The priority for the displayed color is Delay > Abend > Warning.

For example, if you specify A-W-D and a jobnet ends abnormally due to a delay, the color for abnormal ends (light red) is displayed. If you specified D-A-W, the color for delayed ends (cherry blossom color) is displayed.

Select a priority according to the importance placed on delays when monitoring the system. The default is A-W-D. To prioritize the monitoring of delays in units whose execution impacts the business as a whole, specify D-A-W.

Hold plan

You can specify whether to use the color for Hold plan for unit icons and color images in the Status and Result columns if a unit is in a wait status and its hold attribute has been set. The wait status is Wait for start time, Wait for prev. to end, Waiting to execute, or Wait for start cond.

To Page Top

(4) Settings for restricting the operations that Web GUI (Job Portal) users can perform

You can restrict the operations that can be performed by each JP1 user who logs in to the Web GUI (Job Portal).

To restrict the operations that users can use the Web GUI (Job Portal) to perform, first, change the following two settings in the environment settings file (ajs3web.conf) on the Web Console server:

Enable the operation restriction function: Enable the operation restriction function, which is disabled by default. If the operation restriction function is enabled on a Web Console server, the function is available on all manager hosts to which the Web Console server connects. Immediately after this function is enabled, the default setting (permit only viewing) is applied to all users.
Specify a user who can set operational restrictions: Specify a JP1 user who can change the operation restriction settings of individual JP1 users for each manager host to which a connection is to be established. This JP1 user is referred to as a user who sets permissions.

A user who is appointed as a user who sets permissions can set operational restrictions for each JP1 user by applying the operating permission configuration file from the Web GUI (Job Portal). Note that you must apply the operating permission configuration file to each manager host to which a connection is to be established.

For details about environment-settings file (ajs3web.conf), see the sections corresponding to the OS. For Windows, see 3.4.3 Details on the settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide. For Linux, see 13.3.3 Details on settings in the environment-settings file (ajs3web.conf) in the JP1/Automatic Job Management System 3 Configuration Guide.

For details about the operating permission configuration file, see 15.4.2 Customizing the operation restriction settings for each user in the JP1/Automatic Job Management System 3 Operator's Guide.

The following table lists the operations that can be restricted by using the operating permission configuration file.

Table 4‒16: Operations that can be restricted by using the operating permission configuration file
No.	Operation that can be restricted	Description
1	Register for Execution	Registers a unit for execution.
2	Cancel Registration	Cancels the execution registration of a unit.
3	Adding an execution schedule	Schedules a unit to run at a specified time.
4	Change plan (change time)	Temporarily changes the start time of a unit that has been registered for execution.
5	Change plan (execute immediately)	Temporarily changes the execution schedule of a unit that has been registered for execution so that the unit is executed immediately.
6	Change plan (execution prohibited)	Temporarily changes the execution schedule of a unit that has been registered for execution so that execution of the unit is canceled.
7	Change plan (prohibit execution of retention generations)	You can stop execution of the execution generations that are in Wait for start cond. status.
8	Change plan (release change)	Restores the execution schedule of a unit whose execution schedule was temporarily changed.
9	Change Delay Monitor	Temporarily changes the delay monitoring settings of a unit that has been registered for execution.
10	Rerun	Reruns a unit that has already been run.
11	Interrupt	Interrupts the execution of a unit.
12	Kill	Kills the execution of a unit.
13	Change job status	Changes the job status.
14	Edit definition	Lets you edit the detailed definition of a job (PC job or Unix job only).
15	Hold	Sets the hold attribute of the unit.
16	Hold Release	Cancels the hold attribute of the unit.
17	Change Exec Order Method	Temporarily changes the execution order control method of the root jobnet.
18	Change Wait Status	Temporarily changes the wait status of a unit with wait conditions (whether a unit with wait conditions is still waiting for the end of the waiting-target unit).

To Page Top

(5) Settings on manager hosts to which the Web Console server can connect

Determine the manager hosts to which the Web Console server can connect. You can restrict the manager hosts to which the Web Console server can connect by changing the settings in the environment settings file (ajs3web.conf) on the Web Console server.

Manager hosts to which the Web Console server can connect

The Web Console server can connect to only those manager hosts whose names are specified in the environment settings file (ajs3web.conf). With the default settings, any management host is connectible. You can specify the following names as manager host names:

In physical host:: Host name that is output when the hostname command is run on a manager host
In logical host:: Logical host name that was specified when the logical host environment was set up

Method of specifying a value for [Host to connect] that appears in the Web GUI login screen

If the connectible manager hosts are restricted, you can change the Host to connect item appearing in the Web GUI login screen into a drop-down list that displays only the manager hosts that the user can connect to. By default, the Host to connect item is displayed as a text box in which the user enters the name of the connection-destination host.

Linkage with JP1/IM

To link JP1/AJS3 - Web Console with JP1/IM, you must permit connections to the JP1/AJS3 manager host that is to be monitored by JP1/IM.

To Page Top

(6) Restricting execution of API functions from user applications

In JP1/AJS3 - Web Console, API functions can be used to perform operations on units from user applications. You can also restrict execution of API functions by changing the settings in the environment settings file (ajs3web.conf) on the Web Console server. The default is that there are no restrictions. If restriction on execution of API functions is enabled, the users cannot run any API functions from user applications.

To Page Top

(7) Setting whether to display information about the connection-destination manager host

Consider whether the host name, OS, and other information about the connection-destination manager host is to be displayed from the Web GUI (Job Portal). Information about the connection-destination manager host can be displayed from the Web GUI (Job Portal) by changing the settings in the environment setting file (ajs3web.conf) on the Web Console server. The user can specify the information items to be displayed. If information about the connection-destination manager host is displayed from the Web GUI (Job Portal), the background color of the display areas and the font color can be changed.

The following figure shows an example of a window that displays information about the connection-destination manager host from the Web GUI (Job Portal).

Figure 4‒13: Example of a window that displays information about the connection-destination manager host from the Web GUI (Job Portal)

Information about the connection-destination manager host displayed from the Web GUI (Job Portal):: Information about the connection-destination manager host can be displayed in a window from the Web GUI (Job Portal) by specifying the information about the connection-destination manager host in the environment setting file (ajs3web.conf). By default, this information is not displayed. If the user can connect to multiple manager hosts from the Web GUI (Job Portal), the host name, OS, and other information about the connection-destination manager host will help the user connect to the correct manager host.
Background and font colors of the area that displays information about the manager host from the Web GUI (Job Portal): You can change the background color of the area that displays information about the connection-destination manager host and the font color of the information to be displayed. The Web GUI (Job Portal) user can easily identify the connection-destination manager host by changing the background color of the display area for each manager host that the user can connect to. Note that some combinations of background and font colors might affect the readability of text. If you change the background color of the area that displays information about the connection-destination manager host, select a font color that is easy to read on the background color.

To Page Top

(8) Setting the session timeout period for the Web GUI

Consider the proper session timeout period for the Web GUI. You can specify the session timeout period for the Web GUI by changing the setting in the environment settings file (ajs3web.conf) on the Web Console server. The default is 15 minutes.

To Page Top

(9) Setting the port number for connection to JP1/AJS3 - Manager when using the Web GUI (Management Portal)

Consider the port number for connection to JP1/AJS3 - Manager when the Web GUI (Management Portal) is used. If the default port number cannot be used for JP1/AJS3 - Manager, you must use another port number.

For details about network-settings file (ajscd_ajs3web.properties), see the sections corresponding to the OS. For Windows, see 3.4.4 Details on the settings in the network-settings file (ajscd_ajs3web.properties) in the JP1/Automatic Job Management System 3 Configuration Guide. For Linux, see 13.3.4 Details on settings in the network-settings file (ajscd_ajs3web.properties) in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top