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.

Upgrade prerequisites

This topic describes the prerequisites that you must perform before you upgrade your BMC Cloud Lifecycle Management solution in both High-Availability (HA) and non-HA environments.

Checklists for performing the upgrade

Before upgrading to this version, ensure that your environment fulfills the hardware and software requirements. 

For details, see System-requirements. 

Creating backups and snapshots

  1. In case of virtual machines, ensure that you take the final snapshot of each and every product host and the database servers.

  2. In case of physical servers, take backup of the product file system the database servers.

    Note

    If the databases are on remote hosts, take snapshots of the remote database hosts as well.  

  3. Back up any customizations that you have made to your components such as AR System , Cloud Portal Web Application before you upgrade or you will lose the customizations.
  4. Review the product configuration files that are changed due to the upgrade and back them up.

Preparing for product upgrades in a non-HA environment

This section explains the steps that you must perform to prepare your product hosts for upgrading on non-HA servers. These steps are 

Product

Steps

BMC AR System Server – Cloud Portal Database (Primary and Secondary)

Before you upgrade the Enterprise-AR host, you must complete the following prerequisites:

  1. If you are upgrading Linux, reset the symlink for /usr/java/latest to JRE installation path.

  2. Verify that the following queue parameters are listed in the ar configuration file (ar.cfg on Windows and ar.conf on 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

    If the queue parameters are not present on  primary and secondary hosts, add these parameters in the ar configuration file and restart the AR System server services.

  3. Tune your MS SQL and Oracle databases according to the guidelines in the BMC Remedy AR System documentation: Preparing-your-database-for-an-upgrade.

  4. Open the CMF:PluginConfiguration form for Enterprise-AR, review the following attributes, and update them if necessary.
    For example: 

    http://CLM-MT:8080/arsys/plugins/CloudCallBackPlugin/params?server=
    <EnterprisePrimaryHostname>&username=csmcallback&pwd=csmcallback
    • Callback URI: set to the host name on which you installed the Enterprise-AR – Primary
    • FIELD_AO_HOST: set to host name on which you installed TrueSight Orchestration – Primary

  5. Review the BMC.CLOUD:BMC_Callout join form on Cloud-AR host. 

    [http://clm-mt:8080/arsys/plugins/CloudCallBackPlugin/params?server=]
    <ITSMPrimartHost>&username=csmcallback&pwd=csmcallback&operation=
    CHECK_CHANGE_REQUIRED
    1. Search for the CSM Change integration HTTP Callout entry.
    2. Click View relationship and open the URL entry.
    3. From the Custom tab, review the Attribute Value with the host name on which you installed the Enterprise-AR – Primary, and update it if necessary.
  6. To ensure an efficient BMC AR System Server and IT Management Suite upgrade, consult the product documentation for the steps. For details, see Preparing for an upgrade.

To prepare Atrium Web Registry for upgrade

(Perform these steps for bundled Tomcat only)

Atrium Web Registry upgrade using bundled tomcat is not supported on production environments.

For Windows:

  1. Login to the Atrium Web Registry host and stop the Atrium WebRegistry (atriumTomcat7) service.
  2. Copy C:\Program Files\BMC Software\Atrium Web Registry\shared folder to C:\Program Files\BMC Software and rename it to AtriumWRTomcat.

  3. Launch the command prompt and run these steps:

    C:\Users\Administrator>sc delete atriumTomcat7
    [SC] DeleteService SUCCESS
    C:\Users\Administrator>set JRE_HOME=C:\Program Files\Java\jre7
    C:\Users\Administrator>cd C:\Program Files\BMC Software\AtriumWRTomcat\tomcat7.0\bin
    C:\Program Files\BMC Software\AtriumWRTomcat\tomcat7.0\bin>service.bat install atriumTomcat7
    Installing the service 'atriumTomcat7' ...
    Using CATALINA_HOME:    "C:\Program Files\BMC Software\AtriumWRTomcat\tomcat7.0"
    Using CATALINA_BASE:    "C:\Program Files\BMC Software\AtriumWRTomcat\tomcat7.0"
    Using JAVA_HOME:        ""
    Using JRE_HOME:         "C:\Program Files\Java\jre7"
    Using JVM:              "C:\Program Files\Java\jre7\bin\server\jvm.dll"
    The service 'atriumTomcat7' has been installed.
  4. Restart the Atrium WebRegistry (atriumTomcat7) service.
  5. Verify whether the Atrium WebRegistry URL is accessible: 
    http://<AtriumWebRegistryHost>:<httpPort>/cmdbws/server/cmdbws.wsdl
  6. Delete the C:\Program Files\BMC Software\Atrium Web Registry\shared folder.

  7. Go to C:\Program Files\BMC Software\Atrium Web Registry\AtriumCoreInstalledConfiguration.xml file and set the properties as below:

    <property>
         <name>BMC_REG_TOMCAT_HOME</name>
         <value>C:\Program Files\BMC Software\AtriumWRTomcat\tomcat7.0</value>
    </property>
    <property>
         <name>BMC_REG_TOMCAT_SERVICE_NAME</name>
         <value> atriumTomcat7</value>
    </property>

For Linux: 

  1. Login to the Atrium Web Registry host and run the following command to stop the Atrium WebRegistry (atriumTomcat7) service:

    /opt/bmc/AtriumWebRegistry/shared/tomcat7.0/bin/shutdown.sh
  2. Copy the /opt/bmc/AtriumWebRegistry/shared folder to /opt/bmc and rename it to AtriumWRTomcat.

  3. Run the following command to start the Atrium WebRegistry (atriumTomcat7) service:

    /opt/bmc/AtriumWRTomcat/tomcat7.0/bin/startup.sh

  4. Verify whether the Atrium WebRegistry URL is accessible: 
    http://<AtriumWebRegistryHost>:<httpPort>/cmdbws/server/cmdbws.wsdl
  5. Delete the /opt/bmc/AtriumWebRegistry/shared folder.

  6. Go to opt/bmc/AtriumWebRegistry/AtriumCoreInstalledConfiguration.xml file and set the properties as below:

    <property>     
      <name>BMC_REG_TOMCAT_HOME</name>     
      <value>/opt/bmc/AtriumWebRegistry/shared/tomcat7.0/</value>
    </property>

To prepare TrueSight Server Automation Application Server for upgrade

Back up the C:\Program Files\BMC Software\BladeLogic\RSCD\daal (Windows) or /opt/bmc/bladeLogic\rscd\daal (Linux) folders.

To prepare TrueSight Server Automation PXE for upgrade

  1. Back up the tftp directory on the BladeLogic PXE VM and PXE datastore.
  2. Shut down all the pxe and tftp services.

To prepare Cloud Platform Manager for upgrade (For Linux only)

  1. On the host where you want to upgrade the Platform Manager, go to /root/.bash_profile, and add the following entry:

    ulimit -n 20000
  2. Restart the host.

Back to top

Preparing for product upgrades in an HA environment

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

Task

Steps

To upgrade to an HA environment

The initial steps for preparing your environment for upgrading on HA servers are the same as the non-HA servers. For HA, ensure that you perform these steps on the primary and secondary servers.

Perform the steps described in Preparing for product upgrades in a non-HA environment.

To prepare the Cloud Platform Manager for upgrade

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

 

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