Skip to Content
Author's profile photo Henry Banks

A forray into Lumira SP12 – new features and findings

Hi Everyone,

With Lumira desktop SP12 released last week, I wanted to take this opportunity to introduce a few of the new features!

Firstly, I recorded some videos to cover the 3 main enhancements:

  • New HTML 5 User-Interface ‘look-and-feel’:

  • “Compose Storyboards” – create interactive, composite views of visualizations:

  • Data acquisition using BW-SQL .UNX universes is now supported:

I must also mention these incremental updates:

  • Improved in-product registration.
  • BIP 4.1 support.
  • HANA SP06 support.

I thought you’d be interested to know some of the more techy stuff I discovered recently:

1. Whilst testing, I noticed 2 additional 32-bit Lumira process showing up in the Task Manager, and I was told that this SP12 release now uses a revised      ‘Chromium’ multi-process architecture.  With the interface now rendering in HTML, this task has been decoupled from the application’s JVM ‘back-end’      process.  There are always 2 of these processes: one central/global process, one for the HTML page itself. More info here: 


2. I was stress-testing the BW-SQL pretty heavily and made some interesting findings.  Firstly, I had recently upgraded my BI Platform from 4.0 SP06 to BI 4.1 SP01 and was hitting errors like “getSessionInfosEx – could not load the selected universe” (and the ‘csEX’ error below) when trying to acquire from      BI Universes:

csEX (WIS 00000).png

As it transpired, my problem was related to Adaptive Processing Server (APS) configuration on the BI Platform. After updating to 4.1+ , my old 4.0 APS configuration wasn’t working with Lumira (although reporting content was fine from BILaunchPad). I suspected a problem with the Adaptive Connectivity Service. To solve the issue, I ran the CMC’s new “System Configuration Wizard” (thus recreating all APSs) and then my acquisition worked!  🙂

sys config wiz.png

So now i could connect to BW-SQL universes 🙂   My next issue was when consuming very large infocubes..  I had expected some slowness as my cube had several million rows in its fact table, but eventually I hit an error:


The solution was to increase some specific parameters on the Web Intelligence Processing Server (default shown in black outline):

max char stream.png

The crucial parameter here is the “Maximum Character Stream Size (MB)” setting.  This needs to be upped from 15 to anything between 40-100Mb (depending on the # of rows being fetched). Although this hasn’t been absolutely proven empirically, the “ball-park figures” i’m communicating are in the range of: 

    • 100 000 rows -> 20 MB
    • 200 000 rows -> 40 MB
    • 500 000 rows -> 100 MB

3.  Unfortunately, there are a number of ‘release restrictions’ which need to be kept in mind.   The article of interest can be found here

4. If connecting to BOE XI3.1, it has come to our attention that you can see MDX OLAP .UNV (BAPI access) listed in the universe browser – but this type of data access isn’t supported!!  A bug has been logged (they should be hidden) . Many thanks to Bart Bart Verweijen  for the feedback

5. As being discussed here for Predictive Analysis users, there will be no SP12 release (and probably no SP13).  These applications have ‘de-couple’ temporarily, but will resume by SP14.  However, this presents a dilemma for PA SP11 users who want to use Lumira SP12 – as there’s currently no officially supported way of having the 2 products installed side-by-side..

6. *update* With regards to this old article: 1782010 – SAP Visual Intelligence 1.0: How to analyze VI processing problems using the native Debugger utility

I realized last week that this tip no longer applies in SP12!   The equivalent debugger/profiler is accessible in SP12 by double clicking on the ” – ” symbol in the status bar:


I hope this information is of use to you. 

Please feel free to ask your questions here, i’ll be happy to respond .

Kind regards,


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Manikandan Elumalai
      Manikandan Elumalai

      Looks Interesting Henry.

      Author's profile photo Former Member
      Former Member

      Not only is this interesting, it's a fully documented and great way to show everyone how to use and setup Lumira.

      *wow* is an understated word.

      Author's profile photo Henry Banks
      Henry Banks
      Blog Post Author

      addendum - i just added some new info about the debugger / profile tool 🙂

      Author's profile photo Former Member
      Former Member

      Checked the addendum out, another great addition to an already comprehensive post.

      Author's profile photo Florian HAMON
      Florian HAMON

      Hello Henri !

      Great investigation on the product, thx ! On the downside, I would add that unfortunately the "associative highlighting" in the facets, that was available in the previous version is no longer here. It was a big point against Qlick.

      Author's profile photo Henry Banks
      Henry Banks
      Blog Post Author

      thanks Florian 🙂   yeah, i reported that omission during solution validation - see defect BITLUMDAM1-2101   when i noticed i couldn't right-click "computing correlated values" on facets in the new UI5..  regards, H

      Author's profile photo Former Member
      Former Member

      Hi Henry,

      Really interesting post, good job.

      Found some bugs in Lumira 12 last week, any idea where it's the best place to report them?



      Author's profile photo Henry Banks
      Henry Banks
      Blog Post Author

      Hi Matt,

      thanks for compliment.

      Infact, i was just talking to Bijan (Irshaad Bijan Adatia) about our next steps for your thread here

      we're going to work with you.  But as a first question, do you have an SAP Support contract, with access to the service marketplace? 

      Ideally, we want customers to field OSS support ticket to component BI-LUM-DSK , but this wont be possible for customers who've acquired lumira through the e-store, trial, or Cloud.

      let us know!



      Author's profile photo Former Member
      Former Member

      Hi Henry,

      Thanks for your reply. Yes I do have a support account but not sure which method we used to download the software.

      Will find out on Monday and try logging it with support.



      Author's profile photo Former Member
      Former Member

      Hi Henry,

      Good Day!

      Nice analysis! I appreciate.

      Keep sharing new things. Have a nice day!


      Hari Suseelan

      Author's profile photo Srinu S
      Srinu S

      Hi Henry,

      Good job. Very good analysis done by you.Keep sharing 🙂



      Author's profile photo chandra koduri
      chandra koduri

      Thanks Henry.

      Good Explanation.

      Author's profile photo Amardip Selmokar
      Amardip Selmokar

      Hi Henry,

      Thanks for the article.It is really helpful.

      We are using Lumira 2.0 and We are using BEx query as source.We are connecting to source by SAP Logon credentials (By SAP BW option, not by OLAP Connection ). it is taking long time for data acquisition.

      In article you have mentioned,we need to change some Web intelligence server parameters to improve the performance.

      Please let me know is this solution will work for Lumira Desktop client as well, as for desktop client I think we are not leveraging on BO servers as well ??

      Looking for your helpful response.


      Author's profile photo Henry Banks
      Henry Banks
      Blog Post Author


      this is a really old article from the early days of 1.0 so please disregard it.

      A lot of the process flows have changed in 2.0  the tool has been rearchitected in many way

      if you are using a local BW connection, then no BI platform is involved, so Webi settings don't  apply.

      the time is being spent 'somewhere' between your desktop client (check to see what's happening in Task Manager process ids) and BW engine (check to see what's happening in the work processes in transaction SM50 or STxx )

      and of course, network in between

      best of luck