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 "11.1.4 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.
Host Name Checks
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.
hosts File
System_drive\Windows\System32\drivers\etc\hostsNote
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 127.0.0.1 localhost.localdomain localhost
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.
This configuration is necessary when Single Sign-On is configured.
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
Uninstall exclusive software before installing Resource Orchestrator.
For details of exclusive software, refer to "6.1.2.5 Exclusive Software" in "Overview".
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, perform the following operations.
In addition, check that the required software, such as ServerView Operations Manager, given in "6.1.2.4 Required Software" in the "Overview" has been installed. If it has not been installed, install it before continuing.
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.
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 are 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
ServerView Operations Manager Settings
In order to open the console screen of the managed server, register the account of the Remote Management Controller with the ServerView Operations Manager.
For the setting method, refer to the ServerView Operations Manager manual.
Required settings for versions earlier than ServerView Operations Manager 5.50
When installing a version earlier than ServerView Operations Manager 5.50 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, edit the following file of ServerView Operations 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:
a. ServerView Download Services
b. ServerView Services
c. ServerView JBoss Application Server 5.1
Start the services:
a. ServerView JBoss Application Server 5.1
b. ServerView Services
c. 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 be 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 Windows documentation.
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 the [Authorize] button.
The [Authorize DHCP Server] window will be displayed.
Enter the admin IP address of the admin server in [Name or IP address].
Click the [OK] button.
The [Confirm Authorization] window will be displayed.
Check the [Name] and [IP Address].
Click the [OK] button.
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.
Required Patch Checks
Before installing Resource Orchestrator, check that the required patches for the manager listed in "6.1.2.2 Required Patches" in the "Overview" 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)
rcxctdbbpm (for starting up database services for process management)
rcxctdbchg (for starting up database services for metering)
rcxctdbdsb (for starting up database services for the dashboard (pool status))
Single Sign-On Preparation and Checks (when used)
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 Configuring Single Sign-On" in the "Design Guide CE".
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 "6.1.2.6 Static Disk Space" and "6.1.2.7 Dynamic Disk Space" in the "Overview".
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 "6.1.2.7 Dynamic Disk Space" in the "Overview".
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.4 Checking Used Port Numbers".
Directory Service Connection Information for Single Sign-On of ServerView Operations Manager
Confirm that the directory service used for Single Sign-On of ServerView Operations Manager is correctly configured.
This can be performed using either of the following procedures:
Log in to ServerView Operations Manager.
Refer to the following manuals:
Manual for ServerView Operations Manager:
"ServerView user management via an LDAP directory service" in "FUJITSU ServerView Suite User Management in ServerView"
Manual for ServerView Operations Manager:
"Starting ServerView Operations Manager" in "FUJITSU Software ServerView Suite ServerView Operations Manager" (User's guide)
Perform modification installation of ServerView Operations Manager.
When performing modification installation, the settings of directory service can be checked.
Refer to the following manuals:
Manual for ServerView Operations Manager:
"ServerView user management via an LDAP directory service" in "FUJITSU ServerView Suite User Management in ServerView"
Manual for ServerView Operations Manager:
"Modify installation of Operations Manager software" in "FUJITSU Software ServerView Suite ServerView Operations Manager Installing ServerView Operations Manager Software under Windows"
If the settings of the directory service for ServerView Operations Manager are correct, exit the modification installation without making any changes.
If there are errors in the settings of the directory service for ServerView Operations, perform modification installation of ServerView Operations Manager to correct the errors.
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. Default value: System_drive\Program Files (x86)\Resource Orchestrator The installation folder can contain 45 characters or less including the drive letter and "\".
The following folder and its subfolders cannot be specified for the installation folder.
Specify an NTFS disk. |
2 | 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. |
3 | Authentication Method Selection | Authentication Method | Select one of the following options.
|
4 | Administrative User Creation | User Account | This is the user account name to be used for logging into Resource Orchestrator as an administrative user. The name must start with an alphanumeric character and can be up to 16 alphanumeric characters long, including underscores ("_"), hyphens ("-"), and periods, ("."). Input is case-sensitive. |
Password | The password of the administrative user. The string must be composed of alphanumeric characters and the following symbols (excluding blank spaces), and can be 8 - 16 characters long. "!", """, "%", "&", ",", "<", ">", "^", "|" If any of the above symbols are specified, change the password of the privileged user after setup is complete. | ||
Retype password | |||
Administrative User Settings | 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 (when used)" in "2.1.1.2 Software Preparation and Checks". When using the directory service provided with ServerView Operations Manager, specifying "administrator", which is the administrator account of ServerView Operations Manager, enables Single Sign-On coordination with ServerView Operations Manager. The name must start with an alphanumeric character and can be up to 16 alphanumeric characters long, including underscores ("_"), hyphens ("-"), and periods, ("."). Input is case-sensitive. | |
5 | Language Settings | Language | Select one of the following options.
|
Ports Automatically Set in the services File of the System
When Resource Orchestrator is installed, the following port numbers used by it will automatically be set in the services file of the system.
If the following 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.
# service name port number/protocol name RCXCTDSB_sqcdcm_dbm 2511/tcp RCXCTDSB_sqcdcm_fcmsys 2512/tcp rcxctext 3500/tcp rcxctext2 3501/tcp rcxctdsb 3502/tcp rcxctrestchg 3550/tcp rcxctint 3551/tcp rcxctdbchg 5441/tcp rcxctdbdsb 5442/tcp rcxcfvsys 8013/tcp rcxcfapi 8014/tcp rcxctacnt 8015/tcp RCXCTDSB_CMDB_GUI 13200/tcp RCXCTDSB_CMDB_MGR 13201/tcp nfdomain 23457/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 rcxjeedomainadmin 23851/tcp rcxjeedomaininstance 23852/tcp rcxjeedomainjmx 23853/tcp rcxjeehttpssl 23854/tcp rcxjeejms 23855/tcp rcxjeeorblistener 23856/tcp rcxjeeorbmutualauth 23857/tcp rcxjeeorbssl 23858/tcp rcxmessagebroker 23861/tcp rcxbpmsvasadminlistener 23862/tcp rcxbpmsvhttplistener 23863/tcp rcxbpmsvhttpssllistener 23864/tcp rcxbpmsviioplistener 23865/tcp rcxbpmsviiopssllistener 23866/tcp rcxbpmsviiopsslmutualauth 23867/tcp rcxbpmsvjmxsystemconnector 23868/tcp rcxbpmsvjavadebugger 23869/tcp rcxbpmconasadminlistener 23870/tcp rcxbpmconhttplistener 23871/tcp rcxbpmconhttpssllistener 23872/tcp rcxbpmconiioplistener 23873/tcp rcxbpmconiiopssllistener 23874/tcp rcxbpmconiiopsslmutualauth 23875/tcp rcxbpmconjmxsystemconnector 23876/tcp rcxbpmconjavadebugger 23877/tcp rcxbpmsvdb 23878/tcp RCXCTDSB_EFServer 41320/tcp
Checking Port Usage Status
Execute the "Environment setup conditions check tool" in "2.1.1.5 Configuration Parameter Checks" to check the port usage status.
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.
When ports are being used for something other than Resource Orchestrator, change the ports to use.
For the port information used by Resource Orchestrator, refer to "Appendix A Port List" in the "Design Guide CE".
Changing Port Numbers
To change port numbers after installing 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
Check configuration parameters following the procedure below:
Log in as the administrator.
Confirm that a single folder path is set for the TEMP environment variable.
Information
If the TEMP environment variable is not configured or if multiple folder paths are set for the TEMP environment variable, the Environment setup conditions check tool outputs the following message and cancels the process.
The check tool cannot be processed because the temporary folder %temp% cannot be accessed. Please set the TEMP environment variable of current user correctly, then rerun the check tool. press enter key to exit... |
If the above message is output, set a single folder path for the TEMP environment variable, then execute the Environment setup conditions check tool again.
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 the check items with the edition name displayed in the check results, check only the items corresponding to the edition to be installed.
When configuration parameter checking is completed, the check results will be saved in the following location.
%temp%\ror_precheckresult-YYYY-MM-DD-hhmmss.txt
The check results are output to Notepad at the same time.
The following items are displayed as the items to be checked:
Required Software (LAN Manager module)
Required Software (Windows PowerShell)
Required Software (ETERNUS SF Storage Cruiser)
Disk Space (Express/Virtual Edition)
Disk Space (Cloud Edition)
Memory Size (Express/Virtual Edition)
Memory Size (Cloud Edition)
cpu
SNMP Service
Port Status (Express/Virtual Edition)
Port Status (Cloud Edition)
Confirm that "Warning" or "NG" is not included in the check results. If there are check items that were determined as "Warning" or "NG", resolve the cause of the problem based on the output message. For details of the corrective actions, refer to "2.1.1.1 Preparations" and "6.1 Software Environment" and "6.2 Hardware Environment" in the "Overview".
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 Remote Desktop Session Host server has been installed, execute the following command using the command prompt to place the Remote Desktop Session Host server into installation mode.
CHANGE USER /INSTALL User session is ready to install applications.
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 to the system as the administrator.
Log on to the system on which the manager is to be installed using the Administrator account of the local computer.
Set the first Resource Orchestrator DVD-ROM.
Then, the installer starts automatically.
Information
If the installer does not start, execute "RcSetup.exe" from the DVD-ROM drive.
Select [Cloud Edition].
Click [Manager installation].
Perform installation according to the installer's interactive instructions.
Enter the parameters designed and checked in "Parameters Used for Installation" in "2.1.1.3 Collecting and Checking Required Information".
When the wizard requests switching of the DVD-ROM, insert the second DVD-ROM to continue the installation.
Note
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 "11.1.2 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 "11.1.2 Uninstallation [Windows Manager]". If the problem persists even if reinstallation is performed, please collect troubleshooting information and contact Fujitsu technical staff.
Post-installation Cautions
When a Remote Desktop Session Host server has been installed, execute the following command using the command prompt to place the Remote Desktop Session Host server into execution mode.
CHANGE USER /EXECUTE User session is ready to execute applications.
The following users are added. When installing Resource Orchestrator, do not delete these accounts.
Account Name | Usage |
|---|---|
rcxdb | rcxdb is used as the OS account for connecting to the database service of Resource Orchestrator. |
rcxctdbbpm | rcxctdbbpm is used as the OS account for starting the database service for process management. |
rcxctdbchg | rcxctdbchg is used as the OS account for starting the database service for metering. |
rcxctdbdsb | rcxctdbdsb is used as an OS account to start the database service for dashboards. |