This section explains installation of Windows managers.
This section explains the preparations and checks required before commencing installation.
Post-uninstallation Procedure
Before installing Resource Orchestrator in an environment from which Resource Orchestrator has been deleted, perform the post-uninstallation procedure.
Refer to "20.1.5 Post-uninstallation Procedure".
Software preparation and checks are explained in the following sections.
This section explains the preparations and checks required before commencing the installation of Resource Orchestrator.
It is necessary to set the host name (FQDN) for the admin server to operate normally. Describe the host name in the hosts file, using 256 characters or less. In the hosts file, for the IP address of the admin server, configure the host name (FQDN) and then the computer name.
System_drive\Windows\System32\drivers\etc\hosts |
Note
When configuring the hosts file, note the following.
Do not set the host name (FQDN) and the computer name to "127.0.0.1".
Confirm that "127.0.0.1" (IPv4 format) is set to "localhost".
Note that IPv6 format must not be set.
Example
When configuring the admin server with the IP address "10.10.10.10", the host name (FQDN) "remote1.example.com", and the computer name "remote1"
10.10.10.10 remote1.example.com remote1 |
For the admin client, either configure the hosts file so access to the admin server is possible using the host name (FQDN), or name resolution using a DNS server.
System Time Checks
Set the same system time for the admin server and managed servers.
If the system time differs, correct values will not be displayed in the [System Condition] tab on the ROR console.
Exclusive Software Checks
Before installing Resource Orchestrator, check that the software listed in "2.4.2.5 Exclusive Software" in the "Design Guide CE" and the manager of Resource Orchestrator have not been installed on the system.
Use the following procedure to check that exclusive software has not been installed.
Open [Add or Remove Programs] on the Windows Control Panel.
The [Add or Remove Programs] window will be displayed.
Check that none of the software listed in "2.4.2.5 Exclusive Software" in the "Design Guide CE" or the following software are displayed.
"ServerView Resource Orchestrator Manager"
If the names of exclusive software have been displayed, uninstall them according to the procedure described in the relevant manual before proceeding.
If managers of an earlier version of Resource Orchestrator have been installed, they can be upgraded. Refer to "F.2 Manager".
When reinstalling a manager on a system on which the same version of Resource Orchestrator has been installed, perform uninstallation referring to "20.1 Manager Uninstallation", and then perform the reinstallation.
Information
For Windows Server 2008 or later, select [Programs and Features] from the Windows Control Panel.
Note
When uninstalling exclusive software, there are cases where other system operation administrators might have installed the software, so check that deleting the software causes no problems before actually doing so.
Required Software Preparation and Checks
Before installing Resource Orchestrator, check that the required software, such as ServerView Operations Manager, given in "2.4.2.4 Required Software" in the "Design Guide CE" has been installed. If it has not been installed, install it before continuing.
Microsoft LAN Manager Module
Before installing Resource Orchestrator, obtain the Microsoft LAN Manager module from the following FTP site.
The Microsoft LAN Manager module can be used regardless of the CPU architecture type (x86, x64).
URL: ftp://ftp.microsoft.com/bussys/clients/msclient/dsk3-1.exe |
Prepare for the following depending on the architecture of the installation target.
When installing a manager on Windows 32-bit (x86)
The Microsoft LAN Manager module can be installed without extracting it in advance.
Deploy the obtained module to the folder that has been set for environment_variable%SystemRoot%.
When installing a manager on Windows 64-bit (x64)
The obtained module must be extracted using the Expand command on a computer with x86 CPU architecture.
The obtained module is for x86 CPU architecture, and cannot be extracted on computers with x64 CPU architecture.
For details on how to extract the module, refer to the following examples:
Example
When dsk3-1.exe was deployed on c:\temp
>cd /d c:\temp <RETURN> |
Use the Windows 8.3 format (*) for the folder name or the file name.
After manager installation is complete, the extracted Microsoft LAN Manager module is no longer necessary.
* Note: File names are limited to 8 characters and extensions limited to 3 characters.
After extracting the following modules, deploy them to the folder that has been set for environment_variable%SystemRoot%.
PROTMAN.DOS
PROTMAN.EXE
NETBIND.COM
When installing Resource Orchestrator to an environment that already has ServerView Deployment Manager installed, it is not necessary to obtain the Microsoft LAN Manager module.
Changing Settings of ServerView Operations Manager
When installing ServerView Operations Manager 5.50 or an earlier version on the admin server, the ServerView Virtual-IO Manager service may not be able to be started. This can be handled by changing the settings of ServerView Operations Manager.
If ServerView Operations Manager 5.50 or later is used, this procedure is not necessary.
Before Installing Resource Orchestrator, please edit the following file of ServerView Operation Manager (hereinafter SVOM).
SVOM installation folder\ServerView Suite\jboss\bin\run.conf.bat |
Example
C:\Program Files (x86)\Fujitsu\ServerView Suite\jboss\bin\run.conf.bat
rem set "JAVA_HOME=C:\opt\jdk1.6.0_13" |
Uncomment this line, and set the proper path for the JRE 1.6.
Example
Before changing
rem set "JAVA_HOME=C:\opt\jdk1.6.0_13" |
After changing
set "JAVA_HOME=C:\Program Files (x86)\Java\jre6" |
If the editing procedure above is performed after installing the Resource Orchestrator manager, after that restart the SVOM services in the following order.
Stop the services:
ServerView Download Services
ServerView Services
ServerView JBoss Application Server 5.1
Start the services:
ServerView JBoss Application Server 5.1
ServerView Services
ServerView Download Services
SNMP Trap Service Settings
In order for Resource Orchestrator to operate correctly, the following settings for the standard Windows SNMP trap service are required.
Open [Services] from [Administrative Tools] on the Windows Control Panel, and then configure the startup type of SNMP Trap service as [Manual] or [Automatic] on the [Services] window.
Set the service status to "Started".
Settings for ServerView Virtual-IO Manager
When using VIOM, in order for Resource Orchestrator to operate correctly, ensure that the following settings are made when installing ServerView Virtual-IO Manager for Windows.
When using the I/O Virtualization Option
Clear the [Select address ranges for IO Virtualization] checkbox on the virtual I/O address range selection window.
When not using the I/O Virtualization Option
Check the [Select address ranges for IO Virtualization] checkbox on the virtual I/O address range selection window, and then select address ranges for the MAC address and the WWN address.
When there is another manager, select address ranges which do not conflict those of the other manager.
For details, refer to the ServerView Virtual-IO Manager for Windows manual.
DHCP server installation
Installation of the Windows standard DHCP Server is necessary when managed servers belonging to different subnets from the admin server are to be managed.
Depending on the functions used, it may necessary to configure the router settings. For details, refer to "9.2.4.2 Admin LAN Settings" in the "Design Guide CE".
When registering managed servers that belong to a different subnet from the admin server, they must be registered on the admin LAN subnet in advance.
For details, refer to "5.11 Registering Admin LAN Subnets" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Install the DHCP Server following the procedure below:
Add DHCP Server to the server roles.
Perform binding of the network connections for the NIC to use as the admin LAN.
For the details on adding and binding, refer to the manual for Windows.
Open [Services] from [Administrative Tools] on the Windows Control Panel, and then configure the startup type of DHCP Server service as [Manual] on the [Services] window.
From the [Services] window, stop the DHCP Server service.
When an admin server is a member of a domain, perform step 4.
Authorize DHCP servers.
Open [DHCP] from [Administrative Tools] on the Windows Control Panel, and select [Action]-[Managed authorized servers] on the [DHCP] window.
The [Manage Authorized Servers] window will be displayed.
Click <Authorize>.
The [Authorize DHCP Server] window will be displayed.
Enter the admin IP address of the admin server in [Name or IP address].
Click <OK>.
The [Confirm Authorization] window will be displayed.
Check the [Name] and [IP Address].
Click <OK>.
The server will be displayed in the [Authorized DHCP servers] of the [Manage Authorized Servers] window.
ETERNUS SF Storage Cruiser
When using ESC, configure the Fibre Channel switch settings in advance.
Stopping the BMC BladeLogic Server Automation service [Solaris Zones] [OVM for SPARC]
Stop the BladeLogic Application Server service in the Services window in Administrative Tools.
Required Patch Checks
Before installing Resource Orchestrator, check that the required patches for the manager listed in "2.4.2.2 Required Patches" in the "Design Guide CE" have been applied.
If they have not been applied, apply them before continuing.
User Account Checks
This product automatically creates the user accounts listed below - if an application is using these OS user accounts, ensure there is no impact on the application before deleting them:
rcxdb (for connecting to the database)
swrbadbuser (for starting up database services for process management)
swrbajobuser (for starting up services for job execution control)
Single Sign-On Preparation and Checks
Before installing Resource Orchestrator, install ServerView Operations Manager.
Configure the directory service at that time.
It is also necessary to prepare certificates and perform registration of an administrator (privileged user) with the directory service.
For details, refer to "Chapter 12 Installing and Defining Single Sign-On" in the "Design Guide CE".
For setting up Resource Orchestrator, it is necessary to establish communication beforehand, since communication between the manager and the directory service requires LDAP (Lightweight Directory Access Protocol) of the TCP/IP protocol protected by SSL.
Use tools or commands to check communications.
When the directory server is Microsoft Active Directory
Right-click the certificate issued by Certification Authority, and install it using the Certificate Import Wizard.
For details, refer to the Microsoft web site below.
How to enable LDAP over SSL with a third-party certification authority
URL: http://support.microsoft.com/kb/321051/en/ |
Language Settings
As Resource Orchestrator installs programs that correspond to the supported language, language settings (locale) cannot be changed after installation.
Therefore, set the language (locale) to Japanese or English according to your operational requirements.
The example of language settings (locale) confirmation methods is given below:
Example
From the Control Panel, open [Date, Time, Language, and Regional Options] and select [Regional and Language Options].
Before installing Resource Orchestrator, collect required information and check the system status, then determine the information to be specified on the installation window. The information that needs to be prepared is given below.
Installation Folder
Decide the installation folder for Resource Orchestrator.
Note that folders on removable disks cannot be specified.
Check that there are no files or folders in the installation folder.
Check that the necessary disk space can be secured on the drive for installation.
For the amount of disk space necessary for Resource Orchestrator, refer to "2.4.2.6 Static Disk Space" and "2.4.2.7 Dynamic Disk Space" in the "Design Guide CE".
Image File Storage Folder
The image file storage folder is located in the installation folder.
Check that sufficient disk space can be secured on the drive where the storage folder will be created.
For the necessary disk space, refer to "2.4.2.7 Dynamic Disk Space" in the "Design Guide CE".
For details of how to change the image file storage folder, refer to 5.9 rcxadm imagemgr" in the "Reference Guide (Command/XML) CE".
Port Number
For details on port numbers, refer to "2.1.1.5 Checking Used Port Numbers".
Directory Service Connection Information for Single Sign-On
Check the settings of the directory service used for Single Sign-On.
Refer to the following manual when the OpenDS that is included with ServerView Operations Manager is used.
"ServerView user management via an LDAP directory service" in the "ServerView Suite User Management in ServerView" manual of ServerView Operations Manager
ServerView Operations Manager V6.1 and later include OpenDJ as a directory service.
In the following descriptions, when "OpenDS" is used, replace it with "OpenDJ".
Parameters Used for Installation
The following table contains the parameters used for installation.
No. | Window | Entry | Description |
|---|---|---|---|
1 | Installation Folder Selection | Installation Folder | This is the folder where Resource Orchestrator is installed. (*)
The installation folder can contain 45 characters or less including the drive letter and "\". A path starting with "\\" or a relative path cannot be specified. Note When using 64 bit Windows Server OSs, the following folder names cannot be specified for the installation folders.
|
2 | Administrative User Creation | User Account | This is the user account name to be used for logging into Resource Orchestrator as an administrative user. Specify the user registered in the directory service in "Single Sign-On Preparation and Checks" in "2.1.1.2 Software Preparation and Checks". Specifying the administrator account, "administrator", of ServerView Operations Manager enables Single Sign-On coordination with ServerView Operations Manager when the OpenDS that is included with ServerView Operations Manager is used. The name must start with an alphabetic character and can be up to 16 alphanumeric characters long, including underscores ("_"), hyphens ("-"), and periods, ("."). Input is case-sensitive. |
3 | Admin LAN Selection | Network to use for the admin LAN | This is the network to be used as the admin LAN. Select it from the list. |
4 | Port Number Settings | Interstage Management Console | This is the port number of the Interstage management console. Default value: 12000 |
Web Server (Interstage HTTP Server) | This is the port number of the Web server. Default value: 80 | ||
CORBA Service | The port number of the CORBA service used by Resource Orchestrator. Default value: 8002 | ||
5 | Admin Server Settings | FQDN for the Admin Server | The FQDN of the authentication server used by Resource Orchestrator. The FQDN of the authentication server must be the FQDN of the admin server. |
* Note: Specify an NTFS disk.
Check configuration parameters following the procedure below:
Log in as the administrator.
Start the installer.
The installer is automatically displayed when the first DVD-ROM is set in the DVD drive. If it is not displayed, execute "RcSetup.exe" to start the installer.
Select "Tool" on the window displayed, and then click "Environment setup conditions check tool". Configuration parameter checking will start.
For ports with "is in use" displayed for the result of "Port status", confirm that those ports are used with the purpose of usage for Resource Orchestrator defined in C:\Windows\System32\drivers\etc\services.
For the port information used by Resource Orchestrator, refer to "Appendix A Port List" in the "Design Guide CE".
When ports being are used for something other than Resource Orchestrator, change the ports to use.
For details on how to change ports to use, refer to "Appendix A Port List" in the "Design Guide CE".
When configuration parameter checking is completed, the check results will be saved in the following location.
C:\temp\ror_precheckresult-YYYY-MM-DD-hhmmss.txt
Refer to the check results, and check that no error is contained. If any error is contained, remove the causes of the error.
The file containing the results of confirmation is not automatically deleted during installation. Please delete it when it is no longer necessary.
When Resource Orchestrator is installed, the port numbers used by it will automatically be set in the services file of the system. So usually, there is no need to pay attention to port numbers.
If the port numbers used by Resource Orchestrator are being used for other applications, a message indicating that the numbers are in use is displayed when the installer is started, and installation will stop.
In that case, describe the entries for the following port numbers used by Resource Orchestrator in the services file using numbers not used by other software, and then start the installer.
Example
# service name port number/protocol name nfdomain 23455/tcp nfagent 23458/tcp rcxmgr 23460/tcp rcxweb 23461/tcp rcxtask 23462/tcp rcxmongrel1 23463/tcp rcxmongrel2 23464/tcp rcxdb 23465/tcp rcxmongrel3 23466/tcp rcxmongrel4 23467/tcp rcxmongrel5 23468/tcp |
For details on how to change the port number of the manager, refer to the following:
"6.2 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE"
"8.3 Settings for Port Number of Admin Servers" in the "Operation Guide CE"
ephemeral Port
When the range of ephemeral port numbers on Windows is changed, the ephemeral port and the port to use conflict. In that case, select a port number which is not included in the range of the ephemeral port numbers.
The range of ephemeral port numbers is as below.
For Windows 2008 or later
49152 to 65535
Other Ports
Check that the following ports are not used, and they are not included in the range for ephemeral ports.
If the following ports are in use or are included in the range for ephemeral ports, contact Fujitsu technical staff.
7676
8686
12001
23600
23601
23602
23700
28080
The procedure for manager installation is given below.
Before installation, check if "2.1.1.1 Preparations" have been performed.
Precautions for Installation
When a terminal server has been installed, execute the following command using the command prompt to change the terminal service to installation mode.
CHANGE USER /INSTALL |
Nullifying Firewall Settings for Ports to be used by Resource Orchestrator
When installing Resource Orchestrator on systems with active firewalls, in order to enable correct communication between the manager, agents, and clients, disable the firewall settings for the port numbers to be used for communication.
For the port numbers used by Resource Orchestrator and required software, refer to "Appendix A Port List" in the "Design Guide CE".
However, when port numbers have been changed by editing the services file during installation of Resource Orchestrator, replace the default port numbers listed in "Appendix A Port List" in the "Design Guide CE" with the port numbers changed to during installation.
Installation
The procedure for manager installation is given below.
Log on as the administrator.
Log on to the system on which the manager is to be installed.
Log on using the Administrator account of the local computer.
Start the installer.
The installer is automatically displayed when the first DVD-ROM is set in the DVD drive. If it is not displayed, execute "RcSetup.exe" to start the installer.
Click [Manager(Cloud Edition) installation].
Following the installation wizard, enter the parameters prepared and confirmed in "Parameters Used for Installation" properly.
Upon request of the wizard for DVD-ROM switching, set the second DVD-ROM and the third DVD-ROM to continue the installation.
Point
[Solaris Zones] [OVM for SPARC]
When BMC BladeLogic Server Automation is installed on the admin server and BMC BladeLogic Server Automation is installed after this product was installed, perform the following procedure:
Stop the Interstage data store service in the Services window in Administrative Tools.
Change the startup type from Automatic to Disabled.
It is necessary to set up the manager after installation. For details, refer to "2.1.3 Setup".
Note
Advisory Notes for Changing the Installation Folder
Enter the location using 45 characters or less.
When using 64 bit Windows Server OSs, the following folder names cannot be specified for the installation folders.
"Program Files" Folder
In the event of installation failure, restart and then log in as the user that performed the installation, and perform uninstallation following the uninstallation procedure.
After that, remove the cause of the failure referring to the meaning of the output message and the suggested corrective actions, and then perform installation again.
If there are internal inconsistencies detected during installation, the messages "The problem occurred while installing it" or "Native Installer Failure" will be displayed and installation will fail. In this case, uninstall the manager and reinstall it. If the problem persists, please contact Fujitsu technical staff.
For uninstallation of managers, refer to "20.1.3 Uninstallation [Windows Manager]".
If rolling back to the previous status before an installation failure has not finished, the message "System has some on incomplete install information. Please delete before this installation" will be displayed and installation will fail. Uninstall the manager and reinstall it. For uninstallation of managers, refer to "20.1.3 Uninstallation [Windows Manager]". If the problem persists even if reinstallation is performed, please collect troubleshooting information and contact Fujitsu technical staff.
If used ports exist when performing installation, the message "The specified port number Port Number selected for ServerView Resource Orchestrator is already used." will be displayed, and installation will fail. If this happens, please contact Fujitsu technical staff.
The following files are created under the system drive after installation.
F4ANsetup.log
swinst.err
swrba_inst.log
These files are the material for investigation of installation failure.
Post-installation Cautions
When a terminal server has been installed, execute the following command using the command prompt to change the terminal service to the execution mode.
When continuously setting up after installation, this step is not necessary.
CHANGE USER /EXECUTE |
The following users are added.
swrbadbuser
swrbadbuser is used as an OS account to start the database service for process management. Do not delete this account when Resource Orchestrator has been installed.
swrbajobuser
swrbajobuser is used as an OS account to start service for job execute control.
Do not delete this account when Resource Orchestrator has been installed.
