Installing the Infrastructure Management server in the disaster recovery mode
Where you are in the Installation process
Step | Task |
---|---|
1 | Complete the planning activities |
2 | Prepare for TrueSight Operations Management installation |
3 | Install Remedy Single Sign-On |
4 | Install TrueSight Presentation Server |
5 | Install TrueSight Infrastructure Management — Phase A (You are here) |
Install TrueSight Infrastructure Management — Phases B and C | |
6 | Install App Visibility Manager (If licensed) |
7 | Install Real End User Experience Monitoring Software Edition (If licensed) |
8 | Install TrueSight IT Data Analytics (If licensed) |
9 | Complete the post-installation activities |
Infrastructure Management Server can be installed with Oracle or SAP SQL Anywhere as the database. Infrastructure Management is integrated with SAP SQL Anywhere, which is configured by default. If you want to install it with Oracle, you can configure the Oracle database during installation.
Note
- Ensure that there are no Integration Services installed on the computer where the TrueSight Infrastructure Management Server will be installed. If any Integration Services are installed on this computer, the TrueSight Infrastructure Management Server installation fails.
- If you are using the Remote Desktop Connection (RDC) to install the product, put the RDC in console mode.
- If you are installing the Infrastructure Management Server with Oracle, ensure that port 7 is opened between the Server and the Oracle database system. If port 7 cannot be opened due to security restrictions, run the installer using the following option:
- (Windows)
install.cmd -J SKIP_PING_VALIDATION_ERROR=true
- (Linux)
./install.sh -J SKIP_PING_VALIDATION_ERROR=true
- (Windows)
- BMC recommends that you use MobaXterm as the UI to install TrueSight Infrastructure Management on Linux computers.
- (Windows or Linux) Ensure that the commands
domainname -f
andhostname
return the same output before proceeding with the installation. To disable the validation for oracle parameters during installation, set the following property to
false
in the oracle_db_configuration.conf file at (Windows) <TSIM Installer Directory>\Disk1\oracle_db_configuration.conf or (Linux) <TSIM Installer Directory>/Disk1/oracle_db_configuration.conf:pronet.oracle.instance.parameters_validate=false
You need to perform the following tasks to install the Infrastructure Management server in the disaster recovery mode:
Step A: To install the Infrastructure Management server on the primary host computer
Do the following:
Log in to the host computer on which you want to install the Infrastructure Management Server, and delete all the files from the temporary directory:
- (Windows) %temp%
- (Linux) /tmp
Note
If you are reinstalling the Infrastructure Management Server due to a failure, you must delete all the existing installation directories and files.
Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:
- (Windows) C:\Program Files
- (Linux) /opt
(Linux) Apply executable rights to all the installation files by running the following command:
chmod -R 755 installationDirectoryFolderName
installationDirectoryFolderName is the name of the folder that contains all the installation files.
For example,
chmod -R 755 Disk1
- (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
export DISPLAY=<IP address of the host computer>:0.0
Note
Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the installation. However, in a test environment, you can skip the system requirements validation and run the installer by using the
-J MINIMAL=true
argument.- Total RAM (in MB): 32,000
- Available RAM (in MB): 25,000
- Total swap space / page file (in MB): 8,000
- Available swap space / page file (in MB): 8,000
By default, the TrueSight Infrastructure Management Server uses 256-bit encryption. However, AES 256-bit encryption is not allowed in some countries due to import regulations. You can change the default encryption key size when you invoke the installer.
Navigate to the Disk1 directory of the extracted folder, use one of the following options to run the installer.
BMC recommends that you run the installer by using
install.cmd
and notsetup.exe
.You must right-click on install.cmd and select Run as administrator.
Environment type Command Production environment with the default encryption setting
(Windows)
install.cmd
(Linux)
./install.sh
Production environment with user-specified encryption setting (Windows)
install.cmd –J BMC_TS_KEY_SZ=<128/256>
(Linux)
./install.sh –J BMC_TS_KEY_SZ=<128/256>
Test environment with the default encryption setting (Windows)
install.cmd -J MINIMAL=true
(Linux)
./install.sh -J MINIMAL=true
Test environment with with user-specified encryption setting
(Windows)
install.cmd –J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true
(Linux)
./install.sh –J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true
- Review the welcome page, and click Next.
- Read the license agreement, agree to the terms, and click Next.
(Windows) Start the Windows Firewall service from services.msc and run the following commands:
- (Microsoft Windows 2012 R2)
netsh advfirewall set allprofiles state on
- (Microsoft Windows 2012)
netsh firewall set opmode mode = ENABLE
- (Microsoft Windows 2012 R2)
Note
If you turn on the firewall when Remote Desktop Protocol (RDP) is running, the RDP session may get disconnected if it is blocked by the firewall.
(Windows) On the Configuring Firewall Rules page, perform one of the following tasks, and click Next.
- Select Automatically configure the Windows Firewall rules.
- The Windows Firewall inbound rules are configured.
- Select I will manually configure Windows Firewall Rules now before proceeding further and configure inbound rules for the pw processes that are listed on the page.
If you prefer to use a third party firewall application that is installed on your computer, you must manually create the firewall inbound rules. For more information about creating firewall inbound rules, refer to the documentation of the third party firewall application.
The default installation directory is:
(Windows) C:\Program Files\BMC Software\TrueSight
(Linux) /opt/bmc/TrueSight
Note
- (Windows) Do not install TrueSight Infrastructure Management Server in the root directory (for example C: or D: ), on a shared drive, or in the Documents and Settings folder.
- (Windows) While installing TrueSight Infrastructure Management Server on a 64-bit Windows computer, ensure that you do not install it in the Program Files (x86) directory path.
- (Linux) Do not install TrueSight Infrastructure Management Server in the root directory.
- (Linux) The directory in which the TrueSight Infrastructure Management Server is installed and all its parent directories must have 755 permissions (read, write, and execute permissions to owner, groups, and others) and must be owned by root as well as the other group. Without these permissions and ownership, you will not be able to log in to the TrueSight Infrastructure Management Server.
- (Linux, as a non-root user) To avoid problems related to user permissions, ensure that you log in to a new session as a non-root user (without using the su command).
- For Chinese, Korean, and Japanese installations, ensure that the system default locale is a UTF-8 locale. This enables the Input Method feature in the administration console.
The installer detects the FQDN of the host computer and populates the FQDN field automatically. Ensure that the FQDN is accessible by the other TrueSight components in your environment.
If you modify the FQDN:Do not manually type any IP address in the FQDN field.
Do not leave this field empty
Confirm this, and click Next.- Select Configure TrueSight Infrastructure Server for Disaster Recovery mode from the System Configuration Tasks, and click Next.
By default, Administrator e-mail from BMC TrueSight Infrastructure Management is selected. You can deselect it.
By default, SAP SQL Anywhere, which is integrated with TrueSight Infrastructure Management, is configured. If you want, you can choose to configure the Oracle database instead. Based on your selection, the applicable configuration pages are displayed. Type the appropriate details, and click Next.
Do not select the DSIM - Enable and Configure option.
(Oracle database only) If you are configuring an Oracle database, specify these details, and click Next.
Review the installation details, and click Install.
Note
If the DNS configurations are not correct, a warning message is displayed. You can either correct the DNS configuration and restart the installation, or provide the IP address instead of the host name when you are prompted to enter the host name.
The installation may take upto 30 minutes.
After the installation is complete, the Installation Summary page is displayed.
- Select View Logs to open the installation logs.
(Linux) Verify that the following environment variables are set.
$BPPM_SERVER_HOME
- $BMC_PROACTIVENET_HOME
Run the following command to verify the Infrastructure Management installation:
(Windows)
# pw system status
(Linux)# pw system status
A list of pw server processes is displayed.
If errors occur, restart the BMC TrueSight Infrastructure Management Server by running the following command:
(Windows)
# pw system start
(Linux)# pw system start
BMCTrueSight.service (Applicable only to version 11.3.04 and later on Linux)
You can use the systemd service
BMCTrueSight.service
located in the /etc/systemd/system directory to start and stop the Infrastructure Management server on Linux. For more information, see Starting and stopping the TrueSight Operations Management components.Apply the Infrastructure Management license.
Note
- Applying or updating the license restarts the JServer process and forces all active user sessions on the Infrastructure Management Server to log off.
- You must have root privileges to apply the license.
When you purchased the product, you would have received the following license files in a .zip file from your BMC Software representative:
- proactivenet.lic
- proactivenet.sign
Do not move or delete the license file
- After loading the license, moving or changing the license files can cause a number of errors.
- When the Infrastructure Management is installed, a hidden .pbk file is created. It is recommended to save a back copy of this .pbk file. If the licence directory is removed and then re-created, the .pbk no longer exists. So the .pbk file must be re-added for Infrastructure Management licensing to function properly. This file can be captured from a backup of the installation (if a backup exists) or from another computer where Infrastructure Management is installed.
Register Infrastructure Management Server with the Presentation Server.
Note
Complete the following configurations to ensure automatic failover when any of the Infrastructure Management servers goes down. If these configurations are not completed, you need to manually restart the Presentation Server each time one of the Infrastructure Management servers goes down (indicated by the Initializing status on the Administration > Components page).
- Configure the primary and secondary server to use the same alias name on the DNS server.
- Configure DNS replication for both the primary and secondary servers.
- While registering Infrastructure Management with the Presentation Server, ensure that you specify the same alias name as the host name for both the primary and secondary servers.
- Ensure that the alias name contains only alphanumeric text and does not contain any special characters like hyphen( - ) and underscore( _ ).
For example: alias name could be pronet, pronet2, or pronettsim.
Use the following format to define the Infrastructure Management Server URL, and launch the application in a browser.
- (Windows) http(s)://<TSIMFQDN>
- (Linux) http(s)://<TSIMFQDN>
- Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.
The Infrastructure Management console opens. (Linux) If you installed Infrastructure Management Server as a non-root user, do the following:
Configure the TrueSight Infrastructure Management process to automatically start each time the TrueSight Infrastructure Management server is restarted. To do this, register the process as a service by running the script described in the following procedure. Running this script also results in copying the Integration Service security files required by the PATROL Agent to connect with the Integration Service.
- Locate the script at <Infrastructure-Management-Installation-Directory>/pw/scripts.
- Run the script in the following format:
create_startup_script.sh [<Non-root-User-Name>]
where,<Non-root-User-Name>
refers to the non-root user name with which the process must be registered as a service.
Providing the non-root user name is optional. If you do not provide the non-root user name, by default, the script uses the non-root user name used for installing TrueSight Infrastructure Management to register the service.
- After you have installed the Infrastructure Management server using a non-root user, ensure that you do not restart the cell as a root user.
Step B: To perform post-install tasks after installing on the primary host computer
- Stop the primary Infrastructure Management Server processes and take a backup of the installationDirectory/pw/ folder.
- Shutdown the primary host computer.
Step C: To install the Infrastructure Management server on the recovery host computer
Install the Infrastructure Management server on the recovery host computer using the same steps that you used while installing on the primary computer. While registering the recovery Infrastructure Management server with the Presentation Server, ensure that you specify the same alias name that you used for the primary server.
Step D: To perform post-install tasks after installing on the recovery host computer
- Stop the recovery Infrastructure Management Server processes and restore a backup of the installationDirectory/pw/ folder on the recovery windows host.
- Restart the TrueSight Presentation Server service.
- Restart both the primary and recovery Infrastructure Management servers.
Step E: To verify that the disaster recovery server is functional
- Add Integration Services and PATROL Agents to the Infrastructure Management Server and observe the data collection.
- Complete the following configurations to ensure automatic failover when any of the Infrastructure Management servers goes down. If these configurations are not completed, you need to manually restart the Presentation Server each time one of the Infrastructure Management servers goes down (indicated by the Initializingstatus on the Administration > Components page).
- Configure the primary and recovery servers to use the same alias name on the DNS server.
- Configure DNS replication for both the primary and recovery servers.
- While registering Infrastructure Management with the Presentation Server, ensure that you specify the same alias name for both the primary and recovery servers.
Important
The system requirements are validated every time you restart the host computer or product services. If the system requirements are not met, the product services are not started. To force-start the product services, see Starting and stopping the TrueSight Operations Management components.
Comments
Log in or register to comment.