6.5 Features of and differences between jobnet monitoring programs

In JP1/AJS3, the following three types of programs can be used to monitor jobnets:

JP1/AJS3 - View
Web GUI
User application

The differences between the above program types are described below.

Differences in the program roles:

JP1/AJS3 - View is a program that allows users to perform a variety of jobnet-related operations, such as definition, execution, and monitoring.

The Web GUI is a program mainly used to execute and monitor jobnets. To define jobnets or jobs, use JP1/AJS3 - View or JP1/AJS3 - Definition Assistant.

User applications are programs that users develop by using the HTTP-based APIs available to JP1/AJS3 users. The role of a user application varies depending on the APIs or design policy.

Supplementary note

JP1/AJS3 - View is a program intended to monitor whole jobs and jobnets. JP1/AJS3 - View is suitable as a GUI for the person who monitors whole applications (the operations manager).

The Web GUI is a program intended to monitor specific jobnets. The Web GUI is suitable as a GUI for the person who monitors a specific application (a person in charge of specific operations).

Use JP1/AJS3 - View and the Web GUI appropriately according to their roles.

Figure 6‒21: Target usage of JP1/AJS3 - View and Web GUI

Differences in the system configuration and implementation method:

JP1/AJS3 - View must be installed as a separate task after JP1/AJS3 - Manager has been installed. JP1/AJS3 - View can be installed in Windows only.

The Web GUI uses a web browser (for example, Internet Explorer) that has already been installed in the client environment. Therefore, it is easier to prepare the monitoring terminal than to use JP1/AJS3 - View. You can also monitor jobnets on a Linux host if a supported web browser has been installed. In this case, however, you must install and set up JP1/AJS3 - Web Console, which provides server functionality, on the server to which the web browser is connected.

User applications are programs developed by users. Users can implement any functions in any programming language according to the APIs, environment, and design policy. In the same way as for the Web GUI, you must install and set up JP1/AJS3 - Web Console on the server to which the user application is connected.

Differences in the connection environment:

JP1/AJS3 - View connects to JP1/AJS3 - Manager via a LAN or WAN environment. The WAN environment used by JP1/AJS3 - View must meet requirements for communication security and line stability. For security, SSL communication (encrypted communication) can be used.

The Web GUI connects to the JP1/AJS3 system via the Internet. Users can monitor, from clients connected to the Internet, the jobnets used in various places or environments. SSL communication (HTTPS communication) can also be used, if necessary.

The connection environment of a user application varies depending on the design policy. For example, as with the Web GUI, a function for monitoring jobnets via the Internet can be implemented in a user application.

Reference standard for the number of monitoring targets

In the case of the Web GUI, the time required to draw images on the web browser screen is proportional to the number of jobs and jobnets displayed. The following table describes a reference standard for the number of monitoring targets with the intention to use the Web GUI with an appropriate drawing time. We recommend that you use the Web GUI if the scale of the jobnets and jobs to be monitored is below this estimate, and JP1/AJS3 - View for systems whose scale exceeds it.

Monitoring target	Reference standard	Effect on drawing performance
Number of definitions of the jobnets and jobs under the root jobnet to be monitored	500^#	This number of monitoring targets affects the time required to draw the following screens and dialog box: Monitor screen and Monitor dialog box Monthly Schedule screen Dashboard screen List screen
Number of saved generations of the root jobnet to be monitored and the jobnets and jobs under the root jobnet	10	This number of monitoring targets affects the time required to draw the following screen: Monthly Schedule screen Dashboard screen

Monitoring target

Reference standard

Effect on drawing performance

Number of definitions of the jobnets and jobs under the root jobnet to be monitored

500^#

This number of monitoring targets affects the time required to draw the following screens and dialog box:

Monitor screen and Monitor dialog box
Monthly Schedule screen
Dashboard screen
List screen

Number of saved generations of the root jobnet to be monitored and the jobnets and jobs under the root jobnet

This number of monitoring targets affects the time required to draw the following screen:

Monthly Schedule screen
Dashboard screen

#

Although monitoring on a larger scale is possible, when using the Monthly Schedule screen of the Web GUI, make sure that the number of units being monitored does not exceed the following limit for the browser. If this limit is exceeded, the screen might freeze or information might not be displayed correctly.

Internet Explorer: 3,000 units
Firefox ESR or Google Chrome: 6,000 units

To Page Top