This topic describes how you can install Application Server components on your computer by running the installation program from a wizard-based UI. During the installation process, you can choose whether to follow a typical or custom installation path. This topic provides the details for both options.
This topic provides the following information:
Related topics
Space requirements
A typical installation requires approximately 3 GB of available storage. The Data Warehouse aging configuration can be specified during installation and will impact the disk space required on the database server.
Before you begin
- The target computers must meet the requirements specified in System requirements.
- To aid in the installation process, fill out the Installation worksheets for Application Server.
- If you cannot run the installation program as a root user, you must perform the tasks described in Preparing to install as a non-root user and Preparing to install without a sysdba password.
- If you choose to enable TLS for internal communication between product components, complete the steps in Preparing for TLS enabled communication between internal database and product components.
Installation options
The following options are available for installing the Application Server components:
Install using the root user: You can use any existing user or create a new user for the product during installation. You can also enter the details required for setting up a shared repository.
If you do not have a sysdba password, follow the steps described in Preparing to install without a sysdba password, and then continue with Installing the Application Server and components.
If you have a sysdba password, continue with Installing the Application Server and components.
Note
- When installing as a root user, the installation wizard displays the option to set the name of the new user. If the user exists, that user is associated to a specific OS group (cpit - gid: 87654321). If this OS group does not exist, this OS group will be created. If the installer is executed by a user of the OS group, no changes will be applied to that user and associated groups.
- BMC strongly recommends that you use the
rootuser to install TrueSight Capacity Optimization. Several steps in the installation process (marked with
in the procedure below) are available only if you run the installer using the rootuser.
- Install using the non-root user: The default non-root user is cpit.
If you do not have a sysdba password, follow the steps described in Preparing to install without a sysdba password, and then continue with Installing the Application Server and components.
- If you have a sysdba password, continue with Installing the Application Server and components.
Information
Some of the screens during the installation process are available only when the installation is run using the root user.
To install the Application server components
Unzip and extract the installation files: In the temporary directory that you created, unzip and extract the installation archive by using the following commands.
Unzip command with example Unzip:
gunzip TSCO_AppServer_<ProdVer>_<OS>.tar.gzExample:
gunzipTSCO_AppServer_ver10.7.00_Linux.tar.gzExtract command with example
Extract:
tar -xvfTSCO_AppServer_<ProdVer>_<OS>.tarExample:
tar -xvfTSCO_AppServer_ver10.7.00_Linux.tarBest Practice
Ensure that the directory permissions are preserved during extraction to avoid any folder permission related errors when you install from a read-only location.
As a best practice, retain the installation archive if you plan to install additional machines.
Change the directory: After extracting the installation files, change to the directory where you extracted the install files. For example,
BCO/Disk1.Set the DISPLAY environment: Set the DISPLAY environment correctly to enable the Installer UI to launch.
Scenario Command If the computer has a local graphical console: Set the DISPLAY environment variable to start the installer UI locally. DISPLAY=<LocalIP Address>:0.0export DISPLAYIf the computer does not have a local graphical console: Set the DISPLAY environment variable to export to an XServer on a different workstation.
Note: On the workstation used to display the UI, provide access grants to every incoming X window. If the workstation is a Linux computer, or running X over a bash shell for Windows, type the command
xhost +DISPLAY=<WorkstationName>:0.0export DISPLAYNote
For launching the installer UI for Linux from the remote a Windows computer, see Forwarding using Xming and Putty
.Run the installation: At the shell prompt, type ./setup.sh and press Enter.
Tip
You can start another session and type
tail –fon the installation log (bco_install_log.txt) to view detailed messages during the installation that will help debug installation issues.Welcome screen and EULA: At the product installation Welcome screen, click Next. Agree to the End User License Agreement (EULA), and click Next again.
Directory Selection: In the Directory Selection screen, type the installation directory (default:
/opt/bmc/BCO) to which you want to install the product, or click Browse to select a directory on your system, and click Next.Avoid using the home directory of the user as the installation directory.- Enter a username: In the BMC TrueSight Capacity Optimization User screen, provide a user name (new or existing user) for running the product after the installation, and click Next.
The installer will not proceed with the default entry,
root, in the username box. Select the installation step: In the Installation Step screen, select Install the first machine and click Next.
(To install the Application Server components on additional computers, see Installing Application Server components on additional computers.)
- Select the type of installation: In the Select Install Setup Type screen, select any one of the following options and click Next.
- Typical Setup: Application Server: Install all Application Server components, including ETL Engine for troubleshooting purposes.
Custom Setup: Select the check box corresponding to the components you want to install.
Typical Setup: Application Server Screen Description/options Web Server Configuration Select a protocol to be used by the TrueSight Capacity Optimization console, and click Next. - HTTP - Select to use the HTTP protocol for transferring information. (Default Port: 8000)
- HTTPS - Select to use the HTTP protocol over SSL/TLS for transferring information. (Default Port: 8443)
Info: The Apache Web server installed by TrueSight Capacity Optimization will be used to set up the encryption for HTTPS. Shared Repository ConfigurationSelect either of the configuration options, type the details as required, and click Next. - Local Repository: Select this option if you have a single Application Server.
Shared Repository:
In an environment that has multiple Application Servers, you must share the Content Repository directory.
The Content Repository directory needs to be accessed in read/write mode by the web console and Primary Scheduler, and in read-only mode by the web application component. In addition, the BMC TrueSight Capacity Optimization user on each computer must have permissions to read, write, and update files in the Content Repository. For users to have the required permissions, the UID of the cpit users must be same across all Application Servers in an environment.
To share the Content Repository between two Application Servers AS1 that is running the web application component, and AS2 that is running the Data hub and Primary scheduler, do the following:
- Run the installer first on AS1 and then on AS2.
- Share the Content Repository that has been created by the installer on each Application Server via a shared file system (that is, NFS, by configuring a mount point on all servers, that maps an external storage).
- Copy the Content Repository both directory and subdirectories structure, from either AS1 or the AS2 to the shared Content Repository location. For more information, see System-level administration overview.
- Mount the Content Repository location from both AS1 and AS2.
Note
Due to operating system limitations, only NFS mount is supported on Oracle Solaris 10.x.
Select any one of the following options, and enter the required information:
NFS: If you are mounting the repository folder from a network share through Network File Sharing.
- Server: Name of the NFS server. For example,
server1 - Path: Address of the NFS server.
For example,nfs://server1/share/path
- Server: Name of the NFS server. For example,
- CIFS: If you are mounting the repository folder from a network share through a Common Internet File System.
- Shared URL: Address of the shared location in URL format.
- User: Name of the user.
- Password: User password.
- Domain: Name of the domain to which you want to connect.
Database Information - Select Database type Select the Database you want to use for installation:
- Oracle - Select to use the Oracle Database.
Expand the following section to view the details required to use a PostgreSQL database for installing TrueSight Capacity Optimization.
If you want to use Oracle database as source for an ETL, ensure that you configure the Oracle database and follow Using Oracle database as source for an ETL.
Database Information - Connection details Enter information for connecting to and configuring the database.
Select Database connection properties OR LDAP Database connection properties (Advanced) or Custom JDBC connection URL (Advanced) for advanced settings. Property Description Database connection properties Use SID (for Oracle only) System ID or service name. Specify the details for the database instance that your database administrator created. Use Service Name (for Oracle only) Database Host Name Name of the database host where the database schema is stored. Listener Port Listener port number for the database. (Default: 1521) LDAP Database connection properties (Advanced) LDAP Host Name Host name or IP address of the LDAP server.
Note: Only LDAP servers that allow anonymous bind connections are supported.LDAP Port Port that should be used for connecting to the LDAP server. Service Name Service name for the database instance. LDAP Context Node from which the database instance search is initiated.
Custom JDBC connection URL (Advanced) JDBC URL JDBC URL of the database through which it is referenced.
Syntaxfor Oracle:jdbc:odbc:<data source name>From the Creation of database users and tablespaces section, select Installer shall create Database users and tablespaces OR Database users and tablespaces have already been created externally for advanced settings. Property Description Installer shall create Database users and tablespaces Privileged User Name Name of the user setting up the database schema. This name is either sys or another user that your database administrator has created for the purpose. Privileged User Password Password of the user that is setting up the database schema. Tablespaces parent directory Path where the datafile is saved by your database administrator.
Some of the common ways to specify the datafile path are:
- Specify an ASM (Automatic Storage Management) path. For example,
+ORATBS1/bcoasm/datafile. - Specify a Fully qualified path for the datafile stored on the TrueSight Capacity Optimization database server. For example,
/apps/oracle/product/SID. In a non-ASM environment, this path must exist on the database. Typically, the path should be changed from the default
/opt/bmc/BCOpath to a directory on the database side.
Testing database connectivity
Usesqlplusfrom the command line, and connect to the TrueSight Capacity Optimization database as thesysuser.export ORACLE_HOME=[Oracle Client Home]
export ORACLE_SID=[Oracle Alias]
$ORACLE_HOME/bin/sqlplus sys@$ORACLE_SID AS SYSDBADatabase users and tablespaces have already been created externally Select this option if you have already created database users and tablespaces for your database externally (manually). Testing database connectivity
Usesqlplusfrom the command line, and connect to the TrueSight Capacity Optimization database as the[DB Owner]user.export ORACLE_HOME=[Oracle Client Home]export ORACLE_SID=[Oracle Alias]export DBUSR=[DB Owner]
$ORACLE_HOME/bin/sqlplus $DBUSR@$ORACLE_SIDFrom the Names for database users and tablespaces section, select Use defaults or Allow me to customize names for advanced settings. Use defaults Select this option if you want to use the (default) database user names and tablespace names provided by TrueSight Capacity Optimization. Allow me to customize names Property Description TNS Names File Location
Location of tnsnames.ora, a configuration file that defines database addresses for establishing connections. It is normally located in /<Oracle Home>/network/admin.Catalog Tablespace Name of the tablespace for the database Catalog. Catalog Index Name of the catalog index. Data Tablespace
Name of the database tablespace where all the data is stored. Data Index
Name of the data index. Views Tablespace
Name of the tablespace where all database views are stored. Console Role
Role of the database owner. DB Owner
Name of the database owner. DB Owner Password
Password of the database owner. Views Role
Database role used by the console for storing view configuration. Views User Name
Name of the database user used by the console for storing view configuration. Views Password
Password of the database user used by the console for storing view configuration. Reports Role
Name of the database role that the console uses to access data for Data Marts and Advanced Reporting public views. Reports User Name
Name of the database user that console uses to access data for Data Marts and Advanced Reporting public views. Reports Password Password of the database user that console uses to access data for Data Marts and Advanced Reporting public views. Data Warehouse Aging Configuration Enter the following information and click Next. Property Description Use default aging configuration Use the default setting for aging configuration, which is approximately 280 GB space for the database considering 5000 systems. This configuration allows you to import historical data from the last two months. Specify custom aging configuration
Set the following Data Warehouse aging parameters for System Data and Business Driver Data. This aging configuration will affect the amount of storage used by the Data Warehouse.
- Detail: Specify Detail values that will be summarized in days or weeks or months or years for System and Business Driver Data.
- Hour: Specify Hourly values that will be summarized in days or weeks or months or years for System and Business Driver Data.
- Day: Specify Daily values that will be summarized in days or weeks or months years for System and Business Driver Data.
- Month: Specify Monthly values that will be summarized in days or weeks or months or years for System and Business Driver Data.
Detail Hour Day Month System Business System Business System Business System Business Short One week One month Two months One year Four months Two years One year Ten years Medium Two weeks One month Four months One year Eight months Two years Two years Ten years Long One month One month Six months One year One year Two years Three years Ten years Note: The summary field below the parameter entry boxes will be updated with the actual total amount of storage that will be used by the DWH for 5000 systems, based on your custom values. This information provides a good overview of your configuration.
To finish a Typical Install on the first computer, go to Step 10.
Custom setup
Custom setup Screen Description/Options Select the Components Select any or all of the following components to install: Component Description TrueSight Capacity Optimization 10.7.00 Installation Selects all components. If you select this option, the installation is similar to a Typical install. Install Database Schema 10.7.00
Install and set up the database schema.
Note
By default, the Database Schema will be installed when you install the Application Server. You cannot clear the option selected for installing the Database Schema.
Install Application Server 10.7.00
If you install the Web Server before installing Datahub, an error is displayed on the web console home page.
The Application Server computer will stay in a suspended state until the Datahub is installed and registered in the database.Install the following Application Server components: - Install Web Server 10.7.00: Install the web server.
Note: An Apache Web Server is installed, even if a server already exists. - Install Datahub 10.7.00: Install the TrueSight Capacity Optimization Datahub.
- Install Primary Scheduler 10.7.00: Installs the Primary Scheduler.
Install ETL Engine Server 10.7.00 Install the ETL Engine Server component: - Install ETL Engine 10.7.00: Install the ETL Engine.
Web Server Configuration The task from this screen onwards (including this screen) is the same as that for performing a Typical Setup.
Connect with existing TrueSight Capacity Optimization Server: Select one of the options given below:
Field Description Direct connection This computer is able to directly access the Database. Enter details for the Web Server Address, Protocol, Web Port. Remote connection This computer is located on a remote network with an unstable or slow connection, and only has HTTP visibility to the DataHub. Installation Preview: In the Installation Preview screen, verify all the installation settings, and click Install.
The installation can take up to 15 minutes.
The Installation Summary screen provides information about whether the installation was completed successfully. You can click View Log from this screen to see more details. Otherwise, proceed to step 12.- Click Done to exit the installer.
(Optional) If required, add additional computers to your deployment. For more information, see Installing Application Server components on additional computers.
Best Practice
To block the upload of malicious files to the Application Server file system, install antivirus software on the systems that host the Application Server.
Troubleshooting
For information about installer-related error codes, see Working with error codes.
Where to go from here
Before you can start using the product, you must verify the installation and configure TrueSight Capacity Optimization.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks
6 Comments
Melody Locke
Melody Locke
Melody Locke
Vikram Shinde
Hi Team,
Use
sqlplusfrom the command line, and connect to the TrueSight Capacity Optimization database as the[DB Owner]user.does this user should have SYSDBA privileges? else can we use BCO_OWN user to connect to database while installation? If sysdba privileges are assigned to BCO_OWN while installation, can they revoked after installation?
Regards,
Vikram
Bipin Inamdar
Bipin Inamdar