6.9.4 Example of creating a general monitoring object (Cosminexus resource monitoring by JP1/Cm2/SSO)

You can use JP1/Cm2/SSO version 8 or earlier to monitor the operating performance of J2EE applications and some logical servers defined by using Cosminexus.

Central Scope allows you to link (automatically generate monitoring trees for) Cosminexus and JP1/Cm2/SSO version 8 or earlier by using the setup commands. When the following requirements are satisfied, you can automatically generate a general monitoring object that monitors the JP1 events issued when the status of the resources of the J2EE applications and logical servers monitored by JP1/Cm2/SSO changes (when Cosminexus and JP1/Cm2/SSO are linked to JP1/IM).

Requirements for automatically generating monitoring trees

The version of Cosminexus is 06-00 or later, and the version of JP1/Cm2/SSO is 7 or 8 (the product name of JP1/Cm2/SSO version 7 is JP1/PFM/SSO).
The products to be linked (Cosminexus and JP1/Cm2/SSO) have already been set up.
The setup commands for linking Cosminexus and JP1/Cm2/SSO to JP1/IM have already been executed.
JP1/Cm2/SSO version 8 or earlier is monitoring the J2EE applications or logical servers that were defined by using Cosminexus.
In the Auto-generation - Select Configuration window, Business Oriented Tree is selected (no monitoring tree is automatically generated when Server Oriented Tree is selected).

The following table describes the types of monitoring objects you can automatically generate when Cosminexus and JP1/Cm2/SSO are linked to JP1/IM.

Table 6‒15: Types of monitoring objects that can be automatically generated when Cosminexus and SSO are linked to JP1/IM
Type of monitoring object	Description	Item monitored
J2EE Server Resource Monitoring (SSO)	Monitors the status of resources used by Cosminexus J2EE servers^#. The status of this object changes when an event related to a J2EE server resource is issued.	J2EE server
CTM Resource Monitoring (SSO)	Monitors the status of resources used by Cosminexus CTM^#. The status of this object changes when an event related to a CTM resource is issued.	CTM
SFO Resource Monitoring (SSO)	Monitors the status of resources used by Cosminexus SFO servers^#. The status of this object changes when an event related to an SFO server resource is issued.	SFO server
J2EE Application Resource Monitoring (SSO)	Monitors the status of resources used by Cosminexus J2EE applications^#. The status of this object changes when an event related to a J2EE application resource is issued.	J2EE application server

#: The events that are monitored by the monitoring object are SNMP traps with event level Warning or higher.

If you want to monitor the status of resources in the Cosminexus environment when the requirements for automatic generation of monitoring trees are not satisfied, you need to create a monitoring object manually.

The following describes how to manually create a monitoring object. Note that the description assumes that you want to monitor the status of resources of J2EE servers, CTM, SFO servers, and J2EE applications of Cosminexus that are defined in the following table.

Table 6‒16: Information about the Cosminexus servers and applications to be monitored
Item to be monitored	Type of monitoring object	Item to be specified	Value to be entered
J2EE server	J2EE Server Resource Monitoring (SSO)	Domain name	`DefaultDomain`
		Logical server name	`J2EE_SV1`
		Name of the manager running JP1/Cm2/SSO version 8 or earlier (event-issuing host)	`HostA`
		Name of the host running the logical server (host name)	`HostB`
CTM	CTM Resource Monitoring (SSO)	Domain name	`DefaultDomain`
		Logical server name	`CTM_SV1`
		Name of the manager running JP1/Cm2/SSO version 8 or earlier (event-issuing host)	`HostA`
		Name of the host running the logical server (host name)	`HostB`
SFO server	SFO Resource Monitoring (SSO)	Domain name	`DefaultDomain`
		Logical server name	`SFO_SV1`
		Name of the manager running JP1/Cm2/SSO version 8 or earlier (event-issuing host)	`HostA`
		Name of the host running the logical server (host name)	`HostB`
J2EE application	J2EE Application Resource Monitoring (SSO)	Domain name	`DefaultDomain`
		Logical server name	`J2EE_SV1`
		Name of the manager running JP1/Cm2/SSO version 8 or earlier (event-issuing host)	`HostA`
		Name of the host running the logical server (host name)	`HostB`

When you create a monitoring object for monitoring the status of resources of the servers and applications described in the above table, you need to enter values for some items during definition. The table below describes the items you need to select as monitoring conditions and the values you need to enter. These items are underlined in the table.

Table 6‒17: Items to be selected as monitoring conditions and values to be entered
Type of monitoring object	Window to be used	Monitoring node attribute name	Attribute name	Monitoring node attribute value	Condition
J2EE Server Resource Monitoring (SSO)	Basic Information Settings window	Category name	`E.SNMP_VARBIND2`	`COSMINEXUS`	Match
		Event-issuing host	`E.SNMP_VARBIND11`	`HostA`^#	Host name comparison
		Host name	`E.SNMP_VARBIND12`	`HostB`^#	Host name comparison
	Status-Change Condition Settings window	Resource group name	`E.SNMP_VARBIND3`	`Server`	`Match`
	Status-Change Condition Settings window	Instance name	`E.SNMP_VARBIND6`	`^DefaultDomain:J2EE_SV1(:.*\|$)`	`Regular expression`
CTM Resource Monitoring (SSO)	Basic Information Settings window	Category name	`E.SNMP_VARBIND2`	`COSMINEXUS`	Match
		Event-issuing host	`E.SNMP_VARBIND11`	`HostA`^#	Host name comparison
		Host name	`E.SNMP_VARBIND12`	`HostB`^#	Host name comparison
	Status-Change Condition Settings window	Resource group name	`E.SNMP_VARBIND3`	`Scheduler (CTM)`	`Match`
	Status-Change Condition Settings window	Instance name	`E.SNMP_VARBIND6`	`^DefaultDomain:CTM_SV1(:.*\|$)`	`Regular expression`
SFO Resource Monitoring (SSO)	Basic Information Settings window	Category name	`E.SNMP_VARBIND2`	`COSMINEXUS`	Match
		Event-issuing host	`E.SNMP_VARBIND11`	`HostA`^#	Host name comparison
		Host name	`E.SNMP_VARBIND12`	`HostB`^#	Host name comparison
	Status-Change Condition Settings window	Instance name	`E.SNMP_VARBIND6`	`^DefaultDomain:SFO_SV1(:.*\|$)`	`Regular expression`
J2EE Application Resource Monitoring (SSO)	Basic Information Settings window	Category name	`E.SNMP_VARBIND2`	`COSMINEXUS`	Match
		Event-issuing host	`E.SNMP_VARBIND11`	`HostA`^#	Host name comparison
		Host name	`E.SNMP_VARBIND12`	`HostB`^#	Host name comparison
	Status-Change Condition Settings window	Instance name	`E.SNMP_VARBIND6`	`^DefaultDomain:J2EE_SV1:AP1(:.*\|$)`	`Regular expression`

#: Map beforehand as the host names the host names used by Cosminexus and the host names used by JP1/Cm2/SSO version 8 or earlier.

The following describes how to set a J2EE Server Resource Monitoring (SSO) monitoring object. The procedure for setting the monitoring objects of other types (CTM Resource Monitoring (SSO), SFO Resource Monitoring (SSO), and J2EE Application Resource Monitoring (SSO)) is omitted because the only difference is the value you enter in step 7. (For the value to be entered in step 7 for each type, see Table 6-16 Information about the Cosminexus servers and applications to be monitored.)

Figure 6‒25: Creating a J2EE Server Resource Monitoring (SSO) a monitoring object (steps 1 to 4)

Figure 6‒26: Creating a J2EE Server Resource Monitoring (SSO) a monitoring object (steps 5 to 8)

Figure 6‒27: Creating a J2EE Server Resource Monitoring (SSO) a monitoring object (steps 9 to 12)

To Page Top