For Azure Resource Manager, you can now modify the compute resources of the provisioned server in the Azure Environment as part of post-deploy activity. For example, you can modify the instance size by specifying an appropriate Azure defined instance size as part of post-deploy activity. The instance size must belong to the supported list as mentioned on Supported Azure instance families.

For more information about how to modify the compute resources, see Creating service offerings for the Azure provider.

While onboarding existing VMware VMs, you can now skip the DNS re-enrollment process by updating the BBNA_SKIP_DNS_OPERATION parameter in the providers.json file. For more information about how to set the attributeValue for BBNA_SKIP_DNS_OPERATION parameter, see How to skip DNS enrollment for existing VMware VMs.

Earlier, you could skip the DNS enrollment process using an AO script and by configuring the DNS. This method needed AO expertise and the knowledge of the DNS configuration.

Now, for VMware, you can choose to get the latest data from TrueSight Server Automation during the Synchronize Virtual Cluster operation in case of any infrastructure changes to the existing vCenter servers. The data is updated with all the infrastructure changes for the Virtual Center or Virtual Infrastructure Manager to which the selected Virtual Cluster belongs. Examples of infrastructure changes include addition or modification of Virtual Cluster, Resource Pool, Virtual Host, or Virtual Disk Repository.

Now, you do not have to wait for the Platform Manager scheduler to update the TrueSight Server Automation cache after specific intervals as mentioned in the BBSA_CACHE_REFRESH_TIME  parameter in the providers.json file.

For more information about synchronizing the virtual clusters in BMC Cloud Lifecycle Management, see the following topics:

• Scaling an existing network pod
• Onboarding and offboarding compute resources

For VMware, you can choose to get the latest list of servers from TrueSight Server Automation while onboarding existing VMs by using QuickStart. For information about onboarding existing VMs, see Onboarding existing VMs.

For Amazon Web Services, you can now refresh the Logical Data Center (LDC) information to include new subnets that have been added to the onboarded logical data centres. For more information, see Onboarding and offboarding Logical Data Centers for Amazon Web Services.

In the Catalog Details page of Cloud End User Portal, now you can display the option choices in a drop-down list instead of a radio button when the number of custom option choices is greater than a certain number. You can configure this number in the OptionChoiceDropdownModeValue parameter in the PreferenceGroup.json file. This feature is available only for the Default Category in the Catalog Details page.

For more information, see Customizing the Catalog service details page.

When you modify the CPU configuration for an existing Amazon Web Services VM, you can specify whether to start or stop the servers by modifying the following parameters in the providers.json file:

• stopServerBeforeConfigChange
• startServerAfterConfigChange
• troOptionsWithoutHotswap

Earlier, if you perform CPU configuration changes to an existing AWS VM, you had to manually start or stop the server for the changes to be effective.

For more information about the access attributes, see Access-attributes-for-service-providers-and-cloud-services.

Now, the Java Runtime Environment (JRE) version that is shipped with BMC Cloud Lifecycle Management has been upgraded to Zulu 1.8.0_222.

Downloading and installing the patch

For instructions on downloading the patch you want to install, see, Downloading-the-installation-files.

Preparing to install a patch

Before installing the patch, ensure that you review and complete the following tasks:

1. Upgrade to one of the following versions of BMC Cloud Lifecycle Management:
   • 4.6.07.002
   • 4.6.07.001
   • 4.6.07
2. Based on your deployment size, ensure that the following services are up and running, :
   • Enterprise BMC Remedy AR System primary and secondary servers
   • Platform Manager
   • QuickStart
   • Self-Check Monitor
   • Cloud Portal Web Application - This is applicable only if the My Cloud Services console or the End User Portal is installed on a remote system and not on the Platform Manager host.
3. Ensure that you have the supported versions of products in the BMC Cloud Lifecycle Management solution. For information about the supported product versions, see Component BMC product service pack and patch levels.
4. Close any open session of BMC Remedy Developer Studio.
5. If you have changed the administrator password or port for the Enterprise BMC Remedy AR System application after the last time you installed BMC Cloud Lifecycle Management, do the following:
   1. On the Enterprise BMC Remedy AR System primary server, generate an encrypted password. Do the following:
      
      1. On the Enterprise BMC Remedy AR System server, navigate to the <CLMInstallationDirectory>\BMCCloudLifeCycleManagement\Utilities directory.
      2. Run the BMCCloudLifeCycleManagementMaintenanceTool.bat/sh file.
      3. Click Encrypt.
      4. In the Password and Confirm Password fields, enter the new BMC Remedy AR System password.
      5. Click Encrypt.
      6. Copy the new encrypted password.
   2. On the Enterprise BMC Remedy AR System primary server, update the encrypted password or port in the installation configuration file. Do the following:
      1. On the Enterprise BMC Remedy AR System server, navigate to the<CLMInstallationDirectory>\BMCCloudLifeCycleManagement\  directory.
      2. Open the BMCCloudLifeCycleManagementInstalledConfiguration.xml file in a text editor and search for the BMC_AR_PASSWORD_HOSTING attribute.
      3. In the value field of the attribute, update the encrypted password.
      4. Save the BMCCloudLifeCycleManagementInstalledConfiguration.xml file.
      5. Open the <ARInstallationDirectory>\ARSystemInstalledConfiguration.xml file.
      6. Search for the BMC_AR_PORT property value.
      7. If the port is not correct, update the correct port number and save the ARSystemInstalledConfiguration.xml file.
   3. On the Enterprise BMC Remedy AR System secondary server, repeat step a and b.
6. Based on your deployment size, take a VM snapshot and a database backup of the following servers:
   • Enterprise BMC Remedy AR System primary server
   • Enterprise BMC Remedy AR System secondary server, if applicable
   • Cloud Platform Manager
   • Self-Check Monitor
   • Cloud Portal Web Application - This is applicable only if the My Cloud Services console or the End User Portal is installed on a remote system and not on the Platform Manager host.
   Warning: Following BMC Remedy AR System best practicesInstalling the patch can affect the BMC Remedy AR objects in a non-overlay mode. Ensure that you follow the Enterprise BMC Remedy AR System best practices for customizations. Customizations made to the base objects in the Developer Studio base development mode are not preserved through upgrades. For more information, see Best Practice Customization modeand Customizing applications using overlays and custom objects.
7. Ensure that you do not set the JAVA_HOME environment variable. 
   If the JAVA_HOME environment variable is set on any of the host servers, remove it and restart the server before upgrading BMC Cloud Lifecycle Management. 
8. Ensure that you do not set environment variables such as JRE_HOME and PATH to bundled Java that is located within a product installation directory. 
9. Ensure that you do not use bundled Java that is located in an installation directory of one product for configurations in a different product. For example, do not use C:\Program Files\BMC Software\BMCCloudLifeCycleManagement\jre, which is the bundled JRE of Cloud Portal AR Extensions in armonitor.conf of AR server for migrating it to Java 1.8. Use external JRE 1.8.
10. Ensure that the X11 libraries are installed on the Linux servers.
11. Ensure that the file paths are not specified by using environment variables like JRE_HOME, JAVA_HOME, or symbolic links in the product configuration files.
    For example, do not use /usr/bin/java  where java is a symbolic link. Replace /usr/bin/java with /usr/jre1.7.0_45/bin/java.
    
    

Back to top

Installing the patch

To install a patch in your environment, perform the following steps:

1. Log in to the host computer as a user with administrator privileges.
2. From the BMC Electronic Product Distribution (EPD)  location, download the patch file based on your operating system.
   
   • (Windows) CLM_FeaturePack_4.6.07.003_Windows_Installer.zip.
   • (Linux) CLM_FeaturePack_4.6.07.003_Linux_Installer.tar.gz
3. Extract the downloaded files to a temporary directory.
   • (Windows) Extract the CLM_FeaturePack_4.6.07.003_Windows_Installer.zip file.

   • (Linux) Extract the CLM_FeaturePack_4.6.07.003_Linux_Installer.tar.gz package using the following command:

     tar –xvf CLM_FeaturePack_4.6.07.002_Linux_Installer.tar.gz

4. Copy the extracted files on all the applicable VMs.
   • For compact deployment, copy the installer to the compact deployment host.
   • For small or medium deployment, copy the installer to the following hosts:
     
     • Enterprise BMC Remedy AR System primary server
     • Enterprise BMC Remedy AR System secondary server, if applicable
     • Cloud Platform Manager
     • Self-Check Monitor
     • Cloud Portal Web Application - This is applicable only if the My Cloud Services console or the End User Portal is installed on a remote system and not on the Platform Manager host.
5. Based on your deployment size, determine the hosts on which you need to install the patch.
   • For compact deployment, install the patch on the compact deployment host.
   • For small or medium deployment, install the patch on the hosts in the following sequence:
     
     1. Enterprise BMC Remedy AR System primary server
     2. Enterprise BMC Remedy AR System secondary server, if applicable
     3. Cloud Platform Manager
     4. Self-Check Monitor
     5. Cloud Portal Web Application - This is applicable only if the My Cloud Services console or the End User Portal is installed on a remote system and not on the Platform Manager host.

6. On the applicable hosts, perform the following steps:

   1. Do the following:
      • (Microsoft Windows) Navigate to the ..\CLMPatchInstaller\Disk1 directory, double-click the setup.exe file.
      • (Linux) Navigate to the ../CLMPatchInstaller/Disk1 directory and run the setup.bin file by using any X clients such as Xmanager or VConsole.
   2. On the Welcome panel, review the instructions, and click Next. 
   3. On the Details panel, read the instructions and click Next.
   4. Depending on your setup, provide the BMC Remedy AR System server details, and click Next.
   5. On the Java Information panel, select any of the following options:
      
      • Use the bundled JRE - Select this option to use the Zulu JRE that is bundled with the installer.

      • Select the JRE path- Select this option to use the external JRE. You can use one of the following options:

        • If you have purchased the Oracle Java license, use the external Oracle JRE path.
        • You can copy the Zulu JRE under ..\CLMPatchInstaller\Disk1\files to an external location and use it as the external JRE.

        Note: Java update by the installer

        The patch installer updates Java for the Platform Manager, Cloud Portal, Self-Checker, Cloud Portal Web Application. The installer does not update Java for Remedy Components which are Enterprise BMC Remedy AR System, Mid-tier, and Atrium Web Services.

   6. On the Cacerts Password Information panel, enter the Cacerts password and click Next. This password is used to restore SSL certificates from older Java cacerts to newer Java cacerts  irrespective of whether the product is configured to use HTTPS or not. 
   7. (Optional and applicable only if you have not configured RSSO details in the Platform Manager during previous upgrades) On the Remedy Single Sign-On (RSSO) Configuration panel, select Enable RSSO. Provide the following details and click Next.
      1. RSSO Service URL in the following format:
         https://<fqdnNameRSSOServer>:<port>/rsso
      2. RSSO Administrator Username
      3. RSSO Administrator Password

      4. RSSO Realm
         For information about how to configure realms, see Configuring realms in BMC Remedy Single Sign-On 9.1 documentation. 

      5. RSSO Session Timeout (in minutes) - This value must be equal to the timeout value set on the RSSO server. The default value is 1440 minutes.
         
         

         Note: Using RSSO

         For using the RSSO authentication, the BMC Cloud Lifecycle Management user must be present in the BMC Remedy AR System server. If you want to use the Administrator portal, you must refer to a local user. To use a SAML or LDAP user for the Administrator portal, set a local password for the user in BMC Remedy AR System server.

   1. On the Installation Preview panel, review the patch installer information and click Install. 
   2. On the Installation Summary panel, review the installation log and click Done to finish the installation.

Back to top

Configuring after installing the patch

Ensure that you perform the following post-configuration procedures after installing the patch.

To update BMC Remedy AR System, Atrium Web Services, and Midtier Configuration files

Do the following:

1. Stop the BMC Remedy AR System, Atrium Web Services, and Mid-tier services on primary and secondary hosts.

2. Upgrade the external JRE to 1.8 on BMC Remedy AR System, Atrium Web Services, and Mid-tier primary and secondary hosts. Use one of the following options:

   • Use External JRE – Oracle - Use this option only if you have purchased the Oracle Java license.

   • Use External JRE – Zulu - You can copy the JRE under ..\CLMPatchInstaller\Disk1\files to an external location.

3. Update the Java path depending on your operating system:

   Windows

   Registry key for BMC Remedy AR System, Midtier, and Atrium Web Services : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\<TomcatServiceName>\Parameters\Java <ARInstallationDirectory>/conf/armonitor.cfg <ARInstallationDirectory>/approval/bin/approval-utils.bat <ARInstallationDirectory>/AREmail/EmailStart.bat <ARInstallationDirectory>/AREmail/EmailStop.bat <ARInstallationDirectory>/pluginsvr/pluginsvr_config.xml <ARInstallationDirectory>/diserver/data-integration/set-pentaho-env.bat <atriumWebservicesInstallationDirectory>/wsc/atriumws81/lib/atriumwsenv.cmd

   Linux

   /etc/arsystem/<hostname>/armonitor.conf  <ARInstallationDirectory>/approval/bin/approval-utils.sh  <ARInstallationDirectory>/bin/arsystem  <ARInstallationDirectory>/AREmail/emaild.sh  <ARInstallationDirectory>/pluginsvr/pluginsvr_config.xml  <ARInstallationDirectory>/diserver/data-integration/set-pentaho-env.sh <midtier_apache_tomcat>/bin/startup.sh <midtier_apache_tomcat>/bin/shutdown.sh <atrium_webservices_tomcat>/bin/startup.sh <atrium_webservices_tomcat >/bin/shutdown.sh <atrium_webservices_tomcat>/bin/bmcAtriumSetenv.sh <atriumWebservicesInstallationDirectory>/wsc/atriumws81/lib/atriumwsenv

4. (For BMC Cloud Lifecycle environment with HTTPS/SSL) For all the following servers, import Platform Manager cacerts into the JRE using the Java keytool utility:
   1. BMC Remedy AR System primary and secondary servers

   2. All Mid-tier servers
      For more details, see Enabling SSL.

5. Start the BMC Remedy AR System, Atrium Web Services, and Mid-tier services on primary and secondary hosts.
   

To configure Remedy SSO (RSSO) agent on End User Portal

This is applicable only if you have not configured RSSO details during previous upgrades. To configure RSSO agent on the End User Portal for BMC Cloud Lifecycle Management, do the following:

1. Download the Remedy SSO 18.05 from the BMC Electronic Product Distribution (EPD) site. For Remedy SSO 18.05 download information, see Downloading the installation files in the Remedy Single Sign-On 18.05 documentation.
2. Extract the downloaded zip files to a temporary location.
3. Stop the End User Portal Tomcat service.
4. Do the following:
   1. Copy rsso-agent-all.jar from the ..\BMCRemedySSO\Disk1\files\rsso-agent directory to the ..\tomcat\webapps\clmui\WEB-INF\lib directory. 
   2. Copy the gson-2.3.1.jar file from ..\BMCRemedySSO-18.05.00\BMCRemedySSO\Disk1\files\lib directory to the ..\tomcat\webapps\clmui\WEB-INF\lib directory.
   3. Copy the rsso-agent.properties file from the ..\BMCRemedySSO\Disk1\files\rsso-agent directory to the ..\tomcat\webapps\clmui\WEB-INF\classes directory.
   4. Edit the rsso-agent.properties file to set the values for the following variables: 

1. 1. 1. agent-id – The URL of the application with which the RSSO agent is integrated.
      2. logout-urls – Set the value to /rssoLogout.html.
      3. excluded-url-pattern – Append any URLs that should not be intercepted by the RSSO web agent.
      4. sso-external-url - URL of the RSSO server (for example, https://<FQDN>:8443/rsso).
      5. sso-service-url – URL of the RSSO server same (for example, https://<FQDN>:8443/rsso).
      6. msp-deployment – Set the value to false.
      7. msp-always-show-domain-entry-page – Set the value to false.
2. Edit the ..\tomcat\webapps\clmui\WEB-INF\web.xml file and uncomment the following RSSO agent filter:

   <filter>
        <filter-name>RSSOFilter</filter-name>
        <filter-class>com.bmc.rsso.agent.RSSOFilter</filter-class>
   </filter>
   <filter-mapping>
        <filter-name>RSSOFilter</filter-name>
        <url-pattern>/*</url-pattern>
   </filter-mapping>
3. Edit the ..\tomcat\webapps\clmui\WEB-INF\classes\config.properties file and set com.bmc.cloud.ui.isRSSOEnabled flag to true.
4. Restart the End User Portal Tomcat service.
5. (Optional) If you want to use Platform Manager in the SSL mode, perform these steps:
   1. Copy the keystore file on the Platform Manager from the <PlatformManagerInstallDir>/security/keystore directory to the server where the End User Portal Tomcat is installed.
   2. Run the following command to import the keystore file:C:\server1\jre1.8.0_73\bin>keytool.exe -importkeystore -srckeystore c:\keystore -destkeystore <pathCacertsFile>\lib\security\cacerts -srcstoretype JKS -deststoretype JKS -srcstorepass changeit -deststorepass changeit

To remove outdated version of Java 

Remove the version of Java that was shipped during earlier product installations. This Java is used for launching product maintenance tools and uninstallers. The following hosts are impacted:

• BMC AR System Server – Cloud Portal database - primary and secondary servers
• Atrium Web Services
• Atrium Orchestrator Content

Do the following:

1. Take a VM snapshot of the impacted servers: Enterprise BMC Remedy AR System - primary and secondary, Atrium Web Services, Atrium Orchestrator.

2. Back up the following directories and delete the directories:

3. Log in to the impacted servers and ensure that you can launch the maintenance tools successfully. Use the following commands:
   
   

   <AtriumCoreInstallationDirectory>/atriumcore/AtriumCoreMaintenanceTool.sh   
   <atriumWebservicesInstallationDirectory>/atriumcore/AtriumCoreMaintenanceTool.sh
   <SRMInstallationDirectory>/Utilities/BMCServiceRequestManagementMaintenanceTool.sh
   <AOContentInstallationDirectory>/Utilities/ContentMaintenanceTool.sh

To clear the cache

To clear the Platform Manager cache, do the following:

1. Stop the Platform Manager service.
   • Windows: BMC CSM
   • Linux: bmccsm
2. Back up the Platform Manager cache and Platform Manager configuration directories. The default values are:
   
   • Platform Manager cache: <CLMInstallationDirectory>/Platform_Manager/cache
   • Platform Manager configuration: <CLMInstallationDirectory>/Platform_Manager/configuration
3. Delete the cache directory.
4. From the configuration directory, delete the following directories:
   • org.eclipse.core.runtime
   • org.eclipse.equinox.app
   • org.eclipse.osgi
5. Start the Platform Manager service.

To clear the mid-tier cache, do the following:

1. Log in to the Mid Tier Configuration Tool. 
2. To remove all items from the caches that BMC Remedy Mid Tier maintains, perform a flush cache.
3. To hard delete the mid-tier cache, do the following:
   1. Stop the mid-tier Tomcat service.
   2. Log on to the mid-tier server, and delete the contents of the following directories:
      • ..\ARSystem\midtier\attstore
      • ..\ARSystem\midtier\cache
      • ..\ARSystem\midtier\cachetemp
      • ..\ARSystem\midtier\dvmodule
      • ..\ARSystem\midtier\PluginsCache
      • ..\ARSystem\midtier\WEB-INF\atriumDeploymentPackages
      • ..\ARSystem\midtier\WEB-INF\AtriumWidget
      • ..\ARSystem\midtier\WEB-INF\AtriumWidget-7604
   3. From the ..\ARSystem\midtier\WEB-INF\lib directory, delete the atrium-* files.
   4. From the ....\...\Apache Software Foundation\Tomcat X.X directory, delete the contents of the work and temp directories.
   5. From the ..\ARSystem\midtier\WEB-INF\Classes directory, delete the viewStats.dat and viewStats.dat.bak files.
   6. Start the mid-tier Tomcat service.

To verify the patch upgrade

Do the following:

1. Launch a browser and clear the browser cache.
2. Use the following URL to open the BMC Remedy Action Request System login page:
   http://<ARSystemhostname>:<portNumber>/arsys
3. Enter the BMC Cloud Lifecycle Management administrator details and click Log In.
4. From the left navigation pane, click Applications > Cloud Lifecycle Management > Administration console.
5. In the top-right pane, click About.
6. Ensure that the displayed version number is correct.

Back to top

Troubleshooting patch installer issues

Issue: After a successful upgrade to the latest BMC Cloud Lifecycle Management patch, when you access BMC Cloud Lifecycle Management Administration Console > Service Designer Console, the user interface is not loaded and stops responding.

Resolution: Ensure that you update the older occurrences of the Java file path in the BMC Remedy AR System, Atrium Web Services primary and secondary, and Mid-tier Configuration files with  Java 1.8 path. For details about the steps to update the older occurrences of the Java file path, see Remove outdated version of Java.

Issue: After upgrading to the latest BMC Cloud Lifecycle Management patch, when you access BMC Cloud Lifecycle Management Administration Console > Service Catalog Console, you receive the following error message:

Resolution: Ensure that you perform the following steps:

• Execute all the Java configurations steps. For details, see Remove outdated version of Java.
• Import the Platform manager Java cacerts into the cacerts of Java used by the BMC Remedy AR System, Atrium Web Services primary and secondary, and Mid-tier servers. For details, see the Enabling-SSL-HTTPS page.