Connecting the on-premise world to the cloud presents many questions and sometimes a picture is the best way to provide an answer. This is why I’ve published architecture diagrams and process flow diagrams for SAP Analytics Cloud consuming SAP BI Platform Universes in a ‘live’ mode.
Live Universe Connectivity Architecture
I’ve presented two diagrams in the wiki:
- a PATH connection, which will use a Reverse Proxy
- a DIRECT connection, which uses CORS bypassing the need for a Reverse Proxy
I encourage you to study the diagrams and here are some noteworthy points:
- The database performance is critical since, the data stays on-premise. It’s never uploaded to the Cloud. Only the model metadata is uploaded to the cloud.
- The BI Platform uses the WACS (Web Application Container Service) as the gateway into the platform via the REST API that it hosts. This in turn talks to
- CMS and the FRS (for the obvious reasons)
- the DSL Bridge Service (to get the universe metadata and map the SAC model to Universe queries)
- Web Intelligence Processing Server (where a .WID is created and a data provider in that document is created and run against the database for each query asked by the SAP Analytics Cloud client)
- Most of the load is on the DSL Bridge and the Web Intelligence Processing Server, so you’ll need to make sure you have these services sized appropriately.
- Each user of SAP Analytics Cloud will connect and login to the BI Platform and thus consume and inherit the security model. Today SAP Analytics Cloud support SAML for SSO, or you can just prompt the user for a user/pass.
- SSL is mandatory and if your organisations browser policy enforces only trusted certificates, you’ll need to make sure the SSL certificate you use will be valid.
Process Flow diagrams
To really help your understanding of the architecture its best to look at the 5 process flow diagrams I’ve created in the wiki. I walk you through, step by step, from creating a new connection, to creating a model and then using that model to build visualisations and sorting and filtering upon it.
Please do study them. Here’s some additional context to help answer your questions!
- Actions such as sorting and filtering are performed by the client, the backend isn’t hit.
- Actions such as filtering of data are all pushed down to the database.
- The Web Intelligence document is
- created in the BI Platforms users a favourites folder called “BOELiveProviderTempFolder” (name can be configured).
- stores the query and results for each query to the database. If you use my Auditing Universe you’ll see a new data provider is created for each query sent. Currently there’s no smart re-use of existing data providers.
- deleted when the user logs out of SAP Analytics Cloud.
Please do post comments, feedback, questions to this blog rather than one the wiki pages. I will try my best to reply as soon as I can. Please do review other people’s comments and my replies before you post!
As new features and function come into the product I will update the diagrams. I will be publishing a lot more content for consuming Universes, so stay tuned and follow me! 😉
Matthew (Twitter @MattShaw_on_BI)