1.2 What is explained in this manual

This manual provides an example of how to recognize a problem that has occurred in an IT base system (whose configuration is shown in the figure below) in each of the following cases and how to identify the target of analysis.

Emails sent by JP1/OA
Requests from customers or operators to check the operational status or to look into a problem
Event information from JP1/IM

If a problem occurred in the IT base system, use JP1/OA to do the following:

Analyze the bottleneck
Analyze the impact and problem severity
Analyze the cause

If you are monitoring applications, do the following in addition to the above analyses:

Analyze the relevance of events that occurred in an application, and identify the event that causes a problem.
Analyze the relevance between the identified event and user resource performance information.

The resources to be used in the analyses and the workflow for the analyses using those resources are as follows:

Consumers use user resources directly or through applications.
User resources use system resources.
JP1/OA monitors, through JP1/IM and JP1/PFM, the operational status of applications to check whether they operate normally.
JP1/OA monitors user resources and system resources. JP1/OA monitors user resources by using service level metrics and monitors system resources based on performance data.
JP1/OA uses this monitoring information to analyze problems.

The following table explains the meanings of the terms "consumer", "application", "user resource", and "system resource".

Term	Meaning
Consumer	A customer of a company, department, or business system that uses the application or IT resources.
Application	Software that operates on IT resources (such as JP1/AJS3 or DBMS that consumers use)
User resource	An IT resource (a logical resource such as a VM or volume) that is used by consumers
System resource	An IT resource (a physical resource such as a server or storage device) that is used by user resources

To Page Top