5.4.1 Overview of Web GUI (Management Portal)

The Web GUI (Management Portal) allows users to check for abnormalities in JP1/AJS3 operation in a visual manner. The following table lists the items that can be checked by using the Web GUI (Management Portal) and the locations where the items can be checked.

Table 5‒4: Items that can be checked by using the Web GUI (Management Portal) and the locations where the items can be checked
No.	Item	Check Location
1	Whether the status of the manager host is normal	Summary screen
2	Whether the status of each scheduler service is normal	Scheduler Service Details screen
3	Time periods in which many jobs are queued or running	Job Execution Details dialog box
4	Whether jobnets with start conditions have been retained	Details on the Retention Status of Jobnets with Start Conditions dialog box
5	Whether there is unreported information	Event Job Retention Details dialog box
6	Whether databases have a large number of unavailable areas	Database Details screen
7	Whether there is a problem with the status of each execution agent	Target host screen
8	Whether JP1/AJS3 services and processes are running	Service Details dialog box Process Details dialog box
9	Load on the JP1/AJS3 system, including the usage of scheduler services and the number of job executions	Usage status of the Scheduler Service dialog box Number of job executions dialog box Number of job executions in a day dialog box
10	Results of job executions on execution agents	Operating status of target host dialog box Operating status in a day dialog box

To use the Web GUI (Management Portal), you must set it up on both the manager host and agent host. For details about how to set up, see 6.7 Settings related to the Web GUI in the JP1/Automatic Job Management System 3 Configuration Guide (in Windows) or 15.8 Settings related to the Web GUI in the JP1/Automatic Job Management System 3 Configuration Guide (in UNIX).

For details on Web GUI (Management Portal) operations, see 16. Management Portal of the Web GUI in the JP1/Automatic Job Management System 3 Operator's Guide.

You can review the JP1/AJS3 operations or address abnormalities in JP1/AJS3 operations by using JP1/AJS3 - View, the Web GUI (Job Portal), or commands. For details on JP1/AJS3 - View operations, see 12. Windows and Dialog Boxes in the JP1/Automatic Job Management System 3 Operator's Guide. For details on Web GUI (Job Portal) operations, see 15. Job Portal of the Web GUI in the JP1/Automatic Job Management System 3 Operator's Guide. For details about commands, see 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

Organization of this subsection

(1) Number of jobs in the Now queuing or Now running status

If it is likely that the number of queued and running jobs will reach the upper limit specified for the MaximumContentJob environment setting parameter in a specific time period, review the jobs that are executed in and around that period. For details about the MaximumContentJob environment setting parameter, see 20.5.2(12) MaximumContentJob in the JP1/Automatic Job Management System 3 Configuration Guide.

To Page Top

(2) Retention of execution generations with satisfied start conditions

If there might be some generations of a jobnet with start conditions remaining unexecuted, you must revise the job definitions in the root jobnet definition. For details on the jobnet for which start conditions, see 3.4.6 Retention of execution generations with satisfied start conditions in the manual JP1/Automatic Job Management System 3 Overview, 3.4.8 Operations on a jobnet registered for execution with a start condition in the manual JP1/Automatic Job Management System 3 Overview and 8.1.1 Stopping a jobnet that is monitoring start conditions.

To Page Top

(3) If there is unreported information

If there is unreported information, a large number of unexpected events might have occurred for a specific jobnet with start conditions. In such a case, take measures by operating units from JP1/AJS3 - View or the Web GUI (Job Portal), or by executing commands. For details about how to take measures, see 2.5 Troubleshooting problems if processing of a jobnet with a start condition is delayed in the manual JP1/Automatic Job Management System 3 Troubleshooting.

To Page Top

(4) If the load on the JP1/AJS3 system (including usage of scheduler services and the number of job executions) becomes high

If the load on the JP1/AJS3 system (including usage of scheduler services and the number of job executions) becomes high, JP1/AJS3 processing performance (for example, throughput) might be affected. In such a case, review the operational conditions or system configuration to reduce the system load. See the information in the following sections and take action if necessary:

1.3.1 Preparatory estimates and settings for running JP1/AJS3 in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide
3.1.1 Job throughput in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide
23.2 Estimating the database area in the JP1/Automatic Job Management System 3 Configuration Guide

To Page Top