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.

Convergence

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

There’s no need to uninstall the old ‘Design Studio 1.x’ Add-on, but like any old Add-on that you’ve updated to a newer version, you can uninstall it. The same applies for Patches and Support Packs too – just don’t uninstall the base Support Pack or you’ll uninstall the whole thing!

If you don’t fancy leaving an old ‘Design Studio 1.x’ Add-on, you can uninstalled the Design Studio 1.x and install a ‘full’ Lumira 2.x Add-on, but we really don’t recommend doing that. We recommend you just update.

Equally you can uninstalled the Lumira 1.x Add-on and install a ‘full’ Lumira 2.x Add-on. We have no major recommendation for either workflow (update or remove first). It’s up to you, but personally I’d recommend the update.

 

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.

13 Comments

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?

    (0) 
  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) 
    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) 
      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?

         

        (0) 
  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?

     

     

    (0) 
  4. Matthew Shaw Post author

    Jawahar,

    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

    (0) 
  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.

    Thanks,

    Mark

     

     

    (0) 
    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

       

       

      (1) 

Leave a Reply