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\ com.sap.hilo.branding.vi_1.17.0.201406070027-1094 \ 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.
 
/wp-content/uploads/2014/09/geektip_1_606432.png
 
cache.PNG
 
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.
 
/wp-content/uploads/2014/09/geektip_2_606434.png
 
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.
 
/wp-content/uploads/2014/09/geektip_3_606441.png
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.
 
/wp-content/uploads/2014/09/geektip_4_606453.png
Extension.PNG
 
Conclusion
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 @ http://www.visualbis.com/blogs/data-discovery/2014/09/04/tweaking-lumira-for-advanced-customization-and-geeky-fun/

To report this post you need to login first.

14 Comments

You must be Logged on to comment or reply to a post.

  1. Hari Srinivasa Reddy

    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

    (0) 
    1. Lord Cedie Dullavin

      Hi!

      I have this problem that relates on your #1.
      I install SAP Lumira the very 1st time with no problem then when I open it. this message always pops up. When i try to change -XmX: 728m > -Xmx:1024 > SAVE.
      the mesage still  pops up.
      can you pls help me? i would appreciate it so much! /wp-content/uploads/2014/09/10681964_941960949153803_486916555_n_537891.jpg

      (0) 
  2. Hari Srinivasa Reddy

    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.

    Cheers,

    Hari

    (0) 
      1. Antoine CHABERT

        Just a side comment. i think your trick 2 is not fully right. This parameter is not about import dataset size, it is about max number of data points allowed in one viz.

        Antoine

        (0) 
        1. Shankar Narayanan SGS Post author

          Antoine,

          You are right, its actually the data points. My language sometimes play with me, so i tend to refer it as import datasize.

          Do post some other tricks you find here.

          Peace

          Shankar

          (0) 
          1. khalid quraynis

            Thanks Shankar, great post

            But for the trick two any idea how can Import a big dataset

            I’ve dataset with  millions of records when I import it

            it comes just around 500.000!

            thanks in advance : )

            (0) 

Leave a Reply