Be aware of the following when installing Systemwalker Operation Manager.
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
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 "<system directory>\system32\drivers\etc\services" according to a function to use.
If the port number has already been used, add a different port number 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
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.
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.
The user restriction definitions will be inherited after the upgrade installation as well.
Installing the Redistributable package
When Systemwalker Operation Manager is installed, the following Redistributable package will be installed automatically if it has not already been installed on the system.
Installation type: Server
Microsoft Visual C++ 2015-2019 Redistributable
Installation type: Client
Microsoft Visual C++ 2015 Redistributable
However, if a package newer than Redistributable package has already been installed, the Redistributable package will not be installed.
Note that the 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 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.
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.x Features or .NET Framework 4.x Features to add the feature. This operation is not required if one of the checkboxes has already been selected.
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.8 Advanced Services. This operation is not required if one of the checkboxes 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
When using a redistributable package, follow the terms of use in the download site of the Microsoft .NET Framework Redistributable package.
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.
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.
