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.

Prerequisites for upgrade

This section describes the prerequisites that you must perform before you upgrade your BMC Cloud Lifecycle Management solution to version 3.1 in a High-Availability (HA) and non-HA environments. In this section, the following topics are provided:

Oracle JRE requirements

 When the product installation or upgrade requires the 64-bit Oracle JRE as a prerequisite, you cannot substitute the OpenJDK version. Before you start:

  1. Check the Java version installed on your host.

  2. If the OpenJDK is installed, uninstall it and replace it with 64-bit Oracle JRE 1.6 or later. 

    Note

    Oracle JRE 7u71 or greater is required for a successful BMC Server Automation installation.

  3. If you removed the OpenJDK and installed the Oracle JRE, verify that the environment variables are properly set to reflect the new JRE version. 

To create backups and snapshots

  1. Take a snapshot of the physical computer or VM and back up database for enterprise AR System and Cloud database at the same time.

  2. Ensure that you restore the database and host computers for enterprise AR System server and Cloud database together. Otherwise, you might encounter possible data corruption issues.

    Note

    After you back up the Cloud Platform Manager host computer, ensure that you back up the hosts and databases for the enterprise AR System and Cloud database products. You must perform this step to save the data that the Cloud Platform Manager created on the Cloud database.

    From the host on which you installed Cloud Platform Manager, back up the Platform_Manager folder.

  3. From the host on which you installed the preboot executable environment (PXE) server, back up the TFTP folder.
     This folder is deleted on the target computer during the upgrade process.

  4. Before you upgrade the PXE server, back up your data store.

    Note

    Ensure that you specify the correct data store location.

  5. For all products that you want to upgrade in the solution:
    1. Take a snapshot of the host on which you installed the product.
    2. Back up the product database, if one exists.
       For example, for BMC Atrium Core – Web Registry components, take a snapshot of the host on which you installed the web registry. For enterprise AR System, backup the the host on which you installed the product and the database.

    3. Back up the following configuration files:

      Product

      File

      Platform Manager

      Linux: <PM_Install_Directory>/Platform_Manager/wrapper.conf
      Windows: <PM_Install_Directory>\Platform_Manager/wrapper.conf

      Enterprise-AR and Cloud-AR

       

      Linux:  <ARS_Home>/conf/ar.conf
      Windows: <ARS_Home>\Conf\ar.cfg

      Enterprise-AR and Cloud-AR

       

      Linux: /etc/arsystem/<hostname>/armonitor.conf
      Windows: <ARS_Home>\Conf\armonitor.cfg

      Enterprise-AR and Cloud-AR

       

      E-AR Linux:
      <ARS_Home>/pluginsvr/pluginsvr_config.xml
      <Cloud_Portal_Home>/Cloud_Portal/plugin/pluginsvr_config.xml

      E-AR Windows:
      <ARS_Home>\pluginsvr\pluginsvr_config.xml
      <Cloud_Portal_Home>\Cloud_Portal\plugin\pluginsvr_config.xml

      C-AR Linux: <ARS_Home>/pluginsvr/pluginsvr_config.xml

      C-AR Windows: <ARS_Home>\pluginsvr\pluginsvr_config.xml

      Mid Tier

      Linux: <TOMCAT_INSTALL_DIR>/conf/server.xml
      Windows: <TOMCAT_INSTALL_DIR>\Tomcat6.0\conf\server.xml

      Atrium Orchestrator AMREPO

      Linux:
       <AMREPO_INSTALL_DIR>/repository/config/repository.xml
       <AMREPO_INSTALL_DIR>/tomcat/webapps/baorepo/WEB-INF/classes/META-INF/repository.xml
      Windows:
       <AMREPO_INSTALL_DIR>\repository\config\repository.xml
       <AMREPO_INSTALL_DIR>\tomcat\webapps\baorepo\WEB-INF\classes\META-INF\repository.xml

      Atrium Orchestrator CDP

      Linux: <CDP_INSTALL_DIR>/tomcat/webapps/baocdp/WEB-INF/classes/log4j.xml
      Windows: <CDP_INSTALL_DIR>\tomcat\webapps\baocdp\WEB-INF\classes\log4j.xml

      BMC Network Automation

      Linux: <BCA_NETWORKS_INSTALL_DIR>/logging.properties
      Windows: <BCA_NETWORKS_INSTALL_DIR>\logging.properties 

      BMC Network Automation

      Linux: <BCA_NETWORKS_INSTALL_DIR>/tomcat/conf/server.xml
      Windows:<BCA_NETWORKS_INSTALL_DIR>\tomcat\conf\server.xml 

      BMC Network Automation

      Linux: <BCA_NETWORKS_INSTALL_DIR>/database.properties
      Windows: <BCA_NETWORKS_INSTALL_DIR>\database.properties

      BMC Database Automation

      GUI PHP Configuration (Manager Host) Linux: <BDA_Install_Dir>/etc/php.ini

      BMC Database Automation

      GUI Web Server Configuration (Manager Host)

      Linux: 

      /etc/httpd/etc/conf/httpd.conf

      /etc/httpd/etc/conf.d/gridapp.conf

       

Enabling logs if you run into problems

This section describes how to enable logging if you run into issues (for example, with E-AR, C-AR, Cloud Portal, or Cloud Extensions upgrades or with Cloud Portal and Cloud Extensions new installations) and you must re-run the installation or upgrade to get additional information for troubleshooting.

Note

  • These steps are optional and you should only perform them on an "as needed" basis, because they can slow down the AR System server response time during installations or upgrades.
  • The AR System must be installed before you can perform this procedure.
  1. Log on to the AR System server.
    http://<hostname:<port>/arsys 
  2. Open the AR System Administration Console (select Applications >AR System Administration >AR System Administration Console).
  3. Open the Server Information window (select System >General >Server Information).
  4. Click the Log Files tab.
  5. Enable the following logs:
    LogFiles.png
    • API Log
    • Escalation Log
    • Filter Log
    • SQL Log
    • Plug-in Log
  6. Click Apply and Save.

Preparing for product upgrades

This section explains that steps you must perform to prepare you product hosts for upgrading on non-high availability servers.

To prepare the BMC ProactiveNet and Performance Manager for upgrade

Before you upgrade the BMC ProactiveNet components, you must complete the following prerequisites:

  1. Ensure that all the BMC ProactiveNet servers and the BMC ProactiveNet Data Collection Host systems with domain names can be pinged by one another.
  2. If the BMC database and the BMC Application Server reside on different systems, ensure that they are synchronized.

Note

If you installed BMC ProactiveNet manually or in an HA environment via operating system cluster in the BMC Cloud Lifecycle Management 2.1 deployment, you must manually apply 8.6.02 patch (8.6 SP2). Then upgrade to version 9.0 using the BMC Cloud Lifecycle Management 3.1 Installer.

Additionally, if you had installed BMC ProactiveNet using BMC Cloud Lifecycle Management 2.1 Installer and are using the BMC ProactiveNet Performance Management Enterprise License, you must apply the 8.6 SP2 patch before upgrading to 9.0. For a BMC ProactiveNet basic license, you need not apply 8.6 SP2 patch.

For fixing issues with the BMC ProactiveNet and Performance Manager upgrade, see Upgrade-issues-with-BMC-ProactiveNet-Performance-Management.

To prepare for BMC AR System Server and IT Management Suite upgrade

To ensure an efficient BMC AR System Server and IT Management Suite upgrade, see the following steps described in the BMC Remedy AR System online technical documentation:

Before performing

Review this topic

BMC AR System upgrade

BMC Atrium Core upgrade

BMC ITSM upgrade

BMC SRM upgrade

BMC SLM upgrade

To prepare for a BMC AR System Server – Cloud Database upgrade

To ensure an efficient cloud database upgrade, see the following steps described in the BMC Remedy AR System online technical documentation:

Before performing

Review this topic

BMC AR System upgrade

BMC Atrium Core upgrade

Preparing for product upgrades in a high-availability environment

This section explains the steps that you must perform to prepare you product hosts for upgrading on HA servers. For recommendations for installing products in a HA environment, see Installing-products-for-HA.

To configure the mid tier for the upgrade

Perform the following steps to ensure that you can access the enterprise AR System and Cloud database using the mid tier:

  1. Open the BMC Remedy Configuration Tool using the following URL: http://:<hostname>:<port>/arsys/shared/config/config.jsp.
  2. On the AR Server Settings panel, click Add Server and specify the enterprise AR System – Primary host name.
  3. On the General Settings panel, set the following fields to he enterprise AR System – Primary host name:
    • Preference Server(s)
    • Data Visualization Module Server(s)
    • Homepage Server
    • Authentication Server
  4. Repeat steps 2 and 3 to add Cloud database to the mid tier configuration.

To remove enterprise AR System and Cloud database from the server group

Before you install the AR Extension, you must remove the AR System servers from the serer group. You must perform this step to remove any load balancer settings that you might have configured in your environment.

  1. Go to ARSystemserverInstallationdirectory\Conf.

  2. Open the ar.conf (on Linux) or ar.cfg(on Microsoft Windows) file and remove the following entries:

    Map-IP-Address: 10.128.253.183 10.128.105.209
    Map-IP-Address: 10.128.106.166 10.128.105.209
  3. Update the Server-Name and Server-Connect-Name properties with the host name on which you installed the enterprise AR System.
  4. Using the mid tier, log on to the Primary and Secondary servers of the enterprise AR System and Cloud database products.
  5. Go to AR System Administration Console > System > General > Server Information > Connection Settings > Configuration tab.
  6. Clear the Server Group Member box.
  7. Restart the AR System Server service on the enterprise AR System and Cloud database hosts.

To prepare the DSO information for the upgrade

If you have installed a server group environment for the following products, ensure that you update the Distributed Server Option (DSO) for them to point to the Primary servers:

  • The enterprise AR System server(all nodes in server group)--Update the DSO target with the Cloud database – Primary host information
  • The Cloud database servers (all nodes in server group)-- Update the DSO target with the enterprise AR System – Primary host information
  1. Using the mid tier, log on to any of the AR System server in the server group.
  2. Search for the Distributed Logical Mapping form and change the Name attribute value to the host name on which you installed the enterprise AR System – Primary or Cloud database – Primary depending on the following points:
    • For the enterprise AR System, specify the Cloud database – Primary host name.
    • For the Cloud database, specify the enterprise AR System – Primary host name.
  3. Using the mid tier, log on to the Primary and Secondary servers of enterprise AR System and Cloud database products.
  4. Go to AR System Administration Console > System > General > Server Information > Connection Settings > DSO Server tab.
  5. Change the Server Nameto the local host name on which you installed the Enterprise AR System server – Primary depending on the following points:
    • For the enterprise AR System, specify the Cloud database – Primary host name.
    • For the Cloud database, specify the enterprise AR System – Primary host name.
  6. Restart the AR System Server service on the enterprise AR System and Cloud database hosts.

To prepare the enterprise AR System for the upgrade

Before you upgrade the enterprise AR System host, you must complete the following prerequisites:

  1. Ensure that the enterprise AR System host has a minimum of 16 GB RAM and 4 CPUs available.

    Note

    Ensure that you have the same amount of RAM and same number of CPUs on the Cloud Database host also.

  2. Verify that the following queue parameters are listed in the ar configuration file (ar.cfg on Windows and ar.confon Linux):

    Private-RPC-Socket:  390601   1   1
    Private-RPC-Socket:  390603   5  10
    Private-RPC-Socket:  390620  12  12
    Private-RPC-Socket:  390621  12  16
    Private-RPC-Socket:  390622   4   6
    Private-RPC-Socket:  390626  12  12
    Private-RPC-Socket:  390635  20  20
    Private-RPC-Socket:  390680   2  25
    Private-RPC-Socket:  390681   4   4
    Allow-Unqual-Queries: T
  3. If the queue parameters are not present on the enterprise AR System primary and secondary hosts, add these parameters in ar configuration file and restart the AR System server services.
  4. Tune your MS SQL and Oracle databases according to the guidelines in the BMC Remedy AR System documentation: Preparing your database for an upgrade.

  5. Open the CMF:PluginConfiguration form for the enterprise AR System and change the following attributes:

     Example: Callback URL: {nolink}http://CLM-MT:8080/arsys/plugins/CloudCallBackPlugin/params?server=<EnterprisePrimaryHostname>&username=csmcallback&pwd=csmcallback{nolink} 
    • Callback URL: set to the host name on which you installed the enterprise AR System – Primary
    • FIELD_AO_HOST: set to host name on which you installed BMC Atrium Orchestrator – Primary

  6. Update the BMC BMC.CLOUD.BMc_Callout join form on the Cloud database host:

     Example:{nolink}[http://clm-mt:8080/arsys/plugins/CloudCallBackPlugin/params?server=]<ITSMPrimartHost>&username=csmcallback&pwd=csmcallback&operation=CHECK_CHANGE_REQUIRED{nolink}
    1. Search for the CSM Change integration HTTP Callout entry.
    2. Click on View relationship and open the URL entry.
    3. From the Custom tab, update the Attribute Value with the host name on which you installed the enterprise AR System – Primary.

To prepare the Cloud Platform Manager for the upgrade

Before you upgrade the Cloud Platform Manager host, you must open the Cloudservice.JSON file and set the attributevalue parameter of Cloud database load balancer setting name to the host name on which you installed the Cloud database – Primary.

Where to go next

Upgrade-sequence

 

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