Preparing to install TrueSight Orchestration Platform

Before installing the Platform, ensure that your environment meets the installation requirements, and complete the tasks described in this section.

Complete the pre-installation tasks for the Platform

Ensure that the target computer meets the system requirements for Platform.
Review the Known and corrected issues section for any installation-related issues.
Ensure that the domain name of the computer where you are installing the Platform does not contain numerical values.
Ensure that you install the product as either of the following user based on the server operating system.
- Linux and Solaris: root or a user with root rights and permissions
  Permissions needed for non-root users
  Any non-root user with write permission to the /opt/bmc directory can perform the installation.
  On Linux and Solaris, the non-root user must also have permission to run the following commands:
  - dmidecode -t 1 | grep Manufacturer
  - lsb_release -d
- Windows: administrator or a user with administrator rights and permissions
Following installation, each server component must run with the same user permissions.
(Before installing CDP) Ensure that you have the lsb_release command in the /usr/bin directory and that you can run it. Use the steps for your operating system.
For Red Hat Linux 7
1. Verify that the lsb_release command is in the /usr/bin directory by running the following command:
  which lsb_release
  For example,
  [root@localHost ~]# which lsb_release
  If it is available, you will see the following response:
  /usr/bin/lsb_release
2. If the command is available, verify that you can run it using the following command:
  lsb_release -d
  For example,
  [root@localHost ~]# lsb_release -d
  If it runs correctly, you will see a response similar to the following:
  Description: Red Hat Enterprise Linux Server release 7.0 (Maipo)
  
  or...
  If the command is not available, copy it from a RHEL6 machine to the RHEL7 machine as follows:
  1. Navigate to the /usr/bin directory and run the scp command to copy the lsb_release command from the RHEL6 machine to the RHEL7 machine.
    scp lsb_release root@<rhel7MachineHostname/IPaddress>:/usr/bin/
  2. On the RHEL7 machine, repeat steps a and b to verify that the command is in the /usr/bin directory and that you can run it.
For SUSE Linux
1. Verify that the lsb_release command is in the /usr/bin directory by running the following command:
  which lsb_release
  For example,
  [root@localHost ~]# which lsb_release
  If it is available, you will see the following response:
  /usr/bin/lsb_release
2. If the command is available, verify that you can run it using the following command:
  lsb_release -d
  For example,
  [root@localHost ~]# lsb_release -d
  If it runs correctly, you will see a response similar to the following:
  Description: SUSE Linux Enterprise Server 11 (x86_64)
  or....
  If the command is not available, download it from the internet or from your operating system vendor's website.
(For UNIX computer) Ensure that the installation path does not contain a backslash ('\').
(For HTTPS) Ensure that your environment supports TLS secure transport protocol.

Configure DEP on Windows computers

Before installing or upgrading the components on a Windows computer, you must configure the data execution prevention (DEP) feature to recognize the installation program. If DEP is not configured, it can block the installation program from continuing and an error message might appear, stating that you must configure your computer before you can proceed with the installation.

Note

Your computer may already have DEP turned on for all programs and services. If so, you do not need to perform this procedure.

To configure DEP on Windows computers

Use the method appropriate for your computer:
1. On the Windows desktop, right-click the My Computer icon, and select Properties.
2. On a Windows VM, use the steps appropriate for your computer:
  - Select Start > Control Panel > System.
  - Select Start > Control Panel > System and Security > System > Advanced System Settings.
Select the Advanced tab, and under the Performance heading, select Settings.
Select the Data Execution Prevention tab, and click Add.
Select {_}path\installationDirectory\installerName{_} and click Apply.
Click OK, and click OK again to close the System Properties window.

Configure terminal services on Windows 2008 R2 and Windows 2012 computers

If you are installing or upgrading the components on a Windows 2008 or 2012 computer, you must configure the terminal services to recognize the installation program.

Note

This may already be done on your computer. If you run the installer and your computer is not properly configured, the installer will instruct you to configure terminal services.

To configure terminal services on a Windows 2008 R2 computer

Select Start > Run.
In the Open field, type regedit.
Navigate to Computer >HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server.
Double-click the DeleteTempDirsOnExit entry, update Value data to 0, and then click OK.
Double-click the PerSessionTempDir entry, update Value data to 0, and then click OK.
Restart the computer for the registry changes to take effect.

To configure terminal services on a Windows 2012 computer

Access the Charms bar by moving the mouse to one of the right corners of the screen and click Search (the magnifying glass).
In the text box, type regedit.
Navigate to Computer >HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server.
Double-click the DeleteTempDirsOnExit entry, update Value data to 0, and then click OK.
Double-click the PerSessionTempDir entry, update Value data to 0, and then click OK.
Restart the computer for the registry changes to take effect.

Run the rngd service on Linux computers

Before installing or upgrading components on a Linux computer, run the rngd service to ensure that the system has adequate entropy.

Verify that rng-tools is installed on your Linux computer. If it is not, install it, working with your system administrator to ensure that you correctly install the rng-tools for your operating system.
At the command line, run the following command:
rngd -r /dev/urandom

After installing , ensure that this command is running at server startup or before starting the service.

For more information, see Workaround when a component server startup on Linux hangs.

Provide database user permissions

There are several user accounts that you must create to install the product and use embedded and external databases.

Audit and metric external database permission requirements

You use Grid Manager to set up the connection to the audit and metric external databases by using the database vendor's JDBC drivers. One of the require database connection parameters is a user name which must already exist within the target database environment. This user must have following generic permissions on the target database schema for both the audit and metric configurations to work successfully.

Audit and metric external database permissions

For the initial configuration of audit and metric external database connections and the subsequent upgrade of components across service packs and versions, the database user must have the following permissions:

Create Table
Create Index
Create Foreign Key Constraint
Create Sequences (Oracle, or the equivalent)

Grid management and job execution permissions

For grid management and job execution which might insert, update, or delete data into the audit and metric tables, the database user must have the following permissions:

Select
Insert
Update
Delete

It is the database administrator's responsibility to ensure that the user configured within the audit and metric database configurations has the required permissions.

Repository database permissions

For both the embedded and external repository databases to work successfully, the user must have the following permissions:

Create Session
Create Table
Create Index
Create Foreign Key Constraint
Create Sequences (Oracle, or the equivalent)

Encrypt passwords for a silent installation

If installing the platform components silently, ensure that you encrypt the passwords to be specified in the options file by using the Maintenance Tool utility.

Before you begin:

Download the Maintenance Tool utility from BMC Electronic Product Download site.
For details, see Downloading the installation files.
Set JAVA_HOME variable on the host where you want to run the utility.

To encrypt a password using the Maintenance tool utility:

Navigate to the directory where the Maintenance Tool utility is located and start one of the following programs:
- Windows: PlatformMaintenanceTool.cmd
- UNIX: PlatformMaintenanceTool.sh
On the TrueSight Orchestration Maintenance Tool window, click Encrypt.
Type and confirm the password.
Click Encrypt.
The encrypted password is displayed in the Encrypted password text box.

Where to go next

If you are planning to install content after installing the platform, prepare your environment for installing content. If you want to skip content and directly install the platform, go to Installing – Classic mode for the complete installation process.