No, the Cloud Connector currently supports only basic authentication.
As of version 2.9, you can connect multiple Cloud Connectors to a single subaccount. This lets you assign multiple separate corporate network segments.
Those Cloud Connectors are distinguishable based on the location ID, which you must provide to the destination configuration on the cloud side.
SAP Analytics Cloud refers to an all-in-one cloud platform offered as software as a service (SaaS) specifically for planning, business intelligence (BI), planning and predictive analytics providing data discovery, data visualization, simulation, what-if, forecasting besides the many other capabilities. This has been built primarily on SAP Cloud Platform, and this provides a complete, unified and secure public cloud analytics experience meant for maximizing data-driven decision making.
The connection is opened from the on-premise system to the cloud, but is then used in the other direction.
An on-premise system is, in contrast to a cloud system, normally located behind a restrictive firewall and its services are accessible thru the Internet. This concept follows a widely used pattern often referred to as reverse invoke proxy.
Initially SAP supported the provisioning of a SAP Cloud Platform Integration tenant with the help of the web tooling capability only, i.e., without any runtime node. At present, this offering is unavailable. In case you have any SAP Cloud Platform Integration license, then you can use the Web Application of the SAP Cloud Platform Integration tenant you have.
No, the audit log monitors access only from SAP Cloud Platform to on-premise systems.
The Cloud Integration Content Runtime can only be used together either with the SAP Process Orchestration or with SAP Process Integration. Either of the products is required to be licensed separately. Besides configuration of the cloud integration content in the new offering, the user will also require a SAP Cloud Platform Integration license.
No, currently there is only one role that allows complete administration of the Cloud Connector.
As of version 2.10, this is possible using the TCP channel of the Cloud Connector, if the client supports a SOCKS5 proxy to establish the connection. However, only the HTTP and RFC protocols currently provide an additional level of access control by checking invoked resources.
You can also use the Cloud Connector as a JDBC or ODBC proxy to access the HANA DB instance of your SAP Cloud Platform subaccount (service channel). This is sometimes called the “HANA Protocol”.
The amount of bandwidth depends greatly on the application that is using the Cloud Connector tunnel. If the tunnel is not currently used, but still connected, a few bytes per minute is used simply to keep the connection alive.
No, this is not possible. For client certificate authentication, an end-2-end TLS communication is required. This is not the case, because the Cloud Connector needs to inspect incoming requests in order to perform access control checks.
This does not affect the tunnel, even if you restart the Cloud Connector.
This happens when you try to access the Cloud Connector over HTTP instead of HTTPS. HTTP is the default protocol for most browsers.
This is not possible. Basically, this is a desired man-in-the-middle attack, which does not allow the Cloud Connector to establish a mutual trust to the SAP Cloud Platform side.
Package the following three folders, located in your Cloud Connector installation directory, into an archive file:
These folders contain all the relevant configuration information. As the layout of the configuration files may change between versions, we recommend that you don't restore a configuration backup of a Cloud Connector 2.x installation into a 2.y installation.
The Cloud Connector can connect an SAP Business Suite system version 4.6C and newer.
We recommend that you use at least three servers, with the following purposes:
As of version 2.10, the Cloud Connector is able to establish a connection to regions with the SAP Cloud Platform Cloud Foundry environment.
It depends on the scenario: For pure point-to-point connectivity to call on-premise functionality like BAPIs, RFCs, OData services, and so on, that are exposed via on-premise systems, the Cloud Connector might suffice.
However, if you require advanced functionality, for example, n-to-n connectivity as an integration hub, SAP Cloud Platform Integration – Process Integration is a more suitable solution. SAP Cloud Platform Integration can use the Cloud Connector as a communication channel.
SAP Analytics Cloud functions exclusively on SAP Cloud Platform which regularly meets the international security standards.
Each Cloud Connector version is supported for 12 months, which means the cloud side infrastructure is guaranteed to stay compatible with those versions.
After that time frame, compatibility is no longer guaranteed and interoperability could be dropped. Furthermore, after an additional 3 month, the next feature release published after that period will no longer support an upgrade from the deprecated version as a starting release.
Yes, the SAP Analytics Cloud has been available as a public cloud (software as a service, multi-tenant) offering. A ‘private cloud’ (software as a service, single tenant) is available as an option.
We currently support 64-bit operating systems running only on an x86-64 processor (also known as x64, x86_64 or AMD64).
Yes, you should be able to connect almost any system that supports the HTTP Protocol, to the SAP Cloud Platform, for example, Apache HTTP Server, Apache Tomcat, Microsoft IIS, or Nginx.
For the portable versions, JAVA_HOME must point to the installation directory of your JRE, while PATH must contain the bin folder inside the installation directory of your JRE.
The installer versions automatically detect JVMs in these locations, as well as in other places.
For productive instances, we recommend installing the Cloud Connector on a single purpose machine. This is relevant for Security.
At present, SAP Analytics Cloud functions on the runs on SAP Cloud Platform data centers all around the world. SAP has also recently announced partnerships with Amazon Web Services (AWS), Google Cloud Platform (GCP) and Microsoft Azure for running SAP Cloud Platform and they also plan to run SAP Analytics Cloud on these IaaS platforms soon. Although there are no plans for running on other IaaS platforms.
Starting with version 2.10, the Cloud Connector offers a Service Channel to S/4HANA Cloud instances, given that they are associated with the respective SAP Cloud Platform subaccount. Also, S/4HANA Cloud communication scenarios invoking remote enabled function modules (RFMs) in on-premise ABAP systems are supported as of version 2.10.
The response is lost. The Cloud Connector only provides tunneling, it does not store and forward data when there are network issues.
Yes, you can create an archive file of the installation directory to create a full backup.
Before you restore from a backup, note the following:
If you restore the backup on a different host, the UI certificate will be invalidated.
Before you restore the backup, you should perform a “normal” installation and then replace the files. This registers the Cloud Connector at your operating systems package manager.