This section provides important notes to take into account before installation.
Product to install
If applications have been created using the 32-bit API for Systemwalker Operation Manager, use the 32-bit version of Systemwalker Operation Manager, even if Systemwalker Operation Manager is being used in a 64-bit environment.
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
Systemwalker Service Quality Coordinator Operation Management Client V13.4.0 or later (*)
*: If the Systemwalker Single Sign-On function is installed.
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.
If SMEE or SCLR library packages already exist [Linux/Solaris]
If the following package, which is an earlier version than this product, has already been installed on the computer where Systemwalker Operation Manager will be installed, uninstall the earlier version of the appropriate package before installing Systemwalker Operation Manager.
[Solaris]
FJSVsmee (for Solaris 32-bit version or Solaris 64-bit version)
FJSVsclr (for Solaris 32-bit version or Solaris 64-bit version)
FJSVsme64 (for Solaris 64-bit version)
FJSVscl64 (for Solaris 64-bit version)
[Linux]
FJSVsmee (for Linux x86 version)
FJSVsclr (for Linux x86 version)
FJSVsmee64 (for Linux x64 version)
FJSVsclr64 (for Linux x64 version)
Refer to the Release Note for information on the version of the above packages included with this product.
Defining port numbers
During installation, the following port number will be added to /etc/services automatically.
Function name | Service name | Port number |
|---|---|---|
Security | mpaclmgr | 4013/tcp |
If the port number is already in use, it will not be added. The system administrator must check the port numbers used by Systemwalker Operation Manager against the "Appendix C Listing of Port Numbers", change any that are already in use to a port number not used on any server, and then add those port numbers to the file "/etc/services".
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 function" in "2.2.2 Changing Port Numbers", and set up the Web server again.
Refer to "2.2.2 Changing Port Numbers" for details on how to change the port number.
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.
Setting of /etc/hosts (For Linux/Solaris)
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 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 of Solaris 10 or later
When installing Systemwalker Operation Manager in the Non-Global Zone of Solaris 10 or later system, 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
Installation in Solaris 11
The following packages must have been installed before you install Systemwalker Operation Manager in Solaris 11:
system/locale
system/locale/extra
package/svr4
system/library/iconv/extra
system/library/iconv/unicode