Service platform notifies JP1 of the failure messages that occur as JP1 events. You can thereby collect the error messages that are output and centrally monitor these messages on JP1 integrated console.

Along with receiving JP1 specific events (error messages) at JP1 side, you can automate system operations such as executing commands automatically and notifying error occurrence to system administrator and executing commands for recovery.

For details about the settings for monitoring on JP1 integrated console, see "2.8 Environment setup while using JP1 integrated functionality". For details about the message mapping file (system log mapping file for JP1/IM linkage) see "10.19 System log message mapping file for JP1/IM linkage" in "Application Server Definition Reference Guide".

INTENTIONALLY DELETED

The following table lists the processes for which monitoring in JP1 is recommended:

Table 7-130 Table Process for which monitoring in JP1 is recommended

Process for which monitoring is recommended	Process name
	In Windows	In UNIX
Management Server	mngsvr.exe	Cjstartsv#
Administration Agent	adminagentsv.exe	adminagent

Note #

Monitor in command line name (ps -ef suitable). Following is an execution example:

/opt/Cosminexus/CC/server/bin/cjstartsv cosmi_m

"cosmi_m" is default server name. When you change the server name to something other than "cosmi_m", you also need to change the command line name that you want to monitor.

When you use database, JP1 monitoring is also recommended for the processes in the database in use. For details about these process names, see the manual for each database.

For details about process monitoring by JP1, see "7.1.2 Monitoring processes through JP1" in "Service Platform Overview".