Preparing to install Infrastructure Management
Before installing the TrueSight Infrastructure Management server, ensure that your environment meets the installation requirements, and complete the tasks described in this section:
Complete the preinstallation tasks
Ensure that the target computer meets the System requirements and product compatibility for Infrastructure Management.
- Review the Known and corrected issues issues section for any installation-related issues.
- If you are installing TrueSight Infrastructure Management on the same computer where an earlier installation existed, you must uninstall the earlier installation and clean up the installation folders completely.
- Ensure that any installed security software does not hamper the deletion of any *.war files.
- If you are installing TrueSight Infrastructure Management on an IPv6 Windows host, ensure that the IP helper service has been started.
TrueSight Infrastructure Management Server communicates with the Oracle database using Java Database Connectivity (JDBC). Therefore, do not install additional software such as Oracle Client on the TrueSight Infrastructure Management server host.
Ensure that you have configured the firewall to allow TCP port 7, which is used to communicate with the other TrueSight Infrastructure Management hosts.
- Disable the X Windows access control by using the xhost command.
Ensure that the nobody user account exists on the target computer.
Disable the on-demand antivirus scan of the system.
- 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.
Complete the additional tasks for Windows
- Ensure that you have Administrator permissions.
- If you are using the Remote Desktop Connection (RDC) to install the product, put the RDC in console mode.
- Ensure that you have enabled the Windows short path configuration.
- If you want the non-Administrator users with administrator privileges to access TrueSight Infrastructure Management after the installation, you must turn off the User Access Control (UAC) before you install the server.
- Ensure that you do not select a mount point as the installation directory. If the existing TrueSight Infrastructure Management installation directory is a mount point, you might have problems associated with the upgrade process when attempting to rename directories. Allocate a directory for the existing environment that is not a mount point.
- Ensure that you do not select a root directory like C: or D: as the installation directory. If the existing TrueSight Infrastructure Management installation directory is a root directory, you might have problems associated with the upgrade process when attempting to rename directories. Allocate a directory for the existing environment that is not a root directory.
- If you want to integrate TrueSight Infrastructure Management with SCOM 2007 and 2012, ensure that .NET Framework version 3.0 is installed. If you are installing it on Windows 2008 R2, use the Role Management tool. For more information about installing .NET Framework, see the Microsoft website.
- On European locales (French, German, and Spanish): Do not change the default localized Administrators group name. TrueSight Infrastructure Management installation works only with the default localized Administrators group names. For example:
- English: Administrators
- German: Administratoren
- French: Administrateurs
- Spanish: Administradores
- Configure the Windows terminal services
On Windows, to run the installation utility through a Terminal Services connection or a remote desktop session, configure the Terminal Server options that pertain to temporary folders.
Note
You must configure the Terminal Server options only once on a host computer. You do not have to configure the options if you reinstall a TrueSight product on the same host computer.
Do the following:
- On the host computer, open the Local Group Policy Editor by selecting Start > Run, and type gpedit.msc.
- Expand the following folder: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders.
- Double-click the following options to set them to Enabled:
- Do not delete temp folder upon exit
- Do not use temporary folders per session
- On the host computer, open the Registry Editor by selecting Start > Run and typing regedit.
- Expand the following folder: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
- Set the value for PerSessionTempDir and DeleteTempDirsOnExit to 0.
- Restart the computer.
You can revert these changes after you complete the installation process. You might need to restart the computer.
Complete the additional tasks for Linux
Ensure that you have a non-root user created. You can install TrueSight Infrastructure Management as a non-root user.
- Ensure that umask is set to 022.
- Ensure that you install the csh and tcsh shells.
- Ensure that you install the 'ed' editor for Linux.
- The ports 80 and 443 are valid only if a root user is installing the TrueSight Infrastructure Management server.
- For a non-root user installing the TrueSight Infrastructure Management server, the port numbers must be greater than 1024.
- To be able to perform the installation, a non-root user needs the following permissions:
- Read, write, and execute permissions for: TrueSight Infrastructure Management installation directory, /var/tmp, /tmp, /usr, and usr/bin directories.
- Execute permission for the /Linux/Disk1/setup.bin file.
Read and write permissions for the /opt/bmc directory.
Note
The ProductRegistry.xml file is created in the /opt/bmc directory. Therefore, the /opt/bmc directory requires read and write permissions. If the bmc directory does not exist, create it with read and write permissions.
You can run the config_nonroot.sh script as a root user from the following location to give the non-root user the above required directory permissions :
From the command line, go to
<Download_Location>/TSIMServer/Disk1/utility
.
As a root user, run
sh ./config_nonroot.sh <Non-root-User-Name> <Install_directory-location>
Example:
sh .
/config_nonroot.sh tsimnonroot /opt/bmc/tsim
<Non-root-User-Name>
refers to the non-root user who will install the TrueSight Infrastructure Management product.<Install_directory-location>
refers to the absolute path to the directory where you plan to install or upgrade the TrueSight Infrastructure Management product.
Start a new session for the changes to take effect.
The config_nonroot.sh script sets the following minimum limits for creating the number of files and processes in the /etc/security/limits.conf file:
<Non-root-User-Name> soft nofile 16096
<Non-root-User-Name> hard nofile 16096
<Non-root-User-Name> soft nproc 4096
<Non-root-User-Name> hard nproc 4096
Note
As a non-root user, you cannot upgrade Infrastructure Management without these minimum limits. However, you can manually edit the limits.conf file to increase the limits.
- Ensure that the non-root user who installs the product has the home directory, and it contains the user profile file on the host computer where TrueSight Infrastructure Management is to be installed. This is required for setting the
BMC_PROACTIVENET_HOME
andMCELL_HOME
environment variables to be set in the user profile file. - Ensure that the TrueSight Infrastructure Management installation directory and all its parent directories have 755 permissions. Without these permissions, you will not be able to log into the TrueSight Infrastructure Management Server.
- Ensure that you do not select a mount point as the installation directory. If the existing TrueSight Infrastructure Management installation directory is a mount point, you might have problems associated with the upgrade process when attempting to rename directories. Allocate a directory for the existing environment that is not a mount point.
If you are installing the TrueSight Infrastructure Management on a SUSE Linux host, ensure that the glibc library version is 2.12 or later.
Ensure that the required fonts are present on the Linux OS on which you plan to install Infrastructure Management.
Install Arial fonts.
Install all fonts other than Arial. Run the following command to install the fonts on both the primary and secondary servers::
yum install urw-fonts
- Ensure that the core file size is set to unlimited to generate the heap dump (HPROF) when the Agent Controller, JServer, or Rate process crashes. The HPROF file assists in troubleshooting.
Run the following command to check if the core file size is set to 0 (disabled).ulimit -c
If disabled, enable the core file by updating the /etc/security/limits.conf file:<Non-root-User-Name> soft core unlimited
<Non-root-User-Name> hard core unlimited
- Ensure that the system default locale is set to UTF-8 locale.
Configure the Oracle Database
Note
By default, TrueSight Infrastructure Management is integrated with SAP SQL Anywhere. You can choose to use Oracle as your database. During installation, you can configure either the SAP SQL Anywhere database or the Oracle database. For more information on Oracle DB requirements, see Oracle database server requirements.
You can either allow the Infrastructure Management installer to create the schema in the Oracle database, or you can create the schema manually using scripts provided with the installer. Follow one of these procedures to configure Oracle Database:
Installing Oracle Database and other common tasks
Deploy the Oracle database and the TrueSight Infrastructure Management Server on separate host machines.
Create an Oracle database instance. Oracle must be installed and running as a basic database instance. The Oracle database instance must be dedicated toTrueSight Infrastructure Management. For instructions on creating an Oracle database instance, see the Oracle database documentation.
Each schema in an Oracle instance must have a unique Oracle database user as its owner. The installer prompts you for the user who owns the schema for the current instance. Ensure that you enter a unique user for each TrueSight Infrastructure Management Server instance that you install.
Each unique schema must be installed in separate data files and corresponding tablespaces in the Oracle Instance. The TrueSight Infrastructure Management Server installer allows you to specify these criteria.
Install and configure the SQLPlus or the Oracle Instance Client with SQLPlus option on the computer on which Infrastructure Management will be installed. This is needed for validation, and to run the set_system_parameter_oracle_pnet.sql script.
Note
This client installation is required only for verifying the connectivity is established with the Infrastructure Management server and running the set_system_parameter_oracle_pnet.sql script. After completing the preinstallation configuration mentioned in this section, you can either uninstall the client or disable it.
To ensure that the TrueSight Infrastructure Management Server can connect to the Oracle database instance you created, install the Oracle SQL*Plus Instant Client on the same computer on which the TrueSight Infrastructure Management Server will be installed.
Configure the Oracle for remote SYSDBA connectivity.
Test the remote connectivity to the Oracle database instance from the host on which you will install TrueSight Infrastructure Management.
Create at least two sets of redo log files with a minimum of 500 MB each on the Oracle database instance.
Ensure that the system tablespaces SYSTEM has a minimum 2 GB and SYSAUX has a minimum 3 GB of free spaces. For troubleshooting SYSTEM and SYSAUX, see Troubleshooting the Infrastructure Management database and operating system issues.
Configure the listener for the Oracle database instance and ensure that it is running. You can configure Oracle so that each database instance has a unique Oracle listener, or a single listener that can support multiple database instances.
Best practice
BMC recommends that you designate a unique Oracle listener for each database instance. This isolates listener issues to a single instance.
- Ensure that the high availability is set up for the Oracle listeners and the databases.
- Provide the port number on which the database listener is listening for connections.
(Oracle 12c) Add the
USE_SID_AS_SERVICE_<listener_name>=on
parameter in listener.ora and reload the listener settings with thelsnrctl reload
command.Note
Do not set the
USE_SID_AS_SERVICE_<listener_name>=on
parameter if you are using Oracle RAC with a SCAN listener.- (Oracle 12c only) Ensure that the administrator user created for the Pluggable Databases (PDBs) is used for the administration purpose only. Do not use this user for installing Infrastructure Management.
(Oracle 12c) Ensure that the PDBs are in the open mode.
- You have an option to configure the other Oracle settings at the time of installing Infrastructure Management or manually configure the Oracle Database using one of the following procedures.
- (Recommended) If you choose to configure it at the time of installing Infrastructure Management, you can proceed to Best practices for configuring and administering the Oracle database.
- If you choose to manually configure perform one of the following procedures:
Manually configuring Oracle Database using the BMC provided scripts
Copy the Oracle folder that contains the set_system_parameter_oracle_pnet.sql script from the <Download>/TSIMServer/ folder to the Oracle server.
Configure the Oracle database to use a system parameter file (SPFILE) and ensure that the persistent database system parameters are set. The set_system_parameter_oracle_pnet.sql script references the SPFILE file and displays error messages if the file does not exist.
Set the Oracle database system parameters using set_system_parameter_oracle_pnet.sql script.
Set the Oracle database instance on the Oracle server to run in ARCHIVELOG mode. Running in the ARCHIVELOG mode enables you to back up your log files and perform point-in-time recovery. Use the following commands to check the type and enable archive log mode:
To check the type:
Select log_mode from v$database;
To enable the archive log:
ALTER SYSTEM SET log_archive_dest_1='location=/home/oracle/archivelog' SCOPE=spfile; SHUTDOWN IMMEDIATE; STARTUP MOUNT; ALTER DATABASE ARCHIVELOG; ALTER DATABASE OPEN;
Tip
Archive log files use large amounts of disk space. Ensure that you delete the old archive log files at regular intervals. For instructions on how to set the ARCHIVELOG mode and managing archive log files, see the Oracle database documentation.
- Create a new user in the Oracle database. This user is used exclusively by Infrastructure Management to create reports and view the default views created during the Infrastructure Management installation. You will configure this user in the Configure Oracle Report User screen of the Infrastructure Management installation.
Provide the default or custom tablespace and related temporary tablespace names for Infrastructure Management. The Infrastructure Management installer creates these tablespaces and related database files using these names.
Note
Note down the user details and tablespace details. You need to specify these at the time installing Infrastructure Management.
You can skip the next section and proceed to Best practices for configuring and administering the Oracle database.
Manually configuring Oracle Database without BMC provided scripts
Note
Although you can set up the Oracle database manually, BMC recommends that you run the run_oracle_db_scripts.sql script for setting up the Oracle database.
Best practices for configuring and administering the Oracle database
Note the following additional best practices when using Oracle as the database platform:
Create at least two Infrastructure Management users, one for data storage and one for data views. Consider a third “backend user” to manage issues like locked accounts.
- The backup and restore process must be executed by Infrastructure Management users.
Use BMC Database Recovery Management or an Oracle tool such as RMAN.
Enable archive logging.
Use Oracle Data Guard for disaster recovery.
- Use Oracle Storage Area Network (SAN).
- Run the
OracleSchemaPreInstallCheck.sql
script.
Running the OracleSchemaPreInstallCheck.sql script
After you created a new Oracle user and set up the INIT parameters, ensure that you copy the Oracle folder that contains the OracleSchemaPreInstallCheck.sql script to the Oracle server.
Notes
- You must be a SYS user or a user with SYSDBA privileges to run this script.
- You must run this script on the Oracle server.
Navigate to the Utilities\oracle folder.
For example,
cd Utilities\Oracle
- Run the following command:
(For Oracle 11.x)sqlplus SYS/<password>
@ <SID>/<service_name>
as sysdba
(For Oracle 12c)sqlplus SYS/<password>
@ <PDB>/<service_name>
as sysdba - Run the OracleSchemaPreInstallCheck.sql script on the Oracle server.
SQL> @OracleSchemaPreInstallCheck.sql <Infrastructure_Management_User> <Infrastructure_Management_Report_User> <Infrastructure_Management_Version>
For example,@OracleSchemaPreInstallCheck.sql PROACT PROACTRU 11.3.01
The status report is generated in the oracle_specific_PreInstall_log.html file. Review this file for all OK status.
Complete the preinstall tasks for Integration Service and Remote cell
- Ensure that you do not install Integration Service on the same computer where you have installed the TrueSight Infrastructure Management Server.
- Ensure that the host computer on which you are installing the Integration Service and Remote Cell adheres to the requirements described in the above preparing to install Infrastructure Management sections.
- Ensure that the computer on which you are installing the Integration Service and Remote Cell adheres to the hardware, operating system, and software requirements listed in the System Requirements and Product Compatibility section.
- If you want to install both cell and Integration Service on the same computer on which you have installed only the cell, then you should provide a different locations for installing cell and Integration Service. If you provide the same location where you installed the cell (C:\ProgramFiles\BMC Software\TSIMAgent), the cell entries are removed from the system.
You need a root user permission or root privileges for a non-root user to install the Integration Service.
- You can install multiple instances of an integration service on a same host machine. Each Integration Service can be connected to a single or different TrueSight Infrastructure Management.
- If you are planning to install multiple instances of Integration Services on a same host machine, use different port numbers of each installation instance. Port number can be in the range of 1024-65535.
- (Solaris or AIX) You can only install the Remote Cell on these computers. Integration Services cannot be installed.
- (Linux) Install all the required libraries for the Remote Cell.
If you plan to install a fresh instance of Integration Service or remote cell:
If the host computer does not have any existing instance, ensure that the host computer has a compatible Java version installed on it and update the JAVA_HOME environment variable to point to this Java version. Ensure that you provide read/write access to the cacerts file associated with the Java installed on your system (Windows or Linux). On Linux systems, ensure to follow the soft links to go to the actual location of the cacerts file.
- If the host computer has an existing instance of the Integration Service / remote cell version 11.3.01 or earlier:
- Ensure that the host computer has a compatible Java version installed on it and update the JAVA_HOME environment variable to point to this Java version.
- Ensure that the JAVA_HOME environment variable is not pointing to the JRE that is bundled with an existing instance of the Integration Service and Remote cell.
Note
- Ensure that JAVA_HOME is pointing to 64-bit jre.
- Ensure that the JAVA_HOME must point till the jre directory as shown in the following examples:
- C:\Program Files\Java\jdk1.8.0_20\jre (if you have installed JDK on the host computer)
- C:\Program Files\Java\jre1.8.0_20 (if you have installed only jre on the host computer)
- If you plan to install Remote Administrator Console, ensure that the host computer has a compatible Java version installed on it and update the JAVA_HOME environment variable point to this Java version.
Note: Ensure that JAVA_HOME is pointing to 64-bit jre.
For additional details about Java version details, see Support for Java.
Configure the ports
The Infrastructure Management Server uses several TCP control ports for its operations. You can configure the ports mentioned in this table during the installation of Infrastructure Management. Use the procedure to configure the port configuration in case of port conflict with another application installed on the same host.
Prepare to integrate BMC Atrium CMDB and CMDB Extension for Infrastructure Management
You have an option to integrate BMC Atrium CMBD after installing the TrueSight Infrastructure Management Server. However, if you want to integrate CMDB during the installation, ensure that you have:
- All the required BMC Atrium CMDB details for specifying during the Infrastructure Management installation process.
- Installed the latest supported BMC Atrium CMDB version mentioned in the System requirements and product compatibility for Infrastructure Management topic.
Complete the preinstall tasks for application high-availability mode
Component | Prerequisites |
---|---|
|
You have two options to configure Oracle:
To use a single Oracle instance, perform the following steps:
|
TrueSight Operations Management components |
|
Third-party load balancer |
|
Network | Ensure that:
Ensure that the following ports are available. |
Complete the preinstall tasks for high-availability cluster mode
- Ensure that you have completed all the required preinstallation tasks mentioned in above sections for individual primary and secondary computers.
- Ensure that the cluster configuration is of ‘node and cluster disk majority’ type.
- Ensure that the cluster name does not contain an underscore (_).
- Ensure that a visible quorum disk is available.
- Ensure that the HA installer files are not copied to the shared disk.
- Ensure that you have the identical operating system version (for example, Windows 2008 R2 Enterprise Server) on the primary and the secondary computers.
- Ensure that you have identical hardware configuration on the primary and the secondary computers.
- Ensure that the primary and the secondary computers are located in the same domain.
- Configure the logical IP address.
- Ensure that the primary and the secondary computers have identical time stamps.
- Ensure that the Microsoft Clustering software is installed on both the primary and the secondary computers.
- Ensure that you add the common logical IP address/host name to be allocated to the two computers to the domain name service (DNS).
- Map the disk to be shared between the two computers with the same directory name and/or directory path on both the computers.
- The IP address, disk, and network name must be present in the same group.
- Ensure that your cluster is configured correctly by running the
hostname
command in a command prompt window. - For HA installations on Solaris systems, ensure that this command returns the virtual host name and not the physical host name.
- VMware with VMWare Fault Tolerance (FT) operating system does not support the Infrastructure Management server installation in the high-availability cluster mode.
- For Windows 2019, perform the following tasks:
- Download the TrueSight Infrastructure Management Version 11.3.01 - Windows 2019 OS Cluster Support patch from the EPD site.
- Extract the file (setup.jar) to a temporary location.
- In the extracted Infrastructure Management 11.3.01 installation files, go to the Disk1 folder and delete the setup.jar file. Do this for both the primary and secondary server installation files.
- Copy the setup.jar file that you extracted in step 2 to the Disk1 folder.
Complete the preinstall tasks for disaster recovery mode
Ensure that you configure the Oracle database before you perform the following steps.
Note
The following steps are not mandatory. If you do not perform the following steps, ensure that the alias entry in the \etc\hosts file resolves to the expected host and should not be removed.
- (Standalone disaster recovery)
- On the DNS server, add an alias name for the primary TrueSight Infrastructure Management server. For example, Alias_1.
- If using the Oracle database, create two Oracle users and two Oracle report users, one each for the primary and recovery sites.
For example, db_user_pronet_tsim_a and db_user_pronet_tsim_a_dr; db_user_report_tsim_a and db_user_report_tsim_a_dr.
- (Application high-availability and disaster recovery)
- On the DNS server, add alias names for the primary and recovery TrueSight Infrastructure Management servers. For example, Alias_1 and Alias_2.
- Create four Oracle users and four Oracle report users, two each for the primary and recovery sites.
For example, db_user_pronet_tsim_a, db_user_pronet_tsim_a_dr, db_user_pronet_tsim_b, db_user_pronet_tsim_b_dr
db_user_report_tsim_a, db_user_report_tsim_a_dr, db_user_report_tsim_b, db_user_report_tsim_b_dr
Where to go from here
If you are installing the product, perform the other preinstallation tasks listed in the Preparing to install the TrueSight Operations Management solution page.
Comments
The statement "Ensure that the system default locale set to UTF-8 locale." is unclear. Is this done within TSIM configuration, or database configuration, or Operating system configuration and how?
Was non root install tested at least once ? lots of check missing, install end with WARNING ...
Hi Stephane Guedon,
AFAIK, it was tested. Just to be doubly sure, I am forwarding your query to the internal QA SMEs.
Sure it was not fully tested.. I've seen plenty error (crontab not check, log file created access not check ...)
Hi Stephane, We have tested non root user installation multiple times and some times the issues may be environment specific. We have few CFDs where if customer does not have expr, ed, umask etc the issues were reported and those validations are getting added in current release. Can you please share more details about what are the issues so that we can have a look at it.
Hi Niyati Shah,
Thanks for clarifying.
Hi Stephane Guedon,
Please do share the details with Niyati Shah (Niyati_Shah@bmc.com) and CC me (Harihara_Subramanian@bmc.com).
Copy-pasting Niyati's comment again (Just in case if it is not visible for you)
Hi Stephane, We have tested non root user installation multiple times and some times the issues may be environment specific. We have few CFDs where if customer does not have expr, ed, umask etc the issues were reported and those validations are getting added in current release. Can you please share more details about what are the issues so that we can have a look at it.
Regards,
Hari
Hello Stephane Guedon,
I am closing this thread based on the above inputs. You can share more details here below or you can email it to us.
This requirement "Ensure that the system default locale set to UTF-8 locale." is mandatory for installation TSIM on Windows?
Hi Shreya Gurukiran,
Applicable only to Linux.
Sure Harihara Subramanian thanks!! Have moved the UTF-8 locale content to the Linux section.
Regards,
Shreya
Hi Oleg Protokolov,
Thanks for your feedback. The statement 'Ensure that the system default locale set to UTF-8 locale' is applicable only to Linux and is not applicable to Windows. We have updated the doc to move the statement to the section 'Complete the additional tasks for Linux'. Since the required doc updates have been made, hence closing the comment.
Regards,
Shreya
Log in or register to comment.