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

  • 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.
  • Ensure that the system default locale set to UTF-8 locale.
  • 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:

    1. On the host computer, open the Local Group Policy Editor by selecting Start > Run, and type gpedit.msc.
    2. Expand the following folder: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Temporary folders.
    3. Double-click the following options to set them to Enabled:
      • Do not delete temp folder upon exit
      • Do not use temporary folders per session
    4. On the host computer, open the Registry Editor by selecting Start > Run and typing regedit.
    5. Expand the following folder: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.
    6. Set the value for PerSessionTempDir and DeleteTempDirsOnExit to 0.
    7. 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 this only as a non-root user.

  • Ensure that you install the csh and tcsh shells.
  • Ensure that you install the 'ed' editor for Linux.
  • 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 :

        1. 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.
        2. 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 and MCELL_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.

       Steps to install Arial fonts
      1. Ensure that the user who plans to install or upgrade Infrastructure Management has read, write, and execute permissions to the following:
        • The ../fonts folder that contains the Arial*.ttf file. It is usually located at usr/share/fonts or etc/fonts folder.
        • /pw/apps3rdparty/graphing/ folder
      2. Run the following commands to install Ghostscript:
        • yum install ghostscript
        • yum install ghostscript-fonts

        If you plan to install Infrastructure Management in the HA mode

        Ensure that you run the preceding commands on both the primary and secondary servers.

    • 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

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.

     Character Sets
    • While creating the Oracle database instance, specify the following character sets:
      • Database Character Set to AL32UTF8.
      • National Character Set to AL16UTF16.
      • If you set the NLS_LENGTH_SEMANTICS to BYTE, set the DB_BLOCK_SIZE value to 8192.

      • If you set the NLS_LENGTH_SEMANTICS value to CHAR, set the DB_BLOCK_SIZE value to 16384.

      • Use the default values for all the other fields.

  • 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.

     Perform the following steps
    1. Install the following packages. See the Oracle documentation for installation guidelines.
      • SQL*Plus Instant Client package
      • Either the Basic Instant Client package or the Lightweight Instant Client package
    2. If the password file is not created by default, create the password file as follows:
      1. Go to the ORACLE_HOME directory in which the Oracle server is installed and run following command. See the Oracle documentation for more information about creating the password file.

        ORAPWD FILE=filename [ENTRIES=numusers] [FORCE={Y|N}] [IGNORECASE={Y|N}]
        [NOSYSDBA={Y|N}]
        

        For example,

        orapwd file=samplePasswordFile entries=5 force=N ignorecase=Y

      2. The REMOTE_LOGIN_PASSWORDFILE parameter is exclusive by default. If it is not, set it to exclusive in the Oracle database initialization file as follows. If the Oracle database initialization file does not exist, create it executing the CREATE SPFILE FROM PFILE; command.

        REMOTE_LOGIN_PASSWORDFILE=exclusive

        If the SID is ORA112DB, the database initialization file is named initORA112DB.ora

      3. Restart the database. For more information, see Stopping and starting the Oracle database.
  • 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

     Steps to test the remote connectivity
    1. From the Oracle Instant Client, connect to the remote Oracle database as follows:

      sqlplus <user name>/<password>@//<database_hostname>:<Port>/<SID> [as sysdba]
      

    2. (Oracle 12c only) To allow the Infrastructure Management client connections to connect to the Oracle Pluggable Database (PDB) through JDBC, add the USE_SID_AS_SERVICE_<listener_name>=on entry in the ORACLE_HOME/network/admin/listener.ora file.

      Note

      Do not set the USE_SID_AS_SERVICE_<listener_name>=on parameter if you are using Oracle RAC with a SCAN listener.

    3. (Oracle 12c only) Reload the listener service by using the $ lsnrctl reload command.
      You can now connect to the PDB by using the jdbc:oracle:thin:@<oracle_host_name>:1521:pdb1 URL.
  • 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 the lsnrctl 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. 

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.

     Click here for more details

    Notes

    • Only a user with SYS or SYSDBA privileges can run this script.
    • Run this script on the Oracle server.
    • Use the Auto Memory Management (AMM) option for setting the memory_max_target and memory_target parameters.
    1. Based on your Oracle version, navigate to the following folder and copy the set_system_parameter_oracle_pnet.sql script to the Oracle server:
      • (Windows) /Utilities/oracle/11G or /Utilities/oracle/12C/CDB
      • (Linux) Utilities\oracle\11G folder or the Utilities\oracle\12C\CDB
    2. Run the following command: 
      • (Oracle 11.xG) sqlplus SYS/<password>@ <SID>/<service_name> as sysdba
      • (Oracle 12c) sqlplus SYS/<password>@ <CDB>/<service_name> as sysdba
    3. Run the set_system_parameter_oracle_pnet.sql script on the Oracle server.
      SQL>@set_system_parameter_oracle_pnet.sql
    4. Restart the Oracle database. The script verifies whether the set parameters appear in the Oracle database. For more information, see Stopping and starting the Oracle database.
    5. You can create new users using Infrastructure Management installer. It is convenient to control and access the database from the TrueSight Infrastructure Management during the installation process. However, if you have already created users in Oracle, you can create user accounts and tablespaces for these users using any one of the following methods:
      • (Recommended) Script method: Run the run_oracle_db_scripts.sql script.

        •  Running the script in a standalone Oracle environment
          1. Back up the SPFILE file.

          2. Based on your operating system, navigate to the following folder and access the custom database scripts applicable for your operating system:

            <operating system>\Utilities\oracle

          3. Create a temporary directory on the computer where the Oracle database is installed.

          4. Copy all the files in the \Utilities\oracle directory to the temporary directory you created.

          5. Log in to SQLPlus as sysdba by running the following command:

            sqlplus sys/sys_pwd@ORACLE_SERVICE_NAME as sysdba

          6. Run the run_oracle_db_scripts.sql script by entering by the following command:

            @run_oracle_db_scripts.sql

          7. Provide the following information:

            1. Type a tablespace name (default name is pnet_ts.)

            2. Type the tablespace size (specify smallmedium, or large. A small deployment creates a 15GB tablespace. A medium or large deployment creates a 30GB tablespace. The default tablespace size is small.)

            3. Specify a directory where you want the tablespace to be created.

            4. Type the main user name (default user name is proact.)

            5. Type a password for the main user (default password is proact.)

            6. (Oracle 11.2 only) Restart the database. For more information, see Stopping and starting the Oracle database.

            7. (Oracle 11.2 only) Specify sys username, password, and Oracle SID.

            8. (Oracle 11.2 only) If you have run the set_system_parameter_oracle_pnet.sql script, you can exit the script by pressing the Ctrl+C or Ctrl+D keys.

            The script creates the Oracle system parameters, tablespaces, and the initial user accounts and permissions.

            Note

            Only one data file is added to the tablespace created by the script. However, you can add more data files to the same tablespace before the tablespace is filled up, if required. To add more data files, run the following command:

            ALTER TABLESPACE PNET_TS ADD DATAFILE '<path>' SIZE 1G AUTOEXTEND ON NEXT 500M MAXSIZE 30G;

          8. Log in to SQLPlus as sysdba by running the following command:

            sqlplus sys/sys_pwd@ORACLE_SERVICE_NAME as sysdba

          9. Enter the following commands:

            Alter system set memory_max_target=<mem_amount>M scope=spfile;
            Alter system set memory_target=<mem_amount>M scope=spfile;

            mem_amount is the maximum amount of memory that you can allocate for your Oracle database instance. The memory for each parameter must be set to at least 50% of the total memory available for one Oracle database instance.

            For example, if the RAM size of the computer on which Oracle is installed is 4GB, the memory_max_target and memory_target parameters must be set to 2GB as shown:

            Alter system set memory_max_target=2000M scope=spfile; 
            Alter system set memory_target=2000M scope=spfile;
          10. Restart the database. For more information, see Stopping and starting the Oracle database.

        •  Running the script in an Oracle RAC environment

          Perform the following tasks from any of the available RAC nodes to set the parameters or to create tablespaces and user accounts.

          Note

          The ORACLE_SID for the RAC is different from the RAC Service Name. The following sections refer to the service as RAC_ORACLE_SERVICE_NAME. For example, a RAC setup can have SIDs for node1 as OR112DB1, for node2 as OR112DB2, and the service name of the RAC setup can be ORA112DB.

          1. (Linux or Solaris) Set up the operating system environment variables for Oracle.

            $ . oraenv
            ORACLE_SID = [oracle] ? <RAC_ORACLE_SERVICE_NAME>

          2. Navigate or change the folder to the directory where you copied the BMC-provided Oracle scripts.

          3. Log in to SQLPlus by using the following command:

            $ sqlplus sys/<sys_pwd>@<RAC_ORACLE_SERVICE_NAME> as sysdba

          4. Run the run_oracle_db_scripts.sql script:

            SQL> @run_oracle_db_scripts.sql

          5. Start the Oracle RAC. For more information, see Stopping and starting the Oracle database.

          6. Create a back up copy of the SPFIle.

             To back up the SPFILE file in Oracle RAC

            You must back up the SPFILE from another SQLPlus prompt:

            1. Identify an AMS instance by entering the following command:

              ps -ef|grep smon|grep ASM

              For example:

              oracle 3023 1 0 Jun04 ? 00:00:19 asm_smon_+ASM1 is displayed. The +ASM1 is the ASM instance.

            2. Go to <ORACLE_HOME>/grid/bin of any Oracle RAC node.

            3. At the command prompt, enter the following command:

              $ . oraenv

              ORACLE_SID = [OR112DB] ? +ASM1

            4. Enter the following command:

              $ asmcmd

            5. Change the directory to ASM disk.

              For example: ASMCMD>cd<ASM_diskname>/

            6. Access the Oracle RAC service by running the following command:

              ASMCMD> cd <RAC_ORACLE_SERVICE_NAME>

            7. Determine the name of the SPFILE by running the following command to list the contents of the directory:

              ASMCMD> ls

              The contents of the directory are displayed as follows:

              CONTROLFILE/
              DATAFILE/
              ONLINELOG/
              PARAMETERFILE/
              TEMPFILE/
              spfile<RAC_ORACLE_SERVICE_NAME>.ora

            8. Create a backup copy of the SPFILE file by running the following command: 

              ASMCMD> cp spfile<RAC_ORACLE_SERVICE_NAME>.ora BackUpDirectoryName/RAC_ORACLE_SERVICE_NAME.ora_backup

  • 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: 

    1. To check the type: 

      Select log_mode from v$database;

    2. 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

(Optional) You can manually set the system parameters, create tablespaces, user accounts, and permissions for Oracle single instance database and Oracle RAC.

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.

 Manually creating tablespaces and user accounts

Recommendations and restrictions for creating Oracle objects

Ensure that the following guidelines are met while creating the Oracle objects:

  • The Oracle user name must start with an English alphabet.

  • The tablespace name can start either with a letter or an underscore (_) special character.

  • The Oracle user name and tablespace name can contain special characters within them. The special characters $, #, and _ are allowed.

  • The Oracle user name, tablespace name, and password must not include a space between the characters.

  • The data file entry in a tablespace can have a space between characters. For example, C:\apps<space>oracle\oradata\main<space>ts.dbf.

  • The Oracle user name, tablespace name, and password length must not exceed thirty characters.

Setting the system parameters

- Use the ALTER SYSTEM SET command by using SQLPlus to set the following parameters.

bitmap_merge_area_size =0 scope =spfile; commit_point_strength =0 scope =spfile; db_block_checksum =typical scope =spfile; db_flashback_retention_target =0 scope =spfile; db_writer_processes =2 scope =spfile; fast_start_mttr_target =0 scope =spfile; fast_start_parallel_rollback =LOW scope =spfile; job_queue_processes =20 scope =spfile; parallel_execution_message_size =4096 scope =spfile; remote_login_passwordfile =EXCLUSIVE scope =spfile; replication_dependency_tracking =FALSE scope =spfile; session_cached_cursors =75 scope =spfile; session_max_open_files =20 scope =spfile; streams_pool_size =0 scope =spfile; timed_statistics =TRUE scope =spfile; undo_management =AUTO scope =spfile; undo_retention =10800 scope =spfile; shared_pool_size =0 scope =spfile; java_pool_size =0 scope =spfile; large_pool_size =0 scope =spfile; processes =1000 scope=spfile; open_cursors=4000; sga_target=0 scope=spfile; pga_aggregate_target=0 scope=spfile;

- Set the memory_max_target and memory_target parameters to the maximum memory you can allocate.

The memory for each parameter must be set to a minimum 50% of the total memory available for one Oracle database instance. While setting these parameters, use the Auto Memory Management (AMM) option.

For example, if the RAM size is 4GB, the following parameters must be set to 2GB:

Alter system set memory_max_target=2000M scope=spfile; 
Alter system set memory_target=2000M scope=spfile;

Creating tablespaces

You must create a main and a temporary tablespace, extend the tablespace, and create user accounts and permissions. Use the following procedures.

To create a tablespace

Run the run_oracle_db_scripts.sql script, and when prompted use the following guidelines:

  • Guidelines for tablespace size

    • Small: 15 GB

    • Medium: 30 GB

    • Large: 30 GB

  • Guidelines for the data file sizes:

    • Initial SIZE: 1 GB

    • REUSE AUTOEXTEND ON NEXT: 500 MB

    • MAXSIZE: 15 GB or more (as per your requirement)

CREATE TABLESPACE <tablespace name> DATAFILE '<path>' SIZE 1G REUSE AUTOEXTEND ON NEXT 500M MAXSIZE 15G; Alter system set memory_target=2000M scope=spfile; CREATE TEMPORARY TABLESPACE <temporary tablespace name> TEMPFILE '<path>' SIZE 200M REUSE AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED;


To extend the tablespace

Only one data file is added to the tablespace created by the script. To extend or add more data files to the same tablespace before the tablespace is filled up, use the following command:

ALTER TABLESPACE PNET_TS ADD DATAFILE '<path>' SIZE 1G AUTOEXTEND ON NEXT 500M MAXSIZE 30G;
To create user accounts and permissions

Create the following database users and grant the permissions mentioned in the following procedure:

  • A main or schema user. By default it is proact. This user has the permission to store the Infrastructure Management data. You can configure the name and password.

  • A report user. This user has the permission to access the IInfrastructure Management data.

  1. Create main and report users:

    CREATE USER <userName> IDENTIFIED BY <passwd>;
    ALTER USER <userName> DEFAULT TABLESPACE <tablespace name>; ALTER USER <userName> TEMPORARY TABLESPACE <temporary tablespace name>;


    Where the <userName> is the user being created and <passwd> is the user password. The user is assigned the default tablespace and temporary tablespace. 

  2. Grant privileges to the users.

    GRANT <privilege> TO <userName>;

    <privilege> is the permission and <userName> is the user to whom the permission is granted.

  3. Grant the following permissions for the schema user:

    grant connect
    grant resource
    grant create view
    grant select_catalog_role
    grant execute_catalog_role
    grant gather_system_statistics
    grant select any table
    grant select on dba_data_files
    grant select on dba_temp_files
    grant select on dba_jobs_running
    grant select on dba_jobs
    grant select on dba_scheduler_jobs
    grant QUERY REWRITE
    grant UNLIMITED TABLESPACE
    grant select on sys.v_$parameter
    grant select on sys.dba_free_space
    grant select on sys.dba_tablespaces
    grant select on sys.v_$session
    grant select on sys.v_$lock
    grant select on sys.dba_jobs
    grant select on sys.v_$waitstat
    grant select on sys.v_$sysstat
    grant select on sys.v_$librarycache
    grant select on sys.v_$rowcache
    grant select on sys.dba_users
    grant select on sys.dba_roles
    grant select on sys.dba_tab_privs
    grant select on sys.dba_data_files
    grant select on sys.dba_temp_files
    grant select on sys.v_$instance
    grant select on sys.v_$rollname
    grant select on sys.v_$rollstat
    grant select on sys.v_$system_event
    grant select on sys.v_$log
    grant select on sys.v_$archive_dest
    grant select on sys.v_$database
    grant select on sys.props$
  4. Grant the following permission for the report user:

    grant connect
  5. To create a permanent password that will never expire, use the following commands:

    CREATE PROFILE <UserName>_PROFILE LIMIT PASSWORD_LIFE_TIME UNLIMITED FAILED_LOGIN_ATTEMPTS UNLIMITED; 
    ALTER USER <UserName> PROFILE <UserName>_PROFILE; ALTER USER <report UserName> PROFILE <UserName>_PROFILE;
  6. Restart the Oracle database instance after setting all the above parameters. If you are using Oracle 12c, open all the Pluggable Databases (PDBs) relevant to Infrastructure Management before restarting. For information about stopping and starting the Oracle database, see Stopping and starting 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.
  1. Navigate to the Utilities\oracle folder.

    For example, cd Utilities\Oracle

  2. 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
  3. 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.

     Non-root permissions

    (Linux) You can install the Integration Service as a root user as well as a non-root user. However, to enable non-root users to install the Integration Service, as a root user, you need to provide the following permissions to the the non-root user. 

    • Provide read, write, and execute permissions for the following directories:
      • Installation directory (destination directory where you are planning to install the product)
      • /opt/bmc directory to create ProductRegistry.xml file
      • /etc directory to set environment variable
      • /etc/patrol.d directory to create patrol security
      • /etc/init.d/etc/rc.d/rc0.d/etc/rc.d/rc1.d/etc/rc.d/rc3.d, and /etc/rc.d/rc5.d directories to create service
      • /tmp and /var/tmp directories
    • Provide read and write permissions for the following files and directories:
      • /etc/csh.cshrc file
      • /etc/profile directory to set environment variable permission 
      • (Remote cell on AIX only/home directory
    • If the init file is not copied to the /etc/rc3.d directory, the Integration Service corresponding to the init file is not listed as installed (in the list of existing Integration Service installations) during installation of other integration services.
    • Ensure that you remove the /etc/bmc.cshrc and /etc/bmc.profile files if they already exist. 

    Note:

    Installing the Integration Service with the non-root user is supported only on the Linux operating system. It is not supported on the Solaris or AIX operating system.

  • You can install multiple instances of an integration service on a same host machine. However, each Integration Service must be connected to a 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.

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.

 Ports that can be configured during the installation of Infrastructure Management
PortDescriptionProcedure to configure the port
80Apache HTTP port used for Web browser requests
  1. Open the appropriate files for your operating system:
    • (Linux)/usr/pw/apache/conf/httpd.conf
    • (Windows): pw\ApacheGroup\Apache\conf\httpd.conf and pw\pronto\conf\pronet.conf
  2. Search for the string Port 80 and replace the value 80 with the required port number.
  3. Search for the string Listen 80 and replace the value 80 with the same port number that you provided in the previous step.

  4. Save and exit the .conf files.

  5. (Optional) If you change the default Apache HTTP port number, ensure that you update the SAP port number in the CloudAdapter.xml file and the accessPointUrl port number.

     To update CloudAdapter.xml
    1. Open the CloudAdapter.xml file located in the pw\pronto\conf folder.
    2. Update the SAP port number:

      <param>
         <name>sapprotocol</name>
         <value>{bppmCentralProtocol}</value>
      </param>
      <param>
        <name>saphost</name>
          <value>{bppmCentralHost} (Host name of Central Server)</value>
      </param>
      <param>
        <name>sapport</name>
          <value>{bppmCentralPort} (Infrastructure Management port default is 80)</value>
      </param>
     To update the accessPointUrl port number
    1. Roll back the existing published SAI web service from the UDDI server by running the following command:
      bppmsai_uddi_unpublish
    2. Update the port number in bmc.bppmsaiws.accessPointUrl located in the bppmsai_uddi_registry.properties folder.
    3. Publish the SAI web service to the UDDI server by running the following command:
      bppmsai_uddi_publish
443Apache HTTP port used for Web browser requests in HTTPS mode
  1. Open the appropriate files for your operating system:
    • (Linux)/usr/pw/apache/conf/httpd.conf
    • (Microsoft Windows):pw\ApacheGroup\Apache\conf\httpd.conf and pw\pronto\conf\pronet.conf
  2. Search for the string VirtualHost default: 443 and replace the value 443 with the required port number.
  3. Search for the string Listen 443 and replace the value 443 with the same port number that you provided in the previous step.
448Apache HTTPS port used by the Infrastructure Management server to connect to Remedy Single Sign-On for authentication
1099Used by the administrator console to connect to the Infrastructure Management Server

Change the value of the pronet.rmi.port property to the new port number in your operating system:

  • (Microsoft Windows)pw\pronto\conf\pronet.conf
  • (Linux): pw/pronto/conf/jserv.properties
3084Enables Impact Administration Server actions to be triggered from the cell
  1. Update the new changes in the pw\pronto\conf\ias.properties file.
  2. Ensure that the cell is running.
  3. Restart TrueSight Infrastructure Management server.
3115Used as a gateway from the cell to Service Desk Integration Gateway
  1. Update the port in the files /pw/integrations/ibrsd/conf/IBRSD.dir and /pw/server/etc/mcell.dir.
  2. Restart the Service Desk Integration Gateway.
  3. Restart the BMC PraoctiveNet Cell.
  4. Restart TrueSight Infrastructure Management server.
7777BMC Atrium CMBD port
  1. In the Configuration task selection page, under Integration Configuration Tasks, select Atrium CMDB - Enable and Configure
  2. In the Integrating with CMDB page, provide the following details, and click Next.
    • CMDB Host — Host name of the CMDB or BMC Remedy Action Request (AR) System Server

    • CMDB Port — BMC Atrium CMDB or AR System Server port number. The default is 0. If BMC AR System Server is configured with a portmapper, enter port 0.
    • CMDB User — User name required to log on to the AR System Server. The default is Demo.
    • CMDB Password — Password required to log on to the AR System server
    • UDDI Host — Host name of the UDDI registry for BMC Atrium CMDB
    • UDDI Por — Port number of the UDDI registry for CMDB. The default is 7777.
    • UDDI User — UDDI registry user name. The default is Admin.
    • UDDI Password — UDDI registry password
9843

BMC Server Automation port

  1.  In the Configuration task selection page, under Integration Configuration Tasks, select BMC Server Automation - Enable and configure.
  2. In the Connecting to BMC Server Automation page, provide the following details and click Next.
    • Application server — BMC Server Automation application server name
    • Web service port — Web service port number required to connect to the BMC Server Automation server. The default web service port number is 9843.
    • User — User name for the BMC Server Automation server
    • Password — Password for the BMC Server Automation server
    • Role — Role that is defined to grant permissions to the BMC Server Automation user. The default is BLAdmins.
12123Agent Controller listens for JServer on this port.
  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agentcontroller.port property to the new port number.
  2. Restart the system by running the following command: pw system start
12124

Local IS agent port.

  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agent.port=12124 property to the new port number.
  2. Restart the system by running the following command: pw system start
12128Jserver RMI port 

Change the value of the pronet.rmi.jserver.port property to the new port number in your operating system:

  • (Microsoft Windows): pw\pronto\conf\pronet.conf
  • (Linux): /pw/custom/conf/pronet.conf

Update the port information in the following files:

  1. <Remote Admin Installation Directory>\Infrastructure Management Admin\admin\etc\ix.properties

    # The JServer port on which IX will be communicating for authentication and authorization
    # purpose. IX also uses this port for fetching certain configuration related data
    jserver_comm_port=<Port number on which TrueSight Infrastructure Management Server Integration Service is running>
  2. <Remote Admin Installation Directory>\Infrastructure Management Admin\admin\pronto\conf\pronet.conf

    # Port Number used by RmiRegistry
    pronet.rmi.jserver.port=<Port number on which TrueSight Infrastructure Management Server RMIRegistry is running>

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:


Complete the preinstall tasks for application high-availability mode

 Prerequisites for application high-availability mode


ComponentPrerequisites


Database

  • Application-level HA is supported only with an Oracle database. You cannot configure application-level HA with the embedded SAP SQL Anywhere database. If you are using the embedded SAP SQL Anywhere database, consider the HA cluster mode.
  • BMC recommends that you use Oracle RAC.

You have two options to configure Oracle:

  • Use two different Oracle instances – the users can be created in advance or during installation.
  • Use a single Oracle instance – two sets of users need to be created in advance.

To use a single Oracle instance, perform the following steps:

  1. From the Infrastructure Management installation files, copy the Utilities folder to the secondary server.
  2. From a command prompt on the secondary server, go to the Utilities\oracle\common folder.
  3. Run the following commands:
    sqlplus sys/<password>@INSTANCENAME as sysdba
    @create_pnet_user_with_grants.sql <Name of table space created for the primary server>
    For example:
    @create_pnet_user_with_grants.sql PNET_TS
  4. Enter the values of the proact and reporting user username and passwords that are different than the primary server.


TrueSight Operations Management components
  • TrueSight Presentation Server version 10.7 and later.
  • Two TrueSight Infrastructure Management servers version 10.7 and later, designated as the primary and secondary Infrastructure Management servers.
  • The primary and secondary Infrastructure Management servers must have identical hardware and operating system configuration.
    See the hardware and operating system requirements.

Third-party load balancer

  • A third-party load balancer with reverse proxy configuration support.
  • If using a software-based load balancer, you must install it on a separate server.

    Tip

    If you choose to use NGINX as the load balancer, you can use the attached file as a server configuration example.

  • To detect the active and standby nodes, configure the load balancer to check the HTTP response codes for the following URLs:

    https://<primary hostname>/jsp/ShowError.jsp

    https://<secondary hostname>/jsp/ShowError.jsp

    HTTP response 200 - active node
    HTTP response 503 - standby node

Network

Ensure that:

  • Latency between the nodes is consistently not more than 20 ms
  • A minimum bandwidth of 20 Mbps is available at all times

Ensure that the following ports are available.


Complete the preinstall tasks for high-availability cluster mode

 Prerequisites 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.

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_drdb_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_adb_user_pronet_tsim_a_dr, db_user_pronet_tsim_b, db_user_pronet_tsim_b_dr
      db_user_report_tsim_adb_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.  

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Oludare Ogunmadewa

    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?

    Aug 08, 2019 12:11