13.1.13 Checking the JP1/AJS3 operational status by using the Web GUI

To check whether the JP1/AJS3 system is operating stably during everyday business operation, you must obtain multiple types of information. This section describes how you can use the Web GUI (Management Portal) to check whether the JP1/AJS3 system is operating stably.

Organization of this subsection

(1) Background
(2) Goals
(3) Approach
(4) Configuration example
(5) Manual references
(6) Cautionary notes

(1) Background

In JP1/AJS3, the types of information necessary to check whether the system is operating stably can be obtained separately by using commands. However, command-based operations can sometimes become quite complex.

Figure 13‒25: Example of using commands to check JP1/AJS3 operational status

Suppose that you are using commands to monitor the status of the JP1/AJS3 system in your company and want to simplify the daily system monitoring procedure in order to operate the JP1/AJS3 system in a more stable manner.

To Page Top

(2) Goals

Easily check information about whether the JP1/AJS3 system is operating stably in a visual manner by using a GUI.
Quickly locate problems in the JP1/AJS3 system so that they can be resolved in a shorter time.

To Page Top

(3) Approach

Set up the Web GUI (Management Portal) so that you can check the JP1/AJS3 operating information from a web browser.

The following figure shows an example of the screen displayed when using the Web GUI (Management Portal) to check JP1/AJS3 status information.

Figure 13‒26: Example of the screen displayed when using the Web GUI (Management Portal) to check JP1/AJS3 status information

With the Web GUI (Management Portal), you can check the following information from a web browser:

Whether the JP1/AJS3 services are running
Whether databases have a large number of unavailable areas
Whether there are factors that might stop job execution
Whether the manager and agent hosts can communicate with each other
Operational conditions of the JP1/AJS3 system including the usage states of scheduler services and the number of job executions

To Page Top

(4) Configuration example

To use the Web GUI (Management Portal), set it up on both the manager host and agent host.

When setup of the Web GUI (Management Portal) is complete, log in to it from a web browser to check the JP1/AJS3 status as a routine part of your work.

(a) Example of setting up the Web GUI (Management Portal)

The following shows the procedure for setup on the manager host and agent host:

Specify the following additional settings^# so that the JP1/AJS3 status can be obtained:
- Settings for detecting factors that might stop job execution
- Settings for reducing a delay in job distribution
- Settings for outputting performance reports
Install JP1/AJS3 - Web Console.
On the manager host, set up the Web GUI (Management Portal).
On the agent host, set up the Web GUI (Management Portal).

#:

The Web GUI (Management Portal) can be used even if the preceding three additional settings are not specified. However, if these additional settings are not specified, some of the JP1/AJS3 operating information will not be obtained with the Web GUI (Management Portal).

Settings for detecting factors that might stop job execution
Settings for reducing a delay in job distribution
Settings for outputting performance reports

(b) Example of using the Web GUI (Management Portal)

The following shows the procedure for checking the JP1/AJS3 statuses from a web browser:

Use a web browser to log in to the Web GUI (Management Portal).
On the Summary screen of the Web GUI (Management Portal), check the JP1/AJS3 summary status.

If the JP1/AJS3 summary status is normal, you do not need to check any more items.
If the JP1/AJS3 summary status is abnormal, move to other screens that show detailed information and identify the location of abnormality.
Address the abnormality by using JP1/AJS3 - View, the Web GUI (Job Portal), or commands.

To Page Top

(5) Manual references

Type	Item	Location
Overview	Overview of Web GUI (Management Portal)	8. System Monitoring in the manual JP1/Automatic Job Management System 3 Overview 9.2.3 Management Portal screens in the manual JP1/Automatic Job Management System 3 Overview 4.6.3 Considering the Management Portal execution environment in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide
Estimates	Estimation of the amount of data that will be used by the Web GUI (Management Portal)	3.1.3 Response of Web GUI in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide 3.2.1 Estimating the data flow on the network in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide
Estimates	Estimation of the size of log files that will be used for the Web GUI (Management Portal)	3.4.7 Estimating the size of log files for Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide
Configuration	Setup of the manager host	6.7.2(1) Procedure for setup on the manager host in the JP1/Automatic Job Management System 3 Configuration Guide 15.8.2(1) Procedure for setup on the manager host in the JP1/Automatic Job Management System 3 Configuration Guide
	Setup of the agent host	6.7.2(2) Procedure for setup on the agent host in the JP1/Automatic Job Management System 3 Configuration Guide 15.8.2(2) Procedure for setup on the agent host in the JP1/Automatic Job Management System 3 Configuration Guide
	Settings for obtaining the JP1/AJS3 information	21.5 Setting up the job distribution delay reduction function in the JP1/Automatic Job Management System 3 Configuration Guide 21.7 Settings for detecting factors that might stop job execution in the JP1/Automatic Job Management System 3 Configuration Guide 15.7 Settings related to the output of performance reports in the JP1/Automatic Job Management System 3 Configuration Guide
Dialog boxes		16. Management Portal of the Web GUI in the JP1/Automatic Job Management System 3 Operator's Guide

To Page Top

(6) Cautionary notes

When the Web GUI (Management Portal) is used, whether the communication encryption function is enabled depends on the physical host settings. Therefore, the setting of whether the communication encryption function is enabled must be shared by servers that communicate with each other, among the Web Console server, manager host's physical host, and agent host's physical host. However, if you set INETD for the AJS3SSL environment setting parameter, you can disable encryption for communication between the manager host and agent host even when encryption is enabled for communication between the Web Console server and manager host. If you specify a logical host as the connection destination of the Management Portal when using the Web GUI (Management Portal), the following note also applies. In this case, you must make sure that the SANs of the server certificate on the physical host include the physical host name and the names of all logical hosts that exist on the physical host. For details, see 2.3.6 Encryption of JP1/AJS3 communications with SSL in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
The host connected from the Web GUI (Management Portal) can be used in a cluster environment. In this case, however, the JP1/AJS3 System Control Manager service and JP1/AJS3 System Control Agent service are excluded from the failover-target resources. Therefore, you must specify the settings to achieve either of the following statuses:
- The JP1/AJS3 System Control Manager service and JP1/AJS3 System Control Agent service are running on both the active and standby server machines.
- The JP1/AJS3 System Control Manager service and JP1/AJS3 System Control Agent service are automatically started by, for example, cluster software settings or the jajs_start.cluster.model setting when the logical hosts of the active and standby servers start.
For details, see 8.2.11 Settings for using the host connected from the Web GUI (Management Portal) in a cluster environment in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows) or 17.2.12 Settings for using the host connected from the Web GUI (Management Portal) in a cluster environment in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).

To Page Top