Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor

Source: SAP

Source: SAP

Forward looking statements are subject to change


Focus of this session
Is to provide you with technical insights impacting Lumira Deployment and Sizing:

  • Your usage scenarios will dictate how to best consider your deployment

  • Your specific environment has everything to do with how you would architect

  • The sizing guide and Quick Sizer would support you for sizing servers


Source: SAP

Customers have different architectures and use cases

Generic sizing principles and guidelines apply - user type, concurrency type, still apply for Lumira

Source: SAP

With combining into one product on the back end, there are changes on the back end

Content types impact your environment, and probable impact

Process flow - end users - there are set of request-responses - these interactions depend on components

Source: SAP

Size/scale out to cater to new use cases and load by Lumira on platform

Purple are the Lumira components

APS hosts the velocity engine and BICS connectivity
The Lumira Server processes Lumira content on BI Platform. This server hosts the in-memory data engine which is used as an offline data processing engine for Lumira. It is a separate product from HANA but borrows many concepts such as in-memory, column store, parallelization, and compression. Like other documents in BI Platform, Lumira documents are also saved in the Input / Output File Repository servers. The data is loaded into the in-memory data engine only when a user opens a Lumira document.

Lumira Scheduling Service:
Lumira Scheduling Service is a service within the Adaptive Job Server. This server enables the scheduling of Lumira documents.

Lumira Web Application:
The BI Launchpad and CMC applications are embedded in the Lumira Web Application to allow access to Lumira content in the BI applications.

Lumira Restful Web services:
Lumira Restful Web Services provides the web services required by Lumira Desktop to interact with the BI Platform such as login or to save Lumira document. (Source: SAP)

Reconsider sizing for APS, CMS, file repository

Source: SAP

Design Studio supports compatibility mode; work with 1.6 applications without touching them

Even though support compatibility mode, after you upgrade add-on, even execution of these applications occurs via Lumira 2.0 server; still need to size your Lumira server to size the documents

Source: SAP

Two experiences

Discovery - stories are output

Designer - applications are output

Use the common lumx file format

Resource consumption would be the same - how the content is created / connected to data source - live mode versus importing from data source - this will impact consumption of data source

Source: SAP

Live connectivity - delegate calculation to BW/HANA engines

If connect in live mode - Velocity engine doesn't come into play

If you import the data, makes use of memory on node where Lumira server is running; data is loaded to velocity engine - for either Discovery/Designer
Velocity Engine can consume upto 85% (memory consumed depends on usage, isn’t assigned at start up) system memory (source: SAP)


Other impact is how users are using the application:
Refresh and Analysis have different resource requirement for Imported data connections

  • Refresh and Analysis are similar workflow and have similar resource requirements for Live documents, Refresh or Analysis have a different resource requirement for Imported data

  • In case of imported data sources, Refresh would result in creating additional workspace to contain data for each users (who has refreshed)

  • Same is applicable while saving the document

  • Rest all workflows for Analysis e.x. filter, drill, calculations and adding new visualizations would continue to utilize common workspace containing the data across users (source: SAP)

Users who will refresh vs those who use document already created

Process Flow (Source: SAP)
Understanding which components are utilized by the system for your workflows will help you focus on sizing the components accordingly

Source: SAP

Browse repository, CMS, WACS, and Lumira Server come into play; need to consider additional load

Source: SAP

When publishing, have CMS, WACS, Lumira Server and Input FRS come into play

Source: SAP

Acquire data from universe - sizing considerations are shown above

Source: SAP

Access Input FRS

Source: SAP

HANA Live uses BICS or INA connectivity

Source: SAP

Similar workflow when using BI Launchpad accessing Discovery document using HANA Live using INA connectivity

Source: SAP

HANA Import mode workflow

Source: SAP

BW live uses BICS Connectivity

Source: SAP

Designer uses the dswsbobje unlike Discovery which uses WACS for all scenarios


Other impacting factors:
Sub optimally sized BI Platform

  • Running additional content and increased user concurrency would further impact response and throughput

Poorly provisioned databases will have an invisible effect:

  • CMS DB latencies have a cascading effect – one BI admins can’t see!

  • Ensure that each reporting database and it’s I/O paths are large enough

  • Ensure that each reporting database is configured appropriately for best response

I/O bottlenecks – disk and network – have severe effects:

  • Worst thing you can do to an I/O intensive application is to starve it for data

  • Being on an underperforming file server can starve the entire BI system

Ensure virtualization hosts can handle aggregate requirements:

  • Putting 5 processing server VMs on one host means the host must have at least 5x the IO capability and 5x the RAM! Source: SAP

Reference/Links (source: SAP)

Lumira 2.0 Sizing guide:

Quick Sizer (including Lumira):

Measuring in SAPS:

BEx query performance:

Virtualization: service level and performance:

Quick Sizer:

BI Patten Books:

Product availability matrix:

SAP Application benchmark standard:

Using Quick Sizer on BI Applications:

Sizing and deploying SAP Business Objects BI 4.X Platform and Add-ons:

Question & Answer

Q:I am looking for actual Sizing Guide document on Lumira 2.0, not just link to the slide. More details are need to properly size you BI Platform with Lumira 2.0

Q: is 85% the upper limit that is imposed by LS4BIP? secondly can it be changed by a customer & if yes, how?

A: You can control it in the server property with a parameter like this: -Dhl.maximummemory=50%, if you want to limit it to 50%, where by default this is 85%.

Q: Is velocity engine part of Lumira 2.0?

A: It is part of the installation

Q: for a customer already deployed Lumira 1.x & Design Studio, assuming no change in usage patterns would the same sizing be good enough for Lumira 2.0?

A: Assuming no changes in user pattern - all the requests for DS 1.x would go to server - for 2.0 processing also by Lumira Server - look at server resource load

Q: Is the BI Platform Lumira Discovery add-on for Solaris still on schedule to be release by Dec 2017

A: Not part of 2.1; however working on identifying feasibility and effort for unix on 2018 releases

Q: 1. What is the minimum Lumira and DS 1.X versions required to update to Lumira 2.0 SPx Are we supposed to be able to access OLAP connections from SAP HANA/BW Live connector ?

A: Upgrade Lumira 1.3 onwards, Design Studio upgrade for 1.5 onwards; second part - yes

Q: If you have Lumira 2.0 server and already using Discovery, then if you want to start to use Designer (1) Do you need to extra configuration for Lumira Server? (2) Does it affect sizing besides additional users?

A: If you have Lumira 2.0 for Discovery use cases no additional config required - but part of second question consider how much concurrency for users - consider amount of applications used, and available memory resources - are they sufficient?

Q: Do the client machines need a special sizing too or it's only required for the server side?

A: sizing is required for the server - on client machines, need to be aware for acquired - will use system memory to load data

Q: Is there any separate server need to create for lumira designer in CMC ?

A: No, just one server for Discovery and Designer workflows

Q: Is it possible to use the "Resource Usage Estimator" tool for Lumira or it has to be only with Quick Sizer tool?

A: Only Quick Sizer - link is in the slides

Q: Is there a specific process to convert DS 1.x documents to Lumira 2.0 like for Lumira 1.x docs we have to migrate the docs using Lumira desktop 1.31.8

A: Design Studio - open existing app in Designer client - preqs - apps are in .m mode - for HANA JDBC need to convert to INA

Q: Can we use promotion management to promote .lumx documents? Is there a best practice that needs to be followed?

A: Yes, support this using promotion management tool, on BI platform need for a patch version 4.2 sp03/4 - check the PAM

Q: Have heard that RESTful is moving on Tomcat from WACS so after that the workflow will remain same? or is there any changes?

A: with change on BI platform, Lumira would align with that

Q: When we install Lumira 2.0 in same BOE server, Scale up or Scale out is recommended to improve performance?

A: Scale out - memory requirement for velocity engine for data acquisition - for Live (velocity engine not used) if you have SAPS - same system as well.

Q: should Lumira be installed on the CMS and Webi servers even if you don't plan to run it on this server?

A: no such technical requirement - only dependency is for scaling out Lumira Server add-on - need to have BI platform adaptive server installed.

Q: Is Excel a supported data source for refresh(Lumira 2.0 discovery based docs) from BI Launchpad ?

A: yes; also possible in 1.x; prerequsite - while acquiring data from Excel - need to use shared part; Lumira Server user should have read access to shared part

Q: what about using Resource Sizing Estimator for Lumira 2?

A: Now just Quick Sizer

Upcoming ASUG webcasts:

Labels in this area