Skip to Content
Author's profile photo Murali Shanmugham

Setting up High availability for HANA Cloud Connector

UPDATE (Nov-2017): Check out the latest blog by Simen Huuse on this topic – High availability for SAP Cloud Connector – 2.10

The HANA Cloud Connector is a crucial component when it comes to exposing your on-premise business data the HANA Cloud Platform. In the last few months, I have been asked few questions around this topic. Hence, in this blog post, I am going to explain how to setup and configure HANA Cloud Connector for High availability.

 

I am going to setup two HANA Cloud Connectors – Master and Shadow. For demonstration purposes, I am going to have both the SCCs on my laptop but running from different ports. Ideally, they will be installed on different machines.

 

Install the Master HANA Cloud Connector

 

Download and install SCC from SAP Development Tools 

 

 

Proceed with the Installation wizard. Ensure that you select “Master” for the first SCC which you install.

 

 

I have given the port as 8443 (default port). There is a How-To-Guide on how to install and configure HANA Cloud Connector.

 

In the below screen you can see that I have configured my Master SCC to point to my HCP Trial account and I have also configured a connection to one of my ABAP backend systems.

 

To enable High availability, we need to first go to the setting (top right-hand corner) and enable the checkbox shown below

 

 

Install the Shadow HANA Cloud Connector

 

Follow the same steps as mentioned above to install the HANA Cloud Connector. The only difference being, select “Shadow” for installation type and chose a different port. Since I have both on the same machine (for demonstration purpose), I have given a different port – 8434

 

 

Once you login to the Shadow SCC, you will see limited options. The first activity would be to connect to the master SCC.

 

 

Provide the host name and port where the master SCC is running and click on connect.

 

 

Check Interval – represents the time-frequency in which the Shadow pings the master. If the master is not reachable for a while (represented by the takeover delay), the Shadow tries to take over the master role and to establish the tunnel to SAP HANA Cloud Platform. I personally think 60 seconds is a long time and should be carefully considered. I am going to accept the defaults and proceed.

 

Once this your provide the Administrators detail and successfully connect to the master, you will notice all the settings (including mappings/rules) will be copied across. This will be in read-only mode.

 

 

Notice all the system mappings are copied across.

 

 

Test the failover

 

Before I test the failover, I am first going to my HCP account to check the connectivity. I can see a “Shadow Instance” showing up in the connectivity. For demonstration purposes, I have got my Shadow SCC on 2.8 version and master on 2.7 version. Ideally, we should have them on the latest versions.

 

 

I am first going to check if my changes in master configuration replicate to the salve. Hence, I am going to change the resources of U3F system.

 

 

I am going to change the resources from “/” to “sap/opu/odata”

 

 

When I login to my Shadow SCC, I should be able to see the changes being reflected.

 

 

I will shut down my master SCC instance to check if the Shadow SCC connects. Since I have given the check interval as 60 seconds and takeover delay as 30 seconds, it will few take seconds for the Shadow to take over.

 

If I quickly go to my HCP account and check the SCC connectivity, there should be none for few seconds.

 

 

After few seconds, once the Shadow has identified that the master has gone down, it assumes the role of a master and the salve SCC establishes a connection to the HCP account.

 

Notice that the Shadow has already taken the role of a master SCC. I could confirm this with the version of the SCC.

 

 

Now when I login into the Shadow SCC, I will get to see a different UI. Yes, you will start to the see the same screen which you used to see in the master SCC. From here on, the Shadow SCC acts as a Master SCC and when the original master SCC comes online, it will take the role as a Shadow SCC.

 

 

The original Master SCC, will be read-only when it comes back online

 

 

When the original master SCC comes online and if you want to switch the roles, you can click on the “switch roles” button.

 

 

Hope you found this info useful.

Assigned Tags

      14 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Markus Tolksdorf
      Markus Tolksdorf

      The TLA that needs to be used is SCC - not HCC.

      Best regards,

      Markus

      Author's profile photo Craig Davis
      Craig Davis

      Hi Murali - great blog, thanks for sharing. Rgrds Craig

      Author's profile photo Murali Shanmugham
      Murali Shanmugham
      Blog Post Author

      Thanks Craig.

      Author's profile photo Murali Shanmugham
      Murali Shanmugham
      Blog Post Author

      Hi Mark, Thanks for correcting me.

      Author's profile photo Chris Paine
      Chris Paine

      "There's nothing like consistency, and that's nothing like it" 😛

      Have often seen SAP HANA Cloud Connector abbreviated as SCC, and wondered why. I mean we have SAP HANA Cloud Platform -> HCP, SAP HANA Cloud Integration -> HCI seems strange - is it because someone actually realised that it didn't have HANA involved anywhere? (in which case HCI should be renamed perhaps too? 😉 )

      Have a good weekend!

      Cheers, Chris

      Author's profile photo Ulrich Schmidt
      Ulrich Schmidt

      Hi Chris,

      I can perhaps shed a bit light on this: the original name, when the SCC was first released in 2012, was "SAP Cloud Connector". This can still be seen in its OSS component, which is "BC-MID-SCC".

      Then a year or so later, marketing decided that every cool SAP product today needs to have the term "HANA" in its name, no matter whether it actually has anything to do with the HANA database or not... 😉

      So it got renamed. We (development) tried to protest, but invane... But since it is technically impossible to change an OSS component, we at least kept the "SCC" abbreviation... 🙂

      Cheers, Ulrich

      Author's profile photo Jitendra Kansal
      Jitendra Kansal

      HCI has been renamed to HCP-Integration services

      Author's profile photo Chris Paine
      Chris Paine

      Thanks - I was happy that HANA Cloud Portal had been renamed to HCP - Portal services (mainly happy because having two things that reduced to HCP was rather confusing.) but didn't catch the HCI renaming. Are we still referring to it as HCI or now HCP-IS ??

      Cheers,

      Chris

      Author's profile photo Jitendra Kansal
      Jitendra Kansal
      Author's profile photo Markus Tolksdorf
      Markus Tolksdorf

      Hi Chris,

      actually, there is not really an 'official' acronym, normally the full name needs to be used always. But SAP customers are used to abbreviate and they simply use a TLA, often HCC. HCC sounds crazy in my ears, and SCC is part of the support component, so I try to convince everyone that SCC is the better inofficial term when talking about SAP HANA Cloud connector.

      Best regards,

      Markus

      P.S.: Everything ok in Down under?

      Author's profile photo Chris Paine
      Chris Paine

      All good down here! I had fun today when presenting a SuccessFactors strategic design doc to a customer (result of several week's work) when I attempted to get maximum acronyms in one sentence by explaining that the only allowed way to communicate out through SCC to HCP was through a JDBC/ODBC tunnel and if I wanted to use HTTP to HCI then that should just go through their firewall. I got a few blank looks and then they realised I was playing with them and we all had a laugh. Thank goodness for Fridays.

      Author's profile photo Former Member
      Former Member

      Hi Murali,

      After Failover test why it is showing Disconnected status for master in High availability. 

      Author's profile photo Former Member
      Former Member

      Hi Murali,

      I Should everything be configured on master instance, such as : SSL certificate, RFC with SNC, LDAP before connecting the shadow instance?
      Thanks!

      Author's profile photo Bogdan Popescu
      Bogdan Popescu

      Indeed they should be. One mention is that the firewall rules from the source systems must be opened towards all "servers" participating in the master/shadow installation (if 2 different servers are used, then firewall rules must be done independently towards both). What I am currently working on is SSL certificate (done for master) enabled for master and shadow and what happens when shadow is enabled as master. I will use a wildcard because i dont have a Load Balancer in front. Otherwise i think one ssl should be enough.