Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Upgrading Cloud Portal Web Application to version 4.6

This topic describes how to upgrade the 4.5 Cloud Portal Web Application (also called the My Cloud Services console, the End User Portal, or clmui) to version 4.6. 

Supported BMC Cloud Lifecycle Management versions

You must be using BMC Cloud Lifecycle Management 4.5.

Minimum system requirements

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

Category

Minimum requirement

Operating system

One of the following:

  • Microsoft Windows 2012 R2
  • Microsoft Windows 2008 R2
  • Microsoft Windows 2008
  • Red Hat Enterprise Linux 5.5
  • Red Hat Enterprise Linux 6.x
  • Red Hat Enterprise Linux 7.x

Note: Linux systems must have the X environment to run the BMC Cloud Lifecycle Management Dashboards installer.

Hardware

All of the following:

  • 2 CPUs
  • 4GB RAM
  • 60GB Hard disk space

Browser

Any of the following:

  • Microsoft Internet Explorer 9 or greater
  • Mozilla Firefox 26.0 or greater

Java

Java Runtime Environment 8 (1.8.0_60)

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 jre1.8.0/bin/java directory.
  • If you are using Microsoft Internet Explorer, ensure that it is not running in Compatibility Mode.
  • Make sure that port 12333 is not in use. 

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 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 to 4.5 or 4.6 – 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 upgrade the Cloud Portal Web Application

  1. Download the BMC Cloud Lifecycle Management solution from the EPD site.
  2. Start the installer:
    • On Microsoft Windows, double-click the setup.cmd file.

    • On Linux, launch the installer by using Xmanager.
      With Xmanager, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.

      You can also use VConsole to launch the installer.

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

  6. Select the I have read the prerequisites check box and click Next. 
    (optional) 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 upgrades.  

    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, navigate to the location on the host where you want to install the planner and click Next.
    The default location is C:\Program Files\BMC Software\Planner.
  8. On the Installation Preview panel, review the information and click Install.
  9. If NSH is not installed, the system prompts you to install it.
    The default location is C:\Program Files\BMC Software\NSH. 
  10. In the Select Installation Type panel, select Upgrade and then click Next.
  11. In the Integrate Disclaimer Information panel, review the guidance.
    Make sure that upgrading does not impact your customizations or your system performance. 
  12. Click I agree to the terms of the disclaimer, and then click Next. 

  13. On the BMC Installation Registry panel, select if you have a backup registry to use or if you are integrating from scratch, and then click Next. 

    The backup registry lists the target hosts and which products were installed on them. This example does not have an registry available to simplify the upgrade process. If you do not have a registry, you must compile your own list of target hosts.

    For more information, see deployment template for other types to implement.

  14. In the BMC AR System Configuration panel, the installer asks if you use one or more AR System servers in your environment.
    Since this example is based on the 4.1 Small Deployment which uses only only AR System server (this also applies to Compact Deployment or RDS stacks), select Yes, I have only one BMC AR System server, and then click Next. If you were upgrading from 3.1.x which uses two AR System servers, you would select No (I have an Enterprise-AR and a Cloud-AR server).
  15. In the Select Deployment Template panel, select the template that matches your requirements (for example, Small Deployment), and click Next.
  16. In the Deployment Tier Selection panel, select Control Tier, and click Next.
    You can upgrade products in the Control Tier, in the Workload Tier, or in both tiers. The default is Both, but this example only upgrades products in the Control Tier.

  17. In the Host Information for a Small Deployment panel, enter all the product hosts in your environment (in this case, especially the Cloud Portal Web Application host), and then click Next. 
    The installer validates all the hosts on the Control Tier, to ensure a successful integration. You do not need to enter a host name in every field on this panel, just the product hosts currently used in your environment. 

    The Host Information panel performs the integration that, in earlier releases, was a pre-upgrade procedure.

  18. If you are prompted to, enter the operating system user credentials and passwords for the target hosts, and then click Next. 
    You can apply the same credentials for all target hosts. The installer validates the credentials, deploys the RSCD Agent on the target hosts, and performs additional installation actions.

  19. When the installer finishes integrating all the products, review the products, versions, and hosts listed in the Integration Summary panel, and click Next. 

    Note

    After integration, you can review the product versions before and after the upgrade.

  20. In the Select Deployment Type panel, select Upgrade to Cloud Lifecycle Management 4.6.00, and then click Next.
    All product hosts that you integrated with your BMC Cloud Lifecycle Management solution by running the installer are now visible in the Host Information panel. If the host name or the product that you chose for upgrade is incorrect, click Previous to correct the information.
  21. If you are prompted to, enter the operating system user credentials and passwords for the target hosts, and then click Next. 
    You can apply the same credentials for all target hosts. The installer validates the credentials, deploys the RSCD Agent on the target hosts, and performs additional installation actions.  
  22. Review the summary host information, and then click Next.
  1. Review the Welcome panel, and then click Next. 
    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. In the Java Information panel, review the settings (the bundled JRE is selected by default) and then click Next. 
    Using the default bundled JRE simplifies SSL configuration, among other advantages. You can also enter the directory path to an external 64-bit Oracle 1.8 JRE 64-bit directory, for example, C:\Program Files\Java\jre8.

  4. 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.

    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.

     

  5. In the Tomcat Web Server Certificate Information panel, review the keystore information or update it as needed (for example, enter and confirm the keystore password), and then click Next. 

  6. In the Configuration Inputs panel, review the Platform Manager and Self-Check Monitor details, 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>:7070/csm
    https://<SelfCheckerServer>:8443/health
  7. In the Installation Preview panel, review the information, and then click Install. 
    The upgrade does not change directories from where you originally installed the Cloud Portal Web Application.
  8. In the Installation Summary panel, review the information, and then click Done.
  9. To verify that your installation was successful, open the following URL in a browser:
    https:// Cloud Portal Web Application Web Applicationhost:<port>/clmui
    For example (assuming that you used the HTTPS protocol):
    https://vw-aus-asp-dv58:8443/clmui 
  10. If you configured the HTTPS protocol, your connection is initially distrusted in the browser. Add and confirm the site exception.
  1. Log on as a CLM end user.

  1. To use the Cloud Portal Web Application, import the <JRE_HOME>/lib/security/cacerts file on the Platform Manager host into the JRE on the Cloud Portal Web Application and AR System server hosts.
    For example:

    keytool -importkeystore -srckeystore "C:\TEMP\cacerts"
    -destkeystore "C:\Program Files\BMC Software\
    CloudPortalWebApplication\jre\lib\security\cacerts"
    -srcstoretype JKS -deststoretype JKS -srcstorepass changeit  
    -deststorepass changeit -noprompt

    For more information, see To import Self-Signed certificates.

  2. To check the configuration (for example, to see the Platform Manager URL), the configuration URL is stored in the Config.properties file.
    You can find Config.properties by default at     ..\CloudPortalWebApplication\tomcat\webapps\clmui\WEB-INF\classes.

Where to go from here

 

 

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