Shown below are the actions for the problems expected in the system linked with JP1/IM:

Table 2-16 Errorsexpected in a system linked with JP1/IM and their actions

Problem type	Actions
Occurrence of an error at the time of auto generation of the monitoring tree	When an error occurs, investigate the cause of the error based on the Cosminexus adapter command message that is output in the JP1/Base plug-in service log file. For details on the JP1/Base plug-in service log file, see the manual JP1/Base Operation Guide.
No notification of the JP1 event to JP1/IM	Confirm the log of the Administration agent, Management agent, and Management Server to check whether the JP1 event is published to JP1/IM from the system built with Application Server. For details on the storage location of the log of Administration Agent, Management Agent, and Management Server, see 4.3.1 Acquiring the Cosminexus Component Container Logs or 4.4.1 Acquiring the Cosminexus Component Container Logs (system executing batch applications). Take the following actions for the contents of the log of Administration agent, Management agent, and Management Server. When the JP1 event publishing log is not output, confirm the JP1 event publishing settings of the Management Server#. When the JP1 event publishing log is output, confirm the contents of the JP1/Base configuration definition created in the JP1 integrated operation management server. Moreover, confirm the action environment settings of the JP1/Base event service in the Management Server# and J2EE server.
Web browser does not start after starting the JP1/IM-View monitor	Investigate the cause of the error that occurred based on the message output in the mngsvrmonitor.log, which is saved in the directory where the monitor start command is copied.

#

This is the Management Server of Application Server.