Installing BMC Release Process Management

 This topic provides instructions for installing BMC Release Process Management (RPM) on Microsoft Windows, Linux, and Oracle Solaris. If you are upgrading an existing product installation, see Performing-the-upgrade.

Before you begin

Before you begin the installation process, perform the following preparatory tasks:

  • Download and extract the installation files to a temporary location.
  • Verify that your environment meets the requirements listed in System-requirements and verify that you have prepared the installation environment.
  • If you use Microsoft SQL Server as a database server for RPM, ensure that you have the necessary information about the instance of the Microsoft SQL Server that you plan to use, including the following information:
    • Database server host name and port (default port is 1433)
    • Master administrator credentials for the database server that enable you to create new users and databases
    • Dedicated user for managing the RPM database (default user: brpmuser). If you create a new user login account in the Microsoft SQL Server 2008 R2, ensure that you log in as this user to change the password.
    • Database/SID name (default is bmc_rpm_db). To prepare the database for installation, log in as a master administrator and create a new database that will be used by RPM.

  • Ensure that the installation directory for the product is empty.

    Windows:

    • BMC recommends that you install the product with administrator privileges. You can install the product as a normal user without administrator privileges but then you cannot register the product as a service. 

    Linux:

    • BMC recommends that you install the product with superuser privileges. You can install the product as a normal user without superuser privileges, but you cannot register the product as a service.
    • Ensure that there is no Ruby Version Manager (RVM) environment in the installation path. 

    Solaris:

    • BMC recommends that you install the product with superuser privileges. You can install the product as a normal user without superuser privileges, but you cannot register the product as a service.

    • To install RPM 5.0.x on Solaris 10, run the following commands in the terminal:

      cd <installationDirectory>/BRLM
      chmod –R 777 Disk1/

During the installation, ensure the following:

  • For HTTP/HTTPS and messaging system ports, use different port numbers for version 5.0.x and your current product version.
  • For the Application superuser, all passwords must contain at least one letter and at least one number.
  • For the TorqueBox or JBOSS Super User details and Messaging system details, all passwords must contain at least one letter, at least one number, and at least one non-alphanumeric symbol.

Back to top

To install the product 

  1. Start the installation program: 
    Windows: 

    • To install the product with administrator privileges, navigate to \temporaryDir\BRLM\Disk1 and run the setup.cmd command.
    • To install the product as a normal user, double-click setup.cmd.

    Linux or Oracle:

    1. Log in as the root user.
    2. Navigate to the temporaryDir/BRLM/RLM/Disk1 directory.
    3. To make the installation file executable, enter the chmod -R +x . command.
    4. To start the installation program, enter the ./setup.sh command.
  2. On the welcome page, click Next.
  3. On the License Agreement page, select I agree to the terms of the license agreement, and click Next.

  4.  On the Directory Selection page, specify the directory path for the RPM 5.0.x installation, and then click Next.

    By default, RPM is installed in the following directories:

    • Windows: C:\Program Files\BMC Software\RLM
    • Linux/Solaris: /opt/bmc/RLM
  5. On the Installation Type page, select one of the following options, and click Next:
    • If you started the installation as a root user or administrator, select Installer is started with root privileges so perform full installation.
    • If you started the installation as a normal user, select Install solution files and configurations. Do not perform tasks that require special rights.
  6. On the feature selection page, select the required features, and click Next.

    • (Optional) BMC Release Lifecycle Management 5.0.x Installation

      5-0-03-001-Patch-1-for-Service-Pack-3 onward, BMC Release Lifecycle Management is no longer supported. You can install BMC Release Process Management and PostgreSQL, as per your requirement.

    • Install BMC Release Process Management 5.0.x 

    • (Optional)  Install PostgreSQL

      Note

      If you are installing without administrator or root privileges, you cannot install BMC Release Lifecycle Management together with a local PostgreSQL database.

  7. On the BMC Release Process Management data migration page, in the Copy data from list, ensure that No migration required is selected, and then click Next.
  8. On the BMC RPM Server Instance type page, select the deployment mode for RPM, enter the details, and click Next:

    • To run RPM as a single instance, select Standalone, and 

      New in 5.0.03.004

       do the following:

      1. In the Node name box, enter the name of the standalone node.
      2. In the Node IP box, enter the IP address of the standalone node.
    • To run RPM as a node in the cluster, select Cluster, and do the following:
      1. In the Node name box, enter the name of the cluster node.
      2. In the Node IP box, enter the IP address of the cluster node.
  9. On the JRE Information page:
    • To Use the bundled JRE (version <version>), click Next. To see the bundled version of the JRE, see System-requirements.
    • To use any other JRE, clear the Use the bundled JRE (version <version>) check box, click Browse, set the path to the JRE on your computer, and then click Next. 
      Ensure that you have completed the necessary steps for setting your local JRE configuration as described in Preparing for installation.

  10. Generate the certificate information, and click Next:

    • version 5.0.03.004 or later On the Server HTTPS Port Information page, select the Generate Self-Signed Certificate option, and enter the following information if you want to use the self-signed certificate generated by the installer:
      1. In the HTTPS Port box, enter the HTTPS port number. Default is 8443.
      2. In the Passphrase box, create a passphrase for your certificate. 
      3. In the Common Name (CN) box, specify the name that represents the server protected by the certificate. For example, SAT.co.in.
      4. In the Organization Unit (OU) box, specify the name of the name of your organization unit. For example, Accounting. 
      5. In the Organization Name (O) box, specify the name of your organization. For example, SAT Pvt. Ltd.
      6. In the Locality Name (L) box, specify your city or other locality. For example, Brooklyn.
      7. In the State Name (S) box, specify the name of your state, province, or other political subdivision. For example, New York.
      8. In the Country Code (C) box, specify the name of your country. For example, US. You can enter only upto 2 characters.
    • version 5.0.03.004 or later Enter the following information if you want to use a third-party SSL certificate:
      1. In the HTTPS Port box, enter the HTTPS port number. Default is 8443.
      2. In the Private Key box, specify the directory path to the private key for SSL encryption.
      3. In the Certificate File box, specify the directory path to the certificate for SSL connection.
      4. In the Passphrase box, create a passphrase for your certificate.

    • version 5.0.03.003 or earlier On the Server HTTP/HTTPS Port Information page, select the appropriate option and then click Next.

      • To use HTTP to access the RPM server, in the HTTP Port box, enter the HTTP port number, which refers to the port of the TorqueBox server (default: 8080).
      • To use the Secure Sockets Layer (SSL) to access the RPM server:
        1. Select Enable SSL.
        2. In the Private Key box, specify the directory path to the private key for SSL encryption.
        3. In the Certificate File box, specify the directory path to the certificate for SSL connection.
        4. In the Passphrase box, enter the passphrase for your certificate.

      For more information about how to obtain SSL certificates, see Obtaining-test-SSL-certificates.

    Note

    Starting from version 5.0.02, RPM supports only the following combination of Classic UI and Requester UI:

    • Classic UI on HTTP and Requester UI on HTTP
    • Classic UI on HTTPS and Requester UI on HTTPS

    Starting from version 5.0.03.004, RPM does not support the HTTP protocol.

  11. On the Super User Details page, specify the details for the first RPM user with administrator permissions, and then click Next.
  12. version 5.0.03.004 or later On the JBoss Super User Details page, enter the following details, and then click Next:
    • Login: Username for the superuser required to log on to the JBoss server.
    • Password: Password for the JBoss superuser.
  13. version 5.0.03.003 or earlier On the TorqueBox Super User Details page, enter the following details, and then click Next:
    • New in 5.0.03 Hostname with (FQDN): Fully qualified domain name of the host on which the TorqueBox server is installed. 
    • Login: Username for the superuser required to log on to the TorqueBox server.
    • Password: Password for the TorqueBox superuser.
  14. On the Messaging system details page, specify the following details to connect to the messaging system server, and click Next:
    • version 5.0.03.003 or earlier Host: IP address of the messaging system server. The Host box is populated automatically. By default, the installation program detects the IP address of the host computer on which you are installing this product.
    • Port: Port for the messaging system server. The default port value is 5445.
    • User: User name for the messaging system server.
    • Password: Password of the messaging system server.
  15. On the Database details page, specify the relevant details for the database, and then click Next.

    1. In the Database list, select one of the following:

      • POSTGRESQL (Default port is 5432)
        A default user called rlmuser is created for the PostgreSQL database.
      • ORACLE (Default port 1521)
      • SQL_SERVER (Default port 1433)

      The Database list is not available for selection if you have selected Install PostgreSQL on the feature selection page.

    2. In the Host box, specify the computer name of the server where your database is installed.
      The Host box is dimmed if you selected Install PostgreSQL on the feature selection page.
    3. In the Port box, specify the port of the server that you used for installing your database. Depending on the database you specified, the default port is automatically displayed.

    4. In the RPM Database/SID Name box, do the following:

      Warning

      If you are installing RPM with the built-in PostgreSQL database, ensure that the database name does not contain any special characters, otherwise, the installation fails.

      • For PostgreSQL and SQL server, specify the name of the database instance that you created at the time of the database installation.
      • For Oracle, specify the SID name or the service name in the following formats:
        • If your SID name is rpmorclsid, enter rpmorclsid

        • If your service name is rpmorclservice, enter /rpmorclservice

          Note

          For Oracle RAC, use service name only.

    5. In the RPM Database User box, specify the user name of the database instance that you used while creating it at the time of the database installation.
    6. In the RPM Database Password box, specify the password of the database instance that you used while creating it at the time of the database installation.
  16. On the Email Notifications details page, do one of the following: 

    • Not to configure email notifications, click Next.

      Note

      You can configure email notifications later from the RPM UI. For more information, see Changing-the-email-notification-configuration-manually.

    • To configure email notification settings, select Use SMTP, and then specify the following SMTP server details:
      1. SMTP Server: Enter the name or address of the SMTP server used for sending email notifications.
      2. SMTP Port: Enter the SMTP server port. The default SMTP server port is 25.
      3. SMTP Domain: Enter the domain name for your SMTP server. Domain name is the part of the user name after xyz@ in your email address. For example, if your user name is redmine@example.net, your domain name is example.net.
      4. SMTP Authentication: Select the authentication mechanism for your SMTP service.
      5. SMTP User: Enter the user name used to connect to the SMTP server. For example, redmine@example.net.
      6. SMTP Password: Enter the password used to connect to the SMTP server.
      7. TLS: Select TLS if your SMTP server requires a secure connection and is using TLS.
  17. On the Installation Preview page, view the installation details, and then click Install.
  18. On the Installation Summary page, click Done.
    Optionally, click View Log to check the installation logs.

Back to top

After the installation

After you complete the installation, you might need to perform the following tasks:

  • If you installed the product without administrator or root privileges, you must register the product as a service and start the product services whenever you restart your computer. For more information on how to register and start or stop services for the non-root installation, refer to the RLMhome/README_special_config.txt file or see Starting-and-stopping-product-services.
  • To verify that the installation completed successfully, access the product interface. For more information, see Accessing the interface.
  • version 5.0.03.003 or earlier The Stomp host is set to the IP address of the local machine and can be edited from RLMhome/server/jboss/standalone/configuration/standalone.xml.
  • If you configured the SMTP notifications, you must make additional configurations to receive a correct link to RPM in the email messages:

    1. Open the RLMhome/releases/productVersion/RPM/portal.war/WEB-INF/config/smtp_settings.rb file version 5.0.03.004 or LATER or RLMhome/releases/productVersion/RPM/config/smtp_settings.rb file version 5.0.03.003 or earlier, and then replace the  # config.action_mailer.default_url_options = { :host => 'example.com' }  line with the following:

      config.action_mailer.default_url_options = {
          :host => 'example.com',
          :protocol => 'https',
          :port => 8443
    2. Edit the  host ,  protocol , and  port  values as appropriate.
  • To fix the SSH and NSH automation scripts after installation of RPM 5.0.01.00 (for the details, see DRZXB-16048), do the following:
    1. Go to RLMhome/releases/5.0.01.00/RPM/lib/script_support and open the dispatch_script_header.rb file in a text editor.
    2. In line 468, value_str = "#{value}".gsub!('"', '\"'), delete ! after the gsub method.
       Result: value_str = "#{value}".gsub('"', '\"').
    3. Save the file, and then restart the services.


Related topics

System-requirements

Disabling-IPv6

Installing-BMC-Release-Lifecycle-Management-Requester-UI

Rolling-back-after-the-failed-installation-or-upgrade

Replacing-your-existing-SSL-certificates

Troubleshooting

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*