Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Installing Compact Deployment Linux for version 4.5

This topic describes how to install Compact Deployment from start to finish on Red Hat Linux with an Oracle database on one dedicated computer that is dedicated to BMC Cloud Lifecycle Management.  

Before you begin

  1. Review the Oracle database requirements, described in System requirements for Linux.
    1. Make sure that your Oracle instance is started. You use this same Oracle instance when installing BMC AR System Server - Cloud Portal and Database - Primary and BMC Server Automation.
    2. Make sure that your REDO log is 1GB minimum.
  2. Prepare the installer host requirements for Linux, described in System requirements for Linux. 
  3. Prepare the product host requirements for Linux, described in System requirements for Linux. 

  4. Start the rpcbind service on the product host:

    # service rpcbind stop
    # rpcbind -i
    # service rpcbind status

     

  5. Carefully review the planning spreadsheet so that you can enter accurate values in the installer for each product.
  6. Review the known and corrected installation issues to avoid potential problems during installation.

Tip

To ensure connectivity, add the hosts used in the deployment to /etc/hosts on all the hosts. Make sure that all the hosts can ping each other successfully.

To launch the installer

Note

  • Do not run the installer on the same VM where you install the products; use a separate VM. You can recover this VM later, after you finish the cloud installation.
  • Accept the default values in the installer unless you have a good reason to change them.
  • Do not mix and match IP addresses and host names during product select in the Host Information panel. Enter all IP addresses or all host names, but do not combine them.
  • Some special characters create problems during installation. For more information, see Restricting-the-use-of-certain-characters-in-passwords.
    • For BMC Network Automation, do not use special characters except an underscore (_). 
    • For BMC Server Automation, do not use #. 
    • With Linux, the @ character generally causes problems. 
  1. Download the BMC Cloud Lifecycle Management solution, as instructed in the Downloading-the-installation-files.

  2. Launch the installer by using Xmanager or Xming or VConsole.

    # ./setup.sh

    With Xmanager or Xming, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.

    Make sure that your XServer is running.

  3. On the Welcome page, click Next. 
  4. Review the license agreement, click I agree to the terms of license agreement, and then click Next.
  5. On the Installation Prerequisites panel, review all the prerequisites that you must complete before you start the installation.

  6. Select the I have read the prerequisites check box, and then click Next. 
    (Pptional) Select the Do not display this panel for subsequent installations check box if you do not want to view the prerequisites again during other product installations.

    Note

    If you have not completed any of the prerequisites listed on the Installation Prerequisites panel, exit the installer and complete the steps first.

  7. On the Directory Selection panel, review the location on the host where you want to install the planner, and then click Next.
    Accept the default value (/opt/bmc/Planner) if you do not require a specific location for the installation files.
  8. On the Installation Preview panel, review the planner information, and then click Install.
  1. On the NSH panel, review the installation location, and then click Next. 
     The default location is /opt/bmc/NSH. Otherwise, navigate to the directory where you want to install NSH.  
  2. On the Select Installation Type panel, select Install and then click Next.

  3. In the next panel, select New Deployment and then click Next. 
    The following options are available:

    Installer option

    When to choose

    New Deployment

    This is the first time you are launching the BMC Cloud Lifecycle Management Installer and you have no other existing BMC products installed that you want to add to the BMC Cloud Lifecycle Management solution.

    Integrate with an Existing Deployment

    You have existing BMC products that you want to add to the BMC Cloud Lifecycle Management solution. For more information, see Integrating-brownfield-BMC-Remedy-AR-System-applications.

    Modify Existing Deployment

    You already installed one or more products in the solution. Now you want to add install additional products.
    Note: This option only appears on the BMC Cloud Lifecycle Management Installer UI when you launch the installer after completing an installation. Otherwise, the two options that are visible to you are New Deployment and Integrate with an Existing Deployment.

     

  4. On the Select Deployment Template panel, choose Compact Deployment. 
    For more information, see deployment template for other types to implement.
  5. Click Next. 
    The Host Information for Compact Deployment panel appears for the Control Tier.

  6. Enter the target host for products used in a Compact Deployment cloud environment. 
    Ping the target host to make sure that it is valid. You can also enter an IP address. 

    Note

    If necessary, you can install products in multiple sessions.

  7. Click Next.
    The installer validates the target host and performs additional verification actions. 

  8. Enter the operating system user name and password for the target host, and then click Next. 
    The installer validates the credentials, deploys the RSCD Agent on the target hosts, and performs additional installation actions.  

    Deployment is much faster if the installer host and the target host are in the same subnet (about 3 minutes per VM). Otherwise, this step can take quite a long time to complete. Depending on your environment, deploying the RSCD agents can take up to an hour to install per VM if you are installing across the WAN.

  9. In the Remote Staging Directory Information panel, review the directory (by default, /tmp), and then click Next.
    Optionally, select Enable sub product remote staging directory option to enter an alternative staging area that you can use for all product installations if the /tmp directory on the remote hosts does not have sufficient space. This example selected /data1 because /tmp (the default) did not have enough space.
  10. When the deployment confirmation panel appears, carefully review the summary of the host settings.
    Make sure that the products are installed on the correct target hosts.

  11. Click Next to continue the installation. 
    The Installation Progress panel appears.The installer stages products into the Currently Installing and Upcoming Installs trees, and automatically selects the correct product to install in its proper order. 

    Currently Installing

    Product does not depend on other products to install, for example, BMC AR System Server - Cloud Portal and Database - Primary.

    Upcoming Install

    Product depends on other products being installed first. For example, before you can install Cloud Platform Manager, you must successfully install five products. As a result, products that have an unmet dependency remain in the Upcoming Installs tree until the installation of the product on which they depend is complete.

    You can review the current progress of an installation at any time by selecting the product in the Currently Installing tree. Click View Deployment Status to review previous progress.

    ITSMwelcome.jpg

  12. Select BMC AR System Server - Cloud Portal and Database - Primary from the Currently Installing tree and click Next.

To install BMC AR System Server - Cloud Portal and Database - Primary

Note

Before you begin:

  1. On the Welcome panel, click Next. 
    The installer copies files to the target host.
    ITSMwelcome.jpg 

  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.

    Note

    The planner automatically defaults to /data1 because you previously had enabled an alternate staging directory.


  3. Take a VM snapshot of the target host, and then click Next.  

    These snapshots are incredibly important if you encounter an error. You can revert to the saved snapshot, fix the problem, and then continue with the installation. 

  4. If the installer prompts you to start and stop the rpcbind service, perform the instructions at a command line before you continue with installation. 

    PrereQValidation.jpg

    rpcbind.png

  5. Click Next to continue.
  6. In the Language Selection panel, specify the language selection. and then click Next. 
    The default is English, which significantly speeds up installation. You can also select All Languages, which includes all supported languages – English, German, Spanish, French, Italian, Japanese, Korean, Simplified Chinese, and Portuguese Brazilian.
  7. Select the Remote Destination Directory of the target host, and then click Next. 
    The default is /opt/bmc. Make sure that you enter a directory with enough space to perform the installation. For example, you might select /data1 because /opt (the default) does not have enough space.
  8. Enter the Oracle JRE 1.7 64-bit directory (for example, usr/lib/jvm/jre.1.7.0), and then click Next. 
  9. On the AR System Server Database Platform Information panel, enter the Database Client Home Path (for example, /data1/oracle/product/11.2.0), and then click Next. 
  10. Enter the user and database credentials to access the Oracle database that is used with the AR System server. 
    Open the tnsnames.ora file on the database VM to locate the Oracle Connection Identifier (ORA112DB) and the Oracle SID (ORA112DB).
    tnsnamesora.png 
  11. Enter the database host name and database credentials from the tnsnames.ora file, and then click Next. 

  12. Review the AR System Server administrator credentials (by default, Demo/no password), and then click Next. 

    Note

    You cannot modify the Administrate Name, Password, and TCP Port values because the database is imported during installation. After installation, you can update these values as needed.


  13. Enter the credentials for the DBMS administrator (for example, system and the password), and then click Next.
  14. Review the AR System Server database file (ARSys), temporary tablespace (ARTMPSPC), and temporary datafile (artmp) for the AR System server database (ARSystem), and then click Next.
  15. Enter the passwords for local DSO user, Application Server, and Mid Tier administration, and then click Next. 
  16. Review the Normalization Engine (9555) and Atrium Plugin (9556) ports, and then click Next.
  17. Review the AR System Server RMI ports, and then click Next. 
    The Flashboards RMI port is 1099, and the RPC program number is 0. The Email Engine RMI port is 1100, and the RPC program number is 0.
  18. Specify Yes to install the Tomcat servlet used with the BMC Mid Tier, and then click Next. 
  1. Review the Tomcat installation directory, and then click Next. 
    The default is /opt/apache/tomcat6.0. To stay consistent, this example installs Tomcat in /data1/apache/tomcat6.0.
  2. Review the Tomcat configuration parameters, and then click Next. 
    By default, the Tomcat initial memory pool is 1536, the maximum memory pool is 2048, and the HTTP port is 8080.
  3. Preview the products and versions listed in the BMC AR System Server – Cloud Portal and Database stack, and then click Install.  
    The installer copies the stack installer files to the target host and starts the installation process. 

  4. Review any validation warnings that appear, make any necessary changes, and then click Next.

    Warning

    Not all of these warnings are information only. During different installations in the BMC IDD lab environment at various times, changes were made to the temp space, system libraries, the Oracle character sets, the Oracle UNICODE settings, or the Redo log size, as shown in the following 4.1.00 screenshot. Make sure that you read the installation prerequisites carefully before you start installation!

    ValidationWarnings.png

    The following information-only warnings appear in an environment that is properly configured:
    ITSMinstallvalidationwarnings.png 

  5. When the installation is finished, review the install log, and then click Next. 
    You can safely ignore the warnings. 
  6. Enter a valid AR System server license key, and then click Next. 
  7. When you are prompted that the AR System server is successfully licensed, click Next.
    The installer cleans up temporary files on the target host.  
  8. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  9. Continue with configuring the AR System server post-installation steps. 

To configure AR post-installation 

  1. In the Welcome panel, click Next to continue.
    The installer copies files to the target server, verifies free space, and so on.
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space.
  3. Take a VM snapshot of the target host, and then click Next.
  4. Enter the AR System Server user inputs (for example, Demo/no password), and then click Next. 
    The installer copies additional files to the target server, starts the remote installation, removes temporary files, and so on.
  5. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  6. Continue with installing the Atrium Core - Web Registry Components.

To install Atrium Core – Web Registry Components

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, Atrium Core - Web Registry Components would be installed in /data1/bmc/AtriumCore.
  3. Take a VM snapshot of the target host and the BMC AR System Server - Cloud Portal and Database server, and then click Next.
  4. Enter the information for the BMC AR System Server - Cloud Portal and Database (for example, Demo/no password), and then click Next.
  5. Review the Tomcat HTTP (8080) and HTTPS (7776) ports, enter the 64-bit Oracle 1.7 JRE path, and then click Next.
  6. Review the products and versions listed in the installation preview, and then click Install.  
    The installer copies the web registry installer files to the target host and starts the installation process.
  7. Review any validation warnings that appear, make any necessary changes to the target host, and then click Next.
    In this example, BMC added more RAM to the target host.
    ACWSvalidationwarnings.png 
  8. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  9. Continue with installing the BMC Server Automation - App Server & Console.

To install BMC Server Automation – App Server & Console

Before you begin installing BMC Server Automation – Application Server & Console:

  • Make sure that the Oracle instance is running. For Compact Deployment, use the same Oracle instance ID that you used with BMC AR System Server - Cloud Portal and Database - Primary. 

  • Ensure that port 9700 is available on the host on which you want to install the product. For example, enter the following command to verify if port 9700 is busy:

    netstat -anp | grep 9700


Installing BMC Server Automation – Application Server & Console includes the following components:

This installation example skips the optional BSA - File Server deployment on another VM. You can install it later, if needed.

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.  
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, the App Server & Console would be installed in /data1/bmc/bladelogic. 
  3. Take a VM snapshot of the target host, and then click Next.
    BSAappserversnapshot.png
  4. Select the Remote Destination Directory of the target host, and then click Next. 
    The default is /opt/bmc/bladeLogic. Make sure that you enter a directory with enough space to perform the installation. For example, you might select /data1/bcm/bladelogic because /opt (the default) does not have enough space, and because the other applications up to this point have been installed in data1 (because you selected it in an earlier procedure).
  5. Enter the Oracle instance ID, DBA user, and password for the Oracle database.
    BLADE is the default Oracle instance ID. But you must use the pre-created Oracle instance ID that you used with BMC AR System Server - Cloud Portal and Database - Primary, for example, ORA112DB. 
    If you select Oracle Service, you can also enter Advanced Connection Settings. 
    BSAOracleInstanceID.png
  6. Create a bladelogic password, review the Oracle settings, and then click Next.
  7. Create a certificate password to use SSL, and then click Next.
  8. Create a file server for BladeLogic storage, and then click Next.
  9. Enter the maximum JVM heap size for the Application Server, and then click Next. 
    The default is 6144 MB. 
  10. (Optional) Specify the SMTP and SNMP servers, and then click Next.
  11. Review the products and versions listed in the BMC Server Automation Application Server installation preview, and then click Install.
    The installer copies the installer files to the target host, installs the database schema, and then installs the application.  
  12. In the Installation Summary panel, review the installation log, and then click Done to finish the installation. 
  13. Continue with installing the BMC Server Automation Console.

To install the BMC Server Automation Console (BladeLogic content)

In this step, you are installing the BladeLogic content for the BMC Server Automation Console. Later you install the Atrium Orchestrator content for the BMC Server Automation Console. 

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.   
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, the BMC Server Automation Console would be installed in /data1/bmc/bladelogic.
  3. Take a VM snapshot of the target host, and then click Next.
  4. Review the products and versions listed in the BMC Server Automation Console installation preview, and then click Install.
    The installer copies the installer files to the target host and then installs the console.
  5. In the Installation Summary panel, review the installation log, and then click Done to finish the installation. 
  6. Continue with configuring the BMC Server Automation post-installation.

To configure the BMC Server Automation post-installation

Before you start:

  • Make sure that the AR System server is started. 

  • If port 9700 is in use, open the /etc/services file and comment out the following lines:

    board-roar9700/tcp#Board M.I.T. Service
    board-roar9700/tcp#Board M.I.T. Service
  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.   
  2. Take a VM snapshot of the target host, and then click Next.
  3. Enter the login and password to connect to the BMC AR System Server - Cloud Portal and Database, and then click Next.
  4. Create the RBACAdmin and BLAdmin passwords, and then click Next.
  5. In the BMC Server Automation User Information panel, create the BLGuest password, and then click Next.
  6. Review the products and versions listed in the post-installation preview, and then click Install.
    The installer performs the post-installation configuration to the Operations Manager application server and other related operations. 
  7. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, the post-installation stage would be configured in /data1/bmc/bladelogic. 
  8. In the Installation Summary panel, review the installation log and then click Done to finish the installation. 
  9. Continue with installing BMC Atrium Orchestrator Access Manager and Repository (AMREPO).

To install Atrium Orchestrator AMREPO

Note

Installing BMC Atrium Orchestrator includes the following components::

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, the post-installation stage would be configured in /data1/bmc/ao-platform/amrepo.
  3. Take a VM snapshot of the target host, and then click Next.
  4. Specify the directory of BMC Atrium Orchestrator, and then click Next. 
    The default is /opt/bmc/ao-platform/amrepo.
  5. Review the Access Manager HTTP port (9090 by default) and shutdown port (9005 by default), and then click Next.
  6. On the Access Manager Communication Settings panel, review the Web Server Port Number (9090, the same as the HTTP port) and Communications Port (61616), and then click Next. 
  7. Review the products and versions listed in the installation preview, and then click Install.
  8. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  9. Continue with installing Atrium Orchestrator CDP.

To install Atrium Orchestrator CDP

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, the post-installation stage would be configured in /data1/bmc/ao-platform/cdp.
  3. Take a VM snapshot of the target host, and then click Next.
  4. Review the directory of BMC Atrium Orchestrator CDP, and then click Next. 
    The default is /data1/bmc/ao-platform/cdp.
  5. Review the CDP HTTP port (28080 by default) and shutdown port (28005 by default), and then click Next.
  6. Enter the certificate holder password for the CDP peer, review the other settings, and then click Next.
  7. Review the repository communication settings, and then click Next.
  8. Review the products and versions listed in the installation preview, and then click Install.
  9. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  1. Continue with installing BMC Cloud Lifecycle Management Content.

To install BMC Cloud Lifecycle Management Content

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on. 
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, the post-installation stage would be configured in /data1/bmc/ao-content.
  3. Take a VM snapshot of the target host, and then click Next.
  4. Review the directory of BMC Cloud Lifecycle Management Content, and then click Next. 
    The default is /data1/bmc/ao-content.
  5. Review the Repository Communication Settings, enter the repository password (by default, admin123), and then click Next.
  6. Review the products and versions listed in the installation preview, and then click Install.
  7. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  8. Continue with configuring Atrium Orchestrator post-installation.

To configure Atrium Orchestrator post-installation

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. Review the settings to enable the ARS Adapter, and then click Next.
    The orchestrationuser user name and password (aouser) are defined by default and you cannot modify them.
  3. Specify the BLAdmin SRP password, review the remaining settings, and then click Next.
    The BLAdmins user role and BLAdmin user name are entered by default. 
  4. Specify the settings to enable the Net App Adapter, and then click Next.
    If you do not need the Net App Adapter or you are not running a Net App server, disable the setting and continue with configuration.
  5. Review the products and versions listed in the installation preview, and then click Install.
  6. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  7. Continue by installing BMC Network Automation.

To install BMC Network Automation

Before you begin installing BMC Network Automation. make sure that the Oracle instance is running. For Compact Deployment, use the same Oracle instance ID that you used with BMC AR System Server - Cloud Portal and Database - Primary and BMC Server Automation. 

  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, BMC Network Automation would be installed in /data1/bmc/bca-networks.
  3. Take a VM snapshot of the target host, back up your database, and then click Next.
  4. Specify the directory of the BMC Network Automation data, and then click Next. 
    The default is /var/bca-networks-data.
  5. Specify the OS User Account to the BMC Network Automation server:
    1. Enter a OS user account, for example, bna_user. 
      For BMC Network Automation, do not use any special characters except an underscore (_). Do not use a dash (for example, bna-user).
    2. Enter a password and then confirm it.
      For BMC Network Automation, do not use any special characters except an underscore (_).  
    3. Enter the name of the Unix group, for example, bna_group.
      For BMC Network Automation, do not use any special characters except an underscore (_). 
    4. Click Next. 
  6. Specify the web server information, and then click Next. 
    if you do not want to redirect HTTP requests to HTTPS, clear the Redirect check box.
  7. Enter the database information for the BMC Network Automation server:
    1. On Linux OS, use Oracle database only. 
    2. Enter the existing Oracle SID (for example, ORA112DB). 

    3. Create a new database user account and password (for example, bna_user).

      Warning

      Do not use the existing system database user.

    4. (Optional) For Advanced Connection Settings, use this field if you are using Oracle RAC. Otherwise, skip this option.
    5. Click Next. 
  8. Enter the settings for the database administrator to create the database and database user:
    1. Enter the DBA user name and password. The installer defaults to the Oracle system administrator. 
    2. Enter the name of the database datafile with the correct .dbf extension. For example:
      /data1/oracle/product/databases/ORA112DB/BNA_data.dbf 
      Verify that the database file folders exist before you start the installation.  
    3. Click Next. 
  1. Review the information to generate the HTTPS certificate, and then click Next.
    The keystore password is typically already defined.
  2. Enter the amount of memory that the software allocates and holds upon startup, and then click Next.
    You can also specify additional startup options for the application. The FAQ and Knowledge Base articles at BMC Customer Support recommend additional startup options to solve issues unique to your environment. For example, if running on a headless server (no graphics card or monitor), you might have to specify -Djava.awt.headless=true for all the features of application to work properly in your environment.
     
  3. Enter the settings to enable Atrium Orchestrator integration:
    1. Enter the user name and password (for example, admin/admin123).
    2. Enter the grid name, for example, BNA_GRID. 
    3. (optional) Enable continuous compliance for network automation. This setting is disabled by default. 
    4. Create an AO user account, for example, ao_adapter. 
    5. Create an AO user password. 
    6. Click Next.
  4. Enter the settings to enable CMDB integration, and then click Next.
  5. Enter the settings to integrate BMC Network Automation with Cloud Lifecycle Management, and then click Next.
  6. Specify the directory of BMC Network Automation, and then click Next. 
    The default is /opt/bmc/bca-networks. The example in these procedures has used /data1, so the directory to specify would be /data1/bmc/bca-networks.
  7. Review the products and versions listed in the installation preview, and then click Install.
  8. In the Installation Summary panel, review the installation log and then click Done to finish the installation.
  9. Continue with installing Cloud Extensions & Platform Manager.

To install Cloud Extensions & Platform Manager

Note

Before you begin, install 64-bit Oracle JRE 1.7 on the target host if you want to use an external JRE. Pre-installing the JRE is optional. This applies to the CLM Core components, Self-Checker Monitor, and Cloud Portal Web Application. 

Note

Compact Deployment has the following restrictions:

  • Cloud Portal Web Application is installed by default during the Cloud Extensions and Platform Manager installation. Cloud Portal Web Application runs on the jetty server and on the same port as Platform Manager (9443).
  • CLM Self-Checker Monitor is not installed during Compact Deployment. If you need to install it in your environment, use the standalone Applications\SelfChecker executables to manually install it. BMC recommends that you install the Self-Checker on a separate host. For detailed steps, see Installing-standalone-CLM-Self-Check-Monitor.
  1. In the Welcome panel, click Next to continue. 
    The installer copies files to the target server, verifies free space, and so on.
  2. On the Alternate Remote Staging Directory panel, enter an alternate directory if you need additional space to perform the installation, and then click Next.
    For example, you might select /data1 because /tmp (the default) did not have enough space. In this example, Cloud Extensions & Platform Manager would be installed in /data1/bmc/BMCCloudLifeCycleManagement.
  3. Take a VM snapshot of the target host, back up your database, and then click Next.
  4. Specify the directory of Cloud Extensions & Platform Manager, and then click Next. 
    The default is /opt1/bmc/BMCCloudLifeCycleManagement. This example used /data1/bmc/BMCCloudLifeCycleManagement.
  5. Specify the Oracle JRE 1.7 path (for example, /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71.x86_64/jre), and then click Next. 
    You can also use the bundled JRE.  
  6. Specify the user inputs to the AR System server (for example, Demo and no password), and then click Next.
  7. Specify an unused TCP port (9899 by default) for the Java plugin server, and then click Next. 
  8. Specify a password for the cloud administrator (clmadmin), and then click Next.

  9. (Optional) In the Cloud Vista cross launch panel, select Yes to enable integration between Cloud Vista and TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server.
    By default, the No option is selected in the installer. 

    Note

    Do not select Yes unless you already installed TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server. BMC customers who purchased and manually installed standalone TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server can integrate BPPM as a brownfield product with BMC Cloud Lifecycle Management.

  10. If you selected Yes in the Cloud Vista cross launch panel, enter the TrueSight Infrastructure Management Server or BMC ProactiveNet Central Server details, and then click Next.
  11. Specify the directory of the Platform Manager configuration files, and then click Next. 
    The default is /opt/bmc/BMCCloudLifeCycleManagement/Platform_Manager/configuration. If you selected /data1 in previous procedures, you might select /data1/bmc/BMCCloudLifeCycleManagement/Platform_Manager/configuration. 
  12. Specify the OSGi port (9443) and protocol (the 4.5.00 default is https), and then click Next. 
    To deploy the product in HTTP mode, enter http. The pre-populated OSGi Port is 7070.
     
  13. In the Configuration Inputs panel, review the self-check monitor URL and session timeout, and then click Next. 
    If you plan to install the Self-Check Monitor and you already know the host name, enter the URL. For example:
    https://selfCheckerHost:8443/health
    If you do not plan to deploy the Self-Check Monitor at this point, proceed with the pre-populated values. You can change the values later in the<CLM_Install_Dir>\Platform_Manager\configuration\preferences\PreferenceGroup.json file.  

  1. In the Custom CA Certificate Configuration panel, review or modify the settings, and then click Next.
    You can choose to install using the existing self-signed certificate, or you can provide the location of a third-party certificate and password.

    Note

    You must copy the third-party certificate to the target host.

  2. In the Tomcat Web Server Certificate Information panel, enter the information to create a self-signed certificate, and then click Next. 
    If you create a self-signed certificate, you must import the cacerts product certificate into the JRE used by other products after you finish the installation. For more information, see To import Self-Signed certificates.
  3. Click Next to accept the Platform Manager host. 
    You cannot modify these settings.
  4. Review the web server URL (for example, http://webserver:8080), and then click Next. 
    Do not enter the full Mid Tier URL.
  5. Enter a super user password to the login service, and then click Next.
    You use this super user password during the Cloud Portal AR Extensions installation.
  6. Specify the correct database timezone under Persistence Manager details, and then click Next. 
  7. Review the core cloud service details, and then click Next. 
  8. Enter the Resource Manager details:
    1. Enter the BBNA provider user and password. Make sure that you enter the BBNA user that you created earlier (for example, bna_user). 
    2. Enter the BLAdmin password. 
    3. Enter the BLGuest password.
    4. Enter the Atrium Orchestrator callout provider password (by default, admin123).
    5. Click Next. 
  9. Enter the SMTP Configuration details, and then click Next.
  10. Click No (the default) to disable the on-premise database as a service (DBaaS), and then click Next. 
    You can still configure DBaaS later after you finish installing Compact Deployment. If you select Yes now, the next panel prompts you for the BMC Database Automation (BDA) Manager host name, user, and password.
  11. (Optional) If you selected Yes in the Configure BDA for BMC Cloud Lifecycle Management panel, enter the BMC Database Automation details, and then click Next.
  12. Click No (the default) to disable the VMware vCloud Director Provider, and then click Next. 
    You can still configure vCloud later after you finish installing Compact Deployment. If you select Yes now, the next panel prompts you for the vCloud server name, administrator, password, and so on.
  13. (Optional) If you selected Yes in the Configure Vmware vCloud Director Provider for BMC Cloud Lifecycle Management panel, enter a password, review the remaining details, and then click Next.
  14. Review the products and versions listed in the installation preview, and then click Install.

  15. In the Installation Summary panel, review the installation log and then click Done to finish the installation.

    Note

    The following warnings are benign and you can safely ignore them.

    PMinstallsummary.png 

  16. Review the Compact Deployment installation summary and then click Next.
  17. Click Exit the Installation to close the installer and exit the program, and then click Next. 
    You can also click Modify Existing Deployment if you want to install an additional application, for example, a PXE server.
  18. Click Done to exit the installer. 
    You have successfully installed the BMC Cloud Lifecycle Management Compact Deployment.

Where to go from here

  1. If Cloud Extensions and Platform Manager are installed on SSL with a self-signed certificate:

    • Import the Platform Manager cacerts on the Enterprise-AR Server.
    • Import the Self Checker certificate (if you installed the Self Checker Monitor) into the cacerts of JRE used by Platform Manager and Cloud Portal Web Application.
      For more information, see To import Self-Signed certificates.

  2. If Cloud Extensions and Platform Manager are installed on SSL with a third-party certificate using the bundled JRE, import the certificate into the JRE of the Cloud Portal and Database AR System. For more information, see To configure third-party certificates.

  3. Apply the following hotfixes after you install or upgrade version 4.5.00:
    • 1088– This hotfix provides missing files necessary for using a currency other than USD.
    • 00011110 –you have BM TrueSghtapacity Optimization deployed in your environment.
    • 000090568 – This hotfix is required when Platform Manager is running on SSL and the Restart All Components option is not available in the CLM Self Checker.
    • 000107881 – This hotfix is required for all BMC Cloud Lifecycle Management deployments.
  4. Verifying-the-installation

 

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