Installing standalone Cloud Portal Web Application

This topic describes how to install the Cloud Portal Web Application (also called the My Cloud Services console, the End User Portal, or clmui) as a standalone application. 

The following BMC Communities video describes how to install a standalone BMC Cloud Lifecycle Management Web Portal.

https://youtu.be/ce4fi32grUE

Supported BMC Cloud Lifecycle Management versions

Minimum system requirements

To install Cloud Portal Web Application, your system must meet the following minimum system requirements.

Additional requirements for the Cloud Portal Web Application

In addition to the minimum system requirements, ensure that the following requirements are met:

• You are an Administrator or the root user of the computer on which you will install the Cloud Portal Web Application.
• All BMC Cloud Lifecycle Management component products (such as BMC Remedy AR System, BMC Server Automation, and so on) are accessible from the computer on which you will install the Cloud Portal Web Application.
• RSCD Agent is installed on the computer on which you will install the Cloud Portal Web Application. You can use the RSCD installer bundled with your BMC Cloud Lifecycle Management installer files (and not the directory of your installed BMC Cloud Lifecycle Management solution) in the Applications\BL-RSCD directory. For more information about installing RSCD, see Installing only the RSCD agent (Linux and UNIX) and Installing an RSCD agent (Windows).

• On Linux systems, ensure that you have execute permission for the JRE directory.

• If you are using Microsoft Internet Explorer, ensure that it is not running in Compatibility Mode.

Configure JRE_HOME in your PATH

Ensure that JRE_HOME is in your system PATH variable.

Running the Cloud Portal Web Application in a 2-AR System server environment with LDAP after an upgrade

If you run the Cloud Portal Web Application in a 2-AR System server environment – for example, after you upgraded from 3.1 – users have encountered problems if they have integrated LDAP only with the Enterprise-AR server. Specifically, users could not log on to the new user interface nor could they see their blueprints.

If you are using LDAP in your upgraded environment, BMC recommends the following courses of action:

• As soon as possible, merge the two AR System servers into one AR System server after you finish upgrading. For more information, see Merging two AR System servers into one AR System server.
• If merging the two servers together is not possible at the current time, you must also integrate the Cloud-AR server with LDAP, not just the Enterprise-AR server, before you install the Cloud Portal Web Application. 

To install the Cloud Portal Web Application

1. Obtain the installer.zip file:
   • Download the installer.zip file from EPD to the computer on which you want to install the Cloud Portal Web Application.  
   • Navigate to the ..\Applications\CLM-UI\Windows folder and locate installer.zip.
2. Unzip the installer file.

3. Do one of the following:

   Environment	Steps
   Windows	Navigate to the Disk1 folder and double-click the \Disk1\setup file. The Cloud Portal Web Application Web Application screen appears
   Linux	Start the X graphical environment, navigate to the Disk1 folder, and then enter the following command: ./setup.bin The Cloud Portal Web Application Web Application screen appears.

4. Review the Welcome panel, and then click Next. 
   The installer copies files to the target server, verifies free space, and so on.

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

6. Review the Destination Directory (by default, C:\Program Files\BMC Software\CloudPortalWeb Application for Windows or /opt/bmc for Linux), and then click Next.
   If the path does not exist, you are prompted to accept that the directory will be created. Make sure that you enter a directory with enough space to perform the installation. 

   Note

   For Linux installations, the path must not contain spaces.

7. Select the Use Bundled JRE option to simplify SSL configuration (among other advantages), and then click Next. 
   You can also enter the directory path to an external 64-bit Oracle 1.8 JRE directory – for example, C:\Program Files\Java\jre8.

8. Review the HTTPS or HTTP port numbers (the HTTPS default port is 8443) used to start up (9070) and shut down (9005) the the Cloud Portal Web Application server, then click Next.
   Make sure that you use an unused port.

9. In the Custom CA Certificate Configuration panel, review the certificate information (the default is NO), and then click Next.
   You can chose 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.

    

10. In the Tomcat Web Server Certificate Information panel, review the keystore information or update it as needed, and then click Next. 
    1. In the Common Name (CN) field, enter the FQDN for your host under Common Name (CN).
    2. In the State Name (S) field, enter the full name of the state or province and not its abbreviation (California, not CA). 

    3. Click Next.
        

11. In the Configuration Inputs panel, enter the Platform Manager and Self-Check Monitor details (as shown in the following screenshot), and then click Next. 
    The installer provides sample URLs to open the Platform Manager and Self-Check Monitor. Use the product hosts in your environment to construct the URLs. For example:
    https://<PlatformManager>:9443/csm
    https://<PlatformManager>:7070/csm
    https://<SelfCheckerServer>:8443/health

12. In the Installation Preview panel, review the information, and then click Install.

13. In the Installation Summary panel, review the information, and then click Done.

14. Before you go any further, verify the installation and then configure the My Cloud Services Console. 
    

Where to go from here

Verifying the Cloud Portal Web Application installation

Configuring the My Cloud Services Console

Related topics

• Enabling SSL HTTPS on core Linux CLM applications that currently use HTTP
• Enabling SSL HTTPS on core Windows CLM applications that currently use HTTP
• Using the Cloud Portal Web Application