Live Data Connections to SAP BPC Embedded
You can create live data connections to an SAP BPC embedded configuration system using the Direct connection type.
Tuple filters on multiple dimensions are supported, with the following considerations:
Prerequisite BW version: BW/4HANA 2.0.
- Filters are created by selecting multiple data points in a widget (the created filters are read-only).
- The “Exclude selected members” option isn't available because the BW back end doesn't support the NOT operator.
- Linked analysis is not supported if the receiver widget already has a tuple filter applied.
- Hierarchies in tuple filters are not supported.
- The Currency/Unit dimension cannot be filtered.
- Blending is not supported.
- Queries with two structures do not support tuple filters.
For more information, see System Requirements and Technical Prerequisites.
SSL must be configured on your SAP Netweaver server. For more information, see Configuring SAP NetWeaver AS for ABAP to Support SSL, and SAP Note 510007.
- You don't want to set up a reverse proxy on your local network and put SAP Analytics Cloud behind it.
To use this connection type, you must configure Cross-Origin Resource Sharing (CORS) support on your SAP BW system.
- Supported Features and Known Limitations to SAP BPC Live Data Connections
- SAP Analytics Cloud Support Matrix for Live Connectivity to SAP NetWeaver BW
- For information on supported features and known limitations to SAP BW, which equally applies to the embedded configuration of SAP BPC, see SAP note 2715030 .
HTTP/2 is supported for SAP BW data sources. This backwards compatible protocol optimizes network and server resource usage to increase performance.
When to use HTTP/2
Measurements show that performance gains can be expected when there are long running queries with multiple widgets.
Fast queries (query execution time is 2 seconds or less)
If there are fast running queries, for example because of OLAP caching, there will be no noticeable difference in the overall story loading performance.
If the query execution time is 3-5 seconds or longer, browser connections would likely stall during story loading (previously, under HTTP/1.1), especially when there are multiple widgets on one page. But utilizing HTTP/2, a performance improvement of 20-30% is expected.
Use the Number of parallel sessions for BW data sources setting in SAP Analytics Cloud to make sure that the BW server can process the sent requests in parallel (to prevent the backend becoming the bottleneck). However, be aware that higher values for this setting will increase the load on the BW server, so you'll need to ensure that the BW server is configured to handle this load. It might be necessary to increase icm/max_conn and other parameters. For more information, see the following two documentation links.
How to enable HTTP/2
- Backend side: See https://help.sap.com/doc/7b5ec370728810148a4b1a83b0e91070/1610%20000/en-US/frameset.htm?c7b46000a76445f489e86f4c5814c7e8.html and this blog post: https://blogs.sap.com/2016/10/19/connectivity-news-abap-7.51/.
SAP Analytics Cloud only supports HTTP/2 connections using the direct connection type.
Be aware that all browser vendors support HTTP/2 exclusively over HTTPS.