This section provides important notes to take into account before installation.
Stopping daemons
All of Systemwalker Operation Manager daemons are stopped automatically when the system is installed. If it coexists with Systemwalker Centric Manager in the same environment, the Systemwalker Centric Manager daemons are also stopped automatically.
Stopping Systemwalker products
Stop the following Systemwalker product before starting the installation.
Systemwalker Operation Manager V13.8.0 or later
Systemwalker Centric Manager V13.4.0 or later
Refer to the manual of each product for how to stop the product.
Note that the Web server used by each product must also be stopped.
Port numbers
Refer to "Appendix C Listing of Port Numbers" for information on the port numbers used by Systemwalker Operation Manager. Add a port number to /etc/services according to a function to use. If the port number has already been used, add a different port that has not been used on any servers.
Note that some port numbers are added automatically to the services file when Systemwalker Operation Manager is installed. If the applicable port number has already been written, it will not be added.
Refer to "2.2.2 Changing Port Numbers" for information on how to change the port number.
Note
Web Console and Web API port numbers
If the port used by the Web server is already being used elsewhere on the system where the product will be installed, the following message is displayed during installation:
Web server setup failed. |
If this message is output, follow the procedure outlined in the Systemwalker Operation Manager Message Guide or "Changing the port number of the Web Console /Web API function" in "2.2.2 Changing Port Numbers", and set up the Web server again.
Upgrade installations
If a cumulative patch for PC clients has been applied to a client in the Solaris version, that patch must be removed before any upgrade can be installed. Refer to the PC client cumulative patch application procedure guide (README.TXT) provided with the relevant patch for the removal procedure.
The user restriction definitions will be inherited after the upgrade installation as well.
Setting of /etc/hosts (For Solaris/Linux)
In the Red Hat Linux and Solaris 11 or later systems, 127.0.0.1 is set as an IP address for the local host name in the /etc/hosts field by default. This can lead to the following issues:
If the Systemwalker Operation Manager server is installed on this server, the server setup may fail.
If you connect a Systemwalker Operation Manager client or Multi-server Monitoring clients to the server under this condition, it may not be monitored correctly.
If a network job is executed for another server from this server, it will take longer than expected to execute network jobs.
If a network job is executed for another server from this server, the network job may end abnormally.
Therefore, the IP address for the host name of localhost configured in the /etc/hosts file during installation must be an address that can be connected from the client and from the execution server.
An example of /etc/hosts file settings is shown below:
[Before]
127.0.0.1 <host name> localhost[After]
127.0.0.1 localhost
xxx.xxx.xxx.xxx <host name>Note: xxx.xxx.xxx.xxx is the IP address for <host name> (localhost).Installation in Non-Global Zone[Solaris]
When installing Systemwalker Operation Manager in the Non-Global Zone, take the following notes.
One or more logical network interfaces must be assigned from the Global Zone.
The "Directory Inheritance" of the Zone function cannot be used in the Systemwalker installation directory and in the following directories:
All directories locating under /opt
All directories locating under /etc
All directories locating under /var
All directories locating under /usr
The Systemwalker installation directory and the following directories cannot be shared by another Zone.
/opt
/etc
/var
/usr
User restriction definitions for new installation
When a new installation is performed, the user restriction definition is enabled (*1).
*1: The option Restrict so that only users included in the swadmin group can start demand jobs, start jobnet Job execution control attributes or use Jobscheduler command functions. in the Define Operation Manager Shared Parameter window is selected.
Users need to be registered to the swadmin group to submit a demand job, start a job net with the Job Execution Control attribute, and run Jobscheduler commands.
This setting can be changed after the installation.
Refer to "2.4.5 Define User Restrictions" for information on the user restriction definitions.