Applicable versions and levels
Linux version: V17.0.0 or later (Red Hat Enterprise Linux 7 or later)
A
You can only set dependencies.
Use the Extending function of the Unit Configuration (*.conf file) of the OS to set dependencies for the following service unit when you customize.
startswOperation.service
For details on how to use the Extending function of the Unit Configuration, refer to the OS documentation.
Do not edit the systemd service unit file (see below) registered by Systemwalker Operation Manager in the /usr/lib/systemd/system/ directory.
Information
Systemwalker Operation Manager registers the following service unit files with systemd.
startswOperation.service
stopswOperation.service
mpfwsec.service
mpipcmgro.service
JMCAL.service (Note 1)
FJSVfwsec.service
FJSVJMCMN.service
FJSVjmcal.service
FJSVMJS.service
FJSVMJS@.service (Note 2)
FJSVJOBSC.service
FJSVJOBSC@.service (Note 2)
FJSVpmono.service
FJSVpcmiisje6-STFJMJAVAEE_start.service (Note 3)
FJSVpcmiisje6-STFJMJAVAEE_stop.service (Note 3)
Note 1) Only when the automatic reflection function is enabled in a cluster system.
Note 2) Only when operating multiple subsystems
Note 3) Only when setting up the web console
Notes
Note the following about the configuration file (*.conf file) that is added by the Extending function of the Unit Configuration.
Configuration files are not applicable for backup/restore or backup/restore of migrated assets. To restore the environment from backup data or to restore the migrated assets, make the same setting again.
The configuration file is not removed during uninstall. Delete them manually if necessary.
The operation of the target service units may become abnormal due to the contents of the configuration file. Confirm the operation before setting.
