Installing the Manager software in a stand-alone configuration

This topic describes how to install the BMC Database Automation (BDA) Manager software on a stand-alone server.

Before you begin

Make sure that the following prerequisites are met:

• Download the installation files as described in Downloading the installation files.

• Make sure that the PostgreSQL service is running and configured to start automatically at system restart. Depending on the version of Red Hat Enterprise Linux (RHEL) you are installing on, run either of the following:

  PostgreSQL and RHEL	Command
  PostgreSQL 11.x packages for managers running RHEL 7	/usr/pgsql-11/bin/postgresql-11-setup initdb; systemctl enable postgresql-11; systemctl start postgresql-11; ln -snf /var/lib/pgsql/11/data/ /var/lib/pgsql/ chown -H postgres:postgres /var/lib/pgsql
  PostgreSQL 11.x packages for managers running RHEL 6	service postgresql-11 initdb; chkconfig postgresql-11 on; service postgresql-11 start; ln -snf /var/lib/pgsql/11/data/ /var/lib/pgsql/ chown -H postgres:postgres /var/lib/pgsql
  PostgreSQL server 9.6.x packages for managers running RHEL 7.5	service postgresql-9.6 initdb; service postgresql-9.6 start; chkconfig postgresql-9.6 on ln -snf /var/lib/pgsql/9.6/data/ /var/lib/pgsql/ chown -H postgres:postgres /var/lib/pgsql
  PostgreSQL server 9.2.x packages for managers running RHEL 7	service postgresql initdb; service postgresql start; chkconfig postgresql on
  PostgreSQL server 8.4.20 packages for managers running RHEL 6 or RHEL 7	service postgresql initdb; service postgresql start; chkconfig postgresql on
  PostgreSQL server 8.1.23 packages for managers running RHEL 5	su -l postgres -c initdb; service postgresql start; chkconfig postgresql on

• Make sure that the Apache httpd service is configured to start automatically upon a system restart. To do so, run:

  chkconfig httpd on

• For BMC Database Manager to install and run successfully, you must make sure that you do not have SELinux enabled on your server.
• (Only if you are installing on RHEL 6 or RHEL 7) Make sure that you set the following directive in /var/lib/pgsql/data/postgresql.conf:
  Uncomment escape_string_warning and set it to off

• (Only if you are installing on RHEL 6 or RHEL 7 with PostgreSQL server 11.x) Make sure that the following lines are present in /var/lib/pgsql/data/pg_hba.conf:

  local 		GridApp 	tcrimi 						trust 
  host 		GridApp 	tcrimi 		127.0.0.1/32 	trust 
  host 		GridApp 	tcrimi		::1/128 		trust 
  host 		all 		all 	    <ip_address>   255.255.255.255 		trust

  • Restart the postgresql-11 service with the following command:

    service postgresql-11 restart

• (Only if you are installing on RHEL 7.5 with PostgreSQL server 9.6.x) Make sure that the following line is present in /var/lib/pgsql/data/pg_hba.conf:

  Note

  If the line is not present, add it.

  host    all         all        <ip_address>    255.255.255.255    trust

  • Restart the postgresql-9.6.x service with the following command:

    service postgresql-9.6 restart

• For additional requirements, including the Red Hat Package Manager (RPM) packages that must be installed on the OS for the Manager, see OS requirements.

To install the Manager software in a stand-alone configuration

mkdir -p /opt/bmc/BDA /app

ln -s /opt/bmc/BDA /app/clarity

1. To display the list of installed RPM packages, run the following command:

   rpm -qa

2. Check the list of installed RPM packages for a php package.
   If there is a php package, go to step 3. Otherwise, go to step 4.

3. To remove the php package, run the following command:

   rpm -e* <php_package_name>

4. To unpack and install the Manager software, run the following commands:
   
   1. Run tar xvzf <downloaded file BDA_<version>_Manager.tar.gz>
      The example download in Step 4a. would be for base versions that do not contain any patch updates.
   2. Run cd <extracted directory >

   3. Run ./install.sh

      To enable integration with BMC Cloud Lifecycle Management, type --clm. 

      Note

      Components required to enable integration with BMC Cloud Lifecycle Management are not installed by default. These RPMs are required only when performing PaaS provisioning with BMC Cloud Lifecycle Management. If you are performing a typical installation of BDA that does not require integration with BMC Cloud Lifecycle Management, run the install.sh script with no options.

      The following additional options and arguments are required for installing the Manager in a stand-alone configuration: 

      Argument	Description
      --help	Displays help information about the install.sh script and its arguments.
      --os	(Optional) If the OS version is not automatically detected, you can manually pass the OS version as a parameter. The value of the parameter can be RH5, RH6, or RH7.
      --silent	Use these options only for silent installation.
      	To enable the installer to accept the License Agreement automatically, you must provide the following details in the form of parameters: --country <country name> --state <state name> --locality <locality> --organization <company name> --organizational_unit_name <organization name> --mail <email id> --server_common_name --client_common_name <name of the client host>
      	This option must only be used for third-party certificates, and not for self-signed certificates. --use_tp_signed_cert <path where third-party signed certificates are stored>
      	--nossl Installs without enabling secure communication.
      --force	Use this option only if you want to install a Platform Manager version that is lower than the Platform Manager version already installed on a server. Note By default, the installer does not allow you to install a Platform Manager version that is lower than the existing version installed on a server.
      --clm	The installer installs the components required for integrating with BMC Cloud Lifecycle Management. Use this option if you plan on integrating BMC Database Automation with BMC Cloud Lifecycle Management.

5. To access the GUI by using the https protocol, install the Apache mod_ssl package, and run the following command:

   /app/clarity/var/www/mgmt/bin/enable_ssl.sh

   
   

   Note

   Running the enable_ssl script results in the use of the test Secure Sockets Layer (SSL) certificate that ships with the Apache server that came with Red Hat Enterprise Linux. For more information about how to replace this certificate with your own SSL certificate, refer to the Red Hat User documentation.

The software is now installed in the /app/clarity/dmanager directory and by default, GUI is available on port 80 (http protocol) and port 443 (https protocol) of the Manager server. For instructions to access the GUI, see Accessing the interface.

Where to go from here

See one of the following topics:

• Create user accounts
• Configure to support reports