2.4.2 Starting and terminating the Operations-Manager Agent

(1) Starting the Operations-Manager Agent

To start the Operations-Manager Agent:

1. As a superuser, execute the ftsastart command.

   For details about the ftsastart command, see ftsastart - starts the Operations-Manager Agent in 6. Commands.

Notes

• This command returns control immediately after it has moved the Operations-Manager Agent to the background. The Operations-Manager Agent then displays the start message once its services are ready. Therefore, the interval between when the command returns control and when the message is output varies.

• In RHEL 7, CentOS 7, Oracle Linux 7, SUSE Linux 12, SUSE Linux 15, if you do not set up Operations-Manager Agent to start automatically, you cannot start it by using the ftsastart command either.

Automatic startup method (in HP-UX, Solaris, RHEL 6, CentOS 6, and Oracle Linux 6)

There are two ways to have the Operations-Manager Agent start automatically during system startup, as described below. When either of these settings is specified, it takes effect the next time the system is started.

• Use a program (such as a text editor) to open /etc/opt/jp1_fts/startup, delete the comment (:#), and then save the file.

• Replace /etc/opt/jp1_fts/startup with a shell that has been customized using /etc/opt/jp1_fts/startup.model.

Automatic startup method (in RHEL 7, CentOS 7, Oracle Linux 7, SUSE Linux 12, and SUSE Linux 15)

To have the Operations-Manager Agent start automatically during system startup, you must specify the settings described below. These settings take effect the next time the system is started.

1. Creating the start command

If you want to customize the startup procedure, for example, to add environment variable settings, replace /etc/opt/jp1_fts/jp1ftpa.startup with a shell that has been customized by using /etc/opt/jp1_fts/jp1ftpa.startup.model.

If you do not make any changes, this replacement is not necessary.

2. Specifying the automatic startup setting

Use the systemctl command to enable the service.

# systemctl enable jp1_ftpa.service

Do not directly execute /etc/opt/jp1_fts/jp1ftpa.startup. If you directly execute it, the OS cannot correctly recognize the state of the service, and the Operations-Manager Agent might not stop automatically when the OS stops. In addition, a problem might occur the next time the Operations-Manager Agent starts, or after the Operations-Manager Agent starts.

Automatic startup method (in AIX)

To have the Operations-Manager Agent start automatically during system startup, you must specify the settings described below. These settings take effect the next time the system is started.

1. Creating the start command

Create the start command using either of the following methods:

• Use a program (such as a text editor) to open /etc/opt/jp1_fts/startup, delete the comment (:#), and then save the file.

• Replace /etc/opt/jp1_fts/startup with a shell that has been customized using /etc/opt/jp1_fts/startup.model.

2. Specifying the automatic startup setting

Use the mkitab command to specify the automatic startup setting:

# mkitab "jp1_fts:2:wait:/etc/opt/jp1_fts/startup"

If you use JP1-series products, you must first set JP1/Base and then set the other JP1-series products sequentially so that the automatic startup sequence is set correctly. If you use JP1/IM and JP1/AJS3, register the JP1/FTP start command after them.

For example, to have JP1/Base, JP1/IM, JP1/AJS3, and JP1/FTP start automatically in this order, execute the following commands:

# mkitab -i hntr2mon "jp1base:2:wait:/etc/opt/jp1base/jbs_start"
# mkitab -i jp1base "jp1cons:2:wait:/etc/opt/jp1cons/jco_start"
# mkitab -i jp1cons "jp1ajs2:2:wait:/etc/opt/jp1ajs2/jajs_start"
# mkitab -i jp1ajs2 "jp1_fts:2:wait:/etc/opt/jp1_fts/startup"

After you have specified the settings, use the lsitab command to check the settings.

Execute the following command:

# lsitab -a

Example of output

init:2:initdefault:
brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 # Phase 3 of system boot
            :
hntr2mon:2:once:/opt/hitachi/HNTRLib2/etc/D002start
jp1base:2:wait:/etc/opt/jp1base/jbs_start
jp1cons:2:wait:/etc/opt/jp1cons/jco_start
jp1ajs2:2:wait:/etc/opt/jp1ajs2/jajs_start
jp1_fts:2:wait:/etc/opt/jp1_fts/startup

To Page Top

(2) Terminating the Operations-Manager Agent

1. As a superuser, execute the ftsastop command.

   For details about the ftsastop command, see ftsastop - terminates the Operations-Manager Agent in 6. Commands.

Automatic termination method (in HP-UX, Solaris, RHEL 6, CentOS 6, and Oracle Linux 6)

Once it has been installed, the Operations-Manager Agent is set to terminate automatically during system termination. If you want to customize the termination procedure, replace /etc/opt/jp1_fts/stop with a shell that has been created using /etc/opt/jp1_fts/stop.model.

Automatic termination method (in RHEL 7, CentOS 7, Oracle Linux 7, SUSE Linux 12, and SUSE Linux 15)

Once it has been installed, the Operations-Manager Agent is set to terminate automatically during system termination. If you want to customize the termination procedure, replace /etc/opt/jp1_fts/jp1ftpa.stop with a shell that has been created using /etc/opt/jp1_fts/jp1ftpa.stop.model. You cannot change the settings so that the Operations-Manager Agent does not stop automatically. If you do change the settings so that the Operations-Manager Agent does not stop automatically, the Operations-Manager Agent cannot be stopped by using the ftsastop command either.

Do not directly execute /etc/opt/jp1_fts/jp1ftpa.stop. If you directly execute it, the OS cannot correctly recognize the state of the service.

Automatic termination method (in AIX)

To have the Operations-Manager Agent terminate automatically during system termination, add the following settings to /etc/rc.shutdown. If these settings have already been added for automatic termination of the JP1/FTP daemon, there is no need to add them again.

Example

if [ -x /etc/opt/jp1_fts/stop ]
then
    /etc/opt/jp1_fts/stop
fi

If there is no /etc/rc.shutdown file, you must create it. In such a case, set the attributes of the /etc/rc.shutdown file as follows:

chmod 550 /etc/rc.shutdown
chown root /etc/rc.shutdown
chgrp shutdown /etc/rc.shutdown

If you use JP1-series products, you must set this termination processing so that it executes before the termination processing for JP1/Base and JP1/AJS3.

If you want to terminate programs in a different manner from what is shown above, replace /etc/opt/jp1_fts/stop with a shell that has been created using /etc/opt/jp1_fts/stop.model.

To Page Top