Skip to Content
Information
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.

Upgrading from Savvis Provider 1.0 to Savvis Provider 2.0

The following topics provides detailed information about the process that you must perform to upgrade your BMC Cloud Lifecycle Management and Savvis integration from a previous version to the latest. You can upgrade to Savvis Provider 2.0 from Savvis Provider 1.0.

Warning

Note

To troubleshoot a Savvis upgrade issue, see Savvis-provider-issues.

Before you begin

To upgrade to Savvis Provider 2.0

Perform the upgrade sequence in the following table to upgrade from Savvis Provider 1.0 to Savvis Provider 2.0.

Sequence

High level steps

Order of tasks for upgrade

1

Deploy the Savvis module

  1. Deploy latest Savvis module on the grid.
  2. Configure modules for Savvis 2.0.

2

Update the provider definition

  1. Extract the provider definition file from Savvis 2.0.00 Windows Installer for CLM 3.1.00.zip.
    Note: Ensure that you replace the provider definition GUID of the existing Savvis Provider in the downloaded json file. All the existing provider definition GUIDs must be specified.
  2. Manually update the provider definition using the downloaded provider definition file.

3

Import the BMC Remedy AR System definition files

  1. Extract the required BMC Remedy AR System definition files for Savvis Provider 2.0 from Savvis 2.0.00 Windows Installer for CLM 3.1.00.zip.

4

Create the Savvis 1.0 Provider user account information

5

Run the upgrade

  1. Extract the migration-manager-1.0.0.jar from Savvis 2.0.00 Windows Installer for CLM 3.1.00.zip.
  2. Navigate to the BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\lib folder and replace the existing migration-manager-1.0.0.jar file with the downloaded migration-manager-1.0.0.jar file.
  3. Stop the BMC Platform Manager.
  4. Clear cache by deleting all the items present in the \BMC Software\BMCCloudLifeCycleManagement\Platform_Manager\cache and \temp folder.
  5. Start the BMC Platform Manager and ensure that the BMC Platform Manager has started successfully.
    Note: Usually takes 15-20 minutes to start after clearing cache.

  6. Put BMC Platform Manager in maintenance mode by using the REST client.

    POST http://<OSGI-HOST>:8080/csm/node/rejectIncomingRequestsOnAllNodes

  7. Start the migration of Savvis Provider 1.0 to Savvis Provider 2.0 by using the REST client.

    POST http://<OSGI-HOST>:8080/migration/start

6

Verify the upgrade

Verify whether upgrade is completed successfully:

  1. Check the migration status by using the REST client. 

    GET http://<OSGI-HOST>:8080/migration/status

     Success should return for all tasks.

  2. Check the migration status by using the migration.log file.
    Logs will show Migration Completed Successfully.

7

Post-upgrade configuration

  1. Put BMC Platform Manager in normal mode using REST client. 

    POST http://<OSGI-HOST>:8080/csm/node/acceptIncomingRequestsOnAllNodes
  2. Stop, clear cache, and restart BMC Platform Manager.
    Note: Wait for BMC Platform Manager to start successfully. Usually it takes 15-20 minutes to start after clearing cache.

  3. Run config.jsp to clear and flush cache. 

    http://<hosts>:8080/arsys/shared/config/config.jsp

     This will also restart the mid tier.

 

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

BMC Cloud Lifecycle Management 3.1