2.15.1 Defining the Process Monitoring Function

Systemwalker Operation Manager's Process Monitoring function can monitor process operations of Systemwalker itself. The Process Monitoring function regularly monitors whether the processes that start Systemwalker services or daemons are operating. If it detects a process violation (a process that should have started does not exist), it notifies the administrator by outputting an application log reporting the error (or a system log in the case of UNIX). If the processes exist, the Process Monitoring function does not report an error.

Information

If Systemwalker Centric Manager coexists:

If Systemwalker Operation Manager and Systemwalker Centric Manager coexist in the same environment, a report from the Process Monitoring function is automatically passed to the host server by Systemwalker Centric Manager's system monitoring agent function.

Using the Process Monitoring function

As the Process Monitoring function automatically starts at the system start time, the user needs not recognize it. When the function is active, the process of Systemwalker itself is monitored at fixed intervals.

If a process error is detected, the user must check the operation status of Systemwalker Operation Manager on the detected machine and isolate the error cause.

List of processes to be monitored

The following lists the processes which can be monitored by the Process Monitoring function. The corresponding service and function names are also listed.

[Windows]

Abbreviated function category	Function category: Description	Function name	Service name	Service display name	Name of process monitored
BASE	Authentication	Security	Fujitsu MpWalker ACL Manager	Systemwalker ACL Manager	f3crssvr.exe
OMGR	Operation Manager	Calendar	Fujitsu MpWalker MpJmCal	Systemwalker MpJmCal	f3crhcs1.exe f3crhcs2.exe
		Automatic operation support (action execution)	MpAosfX	Systemwalker MpAosfX	f3crhxs2.exe (Note 3) f3crhxs2_64.exe (Note 1, 3) f3crhxs2_x64.exe (Note 2, 3)
		Power control (power control, service/application execution)	MpAosfP	Systemwalker MpAosfP	f3crhsv2.exe
		Automatic operation support (event monitoring, action management)	MpAosfB	Systemwalker MpAosfB	f3crhesv.exe f3crhdsv.exe f3crhxsw.exe f3crhesv_64.exe (Note 1) f3crhdsv_64.exe (Note 1) f3crhxsw_64.exe (Note 1) f3crhesv_x64.exe (Note 2) f3crhdsv_x64.exe (Note 2) f3crhxsw_x64.exe (Note 2)
		Systemwalker Operation Manager infrastructure	Fujitsu MpWalker MpJmSrv	Systemwalker MpJmSrv	mpjmsrv.exe jmnetsv.exe java.exe
		Systemwalker Operation Manager infrastructure	SystemwalkerMpAHSO	Systemwalker MpAHSO	httpd.exe
		Task Link	MpNjsosv	Systemwalker MpNjsosv	CNSSVENG.exe
		Job Execution Control	Fujitsu MpWalker MpMjes	Systemwalker MpMjes	mjssvc.exe mjsoba.exe
		Jobscheduler	Fujitsu MpWalker MpJobsch	Systemwalker MpJobsch	tskmnsrv.exe

Note 1:: This is the process name for the Windows for Itanium version.

Note 2:: This is the process name for the Windows x64 version.

Note 3:: Excluded from monitoring in Windows Server 2008 and later.

[UNIX]

Abbreviated function category	Function category	Function name	Function	Startup command	Name of process monitored
BASE	Authentication	Security	FJSVfwseo	rc.mpfwsec	MpFwsec
OMGR	Operation Manager	Calendar	FJSVjmcal	S99JMCAL	f3crhcs2
		Systemwalker Operation Manager infrastructure	FJSVJMCMN (Note 2)	start_jmcmn	mpjmsrv jmnetsv java httpd
		Job Execution Control	FJSVMJS (Note 2)	S99MJS	mjsdaemon (Note 1) mjsnetsv (Note 1)
		Jobscheduler	FJSVJOBSC (Note 2)	start_jobs	tskmnsrv (Note 1)

Note 1:: A process exists for each subsystem when multi-subsystems are operated.

Note 2:

This is the package name for the Solaris or Linux version. For the HP-UX and AIX versions, the package names are as follows:

[HP-UX version]: Systemwalker Operation infrastructure: FHPJMCMN
Job Execution Control: FHPMJS
Jobscheduler: FHPJOBSCH
Calendar: FHPjmcal

[AIX version]: Systemwalker Operation infrastructure: FAIXJMCMN
Job Execution Control: FAIXMJS
Jobscheduler: FAIXJOBSC
Calendar: FAIXjmcal

Terminating the Process Monitoring function

The Process Monitoring function is stopped automatically when Systemwalker Operation Manager is stopped by the poperationmgr command or when the system is shut down.

To terminate the Process Monitoring function when Systemwalker Operation Manager is operating, specify the following from the Systemwalker Operation Manager server.

[Windows]

Select Control Panel >> Administrative Tools >> Services and shut down the following service.

Systemwalker MpPmonO

[UNIX]

Execute the following command to stop the daemon of the Process Monitoring function.

/opt/FJSVftlo/pmon/bin/stpmppmon

Suppressing the automatic startup of Process Monitoring function

The Process Monitoring function starts automatically when Systemwalker Operation Manager is started up. To suppress the automatic startup of the Process Monitoring function, specify as follows. Your setup is effective in the next startup.

[Windows]

Select Control Panel >> Administrative Tools >> Services and set the following service to "Manual" startup.

Systemwalker MpPmonO

[UNIX]

Definition procedure

On the Systemwalker Operation Manager server, open the definition file of the following daemon startup/shutdown command using an editor.
/etc/opt/FJSVftlo/daemon/custom/rc3.ini
Edit the definition file as follows.
Enter character "#" at the beginning of the line where the daemon startup command of the Process Monitoring function is written. This line will be treated as a comment.
From
...DAEMONnn="/opt/FJSVftlo/pmon/bin/strmppmon"
To
...
#DAEMONnn="/opt/FJSVftlo/pmon/bin/strmppmon"

2.15.1.2 Changing the Processes to be Monitored

You can select a process to be monitored by the Process Monitoring function. The following explains the definition file contents and the method to change them.

Changing the process to be monitored

Use the following procedure to change the process to be monitored.

Change the definition file.
Change the definition file of the process to be monitored. The definition file contents and the method to change the contents are explained later.
Restart the Process Monitoring function.
Monitoring of the selected process is enabled only after you have restarted the Process Monitoring function. Restart the function in the following way.
[Windows]
- Select Control Panel >> Administrative Tools >> Services and restart the following service.
  Systemwalker MpPmonO
[UNIX]
1. Stop the Process Monitoring function.
  To do so, issue the following command.
  /opt/FJSVftlo/pmon/bin/stpmppmon.sh
2. Start the Process Monitoring function.
  To do so, issue the following command.
  /opt/FJSVftlo/pmon/bin/strmppmon.sh

Definition file

The definition file of the process to be monitored is stored in the following location.

[Windows]

Systemwalker Operation Manager installation directory\mpwalker.jm\mpcmtool\pmon\etc\mppmon.usr

[UNIX]

/etc/opt/FJSVftlo/pmon/mppmon.usr

Contents of the definition file

The definition file has the following contents. Change the set values by referring to the "Set values of the definition file" given below.

[Windows]

[BASE]
Fujitsu MpWalker ACL Manager=1
[OMGR]
Fujitsu MpWalker MpJmCal=1
MpAosfB=1
MpAosfX=1
MpAosfP=1
Fujitsu MpWalker MpJobsch=1
Fujitsu MpWalker MpMjes=1
MpNjsosv=1
Fujitsu MpWalker MpJmSrv=1

[UNIX]

[BASE]
rc.mpfwsec=1
[OMGR]
S99JMCAL=1
start_jmcmn=1
start_jobs=1
S99MJS=1

Set values of the definition file

The following explains the values being set in the definition.

[Function category]
Function=Monitoring

Function category:: Abbreviated function category

Function:: Abbreviated function name

Monitoring:

0 or 1

0: No process is monitored.

1: The process is monitored and its error is reported if occurred.

For details including the function categories, functions, and processes belonging to functions, see "List of processes to be monitored".

How to change the definition file?

You can change only the values of a process to be monitored. Do not change the function category and the function.

Example:

To release the Calendar function from being monitored in the Windows version, change the definition file as follows.

From

ŸŸŸ
[OMGR]
Fujitsu MpWalker MpJmCal=1
ŸŸŸ

ŸŸŸ
[OMGR]
Fujitsu MpWalker MpJmCal=0
ŸŸŸ

Note

Monitoring is not performed for the following functions even if you specify the setting to perform monitoring (monitoring action: "1").

Functions that have not been installed
Functions for which the Startup Type in the Services dialog box has been set to Manual or Disabled [Windows]
Functions for which the automatic daemon startup settings have been cleared in the following daemon batch startup customization file [UNIX]:
/etc/opt/FJSVftlo/daemon/custom/rc3.ini

2.15.1.3 Changing the Definition Information of Process Monitoring Function

The Process Monitoring function is executed according to the definition file contents. You can change the definition file contents when necessary. The following explains the file contents and the method to change them.

Changing the definition information

Use the following procedure to change the definition information of the Process Monitoring function.

Change the definition file.
Change the definition file of the Process Monitoring function. The definition file contents and the method to change the contents are explained later.
Restart the Process Monitoring function.
You need to restart the Process Monitoring function to make the changed definition information effective. Restart the function in the following way.
[Windows]
- Select Control Panel >> Administrative Tools >> Services and restart the following service.
  Systemwalker MpPmonO
[UNIX]
1. Stop the Process Monitoring function.
  To do so, issue the following command.
  /opt/FJSVftlo/pmon/bin/stpmppmon.sh
2. Start the Process Monitoring function.
  To do so, issue the following command.
  /opt/FJSVftlo/pmon/bin/strmppmon.sh

Definition file

The definition file of the Process Monitoring function is stored in the following location.

[Windows]

Systemwalker Operation Manager installation directory\mpwalker.jm\mpcmtool\pmon\etc\mppmon.ini

[UNIX]

/etc/opt/FJSVftlo/pmon/mppmon.ini

Contents of the definition file

The definition file has the following contents. Change the set values by referring to the "List of definition items" given below.

# Process Monitoring Definition File
#    Systemwalker Operation Manager

[Common]
StartWait=60      # Interval to Start Monitoring
                  # 60-3600 secs is available

CheckWait=60      # Interval of Each Monitoring
                  # (If, Monitor Result is Normal)
                  # 60-3600 secs is available

RetryWait=60      # Interval of Retry Monitoring
                  # (If, Monitor Result is Abnormal)
                  # 60-3600 secs is available

RetryCount=3      # Time to Retry
                  # 3-255 times is available

[Notification]
Destination=
                  # Destination Nodes to Notify
                  # You can direct until 4 nodes, as
                  # "Destination=node1,node2,node3,node4"
                  # If you don't direct any node, we use
                  # System Monitor default notification node
                  # (If System Monitor is running).

MyIPaddr=
                  # IP address of this host.
                  # If you don't direct, we try to find
                  # the one of this host, and use the one
                  # which we find at first.

MpTrap=OFF        # If you want to use Systemwalker Trap,
                  # edit as "MpTrap=ON",
                  # otherwise edit as "MpTrap=OFF"

MpConsole=OFF     # If you want to notify to Systemwalker Console,
                  # edit as "MpConsole=ON",
                  # otherwise edit as "MpConsole=OFF"

MpEvlog=ON        # If you want to output Eventlog,
                  # edit as "MpEvlog=ON",
                  # otherwise edit as "MpEvlog=OFF"

UserOriginal=OFF  # If you want to use your original command,
                  # edit as "UserOriginal=ON",
                  # otherwise edit as "UserOriginal=OFF"

### End of Definition File ###

List of definition items

The following lists the definition file items of the Process Monitoring function.

[Common] section

Set value	Description	Initial value	Valid entry
StartWait	Specifies a waiting time (in seconds) until the process monitoring is activated during startup.	60	60 - 3600
CheckWait	Specifies a time interval (in seconds) until the process status check.	60	60 - 3600
RetryWait	Specifies a time interval (in seconds) until the recheck of process error after its first detection.	60	60 - 3600
RetryCount	Specifies a number of times to recheck the process error after its first detection and notification.	3	3 - 255

[Notification] section

Set value	Description	Initial value	Valid entry
Destination (Note 1)	Specifies a node to which a process status error is reported. Up to four (4) nodes can be specified. If omitted, the destination of Systemwalker Centric Manager's system monitoring is used. The destination setup is valid if the Trap Notification function or the Customize Notification command is used. Setup example: Destination=node1,node2,node3	None	Up to 4 nodes separated by a comma from each other
MyIPaddr (Note 1)	Specifies an IP address of the source (local node) which detects and reports a process status error. Use the IP address to identify the fixed source IP if the node has multiple IP addresses. The default is the IP address of the first detected local node.	None	xxx.xxx.xxx.xxx format
MpTrap (Note 1)	Allows the Trap Report function to report an error. It is valid if Systemwalker Centric Manager V10.1/V10L20 is running at the destination. ON: Enable/OFF: Disable	OFF	ON or OFF
MpConsole (Note 2)	Displays an error report in the dialog of the screen where the Systemwalker Centric Manager's Systemwalker console is active. ON: Enable/OFF: Disable	OFF	ON or OFF
MpEvlog	Outputs an error information to the application log or system log of the detecting source during error detection. ON: Enable/OFF: Disable	ON	ON or OFF
UserOriginal	Executes the Customize Notification command during error detection. ON: Enable/OFF: Disable	OFF	ON or OFF

Note 1:: It is valid only when Systemwalker Operation Manager coexists with Systemwalker Centric Manager.

Note 2:: It is valid only when the Systemwalker Centric Manager operation management server coexists.

Executing a specific processing during error detection

If a process error is detected by the Process Monitoring function, the user-defined specific process can be executed.

This process must be written in the Customize Notification command (a batch file or shell script) and the UserOriginal parameter must be turned "ON" in the Notification section of "mppmon.ini" file (the process monitoring definition file) in advance so that the specific processing is executed during an error.

Customize Notification command

[Windows]

Systemwalker Operation Manager installation directory\mpwalker.jm\mpcmtool\pmon\bin\mppmonsnd.bat

[UNIX]

/opt/FJSVftlo/pmon/bin/mppmonsnd.sh

Contents of the command

No commands are executed by default. Write processing in the command, if necessary.

[Windows]

mppmonsnd.bat

@echo off
REM ############################################################
REM # [Usage]
REM # mppmonsnd.bat %1 %2 %3 %4 %5 %6 %7 %8
REM #
REM # Parameters
REM # %1: Product Information(CMGR 1, OMGR 2)
REM # %2: Error Process Name
REM # %3: IP Address (My Host)
REM # %4: The Number of Destination Hosts
REM # %5: Destination Host1 (if directed at mppmon.ini)
REM # %6: Destination Host2 (if directed at mppmon.ini)
REM # %7: Destination Host3 (if directed at mppmon.ini)
REM # %8: Destination Host4 (if directed at mppmon.ini)
REM ############################################################

REM # Specify User Original Commands.
REM #
REM # If you want to execute this mppmonsnd.bat, you should edit
REM # mppmon.ini file. you should edit like "UserOriginal=ON" of
REM # [Notification] section. So, in case that some processes of
REM # Systemwalker are in trouble, this mppmonsnd.bat will be
REM # executed.
REM # mppmon.ini is at [INSTALLDIR]\MpWalker.JM\mpcmtool\pmon\
REM #

REM ### End of mppmonsnd.bat ###################################

[UNIX]

mppmonsnd.sh

#!/bin/sh
###############################################################
# [Usage]
# mppmonsnd.sh $1 $2 $3 $4 $5 $6 $7 $8
#
# Parameters
# $1: Product Information(CMGR 1, OMGR 2)
# $2: Error Process Name
# $3: IP Address (My Host)
# $4: The Number of Destination Hosts
# $5: Destination Host1 (if directed at mppmon.ini)
# $6: Destination Host2 (if directed at mppmon.ini)
# $7: Destination Host3 (if directed at mppmon.ini)
# $8: Destination Host4 (if directed at mppmon.ini)
###############################################################

# Specify User Original Commands.
#
# If you want to execute this mppmonsnd.bat, you should edit
# mppmon.ini file. you should edit like "UserOriginal=ON" of
# [Notification] section. So, in case that some processes of
# Systemwalker are in trouble, this mppmonsnd.bat will be
# executed.
# mppmon.ini is at /opt/FJSVftlc[o]/pmon/
#

########### End of mppmonsnd.sh ################################