Upgrading the localized My Cloud Services console for version 4.6

If you localized the 4.5 version of the My Cloud Services console, the install planner automatically backs up the key/value files for your additional locales when you upgrade to version 4.6. After you finish upgrading BMC Cloud Lifecycle Management, you must perform the following steps if you localized the 4.5 My Cloud Services console and you want to preserve your customizations. 

This topic contains the following information:

• • Before you begin
  • Directory location of existing localized files backed up by the installer
  • To update key/value files with new data after you finish the upgrade
  • To copy updated key/value files to appropriate directories
  • To view the localized version of the My Cloud Services console
  • Where to go from here
  • Related topic

Before you begin

Review Preparing-for-upgrades, especially Preserving customizations after upgrade.

Directory location of existing localized files backed up by the installer

The install planner automatically backs up your existing 4.5 localized files from the following directories:

To update key/value files with new data after you finish the upgrade

The My Cloud Services console contains new keys/values for parts of the UI that changed in version 4.6. You must localize these strings after you finish the upgrade.

In addition, date formats were moved out of the resources-locale_en.js file and put into the angular-locale_en.js file. The appropriate date formats for the other locales were put into the other out-of-the-box angular-locale_<language code>.js files.

1. Upgrade the My Cloud Services console to version 4.6. 

2. Copy the new keys and their corresponding values from the installed 4.6 version of resources-locale_en.js to all of your other version 4.5 resources-locale_<locale>.js files that were copied to the <install_directory>/backup directory by the install planner.
   Make sure that you copy the following keys to your resources-locale_<locale>.js files.

   grid.columnlabel.label
   resources.manageLabelDialog.selectedResourcesName
   resources.manageLabelDialog.labelAs
   resources.manageLabelDialog.create
   labelCreateMsg
   resources.manageLabelDialog.labelInputPlaceholder
   catalog.addToCartDisabledMessage.customPanels.invalid
   serverpageLftNav.labels
   myresources.actions.manageLabels
   msg.error.server.action.failed.checklog
   msg.error.service.action.failed.checklog
   msg.error.storage.action.failed.checklog
   catalog.details.owner.tenant
   catalog.details.owner.role
   catalog.details.owner.reasondisabled.owner
   catalog.details.owner.search.empty
   catalog.details.owner.searchplaceholder.findusers
   catalog.details.custom.panel  
   banner.logout.header.confirmationDialog
   banner.logout.body.confirmationDialog
   parameter.input.fail.validation
   grid.columnlabel.complianceExecutionState
   grid.columnlabel.complianceState      
   grid.columnlabel.compliancePercentage    
   resources.manageLabelDialog.invalid-label
   resources.manageLabelDialog.sharedLabelMsg
   resources.serverlistoptions.resetColumn 

   • If you installed the 4.6 version of My Cloud Services console (clmui) on its own host (for example tomcat), the resources-locale_en.js file extracted from the clmui.war file is inside the <tomcat_install_directory>/webapps/clmui/common/i18n/scripts/ directory.
   • If you did not install the 4.6 version My Cloud Services console (clmui) on its own host but on the Platform Manager host, within the <install_directory>/Cloud_UI/custom_sample/i18n directory is the resources-locale_en.js file extracted from the clmui.war file.
     

3. For each new key that you add to your resources-locale_<locale>.js files, add the appropriate translated value.
   For example, add the localized value to the new key to the resources-locale_fr-fr.js file:

   [
      {
          "key": "grid.columnlabel.label",
          "value": "Étiquette de colonne"
      },
      {
          "key": "resources.manageLabelDialog.selectedResourcesName",
          "value": "Nom des ressources Sélectionné"
      },
   ]

    

4. If you modified any angular-locale_<language_code>.js file in version 4.5, add the date formats to the angular-locale_<languageCode>.js file that the install planner backed up to the <install_directory>/backup/clmui/thirdparty/scripts/angular-plugins/angular-i18n directory.

   Note

   You perform this manual step because the date formats were moved from the resources-locale_en.js file to the angular-locale_en.js file.

   For each one of those files (if there are any), add the following properties after the "shortTime": "H:mm" property only if you had modified the angular-locale_fr.js file in 4.5.

   "shortTime": "H:mm",
   "customDate": "dd/MM/yyyy",
   "clmGridDateFormat":"dd/MM/yyyy",
   "clmGridDateTimeFormat": "dd/MM/yyyy HH:mm",
   "clmRequestsDateTimeFormat": "dd/MM/yyyy HH:mm"

To copy updated key/value files to appropriate directories

You can now copy the updated key/value files (described in Directory location of files backed up by the installer) to their appropriate directories on the My Cloud Services Console host.

1. Copy over all of the files inside the <install_directory>/backup/clmui/common/i18n/scripts directory to the <install_directory>/Cloud_UI/custom/i18n/scripts directory.
2. Copy over all of the files inside the <install_directory>/backup/clmui/common/i18n/scripts/bundle directory to the <install_directory>/Cloud_UI/custom/i18n/bundle directory.
3. Copy over all of the files inside the <install_directory>/backup/clmui/thirdparty/scripts/angular-plugins/angular-i18n directory to the <install_directory>/Cloud_UI/custom/i18n/angular-i18n directory.

To view the localized version of the My Cloud Services console

Perform these final steps to test if your localization was successful. 

1. Restart Platform Manager.

1. Set the default locale in your browser to match the resource files that you just created, for example, French. 
2. Clear your browser cache.
3. Log on to the My Cloud Services console to see your localized page, for example, French.
   

Where to go from here

When you finish upgrading, inform your user community to flush the cache on their browsers. Otherwise, they run the risk of seeing a confused mix of old and new functionality in their browsers. 

Related topic

CLM-product-configuration-files-after-upgrade