Skip to Content

Hello Colleagues!

 

In this blog, I have explained the Rolling Software Upgrade procedure of SAP Cloud Platform Integration(f.k.a HCI). This blog is part of the architectural overview of SAP Cloud Platform Integration. You can find all the blogs over here.

 

Rolling software upgrades allows SAP Cloud Platform Integration to upgrade the version of a worker node while not interrupting the message processing service. New traffic will be routed to the higher version of worker node and existing connections will not be interrupted. The cloud managed services team triggers the rolling upgrade of SAP Cloud Platform Integration.

 

The following diagram helps explain the rolling upgrade procedure –

Rolling_Update.png

Currently, the frequency of upgrades is once-a-month. Every month, SAP Cloud Platform Integration releases a new version with new capabilities and this is available to all the customers. Backward compatibility of the integration content is assured – that means, you do not have to check integration flows that you have developed on an older version against the latest version of the runtime.

 

A note on the tool-set when an upgrade is done: During every upgrade, the Web-based IDE is also upgraded. If you are using an eclipse-based toolset, then you must manually upgrade the same from the SAP Cloud Platform Integration Eclipse update site. You shall be notified in Eclipse if you are connecting to a higher version of the runtime.

 

So, the nodes are upgraded without cutting off existing message connections. You can send messages while the upgrade is going-on. No interruption of message processing services and no observable downtime for the end-users.

However, we still have the data maintenance windows for SAP Cloud Platform Integration. This is for two reasons: (1) The underlying SAP cloud platform is also upgraded and (2) During upgrade, you cannot deploy new integration artifacts to the tenant. The existing integration artifacts can continue processing messages.

 

All tenant owners of SAP Cloud Platform Integration shall be notified when an upgrade is done. Information on the maintenance windows depends on the location of the data centre you have chosen and is available in the contracts that you sign when purchasing SAP Cloud Platform Integration.

 

So, that is how we release new versions of SAP Cloud Platform Integration to all customers and partners every month!

 

Best Regards,

Sujit

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Rajesh pasupula

    Hi Sujit – Thanks for the information on the Software Update.

    I like to get a query clarified in this context, how can we check which version of the HCI Runtime eclipse components need to be used based on the tenant version.

    e.g. If My HCI Tenant runtime version is 1.10.,but my eclipse is using different version.

    is it possible to check the Tenant runtime version so that required version can be installed in eclipse ?

    Thanks

    Rajesh

    (0) 
    1. diptee s

      Hello Rajesh,

      As already stated by Sujit, you will a notification in your Eclipse, whenever you start it. No need to really go and check the version for the runtime.

      regards,

      Diptee

      (0) 
  2. Tim Hild

    Sujit,

    Thank you for your blogs here – they are clear and concise.

    One quick question, certain industries like Life Sciences, where landscape validations are a central tenant to operations, may have adverse affects to this rolling upgrade strategy. Are there accommodations / options available to customers to ensure that these rolling upgrades are performed within the context of specific change management procedures?

    Thanks,

    Tim

    (0) 
    1. Sujit Hemachandran Post author

      Hi Tim,

      Thank you. The rolling updates right now are strictly within the context of zero-content management. That is, no content that is already deployed on the tenant have to be changed by the customer. From an operational perspective, the users and authorizations that exist on a tenant continue to do so. No additions or changes there.

      Hope that answers your query!

      Thanks and Regards,

      Sujit

      (0) 

Leave a Reply