Promoting Design Studio 1.x or Lumira 1.x content ...

Matthew_Shaw · ‎10-04-2017

Once Lumira 2 has been installed there are limitations to when old content, from both Design Studio 1.x and Lumira 1.x, can be promoted. This blog shares what is supported and will enable you to plan accordingly.

Whilst Design Studio 1.x content will happily run once Lumira 2.x has been installed (though there are some restrictions KBA 2475223) your Lumira 1.x content can only be held in the Repository for your Lumira 1.x clients to retrieve it. Your Lumira 1.x content, once Lumira 2 has been installed, can not be viewed in either the BI Launchpad or in the Central Management Console. This means the use-cases for promoting Lumira 1 content into a Lumira 2 server is limited, but good to know its possible albeit with some restrictions. More on the Lumira 2 update.

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

If you have performed a fresh install of the BI Platform with the Lumira 2 server add-on and

you’d like to use Promotion Management to promote your old Design Studio applications of version 1.x into it

and Design Studio 1.x BI Platform add-on has not been installed to any machine in the new cluster anytime in the past

then you must install the Design Studio 1.x Add-on (to any machine in the cluster) before installing the Lumira 2 add-on. If you don’t install it beforehand, the BI Platform won’t understand the old Design Studio 1.x application type and the content simply won’t be promoted, It will complain of a missing plug-in. This would then mean you have to convert your old Design Studio 1.x content to Lumira 2.x before you can successfully promote it. More information at KBA 2529186

The Promotion Job can be run either on the source or the target it makes no difference.

The source may or may not have Lumira 2 Server add-on installed, it makes no difference.

The source can be an LCMBIAR file.

If you have installed any Design Studio 1.x BI Platform add-on to any server within the target cluster any time in the past, then you’ll avoid this problem. Your content will promote as expected.

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

If you have performed a fresh install of the BI Platform with the Lumira 2 server add-on and

you’d like to use Promotion Management to promote your old Lumira 1.x documents (.lums) into it

and Lumira 1.x BI Platform add-on has not been installed to any machine in the new cluster

then you must install the Lumira 1.x Add-on (to any machine in the cluster) before installing the Lumira 2 add-on. If you don’t install it beforehand, the BI Platform won’t understand the old Lumira 1.x document type (.lums) and the content simply won’t be promoted, It will complain of a missing plug-in. This would then mean you have to convert your old Lumira 1.x content (.lums) to Lumira 2.x content (.lumx) before you can successfully promote it.

Additionally:

Either the source needs to be an LCMBIAR file OR the source must be a system that hosts your Lumira 1 content and that same source system has NOT been updated to Lumira 2.

The BI Platform that you use to run the promotion job must have Lumira 1 installed on it and it must not have Lumira 2 installed on it (as once Lumira 2 is installed, Lumira 1 content is not shown anywhere in the CMC). Typically this will be the same as your source system, which has already got the Lumira 1 content and Lumira 1 server add-on installed so this shouldn’t be a problem. It means you can not run the job on the target system.

These additional requirements are not applicable for Design Studio 1.x content.

Promoting with option 'Include Application Rights'

If promoting with the option 'Include Application Rights' then all the source applications must exist in the target. For example any add-ons (Analysis, Explorer, Design Studio etc.) in the source must exist in the target. If not, the Promotion will fail and the logs will show errors like

Failed to export object with ID = 23 from source system. com.businessobjects.sdk.biar.BIARException$EngineException: The kind 'VISILums' does not exist in the CMS. (FWM 04030

Lumira 1 add-on is not the same add-on as Lumira 2, so if promoting from a server which has Lumira 1 content to a server with Lumira 2 and with the option 'Include Application Rights', then Lumira 1 must be present in the target, even if the promotion job has not Lumira 1 content.

To avoid the error, either de-select the option 'Include Application Rights' or ensure the target has all the add-on applications that exist in the source.

A related SAP note 1918080