Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 System Design (Configuration) Guide


3.1.4 Response of user applications that use API functions

If you create an original user application that uses API functions, the response time from JP1/AJS3 - Manager can be estimated using the following equation:

Response time =

Processing-time-at-JP1/AJS3 - Manager

+ data-transfer-time

+ Processing-time-at-Web-Console-server

+ Processing-time-at-user-application

Organization of this subsection

(1) JP1/AJS3 - Manager processing time

If the processing performance of the computer in which JP1/AJS3 - Manager is installed is low, the processing time will be long. The processing at JP1/AJS3 - Manager is shown below:

(a) Connection (user authentication)

When a user application connects to JP1/AJS3 - Manager, the application accesses the authentication server for user authentication processing. If the computer running the authentication server has not been started, or multiple authentication servers are used, there will be a corresponding increase in processing time.

In user applications, a user must be authenticated every time the application issues an API request. Therefore, the processing time becomes longer if the application issues a lot of requests.

(b) Acquiring execution schedule and execution result data of the unit

The processing at JP1/AJS3 - Manager differs according to the type of request from the user application but it mainly searches or references the statuses stored on a disk. Therefore, the processing tends to be influenced by the disk performance.

Processing takes more time when it displays a jobnet with many components and many execution generations. The calculation of execution schedule is also influenced by the CPU performance.

To increase stability of performance, you must estimate the entire load on the server, taking into account the frequency of disk access by other applications, the circumstances of CPU use, and so on.

(c) Operations on units

When a lengthy fixed-execution registration is done for a jobnet with many component elements, or the registration of a jobnet with a very large number of logs to keep setting is canceled, the processing time at JP1/AJS3 - Manager will be long. Under such conditions, the communication processing might time out at JP1/AJS3 - Manager. Consider reviewing the user application design to speed up the processing time in JP1/AJS3 - Manager by, for example, reducing the fixed registration period or setting a smaller number of logs to keep.

(d) Operations on execution agents

If operations are performed simultaneously on multiple execution agents, the processing time increases in proportion to the number of target execution agents.

(2) Data transfer time

The data transfer time is influenced by the network performance between the user application, Web Console server, and JP1/AJS3 - Manager.

(3) Processing time in the Web Console server

If the processing performance of the computer in which JP1/AJS3 - Web Console is installed is low, the processing time will be long. The processing at JP1/AJS3 - Web Console is shown below:

(a) Processing a request from a user application

The Web Console server processes requests for authentication, unit manipulation, information acquisition, or other requests from the user application, and sends the requests to JP1/AJS3 - Manager. The processing takes time if there are frequent processing requests from the user application, or if many user applications are connected. To increase performance stability, you need to estimate the loads on the entire server machines considering the number of user applications that can be concurrently connected and CPU usage.

(4) Processing time in a user application

The processing time in a user application is influenced by the machine processing performance or the method used for deploying the user application. If the processing speed of a user application is low, consider the following: