Patches

This topic contains an overview of the enhancements in patches, and provides instructions for downloading and installing the patch.

Build information

The latest patch for BMC Cloud Lifecycle Management is 4.6.07.002. The following table lists the build information for recent patches.

ReleaseEPD version numberRelease date
Patch 2 for version 4.6.074.6.07.002July 16, 2019
Patch 1 for version 4.6.074.6.07.001March 15, 2019
Patch 1 for version 4.6.064.6.06.001April 11, 2018
Patch 1 for version 4.6.004.6.00.001March 16, 2018
Patch 2 for version 4.6.054.6.05.002September 30, 2017
Patch 1 for version 4.6.044.6.04.001March 10, 2017


Updates in recent patches

To locate any update for a particular patch, perform any of the following actions:

  • Select a patch number from the Available in list to filter the table by patch version numbers.
  • Type a character string in one or more of the boxes to filter the list of updates.  
  • Click any column heading to sort this table or change sort direction.

Note

When you install a particular patch version, updates from earlier patch versions are also be included in that patch. 

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

UpdateDescriptionAvailable in
RSSO integration

Now, BMC Cloud Lifecycle Management supports Remedy Single Sign-On (Remedy SSO) 18.05 for Tomcat based End User Portal. The following authentication methods are supported:

  • SAMLv2
  • LDAP

For information about how to configure Remedy SSO in BMC Cloud Lifecycle Management End User Portal, see Configuring RSSO and Configuring Remedy Single Sign-On for BMC Cloud Lifecycle Management.

For information about the REST APIs used for this configuration, see APIs for Remedy Single Sign-On configuration for BMC Cloud Lifecycle Management.

4.6.07.002
JRE version change

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

4.6.07.002
Support for new Hyper-V versions

Now, Hyper-V 2016 and 2019 are supported with TrueSight Server Automation 8.9.04.001.

4.6.07.002
AWS specific environment

You can specify the region if you are using specific AWS environment. For example, if you are using AWS government environment, you can specify us-gov-west-1. If the field is blank, AWS Public platform is used.

A new field default_region is added to Manage User Accounts window. For more information, see Configuring user credentials for Amazon Web Services workloads and Provisioning for AWS CloudFormation.

4.6.07.001
Include new subnets while refreshing a logical data centre.You can refresh a logical data centre to include new subnets that have been added to the onboarded logical data centres. For more information, Managing Logical Data Centers for the Azure Provider.4.6.07.001
Zulu JRE 1.8

BMC Cloud Lifecycle Management Feature Pack Installer now packages Zulu JRE 1.8 as bundled JRE.

4.6.07.001
TLS 1.2

BMC Cloud Lifecycle Management supports Transport Layer Security 1.2 (TLS 1.2).

4.6.07.001
Support NSH script as custom actionYou can now use an NSH script as custom action in the Option Editor for AzureRM Provider. For more information about how to use Options Editor, see Configuring end-user Option Choices in service blueprints.4.6.07.001
Upgrade Brownfield UtilityYou can now upgrade the Brownfield Utility. For more information, see Using the BMC CLM ITSM Brownfield utility.4.6.07.001
Integrating with BMC Remedy ITSM

On the Corporate ITSM server, while creating a change user for a support company, you do not need to add Administrator (BMC Remedy AR System) to the Update Permission Groups list. For a newly created change user, you must set only the following permission groups:

  • Infrastructure Change Config

  • Infrastructure Change User 

For more information, see Integrating with BMC Remedy ITSM.

4.6.07.001
Support Suspend/Resume operation for VMWare

You are able to suspend/resume a Virtual Machine for VMWare Hypervisor (same functionality is already supported for OpenStack).

4.6.06.001
Azure resource group creationYou can place Azure VMs in an existing resource group or allow BMC Cloud Lifecycle Management to create new resource groups.

A parameter named resource-container specifies the name of an existing resource group that you can consume to deploy or consolidate all workloads. You can specify this parameter within a service blueprint at the deployment definition level.

If you select Yes for the parameter’s User Entry field, end users can specify the resource group when requesting the service.

If you select Yes, enter a clear description so that users can click on the tooltip icon next to the field to learn what the field (parameter) requires.

A new field named Relax ARM Resource Group Constraint in the Register Provider page has been added. Select True to create a resource group with the name that the user has provided in the resource-container parameter. If the resource group with the specified name already exists, then it will consume that resource group to deploy or consolidate all workloads. However, if you select False, then ensure that you must specifiy a already existing resource group name in the resource-container parameter. The default is True. For more information, see Service blueprint parameters for Azure.

4.6.05.002
Azure Disk ManagementBMC Cloud Lifecycle Management supports managed disks for Azure. You only have to specify the replication type (Premium or Standard) and the size of disk you need, and Azure creates and manages the disk for you. For more information, see To set up support for managed disk and replication type.4.6.05.002
Availability set at resource group creation

To use the AVAILABILITY_SET_NAME parameter at the resource-set level, you must provide the values with the following naming convention for Name and Default Value field respectively:

Name - ResourceSet: AVAILABILITY_SET_NAME

Default Value - <AvailabilitySetName>:<Fault Domain>: < Update Domain>

where, the value of the Fault Domain and Update Domain must be an integer and accepted by Azure.

For more information, see Service blueprint parameters for Azure.

4.6.05.002
Cross region deploymentsBMC Cloud Lifecycle Management supports cross-region deployments of installable resources. However, you must ensure that the image is present and the image names are identical in all the regions. For more information, see Provisioning for Azure Resource Manager (with or without templates).4.6.05.002
Custom resource names for Azure resources

In BMC Cloud Lifecycle Management 4.6.05.002, you can use a custom host name advisor to control the resource names assigned to provisioned Azure resources. For more information, see Requesting cloud services.

4.6.05.002

Azure Template Provider

You can place Azure workloads in an existing resource group or allow BMC Cloud Lifecycle Management to create new resource groups while performing provisioning operations.

A new parameter named resource-container specifies the name of an existing resource group that you can consume to deploy or consolidate all workloads. You can specify this parameter within a service blueprint at the deployment definition level.

If you select Yes for the parameter’s User Entry field, end users can specify the resource group when requesting the service.

If you select Yes, enter a clear description so that users can click on the tooltip icon next to the field to learn what the field (parameter) requires.

Limitations

  • Do not delete any data sources if the Azure Template Provider references them in a service blueprint. Users cannot add an offering to a cart if the referenced data sources are deleted from the data sources workspace.
  • BMC Cloud Lifecycle Management does not allow you to create data sources with special characters. The #resourceset# value cannot be passed through the resource-container parameter for such data sources.
  • If a referenced provider was deleted and re-added to the system, you must rediscover parameters in an existing blueprint. Parameter discovery rebinds the service blueprint to the newly added provider.
  • Specify the resource-container parameter at the deployment definition level in a service blueprint. Specifying at the resource-set level is not supported

Known issues

  • Occasionally, decommissioned instances are not cleaned up immediately from the Azure inventory; however, they will eventually cleanup automatically within a few minutes. BMC Cloud Lifecycle Management then reports the decommissioning as successful.
  • While consuming an existing resource group, specify the resource group name in lowercase letters only; otherwise, Azure will report a failure for a deployment without the proper name format.
The #service#  value is not supported for the resource-container parameter.
4.6.04.001
Updates for the end user portal

The BMC Cloud Lifecycle Management My Cloud Services console is now updated whenever the Technical Owner field is changed when requesting a service on behalf of another user.

The cloud administrator can also use a custom java script to perform any custom actions.

4.6.04.001
Access attributes

Customized data can now be passed to the LHE placement advisor, which in turn passes the data to an Atrium Orchestrator workflow for LHE placement.

To enable LHE placement, perform the following steps:

  1. Stop the Platform Manager service.
  2. Take backup of existing providers.json present at location <CLM Installation Directory>\Platform_Manager\configuration.
  3. Add the following Access Attribute to providers.json, below the allowTransferOwnershipToEndUserAcrossTenants access attribute:

        ,{
        "cloudClass" : "com.bmc.cloud.model.beans.AccessAttributeValue",
        "accessAttribute" : {
          "cloudClass" : "com.bmc.cloud.model.beans.AccessAttribute",
          "datatype" : "BOOLEAN",
          "description" : "UsePeerHintForLHEPlacement",
          "guid" : "6343f946-1aaa-47b1-b05c-b570b8879e78",
          "isOptional" : false,
          "isPassword" : false,
          "modifiableWithoutRestart" : false,
          "name" : "UsePeerHintForLHEPlacement"
        },
        "attributeValue" : "false",
        "description" : "UsePeerHintForLHEPlacement",
        "guid" : "b726f112-3086-4d18-9a88-012dd7f2a4cc",
        "name" : "UsePeerHintForLHEPlacement"
      }
  4. Save the providers.json file and re-start the Platform Manager service.
4.6.04.001
Changes to the API

With this update, filter criteria is passed to Atrium Orchestrator when a datasource is invoked from a custom JavaScript code using the following API:

clmContext.externalData.fetchAllowableValues (string dataSourceName, string  keyword, object filterCriteria, function callback, function error_callback).

The changes for this update are in the Platfrom Manager jar and the clmui.war file.

4.6.04.001
 A new JavaScript API can be called from custom JavaScript code that obtains the currently selected technical owner and its details to display in the console based on that technical owner.

The changes for this update are in the clmui.war file.

 


This update includes a new API the cloud administrator can use to inject custom log files into the BMC Lifecycle Cloud Management Activity Timeline page in the BMC Cloud Lifecycle Management console.

You invoke the API from Atrium Orchestrator callouts to inject the custom logs in the Activity Timeline.

 Click here to see the API signature to use.
http://<Platform_Manager>:<PORT>/csm/Activity/addActivityTimeline
Method : POST
Request BODY :
{
    "timeout": -1,
    "preCallout": "",
    "postCallout": "",
    "operationParams": [ {
            "name": "transactionId",
            "type": "java.lang.String",
            "multiplicity": "1",
            "value": "b9244652-5d69-40f0-850d-8544822d9c7e"
        }, {
            "name": "ServiceOfferingInstanceId",
            "type": "java.lang.String",
            "multiplicity": "1",
            "value": "558767b4-fdc4-4266-b84f-3e11af9a68a3"
        }, {
            "name": "header",
            "type": "java.lang.String",
            "multiplicity": "1",
            "value": "MB"
        }, {
            "name": "subheader",
            "type": "java.lang.String",
            "multiplicity": "1",
            "value": "MB"
        }, {
            "name": "message",
            "type": "java.lang.String",
            "multiplicity": "1",
            "value": "test message"
        }, {
            "name": "isError",
            "type": "java.lang.Boolean",
            "multiplicity": "0..1",
            "value": false
        } ]
}

transactionId, ServiceOfferingInstanceId : Obtain from CSMRequest XML.
header : Header for Message
subHeader : Sub Heading for the message
Message : Actual Message
isError
: Specify false for success messages otherwise specify true. If true 
specified then failure sytle message will be displayed.
4.6.04.001

Corrected issues in Patch 2 for version 4.6.07

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Back to top

Corrected issues in Patch 1 for version 4.6.07

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Back to top

Corrected issues in Patch 1 for version 4.6.06

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Back to top

Corrected issues in Patch 2 for version 4.6.05

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Back to top

Corrected issues in Patch 1 for version 4.6.04

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Back to top

Supported upgrade paths

You can only upgrade to a particular patch from its base feature pack version. The following table lists the supported upgrade paths:

Patch versionSupported upgrade paths
4.6.07.002

You can upgrade to 4.6.07.002 from one of the following versions:

  • 4.6.07.001
  • 4.6.07
4.6.06.001

You can upgrade to 4.6.06.001 from 4.6.06.

4.6.05.002

You can upgrade to 4.6.05.002 from one of the following versions:

  • 4.6.05.001
  • 4.6.05
4.6.04.001

You can upgrade to 4.6.04.001 from 4.6.04 .

Back to top

Preparing to install a patch 

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

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

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

  3. Close any open session of BMC Remedy Developer Studio.

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

  5. 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 practices

    Installing 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 mode and Customizing applications using overlays and custom objects .

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

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

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

  9. Ensure that the X11 libraries are installed on the Linux servers.

  10. 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, do the following:

Tip

In the BMC lab environment, installing the patch took about 50 minutes in the Windows Compact Deployment. 
  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.

    Patch versionOperating SystemInstallation package nameTo access the installation files
    4.6.07.002WindowsCLM_FeaturePack_4.6.07.002_Windows_Installer.zipExtract the zip package CLM_FeaturePack_4.6.07.002_Windows_Installer.zip
    LinuxCLM_FeaturePack_4.6.07.002_Linux_Installer.tar.gzExtract the package using the following command:
    tar –xvf CLM_FeaturePack_4.6.07.002_Linux_Installer.tar.gz
    4.6.06.001WindowsCLM_FeaturePack_4.6.06.001_Windows_Installer.zipExtract the zip package CLM_FeaturePack_4.6.06.001_Windows_Installer.zip
    LinuxCLM_FeaturePack_4.6.06.001_Linux_Installer.tar.gzExtract the package using the following command:
    tar –xvf CLM_FeaturePack_4.6.06.001_Linux_Installer.tar.gz
    4.6.05.002WindowsCLM_FeaturePack_4.6.05.002_Windows_Installer.zipExtract the zip package CLM_FeaturePack_4.6.05.002_Windows_Installer.zip
    LinuxCLM_FeaturePack_4.6.05.002_Linux_Installer.tar.gzExtract the package using the following command:
    tar –xvf CLM_FeaturePack_4.6.05.002_Linux_Installer.tar.gz
    4.6.04.001Windows4.6.04_Patch1.zip

    Extract the package and navigate to the following path:

    4.6.04_Patch1\PatchInstaller\linux\CLMPatchInstaller\Disk1

    Linux4.6.04_Patch1.zip

    Extract the package and navigate to the following path:

    4.6.04_Patch1\PatchInstaller\windows\CLMPatchInstaller\Disk1

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

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

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

Note about patch uninstallation

Uninstallation of patches using <CLMPatchInstallationDirectory>\UninstallBMCCLMPatchInstaller\uninstall.exe or <CLMPatchInstallationDirectory>/UninstallBMCCLMPatchInstaller/uninstall.bin is not supported.

In case of any failures during patch installation, contact BMC Customer Support.


Back to top

Configuring after installing the patch

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

To refresh the Register Provider screen

If you are upgrading from a version earlier than BMC Cloud Lifecycle Management 4.6.05.002, do the following:

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Providers.
  2. Under Quick Links, select Custom.
  3. On the Providers page, click the Edit icon.
  4. In the Register Provider dialog box, complete or modify the fields, as necessary.
  5. Click Submit.

To update BMC Remedy AR System, Atrium Web Services, and Mid-tier 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 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. 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.
  5. 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>
  6. Edit the ..\tomcat\webapps\clmui\WEB-INF\classes\config.properties file and set com.bmc.cloud.ui.isRSSOEnabled flag to true.
  7. Restart the End User Portal Tomcat service.
  8. (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:

    HostDirectory
    Enterprise BMC Remedy AR System - Primary and Secondary

    <AtriumCoreInstallationDirectory>/BMCAtriumCoreInstallJVM6  
    <SRMInstallationDirectory>/BMCServiceRequestManagementInstallJVM
    <RemedyITSMSuitePreconfiguredStackInstallationDirectory>/BMCRemedyITSMSuitePreconfiguredStackInstallJVM

    Atrium Web Services<atriumWebservicesInstallationDirectory>/BMCAtriumCoreInstallJVM6
     Atrium Orchestrator <AOContentInstallationDirectory>/ContentInstallJVM 
  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:

Failed to login to the Platform Manager

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.

Related video

The following video explains how to apply patches to BMC Cloud Lifecycle Management. It includes information related to preparing and executing the installation, verifying the installation, and troubleshooting any installation issues.

 https://youtu.be/yoV2dIg4-dI

Was this page helpful? Yes No Submitting... Thank you

Comments