Systemwalker Operation Manager Q & A Guide

1.10 Q: How do I prevent the Systemwalker Operation Manager daemon from starting automatically when the server starts?

Applicable versions and levels

• Solaris versions: V17.0.0 or later

• Linux versions: V17.0.1 or later

A

You can prevent the daemons for the Systemwalker Operation Manager functions from starting when the server starts.

How to deter automatic startup

1. Become a superuser.

2. Stop the Systemwalker Operation Manager.
   Execute the following command.

   /opt/systemwalker/bin/poperationmgr

3. Set deterrence of automatic start of the daemon.

   [Solaris versions]

   Rename the following shell script files (change the leading uppercase "S" to lowercase "s").

   File name before change	File name after change	Remark
   /etc/rc2.d/S90mpfwsec	/etc/rc2.d/s90mpfwsec
   /etc/rc3.d/S99startswOperation	/etc/rc3.d/s99startswOperation
   /etc/rc3.d/S28JMCAL	/etc/rc3.d/s28JMCAL	Note

   Note) Only when the automatic reflection function is enabled in a cluster system.

   [Linux versions]

   • Red Hat Enterprise Linux 6 or later

     Rename the following shell script files (change the leading uppercase "S" to lowercase "s").

     File name before change	File name after change	Remark
     /etc/rc2.d/S90mpfwsec	/etc/rc2.d/s90mpfwsec
     /etc/rc2.d/S99startswOperation	/etc/rc2.d/s99startswOperation
     /etc/rc3.d/S90mpfwsec	/etc/rc3.d/s90mpfwsec
     /etc/rc3.d/S99startswOperation	/etc/rc3.d/s99startswOperation
     /etc/rc3.d/S28JMCAL	/etc/rc3.d/s28JMCAL	Note
     /etc/rc5.d/S90mpfwsec	/etc/rc5.d/s90mpfwsec
     /etc/rc5.d/S99startswOperation	/etc/rc5.d/s99startswOperation

     Note) Only when the automatic reflection function is enabled in a cluster system.

   • Red Hat Enterprise Linux 7 or later

     Execute the following command to disable automatic startup from systemd.

     systemctl disable mpfwsec.service

     systemctl disable startswOperation.service

     systemctl disable JMCAL.service (Note)

     Note) Only when the automatic reflection function is enabled in a cluster system.

The daemon for each function of Systemwalker Operation Manager is prevented from starting the next time the server starts.

Note

• For environments that coexist with Systemwalker Centric Manager, use this procedure to deter startup only if you also want to deter startup of Systemwalker Centric Manager.

• When using a cluster, you must also deter the start of the job scheduler daemon and job execution control daemon from the cluster when the OS starts.

• If you uninstall Systemwalker Operation Manager, the files renamed above are not deleted. Therefore, delete them manually.

Information

Differences from the command for deterring startup of the "swstop" service/daemon

If automatic startup is deterred by the swstop command, you cannot use the soperationmgr command to start all daemons at once.

If you want to start the daemons in a batch by using the soperationmgr command after you have detered the start of the daemons, use the method in this section to deter the automatic start.

How to release deterrence of automatic startup

The following describes how to disable suppression of automatic start of daemons by "How to deter automatic startup".

1. Become a superuser.

2. Stop the Systemwalker Operation Manager.
   Execute the following command.

   /opt/systemwalker/bin/poperationmgr

3. Specify the settings for releasing suppression of automatic start of daemons.

   [Solaris versions]

   Rename the following shell script files (change the leading uppercase "S" to lowercase "s").

   File name before change	File name after change	Remark
   /etc/rc2.d/s90mpfwsec	/etc/rc2.d/S90mpfwsec
   /etc/rc3.d/s99startswOperation	/etc/rc3.d/S99startswOperation
   /etc/rc3.d/s28JMCAL	/etc/rc3.d/S28JMCAL	Note

   Note) Only when the automatic reflection function is enabled in a cluster system.

   [Linux versions]

   • Red Hat Enterprise Linux 6 or earlier

     Rename the following shell script files (change the leading uppercase "S" to lowercase "s").

     File name before change	File name after change	Remark
     /etc/rc2.d/s90mpfwsec	/etc/rc2.d/S90mpfwsec
     /etc/rc2.d/s99startswOperation	/etc/rc2.d/S99startswOperation
     /etc/rc3.d/s90mpfwsec	/etc/rc3.d/S90mpfwsec
     /etc/rc3.d/s99startswOperation	/etc/rc3.d/S99startswOperation
     /etc/rc3.d/s28JMCAL	/etc/rc3.d/S28JMCAL	Note
     /etc/rc5.d/s90mpfwsec	/etc/rc5.d/S90mpfwsec
     /etc/rc5.d/s99startswOperation	/etc/rc5.d/S99startswOperation

     Note) Only when the automatic reflection function is enabled in a cluster system.

   • Red Hat Enterprise Linux 7 or later

     Execute the following command.

     systemctl enable JMCAL.service (Note)

     systemctl enable startswOperation.service

     systemctl enable mpfwsec.service

     Note) Only when the automatic reflection function is enabled in a cluster system.

How to start daemon

Start the daemon of Systemwalker Operation Manager that was suppressed by "How to deter automatic startup" by following the procedure below.

1. Become a superuser.

2. Start the daemons for the Systemwalker Operation Manager functions.
   Execute the following command.

   /opt/systemwalker/bin/soperationmgr