Installing the Manager software in a Standalone configuration

This topic describes how to install the BMC Database Automation Manager software on a Standalone server.

Before you begin

• Download the installation files.

• Ensure that the postgresql service is running and configured to start automatically upon a system restart. To do so, run one of the following:
  • (For Postgresql server 8.4.20 packages for managers running RHEL 6):
    service postgresql initdb; service postgresql start;
    chkconfig postgresql on
  • (For Postgresql server 8.1.23 packages for managers running RHEL 5):
    su -l postgres -c initdb; service postgresql start;
    chkconfig postgresql on
    

• Ensure that the Apache httpd service is configured to start automatically upon a system restart. To do so, run:chkconfig httpd on
• Permanently disable SELinux.
• If your Manager is running Red Hat Enterprise Linux release 6 only, you must also set the following directive in /var/lib/pgsql/data/postgresql.conf:
  Uncomment escape_string_warning and set it to off
• Install the Apache mod_ssl package to access the GUI by using the https protocol after install or upgrade.

• See OS-requirements for additional requirements for the Manager.

To install the Manager software in a Standalone configuration

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. tar xvzf <downloaded file BDA_<version>_Manager.tar.gz>
   2. cd <extracted directory>
   3. ./install.sh

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

      Warning

      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 BMC Database Automation 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 Standalone 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, run the following command:
   /app/clarity/var/www/mgmt/bin/enable_ssl.sh

   Warning

   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 the GUI is available by using the http protocol on port 80 of the Manager server.

The browser address is http://<manager server>/login.php and can be initially accessed using a default system administrator role (sysadmin).

Where to go from here

Create user accounts

Configure to support reports