Lumira 2 saw Lumira 1.x and Design Studio 1.x converge into a single technology.
These two different technologies had their own BI Platform service and utilised other services on the BI Platform in a different ways, depending upon the workflow. With the technologies now converged all these workflows have changed. So anyone updating to Lumira 2 will be keen to understand what processes are used when and for what reason.
I have created 26 workflow diagrams showing which process is used when. These Lumira 2 workflow diagrams are available in the SAP Community Wiki.
In summary they cover workflows for the client interfaces:
- Lumira Discovery
- Lumira Designer
- BI Launchpad for both Discovery and Designer authored documents
For each of these they detail which process is used when for:
- Live connections (BW, HANA, Single and Multisource Universe)
- Import data connections (BW, HANA, Single and Multisource Universe, Excel, Query with SQL)
What’s worth noting?
- The Adaptive Processing Service ‘DSL Bridge‘ isn’t used for any workflow. This is because these libraries are now included internally within the client. This in turn means one less ‘hop’ and an improved performance.
- The Lumira Processing Server (on the BI Platform) isn’t used when connecting, from the client, to either HANA or BW. The connection is direct.
- When saving a document to the BI Platform, the WACS (Web Application Container Service) is used using a REST API. So before you may not have necessarily needed this service, however you will with Lumira 2.
- Lumira Discovery uses CORBA to login, whereas Lumira Designer uses SOAP to the dswsbobje web application. (Over time you should see a convergence to use the REST API for these workflows)
- Connectivity to HANA is using InA protocol for online (no longer JDBC) and JDBC for ‘download‘
- Connectivity to BW is using BICS protocol for online and JDBC for ‘download‘
Your feedback is important and I will do my best to reply and keep the diagrams up-to-date and correct any mistakes.
Feel free to post a general question to this blog and post a comment within the page of the particular workflow if you have a particular question about that workflow.
Feel free to ‘like’ this page if you do!
Matthew Shaw (Twitter: @MattShaw_on_BI)