Skip to Content

SAP Lumira – Geek Tweaks

I’ve been playing around with Lumira for a while now and tried some geeky tweaks on it. Here are some of which I am sharing through this post. A word of caution though. Please try them at your own risk. For geeks only.
Trick 1: Minimise ‘low memory’ errors
SAP Lumira runs on SAP JVM. Since the entire system runs on it, there are times when insufficient virtual memory may lead to performance issues, latency etc. Increasing the virtual memory in this case, say 1024 MB for a 4 GB machine, will help you avoid low memory errors and significantly improve performance too.
How do you go about? Well, all you need to do is edit the SAPLumira.ini found on the installation folder. Voila! You’re done.
configuration file.PNG
Trick 2: Import as much as you want

While importing large datasets, it isn’t unusual to encounter an error message thrown by Lumira. This happens because of the cap on the maximum number of rows of a dataset that can be imported into Lumira.

Solution: Edit the maxvizdatasetsize in the SAPLumira.ini file
Page Size.PNG

Trick 3: Personalize the Splash screen
Give a personal touch to the splash screen that you can see while the application is launched. Personalize it with photographs or funny images/texts to your liking & add some fizziness to your start.
Here are the 2 simple steps:

  1. Access the ‘splash.bmp’ image in the folder %HOMEPATH%\ .sapvi\ configuration\ org.eclipse.equinox.launcher\ \ splash.bmp
  2. Replace the image with any .bmp image of your choice.

We’re done.
In case you want to revert it, simply delete the image you uploaded. The default image gets loaded automatically.
Note: Ensure that the image is in .bmp format.
splash screen -1.PNG
splash screen -2.PNG
Trick 4: Speed up Lumira
When you use Lumira for a long time, you may find an unexplainable sluggishness. You’d wish if only there was a way to speed things up. Well, its possible. All you need to do is clean the cache files. Access %HOMEPATH%\.sapvi\desktopCache and delete them.
Trick 5: Why should it be the default port always?
SAP Lumira uses Jetty server for rendering the charts and other visuals on the screen inside the application, and runs on port 54643 by default. But in any case you would want to change the port to something else, you can edit the file
Change the preferredHttpPort property to the port you need.
Port change -1.PNG
Port change -2.PNG
Port change -mod.PNG
Trick 6: Log what matters alone
Log files often get bloated with inconsequeintial messages that are hardly actionable. However, it can be very helpful if there’s a method to streamline it. You can achieve this by editing the file BO_trace.ini found in the installation folder
Set active=true, importance=XL, severity=error. Uncomment the parameters that you want to include. You can also edit other parameters like the log file capacity and the log extension.
Log file -1.PNG
Log file -2.PNG
Trick 7: Creating content behind Lumira
This was the most fun part. You can build content behind Lumira that will be rendered along with the Lumira UI but behind the visualization frame. You will need to scroll down to view the extension.
Note: Extension can be loaded inside the body instead of g division to get this.
You can load other types of Javascript extensions as well inside the body and can modify the property of the default charts with the component CSS.
These are just a very few I found and I’m sure there are many many more. If you find any interesting tweaks, please feel free to comment below.
Happy tweaking!

Read more @

You must be Logged on to comment or reply to a post.
  • Hi Shankar, This is a wonderful post. Truly appreciated.

    I am referring to point Trick 7: Creating content behind Lumira

    Currently I am developing an extension which has an HTML table. in Vizpacker it shows perfectly fine. But when I use this extension in Lumira the HTML table display behind the visualization frame. Which is a strange and funny and not only it disturbs the Lumira menu options as well. Do we have a fix for this. As per me it should be display in as like in-build Lumira extensions. Your help on this highly appreciated.

    - Hari

  • Yes. This issue has been resolved after implementing below changes.

    1) Using div tag.

    2) Adjusting the height and width of the container.

    as I need big container to hold the HTML table which can grow based on the dataset (rows & columns), I have enabled a container scroll-bar option so that i can scroll the and see the data.

    Thanks Raghu and @Matt Lloyd.