CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Upgrade Overview


This section provides details on the nuances for the CloudCenter platform and provides important tips on how to proceed with your upgrade.

The Appliance Jar Files

Upgrading the CloudCenter version generally requires only one step – to run the latest appliance jar files on each component.

Installer Jars
java -jar <component>-installer.jar <component>-response.xml

The Core Upgrade File

In releases involving security patches, upgrade of software packages and addition or change of software packages to a component would require an additional step to run core upgrade binary file.

In these cases, run this additional step – you must run the core upgrade binary file before running the appliance jars.

The core upgrade file is available for all releases. When you run this file, the CloudCenter platform performs a version check and automatically exits – if the core upgrade file is not required for your CloudCenter version.

If you are upgrading:


CloudCenter 4.9.1


Run the core_upgrade.bin command.

Effective CloudCenter 4.9.0, you will see the message that is highlighted in the following image – if an upgrade is not required for this component!

CloudCenter 4.9.0

CloudCenter 4.9.1

CloudCenter 4.9.x
CloudCenter 4.8.2
CloudCenter 4.8.1
CloudCenter 4.8.0
CloudCenter 4.7.3
CloudCenter 4.8.2CloudCenter

You do not need to run the core_upgrade.bin command.

However, depending on which release you upgrade from, you may or may not need this file. See the CloudCenter 4.8.0/1 Upgrade Overview page for additional context on these two releases.

./core_upgrade.bin <os> <cloud> <component>

HA Upgrade Tips

You must reconfigure the IP address for each load balancer after each HA upgrade. See High Availability Best Practices > Load Balancer Requirements for additional details.

Upgrading to CloudCenter in HA Mode

When upgrading CCOs in HA mode, you MUST stop all the CCOs and then start them again. See Upgrade CCO for additional context.

Component Upgrade Order

Upgrade each CloudCenter component in the following order.

See Virtual Appliance Overview to understand components, modes, and roles.

  1. REPO

    Skip this section if:

    1. You do not use custom REPO servers in your CloudCenter setup.

    2. You are only using the Bundle Store (Conditional)

  2. Bundle Store

    Skip this section, if you do not use a custom Bundle Store in your CloudCenter setup.

    In all other cases, you must upgrade the Bundle Store as this component is not automatically updated by the CloudCenter platform – EVEN IF the bundle store and the REPO appliance were configured on the same server. This upgrade must be performed manually.


    If you are upgrading from CloudCenter 4.8.2 or 4.8.2x to a later 4.8.2x or 4.9.x release, you do not need to upgrade the PostgreSQL database VMs.


    If you are upgrading from CloudCenter 4.8.2 or 4.8.2x to a later 4.8.2x or 4.9.x release, you do not need to exchange the SSH keys for CCM HA environments.




    Effective, CloudCenter 4.8.2, the CloudCenter platform converts the Monitor component to the LOG_COLLECTOR as part of the upgrade process – you do not need to delete the monitor instance and setup a new log collector.

    You do not need to upgrade the log collector.

  • Appliance jars are only applicable to the CCM, CCO and AMQP components.

  • Effective CloudCenter 4.8.2:

    • The CCM role is no longer  supported. The existing CCM server that uses the CCM role is converted to the  CCM_SA role during the upgrade process. See Virtual Appliance Overview to understand roles and modes.

    • The CCM server requires additional memory for the changes in the underlying architecture. See Hardware Requirements for details.

To upgrade CloudCenter deployments from 4.5.x or 4.6.x, please contact the CloudCenter Support team.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks