1.3.1 Notes Prior to Installation

Be aware of the following when installing Systemwalker Operation Manager.

Product to install

If applications have been created using the 32-bit API for Systemwalker Operation Manager, use the Windows x86 version of Systemwalker Operation Manager, even if Systemwalker Operation Manager is being used in a Windows x64 environment.

Shutdown of services and jobs

All of Systemwalker Operation Manager services are stopped automatically when the system is installed. If it coexists with Systemwalker Centric Manager in the same environment, the Systemwalker Centric Manager services are also stopped. Ensure that none of Systemwalker Operation Manager jobs are running before system installation. Then, start Systemwalker upgrade installation or reinstallation.

However, those services may fail to stop or those services are not stopped. If this happens, cancel the current installation and stop services manually before starting to install again.

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.

Port numbers

During installation, the following port numbers will be added to system directory\system32\drivers\etc\services automatically. However, port numbers that are already in use will not be added.

Function name	Service name	Port number
Operation Manager common services	JMSRV	9367/tcp
Calendar service and application startup	JMCAL	9368/tcp
Jobscheduler	jobsch_win	9297/tcp
Event Monitoring	JMEVT1	9371/tcp
Action Control	JMACT1	9369/tcp
	JMACT2	9370/tcp
	JMACT3	6961/tcp
Security	mpaclmgr	4013/tcp
Remote Power Control	JMPWR	9373/tcp
Web Console	mpahso	9900/tcp
	mpojeed1httpo	9901/tcp
	mpojeed1httpso	9902/tcp
	mpojeed1admino	9903/tcp
	mpojeed1jmso	9904/tcp
	mpojeed1iiopo	9905/tcp
	mpojeed1iiopsmo	9906/tcp
	mpojeed1iiopso	9907/tcp
	mpojeed1jmxo	9908/tcp
	mpahso	9900/tcp

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 "system directory\system32\drivers\etc\services".

Web Console 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 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.

Installing upgrades

Before installing the upgrade, stop any Systemwalker Operation Manager clients, Systemwalker Operation Manager Environment Setup clients, Master Schedule Management Environment Setup clients, Multi-server Monitoring clients, Jobscheduler Info Printout clients, Master Schedule Management monitor clients or Task Link clients that may be running.
If any of those clients are active, you may fail to install the upgrades.
If an update pack has been applied to a server or client, that update pack must be removed before any upgrade can be installed. Refer to the update pack user guide (README.TXT) provided with the relevant update pack for the removal procedure.
If V13.3.0 or later UNIX client has been installed, upgrade installation to Windows x86 cannot be performed. Uninstall the client before installing the Windows x86 client.

Installing the "Microsoft Visual C++ 2005 Redistributable" package

When Systemwalker Operation Manager is installed, the Microsoft Visual C++ 2005 Redistributable package will be installed automatically if it has not already been installed on the system. Note that the "Microsoft Visual C++ 2005 Redistributable" package is required to operate Systemwalker Operation Manager, and therefore should not be uninstalled if Systemwalker Operation Manager is already installed. If uninstalled, the "Microsoft Visual C++ 2005 Redistributable" package must be manually installed.

Installing and uninstalling the .NET Framework

One of the following versions of .NET Framework is required for installing, using, or uninstalling the Operation Manager client function:

.NET Framework 2.0
.NET Framework 3.x
.NET Framework 4.x

Since the .NET Framework is available as part of operating system functions, use one of the following procedures to install the .NET Framework before installing the Operation Manager client function.

Windows Server 2012:: Select Control Panel >> Programs and Features >> Turn Windows features on or off. In the Add Roles and Features Wizard of the Server Manager window that is displayed, select the server where Systemwalker Operation Manager is installed from Server Selection of the menu, and then select Features. From the feature list displayed, select .NET Framework 3.5 Features or .NET Framework 4.5 Features to add the feature. This operation is not required if one of the checkboxes has already been selected.

Windows Server(R) 2008 R2:: Select Control Panel >> Programs and Features >> Turn Windows features on or off. In the Server Manager window that is displayed, select Features >> Add Feature, and then select .Net Framework 3.5.1 under .Net Framework 3.5.1 Features in the Add Features Wizard, and click the Install button to install the .NET Framework.

Windows Server 2008 (including the x64 Edition):: Select Control Panel >> Programs and Features >> Turn Windows features on or off. In the Server Manager window that is displayed, select Features >> Add Feature, and then select .Net Framework 3.0 under .Net Framework 3.0 Features in the Add Features Wizard, and click the Install button to install the .NET Framework.

Windows(R) 8 or later:: Select Control Panel >> Programs >> Programs and Features >> Turn Windows features on or off. In the Windows Features window that is displayed, select .NET Framework 3.5 (includes .NET 2.0 and 3.0) or .NET Framework 4.5 (Advanced Services). This operation is not required if one of the checkboxes has already been selected.

Windows(R) 7:: Select Control Panel >> Programs >> Programs and Features >> Turn Windows features on or off. In the Windows Features window that is displayed, select Microsoft .NET Framework 3.5.1 and then click the OK button to install the .NET Framework. This operation is not required if the checkbox has already been selected.

Windows Vista(R):: Select Control Panel >> Programs >> Programs and Features >> Turn Windows features on or off. In the Windows Features window that is displayed, select Microsoft .NET Framework 3.0 and then click the OK button to install the .NET Framework. This operation is not required if the checkbox has already been selected.

To uninstall .NET Framework, use the same window as was displayed during installation and perform the uninstallation (function deletion) process.

Refer to "Uninstalling the Operation Manager client function and the .NET Framework" in "1.6.3 Systemwalker Uninstallation from the Windows System" for notes on uninstalling the Operation Manager client function and the .NET Framework.

Note

Notes on installing and uninstalling the .NET Framework

For the above procedures, it is assumed that you have agreed to the Microsoft .NET Framework 2.0 Redistributable EULA, which can be found at the following link:
http://msdn.microsoft.com/ja-jp/library/cc825662.aspx

If you mistakenly installed the .NET Framework after the Operation Manager client function was installed, you will need to manually specify the settings that are normally entered automatically when the client function is installed.

In this case, after the .NET Framework has been installed, execute the following command from the command prompt with administrator privileges:

<Windows directory>\Microsoft.NET\Framework\v2.0.50727\regasm.exe <Operation Manager installation directory>\mpwalker.jm\bin\Fujitsu.OPMGR.Forms.Interop.dll /tlb<Operation Manager installation directory>\mpwalker.jm\bin\com.Fujitsu.OPMGR.Forms.Interop.tlb

If you mistakenly uninstalled the .NET Framework despite using the Operation Manager client function, you will need to reinstall the .NET Framework in order to use the Operation Manager client function.
.NET Framework 2.0 is installed automatically when either .NET Framework 3.0 or .NET Framework 3.5.1 is installed.
To check if .NET Framework 2.0 is included with more recent versions than .NET Framework 3.5.1, refer to the Microsoft Corporation website.

Specifying a directory containing a space as the installation directory

If Systemwalker Operation Manager is installed in the directory that contains a space, such as "C:\Program Files", short file name creation (in 8.3 format) must be enabled in the operating system settings beforehand. It is not possible to install Systemwalker Operation Manager in the directory that contains a space if short names are disabled.
If Systemwalker Operation Manager is to coexist with Systemwalker Centric Manager, only the following can be specified as the installation directory that contains a space:
- C:\Program Files
Specify the NTFS format disk for the installation directory.