New release of the Cloud Connector (v.2.11.)
Backup & Restore
More details in the official documentation.
In the last release (2.10), we have introduced a first set of monitoring APIs that allows you to include monitoring information in your own monitoring tool like the SAP Solution Manager. With the version 2.11, we want to continue providing more APIs. Now you have also a first version of configuration REST APIs that lets you automate the essential parts of the Cloud Connector: initial configuration, management of subaccounts and configuration of your access control. Here is an overview of the available APIs:
|High availability settings||
|Solution management configuration||
|System mapping ressources
|Subaccount service channel
More details in the official documentation.
If you want to connect a subaccount to your on-premise landscape, you need to select a region in the dialog, that appears after clicking on “Add Suaccount”. You can now select the subaccount region from the list of regions, instead of choosing the technical region host.
Configuration of tunnel connections
The new version of the Cloud Connector helps you to better optimize the performance of your applications and the efficiency of your resources. Now you have 2 different options to specify the number of physical connections (per application) based on your needs:
1. You can edit the global parameters for tunnel connections that represent the maximal number of tunnel connections per application. From the Cloud Connector main menu, go to Configuration > Advanced to change the value in the Connectivity section.
Monitoring, audit logging and tracing
In the monitoring section, you can see details about the last 50 recent requests. Till now, you were able to view all requests or only the ones destined for a certain virtual host. A new filter option has been introduced in the version 2.11. In order to faster analyse the performance, you can further restrict the selection of the recents requests by filtering the resources. To do so, select the virtual host for which you want to specify the resource filter and choose one or more of the listed accessible resources.
Moreover, we are continuing to provide more APIs. With 2.11, an additional monitoring API provides a list of “top time consumers”. Using this API, you can read the data of top time-consuming requests provided by the Cloud Connector performance monitor.
Last but not least, you can now configure an automatic cleanup for both audit logs and log/trace files. See Audit Logging and Troubleshooting.
Of course the new version comes with more features and fixes 😉 You can check all the details in the release notes of the SAP Cloud Platform. Its’ worth to have a look at it… for example you will see that we now provide JVM settings for the Cloud Connector and function module units are now supported when processing RFC requests that use tRFC, qRFC, or bgRFC on the cloud side.
The new release of the Cloud Connector comes with many cool new features, so don’t wait too long and download it right now!
As always, I would be happy to hear what you think about it. So don’t hesitate to send your feedback or even questions in the comments section.
Nice @Matthieu thanks for sharing the update. Just downloading now and will check it out.
Superb... This is extremely insightful 🙂
A follow-up question for the Monitoring capability - is there a possibility to sort/ rank list of connections for a particular account based on their usage ? To be more specific, over time we end up having several mappings (Cloud to On-Premise) some of which get obsolete. Such a ranking would help identify "unused" connections and hence can be cleaned up periodically ? (maybe a further extension of "most recent requests" feature).
Thanks a ton.
thanks for your input.
Can you please tell me appr. how many access controls you have per account?
I need to upgrade my old versión 2.10.1 to a newest versión, but tho old versión do nota have a backup option. How do I have to do for no lost my configuration?
Hi @Matthieu ,
thanks for the valuable information. I have a question regarding the configuration of tunnel connections.
We use Cloud Connector für C4C –> CPI –> Cloud Connector –> ERP flow. The protocol is HTTP. We recently had the situation, where an unwanted mass data change in C4C blocked quite a few dialog processes in ERP backend.
We know, we could mitigate impact using e.g. “rdisp/rfc_min_wait_dia_wp” parameter in ERP. However, there’s also “rdisp/scheduler/prio_low/max_quota” which would give us opportunity to fine tune this (https://launchpad.support.sap.com/#/notes/2129291)
Many thanks and kind regards