Skip to Content

If you’re updating your SAP BusinessObjects BI Platform to Lumira 2.x then you’ll have a few questions about the various server Add-ons. This blog provides a high-level view of the steps you need to follow to update your Design Studio 1.x and Lumira 1.x Add-ons to Lumira 2.x.


Lumira and Design Studio have converged into a single product and a single document type. Whilst there two client-side end user interfaces, one for the Designers (SAP Lumira, Designer) and one for Discovering (SAP Lumira, Discovery) there is a single server Add-on.

How do you update to Lumira 2.x?

If you already have deployed Lumira, or Design Studio or both, then you’ll need to know how to update. This diagram is probably the best way to explain:

Workflow A: No existing Lumira 1.x or Design Studio 1.x Add-on

You need to install the ‘full’ Lumira 2.x BI Platform Add-on.

Perhaps very obvious but I thought I’d mention it!

Workflow B: Existing Lumira 1.x

You need to install the ‘patch’ Lumira 2.x BI Platform Add-on.

Since you already have Lumira installed, albeit version 1.x, you need to ‘patch’ from Lumira 1 to Lumira 2.

Workflow C: Existing Design Studio 1.x Add-on

You need to install the ‘full’ Lumira 2.x BI Platform Add-on.

Since you don’t have Lumira installed, you’ll need the ‘full’ install package.

Once you’ve installed the ‘full’ add-on, your old ‘Analysis Application’ BI Platform server service will be redundant. It simply won’t be used any more. So, you should delete it, from within the Central Management Console, to regain some resources from your servers.

I’ve captured a step-by-step workflow, shown below, taking you from start to finish.

Workflow D: Existing Lumira 1.x and Design Studio 1.x Add-on

You need to install the ‘patch’ Lumira 2.x BI Platform Add-on.

Because you have the Lumira Add-on already installed, you’ll need to ‘Patch’ to Lumira 2, even though you’ve also got Design Studio Add-on installed.

Once you’ve installed the ‘patch’ add-on, your old ‘Analysis Application’ BI Platform server service will be redundant. It simply won’t be used any more. So, you should delete it, from within the Central Management Console, so to gain some resources on your servers.


Step-by-Step Workflow C: Existing Design Studio 1.x Add-on Update to Lumira 2.x


Before I apply the ‘full’ Lumira 2.x BI Platform Add-on you can see my existing Design Studio service defined in the Central Management Console. I have a dedicated Adaptive Processing Server with two services: ‘Analysis Application’ (the Design Studio processing server) and ‘DSL Bridge’ (for processing my Universe queries from within my Design Studio applications).

I built a very simple Design Studio Application in Design Studio 1.6. I built it off my Auditing Universe!

On starting the ‘full’ Lumira 2.x BI Platform Add-on installer you see the usual license agreement:

Here you select the services. I always install all the services and I recommend you do the same. Whilst you may not intend to run all of these services on the same machine, doing so provides consistency and the flexibility should you change your mind without having to come back to install them.

Enter the CMS and Administrator password details:

The install then starts:

The install is then finished:

My old Design Studio Application can now be stopped and deleted, since it’s never going to be used again. Instead a new Lumira Server Service will do all the work of what the old ‘Analysis Applications’ service did.

The new Lumira Server Service will also process what the old Lumira Server Service processed too of course. There is one single processing service for both tasks, since it’s completely integrated at the back-end.

With my old ‘Analysis Applications’ Server Service deleted, I can still open my old Design Studio Application. It will be processed by the new Lumira Server Service.

Other workflows

We are not recommending to uninstall the old ‘Design Studio 1.x’ Add-on or uninstalling the old ‘Lumira 1.x’ Add-on.  We strongly recommend you just update without uninstalling any previous Add-on.


Lumira 1 to Lumira 2 document conversion

With your servers now updated to Lumira 2, you will not be able to view any Lumira documents, until you have converted them via the desktop into the new format.

Please follow SAP Note 2509882 for more details on the steps required.


Promoting Design Studio 1.x content or Lumira 1.x into a new cluster with Lumira 2

There are some very special requirements which I have described in this blog


Related articles


Feel free is post a comment and I’ll do my best to reply

For those on Twitter you can ask me a question @MattShaw_on_BI

Enjoy Lumira 2!




To report this post you need to login first.


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

  1. Manikandan Elumalai

    Thanks for Sharing this at the right time Matt. Just wanted to check with you on below as it is bit contradicting. Which one to use – Lumira Patch or Lumira full installer?

  2. Francisco Almeida

    Great post! It may be relevant to note that for cases where “workflow C” applies (i.e. no previous Lumira add-on and Design Studio 1.x upgrade to Lumira 2.0) the upgraded system will probably require a change: the Lumira server has always required its own host/virtual machine, so it can be assumed this will be the case in 2.x.

    This is relevant because the Design Studio Add-on did not have that requirement, so Architects could always scale their systems vertically. As Lumira and Design Studio have been merged into a single add-on, one can assume this will also require a dedicated host (scale horizontally).


    1. Matthew Shaw Post author

      You’ve raise a great question.

      So the requirement is the same. However the ‘old’ requirement (for a dedicated Lumira server) wasn’t really a requirement at all, but just a recommendation. It was documented as though it was a requirement.

      There’s nothing technically to stop you from running the Lumira Server on all your machines in the cluster.

      Lumira 1.x was almost solely used for data acquisition and thus it was an in-memory database which required a lot of (mostly memory) resources (but also plenty of CPU too!). So it was a recommendation to have a dedicated machine for that reason. But you could well run the old Lumira 1.x server on a node that was running other services, including Web Intelligence and Design Studio etc. – as long as that machine was powerful enough.

      So with Lumira 2.x it can have its old role, and it can have the Design Studio role:

      • it can still be an in-memory database for those acquired data enabling super quick slice and dice and visualisations – the general use-case for Lumira 1.x
      • Or as a powerful ‘scripted’ presentation layer when connecting to Live data sources – the general use-case for Design Studio 1.x (though Lumira 1.x also had a HANA live connection)

      Lumira 2.x can do both in a single integrated back-end. So the hardware resources depend upon the use-case you’re using it for.

      If you don’t change your use-case, that is you’re not going to acquire data and not use the powerful Velocity Engine, then you’ll be basically the same as you where before with regard to hardware requirements. If you decide you want to acquire some data, perhaps to enable off-line or scheduling capabilities, then you’ll need more hardware resources.

      So you can, and actually have always been able to, scale both vertically and horizontally.

      I’m not sure if this has helped or not?

      Regards, Matthew



      1. Francisco Almeida

        Of course it has – helpful as always. Is it fair to conclude that if the use case requires the benefits of the Velocity engine for fast data acquisition, the recommendation is still to have a separate host for this service to avoid resource starvation for other APS services?


  3. Jawahar Konduru

    Thanks Matthew for sharing this information. Just want to clarify couple of things, not related to Install. Mine applies to Workflow D. I did apply Lumira 2.0 and patch1. Below issue I am seeing. Looks like we need to rebuild the Lumira documents since there is no migration steps. it will be difficult for us, to rebuild the lot of content which is already there in production. Do you know when we can get the migration tool for Lumira?

    1. Previously built Lumira documents will not work in Lumira 2.0- Is there any migration process is in place?



  4. Matthew Shaw Post author


    With Lumira 2.0 Early Adopter Care you have access to Lumira 2.0 SP0 and SP1. (when you mention Patch 1, I presume you mean Lumira 2.0 SP1). There’s also the Open Beta Program which is Lumira 2.0 SP2 Beta.

    The General Availability Release is planned to be Lumira 2.0 SP2 but without the ‘Beta’. It is not until this release you’ll be able to open your old Lumira 1.x documents in Lumira 2.x. So you’ll need to wait until the General Availability Release Lumira 2.0 SP2 until you can open Lumira 1.x documents. This is mentioned in the release restrictions.

    There’s massive architecture changes between Lumira 1 and Lumira 2, and given the product doesn’t support this function yet, the reality of any Lumira 1 to Lumira 2 ‘migration’, is not fully known, at least not by myself. The plan is, at least, for you to do no migration steps.

    Documents created with Lumira 2.0 SP2 Beta will be supported in Lumira 2.0 SP2 (GA), that is you won’t need to rebuild those for sure.

    I hope this helps, Matthew

  5. Mark Richardson

    Matt –

    We are setting-up a brand new MUDBOX for taking part in the SAP LUMIRA 2.0 EAC program.

    The three new SAP LUMIRA 2.0 (SP01) packages were released to the EAC community last week – DESIGNER desktop, DISCOVERY desktop – and the ADD-ON FOR BI PLATFORM.

    This is a net-new GREENFIELD build of the BI PLATFORM – and we are aware that we can’t go to SAP BO-BI 4.2 (SP04) as our platform baseline for EAC testing, as it is not supported at that level yet.

    However, in looking at the PAMs, etc – it isn’t 100% clear which is the BEST patch-level to deploy on the Platform for the 4.2 (SP03) versions that will support the SAP LUMIRA 2.0 (SP01) EAC  ADD-ON FOR BI PLATFORM…?

    The PAM for EAC appears to say that we need the BI servers to be at BI 4.2 SP03-Patch 07…if we want to use Translation Manager or Promotion Manager with LUMIRA 2.0 content.

    If we are not using those components – should we be on the most recent available patch-level for the platform (SBOP BI Platform Servers 4.2 [SP03] – Patch 6 – Updated 20.04.2017) before we apply the SAP LUMIRA 2.0 (SP01) EAC  ADD-ON FOR BI PLATFORM…?

    Any clarity you can provide would be appreciated.





    1. Matthew Shaw Post author

      HI Mark

      should we be on the most recent available patch-level for the platform (SBOP BI Platform Servers 4.2 [SP03] – Patch 6 – Updated 20.04.2017) before we apply the SAP LUMIRA 2.0 (SP01) EAC  ADD-ON FOR BI PLATFORM…?

      No. You don’t need to be on the patch level before you apply the add-on.

      If you’re not using Promotion Management, Version Management or Translation Manager, then you’ll be just fine. You may get a support engineer commenting that you’re not on a support platform, since they have a process and the process say you need to be on whatever the PAM says!

      Regards, Matthew



  6. Thomas Nielsen

    Hi Matt

    Thanks for your, as always, excellent articles.

    I am still a bit confused, on what would be the best practice for upgrade a clustered and multi-tier environment. Well, the cluster not so much, since you had that covered, but what should be the steps for an upgrade when you have multiple dedicated web-tier (and mobile-tier) on a clustered environment. Do you run the installer on the web-tier as well, or is that done by a WDeploy?

    Looking forward to hear you best practices on this (or link to the information I might have missed) 😉




    1. Matthew Shaw Post author

      Hi Thomas

      You need to apply the add-on on the places you need it – and that may not be so obvious. So a great question/

      For your web tier you need to install it there. You won’t be able to install the non-web tier components on your web tier machines assuming you’ve not already installed the BI Platform there.

      Whilst, on your web-tier you’ll probably only going to install the web-tier option for this add-on, strongly advice installing all the add-on options everywhere as this provides: consistency (always a good thing)  and flexibility. Today, you may only intend to run the Lumira services on 2 of your 4 machines, but why not just install all the add-on options everywhere allowing you to change your mind later. You then have the flexibility to have say 3 or all 4 servers running Lumira.

      Also, the ‘web applications’ component I believe needs to be installed on the machines in your cluster that have the ‘Web Application Container Services’ service running. Since the logon from the Lumira Desktop will use for some workflows.  I’m not 100% on this, but I think we could get that clarified and I can update this comment once I know.

      Hops this helps?  (for everyone – please press the like button, its handy feedback!)

      Regards Matthew



    Hi Matt,

    Thanks for putting this up as this is very imformative.

    I have also installed/upgraded my Lumira 1.31 to Lumira 2.0 SP1 with BI on 4.2 SP3 Patch and Design Studio on 1.6 SP4.


    However when i try to log in to Lumira Designer. i get below error (attached).

    Also after the upgrade we fail to see the “Design Studio Runtime” application under CMC–> Application.

    Can you please suggest as currently its impacting our beta testing programme.




    1. Matthew Shaw Post author

      Can you try the Lumira Designer on a machine that doesn’t have the BI Platform installed on it? I wonder if this is expected or not. Mmmm. Or perhaps there’s a security settings that needs to be looked at. I’m not sure about this aspect.


      The old design studio application will have been removed during the update. This sounds right to me. It will now be the Lumira Designer you should see in the CMC applications.

  8. Kiran Gangaraju

    Hi Matt,

    What is the possibility having Lumira 2.0 SP2 (GA) supported on SBOP BI Platform Servers 4.2 SP04? We have upgraded our Sandbox system to 4.2 SP04 from 4.1 SP07. We are in process of testing. We are hoping to install Lumira 2.0 SP2 when is available. But if we know for sure, it won’t be supported on SP04, then we will upgrade to SP03.

    Can you please suggest?



  9. Kiran Gangaraju

    Looks like it will be supported from below note.

    2467541 – Supported BI Platform Add-On versions information for the SAP BusinessObjects BI 4.2 SP04 release

    Timelines for availability of Compatible Add-on versions Compatible with BI Platform version BI 4.2 SP04

    Lumira 2.0  2.0 SP02  Refer SAP Note 2465894



  10. Nitin Gupta

    Hi Matthew,


    Great article, But i want to clarify one point, our case is not covered in workflow described by you.

    We have a  Node A with BO platform + Lumira add on 1.31

    and  Node B with BO platform + design studio 1.6.

    We will want to keep Lumira 2.0 on the box already running 1.31, so in this case,  we can simple remove design studio 1.6 on node B as its not relevant any more ? or any other precaution need to  be taken care.

    And the dashboards already created in design studio will run with lumira 2.0 on node A  without any additional steps?


    Thanks and Regards,

    Nitin Gupta

    1. Matthew Shaw Post author


      Thank you for you comments.

      so in this case,  we can simple remove design studio 1.6 on node B as its not relevant any more ? or any other precaution need to  be taken care.

      We are not recommending uninstalling at all. (I do know we did a test of the uninstall of Design Studio and a fresh Lumira 2 install and it was ok, but even still our recommendation is don’t)

      Perhaps you could consider installing the add-on on both Node A and Node B, but just not run any Lumira 2 services on Node B. This way you get consistency and flexibility should you find later that you wish to run some Lumira 2 service on Node B. For example, whilst you may not want to run the Lumira 2 Adaptive Processing Service on Node B, you might want to run the WACS service on Node B. Since Lumira 2 requires the WACS service to be updated, you must apply the add-on to the server(s) where you need to run WACS.

      A second best option, would be to just leave the Design Studio 1.6 installation on Node B and leave it untouched, it ain’t broke so lets not fix it.

      Hope this helps (use the like button!), Regards, Matthew

  11. Singh Arun

    Hello Matthew,

    Thank you for the blog,

    One qq, is Lumira 2.o is released for all the users? I am not able to see link to dowload Lumira 2.o  under download software –>Installation and Upgrades –> L –> SAP Lumira, only SAP Lumira 1.o is available.



    Navneet Kaur

    1. Matthew Shaw Post author

      is Lumira 2.o is released for all the users?

      No. Lumira 2.0 SP2 (GA) has not yet been released for general availability.

      Lumira 2.0 SP1 is available for EAC customers (Early Adopter Care)

      Lumira 2.0 SP2 (beta) is available for OpenBeta customers.

      Lumira 2.0 SP2 (beta) is very similar in terms of features/functions as Lumira 2.0 SP1.

      Lumira 2.0 SP2 (beta) isn’t anything greater than Lumira 2.0 SP1

  12. Sameer Ahmed Ahmed

    Hey Matt

    I have the same Question as Arun, we are on BOBJ 4.1 sp 5 & Lumira 1.29, when I look in the SAP store at the location under download software –>Installation and Upgrades –> L –> SAP Lumira, only SAP Lumira 1.o is available.

    Is this not rolled out to all customers yet ?





  13. Nitin Kumar

    HI Mark,

    Thank you for brilliant post. One question about SDK and extensions, does extension built based on DS 1.x SDK will be portable on Lumira 2 Discovery. I guess it will surely will work for Lumira 2 Designer but need clarification for Lumira 2 Discovery. I think it should work as part of inter-portability !?



    1. Matthew Shaw Post author

      Hello Nitin,

      My understanding is that any old extensions you’ve build for Design Studio 1.x will continue to work when those Design Studio 1.x applications are run with a Lumira 2.x BI Platform back-end server add-on component and you’ve not yet converted the application to a Lumira 2.x application. The only restrictions I’m aware of is with that legacy HANA JDBC connections need adaptations, and their bookmarks will become invalid. Please refer to SAP note 2475223 for details.


      There are different types of extensions, from data source extensions, components and visualisations.

      Like with Lumira 1.x and Design Studio 1.x visualisation extensions can be written so it works in both, but they can also be written so it only works in one of them! For Lumira 2.x applications and their extensions the charting engine needs to use the main ‘m’ type and not the original CVOM library. Both charting types are available in Design Studio 1.x.

      For data source extensions, I don’t know if the same applies.

      For custom components, I’m sure these are only applicable for Design Studio and Lumira Designer.

      Does this help?

      Regards Matthew

      1. Nitin Kumar

        Thank you Matthew for response, I understand discovery object working in designer is the best we can get…Ideally would have expected it to work both way thereby utilizing innovations across.

        This led me to why two tools and why not one ? anyway that’s longer talk and out of context question…

  14. Nabil Hassan

    Hi Matthew,

    Could you please provide some light on SAP Lumira Studio Data Source options with web intelligence instances other than third party components.








  15. Stefan Zumbühl

    Hi Matthew


    One Question.

    We have actually a system with BI 4.2 SP4 patch1. This system has this addons: DS 1.6 SP5 patch2, SAP Lumira 1.31 SP7 and Analysis for Office 2.4 SP3 patch1.

    All on one server.

    We will update soon our system to SAP Lumira 2.0 with a second server. I will install only the APS Service for SAP Lumira 2.0 on the new host.

    What is now the exactly upgrade path?

    My thoughts are:

    Server 1: Update the system with the patch for SAP Lumira 2.0.
    Server 2 (new): I install with the full package only the APS service for SAP Lumira 2.0

    After the installation, i will delete the designstudio- and lumira-service on server 1.

    Is this approach ok?

    Regards Stefan


    1. Matthew Shaw Post author

      Hello Stefan

      Spot on with your plan.

      I would recommend that on your new Server2 to install everything (including the full install package of Lumira 2). When I say ‘everything’ I mean all the server components (CMS, FRS, all the components that you have installed on server 1). Why? because it brings consistency and flexibility.

      It’s up to you if you want to install the Analysis for Office Add-on on server 2, but I would generally recommend it for the same reasons of consistency and flexibility.

      Regards, Matthew



    Hi experts,

    I have seen your blog for sap lumira upgrade .I would like some expert advise from you.
    My question is
    We are at BOBJ 4.2 SP2 Patch 9 on Suse Linux/Sybase and moving to BOBJ 4.2 SP4 on Windows/SQL SERVER. (Currently we are at LUMIRA 1.30 ON WINDOWS)
    ( Question -1) So can we go ahead and upgrade lumira from 1.3 to 2.0 and ( question 2) is lumira currently on windows 2012 will it support with the newly environment of BOBJ Windows 2016 /SQL Server 2016, ( Question 3) while we were performing BOBJ to 4.2 SP4 OON WINDOWS/ SQL Server – we need to disconnect our current lumira , how to disconnect ? steps ? ( question 4) once successfully moved BOBJ to 4.2 sp4 on windows/SQL Server – we need to update BI Platform 4.2 SP4 patch at lumira server also + lumira upgrade from 1.3 to 2.0 by only patch not the new install ? is that correct ?
    Could you please help me with this .


    1. Matthew Shaw Post author

      Hello Shafeeq

      Your questions, and really the answers to them, can be a little long and complex.

      Your question is about updating to Lumira 2, but also a general question about updating from one version to another, including changing OS and changing the CMS RDBMS.

      Can I point you to this blog where you’ll find, mostly in the comments, answers to your questions about changing changing OS and changing the CMS RDBMS. There’s no need to perform a full installation is the short answer. To change OS: this is nothing more than extending/expanding the cluster. To change CMS RDBMS then you need to use the CCM-Change Data Source to copy the CMS content to another RDBMS.

      Can I also point you to where you’ll find a general guide about updating including special SP4 gotcha’s that include a number of special bits about Lumira 2 (this blog points to the blog I just mentioned in the related article). This will help to answer your question #1.

      At all the steps you need to make sure you’re on a support platform by checking the Product Availability Matrix (PAM) for the product. This will help you answer your question about the platform you want to use.

      I don’t understand your question about disconnecting Lumira. You can’t disconnect Lumira. You can remove a node that has a Lumira server installed on it. You can’t uninstall an Add-on (at least not from the CMS repository). You can only remove the add-on from the disk (I don’t recommend uninstalling Lumira 1). The ‘Lumira Patch’ is only for a machine that already has Lumira, otherwise its the ‘Lumira full install’.

      I think you need to work out what you plan is. For example do you install Lumira 2 now, or when you get to your target configuration? (you’ll need to check the PAM and the blogs I’ve mentioned). An outline plan might be:

      1. Expand the cluster (to include Windows machines) (when expanding you must install the very same product version as the rest of the cluster). Result=1 cluster of mixed Linux + Windows machines but all on exactly same BI version. (never run CMS process at same time on *nix and Windows)
      2. Change CMS RDBMS (by using CCM)
      3. Update all machines that will be used in the final configuration (no need to update machines you’ll delete)
      4. Delete/remove the nodes of machines you’ll no longer use (perhaps all your Linux machines)
      5. Apply Lumira 2.0 Add-on (either the ‘update’ or the ‘full’ depending – see this blog for more details)

      But there’s a lot of things to check and validate first. Once you’ve worked out your plan you’ll need to test and validate it, before applying the same steps in production.

      In general I’d recommend applying Lumira 2.0 after you’ve done all the other tasks, rather than before.

      I hope this helps, Regards, Matthew (@MattShaw_on_BI for those on Twitter!)

  17. Santhosh Kumar Alladi

    Hi Matt,

    We are on SAP BI 4.2 SP03 and we would like to try Lumira 2.0 on our Sandbox environment, which won’t impact either development or production.

    How do we join Early adopters and download Lumira 2.0 so that we can download and test Lumira 2.0?

    1. Matthew Shaw Post author

      Hello Santhosh, Lumira 2.0 Support Pack 2 is generally available (GA) and so you can download it today. The Early Adopter and Beta Programs have finished for Lumira 2.0, as the product is GA. Regards, Matthew

      1. Santhosh Kumar Alladi

        Thanks Matthew, it would have been great, if existing Lumira documents can be convereted automatically with SAP Lumira discovery with one click in Lumira 2.0

        We are on SAP Lumira 1.31.3 and BIP SP 03 Patch 02.

        So, we need to do following. Do you think, if I have missed any thing?

        1. Update BIP platform with Lumira 2.0 SP02 Platform Add-on
        2. Update SAP Lumira 1.31.3 to SAP Lumira 1.31.8
        3. Install SAP Lumira Discovery 2.0
        4. Convery .LUMS files to LUMX
        5. Uninstall SAP Lumira 1.31.8
        6. Install SAP Lumira Designer 2.0
        7. Convert SAP Design Studio 1.6 to SAP Lumira Designer 2.0
        8. Uninstall SAP Lumira 1.31.3 and SAP Design Studio 1.6
        9. Remove old design studio services from CMC
        1. Matthew Shaw Post author

          Hello Santhosh,

          Thank you for your feedback on the auto-conversion. It’s certainly a good idea. A decision was made not to support side-by-side on the server but to allow side-by-side support for the client. So if you only use the client, then there’s no forced conversion.  If you use the BI Launchpad to view and interact with Lumira v1 documents then you do need to convert them, via the client.

          There’s a good number of architectural changes between v1 and v2 and so the auto conversion is somewhat complicated and in some cases the changes are so fundamental it may not be possible to have exactly like for like.

          Some bits you mentioned are optional:


          • Update BI Platform with Lumira 2.0 SP02 Platform Add-on

          This step is only necessary if you’re using the BI Platform for securing and managing Lumira. For the very large majority of customers this will be necessary including you. As soon as you do this, all existing Lumira 1.x documents will no longer be accessible within BI Launchpad. You can only download/upload Lumira 1.x documents via the Lumira 1.x client.


          • Update SAP Lumira 1.31.3 to SAP Lumira 1.31.8

          Actually this could be optional step. We say its mandatory, but actually it may not be. It depends! Its a little complicated to explain, but lets give it a go! When you saved a document with an early version of Lumira, say 1.25, the metadata of the charts was saved in the format at the time when the chart was created. In more recent versions of Lumira the chart metadata would be saved with more properties. When you then open the ‘old’ document (v.1.25) with a more recent version of Lumira 1.x, say Lumira 1.31.6 it can still read the ‘older’ chart metadata and you don’t notice anything. When you save the document, and you’ve not modified the chart, the chart will still be saved in the older format. However, Lumira 2 is expecting the chart metadata to be of Lumira 1.31 format.  And that’s the problem. So Lumira 1.31.8 forces all the chart metadata to be updated when the document is saved allowing Lumira 2.x to read it ok. There’s been so many changes to the meta data for some many chart types its very difficult to say which documents of which versions will be ok with Lumira 2. This is why we say its mandatory. You might find you don’t need this step, especially if you don’t have old documents created with old versions of Lumira.


          • Install SAP Lumira Discovery 2.0
          • Convert .LUMS files to LUMX
          • Uninstall SAP Lumira 1.31.8

          There’s no harm leaving Lumira 1.x installed on the client. I would recommend you leave it installed until you’re happy that all your Lumira documents have been safely updated to Lumira 2.x


          • Install SAP Lumira Designer 2.0

          Optional. Only needed if you have previously made use of Design Studio 1.x or you’d like to take a Discovery document and enhance it. For you, this step is necessary.


          • Convert SAP Design Studio 1.6 to SAP Lumira Designer 2.0

          Optional.You con convert your old Design Studio 1.6 applications slowly over time. Existing Design Studio 1.6 applications will continue to work as previously as they run in ‘compatibility mode’. There are some minor exceptions, I think to do with JDBC connections to HANA.


          • Uninstall SAP Lumira 1.31.3 and SAP Design Studio 1.6

          The uninstallation of your 1.31.3 will have occurred when you optionally installed Lumira 1.31.8 as you can’t have two version of Lumira 1.x side-by-side (unlike Lumira 1 and Lumira 2 on the client). Again, I would leave Design Studio 1.x installed until you’ve converted any old Design Studio Applications to Lumira Applications. Your conversion could be months, or even years away as you can quite happily use old Design Studio 1.x applications alongside new Lumira Design and Lumira Discovery.


          • Remove old design studio services from CMC

          Takes just a moment. Remember do not uninstall any server-side Lumira 1.x or Design Studio 1.x Add-on.


          I hope this helps. (press the like button if it does!)

          Regards, Matthew


          1. Santhosh Kumar Alladi

            It’s great that it allows side by side installation 🙂

            We test end to end functionality first in Sandbox, if all goes well, then we will plan for Lumira upgrade.

            Yes, we have both Lumira and DS currently, hence might need to convert all of them sooner or later.

            Thanks  a lot for quick response, now I am following you on Twitter 🙂

  18. Amritansh Kumar

    Thanks for such a wonderful explanation Matt.


    I just have a query. I installed “SAP Businessobjects Lumira server for BI platform 2.0 SP2”. Do I need to install any BI add-on for SAP lumira also? However, I do not see any such setup available to download on SAP market place. Can you please suggest?

      1. Matthew Shaw Post author

        Hello Amritansh, What you’ve installed (based on your description) is the BI add-on for SAP Lumira.

        There’s a few ways to tell its installed ok (and assuming you have redeployed the Web Applications).


        The CMC-Applications will have a ‘SAP BusinessObjects Lumira’ entry


        The CMC-Servers will show a ‘Lumira Server Services’ and a ‘LumiraServer’

        And the BI Launchpad will show the ‘Lumira Discovery’ Application:

        Hope this helps? (press Like if it does!)

        Regards, Matthew


        1. Matthew Shaw Post author

          Great. Please do NOT create a local document inside SAP Lumira Designer, Please ALWAYS create the document on the BI Platform. This is important as the document needs a CUID (which is only created when saving the document to the BI Platform). This CUID can then be used by other Lumira documents when referring to it, for example when reusing a composite.  Regards, Matthew

  19. Anup Shankar Belur Shivashankar

    Hi Matthew,

    Is there a document which describes detailed steps for installation of Lumira 2.0 server on BI Platform (Workflow A – No existing Lumira or Design Studio Add-on).

    We are on BI Platform 4.2 and need to install full Lumira 2.0 Add-on.

    Thanks in advance,


  20. Siddhartha Chaudhary

    Has Lumira 2.0 installation media replaced after 14.08.2017? If yes, can you please answer if there was any bug or issue in earlier installation. look at attached image

    Discovery installation media name on 14.08.2017 is 51052366 but on 28.08.2017 is 51052385

    Desinger installation media name on 14.08.2017 is 51052367 but on 04.09.2017 is 51052406



      1. Matthew Shaw Post author

        Sorry for the delay in my reply.

        There’s really nothing to worry about! That might seem a little odd as the file names and sizes are different.

        We republished the Lumira package as we changed the location of where you download Lumira within the Software Centre, this causes the dates to be different. We also created a new build of Lumira desktop to fix a problem where the license edition description and the available days where mixed up. They where swapped over. There’s no changes to the server builds, and the change I mentioned about the client isn’t a change of functionality and has no impact other than displaying the license and available days in the right location.

        So it really doesn’t matter which download of Lumira 2.0 SP2 you use, they are really basically the same.

        Sorry for the confusion! Matthew

  21. Jose Canas Escalante

    Hi Matthew,

    Thank you very much for the article.

    I have an issue after install lumira server 2.0 the data sources of my DS 1.6 dashboards are not loading, any suggestion?

    I have BI 4.2 SP04 with Lumira and DS add-on




    1. Matthew Shaw Post author

      HI Jose,

      Some ideas:

      • check the PAM the connectivity is still supported. JDBC to HANA isn’t supported compared with DS 1.6.x
      • check it works locally to validate the app is ok.
      • enable trace on the server (better to do an end to end trace)
      • create a new app from scratch and see if that works or not. Isolate if 1 app or multiple.

      Please do post back with any progress/solution to help others. Regards, Matthew


      1. Jose Canas Escalante

        Thanks Matthew.

        My app its working locally and have a JDBC connection to HANA.

        So if this its not supported the DS app will not work in the platform right?

        There is no workaround? because we want to use Lumira 2.0 but all our dashboard are using JDBC connection.

        Best regards,


        1. Matthew Shaw Post author

          Hello JC,

          Indeed you are correct in your understanding. The App won’t work on the Platform. You’ll need to change the application so it consumes the HANA source using a HTTP InA protocol. More at KBA 2475223. Our direction is very much HTTP InA and not JDBC. The HTTP protocol doesn’t require any local middleware and its much easier to deploy therefore.

          Regards, Matthew


  22. Michael Hamm


    Hi Matthiew,

    do we really need to install Design Studip 1.6 and Lumira 1.31 if we want to achieve the following?

    Server A

    • Lumira 1.31
    • Design Studio 1.6


    Server B

    • Lumira 2.0 BIP Add-On

    We want to promote the content from Server A to Server B live-to-live.

    Do we need to install Design Studio 1.6 and Lumira 1.31 on Server B first? Manual export is no option with thousands of reports..

    Thanks & BR,


    1. Matthew Shaw Post author


      Hello Michael,


      Once you’ve installed Lumira 2 on a server with Lumira 1, any Lumira 1 documents can not be seen within BILaunchPad or in the CMC. This includes in Promotion Management and Version Management. However, if you have previously installed Lumira 1, then the BI Platform will at least understand the old Lumira 1.x documents so that can be promoted into it.

      BUT, the system that you use to run the Promotion Management will need to be your Server A, not Server B. Server B won’t list Lumira 1.x documents (.lums) even if you did previously install Lumira 1.  So, you need to run your Promotion Management Job on Server A to promote Lumira 1 content into Server B, this is applicable if its live-to-live or LCMBIAR-to-live. When the promotion is made to Server B, the Platform won’t complain the document type is unknown, since Lumira 1 was previously installed on it. If you didn’t previously install Lumira 1, then the promotion will fail as the Platform won’t understand that Lumira 1 (.lums) is a valid file format.

      Lumira 2 uses a different file format .lumx

      If you try to run Promotion Management on Server B it simply won’t see any Lumira 1 content for both live-to-live or LCMBIAR-to-live. (since Lumira 2 has been installed on it. It makes no difference if Lumira 1 was installed on it beforehand or not).

      Do let us know how you get on, what worked or not for you.

      I hope this has helped. Regards, Matthew

  23. Brian Kudera

    Hello team- I’m ready to install 4.2 SP4 on DEV and I’m going to also migrate from Xcelsius to Lumira Designer. I was able to find where to download the desktop software, but I’m not finding the Lumira Server Add-On. Can someone advise which menu the server add-on is under in the downloads, or what I can search for? I still see the Design Studio Add-On but as I understand in looking at upgrade path “Workflow C” there should be a specific Lumira Add-On application?

  24. Asif Ahmad


    Can you help me with following issue please:

    I upgraded Lumira 1.3 to Lumira 2 on BOBJ 4.2 SP3 using patch update (LS4BIP02_0-70002327.exe). Installation work fine. I tried to run Lumira  Discovery from  Applications on the BI Launchpad and get error
    Analysis Application
    Unknown Error While processing the current request, an exception occurred which could not be handled by the application or the framework.

    Login ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

    Unable to process your request. Contact your system administrator.


  25. Nitin Gupta

    Hi All,


    I am trying to upgrade by Lumira 1.3 to Lumira 2.0 for BO on Suse linux. But the Package available for download for Linux on SAP site is showing product version as BuildVersion=2.0.0200.60.lumirateamserveraddon_patch_lumira_cons_LS4SBOPBIP_fa_rel_UNIX-20.0 after extraction and i am getting error in pre check as Failed: #product.teamserveraddon_shortnamed installed (Critical) is missing

    I have download package from location

    Have any one faced this issue with this package.


    Thanks and Regards


  26. Markus Hagedorn


    we are trying to install the Lumira Server Addon 2.0 SP2 Patch 1 (full installation).

    When running the setup only setup from # product.teamserveraddon_name # 4.1 SP5 appears??

    Does anyone have a similar effect?

    We do not want to install on C :.

    How do I change the Installation directory?


    Our BI-server (Windows 2012 R2):

    BI 4.2 SP4 Patch1

    DS-AddOn 1.6 SP5 Patch1


    Best regards


  27. Mark Richardson

    Matt :

    I don’t see this explicitly referenced here – but for Workflow A – a greenfield install, if you are on BIP 4.2 (SP04) as the baseline…you need to patch the platform up to (at least) BIP 4.2 (SP04 – Patch 1) before you can apply the LUMIRA server for BIP 2.0 (SP02).

    2467541 – Supported BI Platform Add-On versions information for the SAP BusinessObjects BI 4.2 SP04 and patch 1 release

    That caught us on a recent SANDBOX project.




  28. Vijayakumar Subramani

    Hi All,

    We are at SAP BusinessObjects BI Platform 4.2 Support Pack 3 Patch 3 and Lumira 1.31. To upgrade Lumira 2.0 I have installed LS4BIP02_0-70002327.EXE – SP02 for SBOP LUMIRA SERVER FOR BIP 2.0 Update in our test system which is Single server instance.

    After installation, able to connect Lumira Discovery & Designer with SSO.

    Based on the results I went ahead and instilled our development environment which is clustered. But after successful installation, Lumira Designer not able to connect.

    As per SAP, Lumira Designer will work only in the Standalone server, not a clustered environment.

    Anybody facing this kind of scenario?





  29. Luis Rivera

    Hi and thanks for the document, it is very helpfull. We have an issue here. We have upgraded to BOBJ SP4 patch 3 and installed new Lumira 2.0 SP2 patch1 and using Lumira Designer 2.0 SP2 patch1, but when trying to upload a document we have a 404 error (attached log here). Have any of you guys experienced that?. I already have opened a ticket to SAP for this issue but was wondering if you have seen that.




    !ENTRY 4 0 2017-10-13 12:48:29.007!ENTRY 4 0 2017-10-13 12:48:29.007!MESSAGE Failed to create document!STACK Failed to create remote document “test3” at at at$1.execute( at org.eclipse.ui.actions.WorkspaceModifyOperation$ at at at org.eclipse.jface.operation.ModalContext$ by: org.apache.http.client.ClientProtocolException: Unexpected response status: 404 at at … 6 moreCaused by: org.apache.http.client.ClientProtocolException: Unexpected response status: 404 at at … 7 more


Leave a Reply