Lifecycle Management Console
SAP BusinessObjects Lifecycle Management console (LCM) is a web-based tool that enables you to move Business intelligence (BI) resources from one repository to other. It also supports the management of different versions of the same BI resource.
It offers some significant improvements over the Import Wizard. One of the most important new features of LifeCycle Management is that you can import categories as well as other types of objects such as: Information Designer, Pioneer, Crystal Reports (next generation), Events and Xcelsius Enterprise.
LifeCycle Management is used for promotion or transporting content from like system to like system, i.e. systems are the same version E.g. Dev to Test to Production.
1.png
This tool has two main roles:
  • To copy Reports, Universes, Folder Structures, Security rules, Events and many other objects between environments. If needed it can also be used as a controlled Fallback to previous versions.
  • To provide Version Management of Reports and Universes via a tool.
LCM Promotion Process
Steps to promote reports and universe between environments.
Log on to SAP BusinessObjects BI Platform Lifecycle Management Console with administrator Credentials.
Once logged in, you’ll be in the Promotion Jobs screen.
Step 1:  Click on New Job in the top left of the screen. A job contains the definition of which objects you will be moving, the source and the destination systems, and a schedule if applicable.
Note: User should have the admin access to create new job
2.png
 
Step 2:  In New Job page enter all the required details.
3.png
NAME: Name of the job that you want to create
Description: Description of the job you want to create. Entering this information is optional.
Save Jobs In: A GUI element that enables you to store the job in a folder of your choice. You must select a folder to create a job.
Source System: The name of the BusinessObjects Enterprise system from which you want to promote a job.
Destination System: The name of BusinessObjects Enterprise system to which you want to promote a job.
 
Step 3:  Click on Create. This creates a new job object and will be stored in a CMS repository. Now select the objects that you want to move.
 
Step 4:  Once the job is created, you need to add infoobjects (ex: Universe, Reports etc. which needs to be promoted) to the job.  To add Info objects click on Add Objects or right click on workspace pane and select Add Objects.
4.png
 
Note: To Promote, User should have admin access in both source and destination systems.
The "Life Cycle Manager Add Objects" dialog box appears, and the Folders and Objects tree structure is displayed. Select Folders and Objects from Left panel. Navigate to the directory where the reports are placed. Select Info Objects and click on Add & Close.
5.png
 
Note: Business Objects recommends that you select a small number of info objects, not more than 100 at a time, for promotion to obtain optimum performance of the LCM tool.
 
The Add Objects window closes, and you’ll find yourself on the main page for the new job. Note that it’s actually a new tab at the top of the screen.
Step 5: If you are planning to promote the report (source) dependent objects like universe\connections, then you can add them using Manage Dependencies option.
6.png
 
Clicking the button will show what other dependent objects in the system are used by the objects that we have selected. In this case, there’s a universe & a connection.
7.png
 
Select Universe and connection and click on Apply & Close.
 
Step 6:  To promote, Click on the objects you want to promote and select Promote.
8.png
The Promote window appears. In the Promote panel we can find four options:
Summary: Check source and destination names to ensure the file is moving from the right source to the correct destination, change management ID.
Security Settings: Check this option when you want to release the security of the  files.
Test Promote: Use this option to ensure that there will not be errors during the conversion.
Schedule Job: This is to plan the promotion task for later, very useful if you are not available to do it manually, typically at out of office times.
9.png
Security Settings: [optional and should be used only if we need to promote the security]
There are two options in this section
 
1. Do not promote Security
2. Promote Security
 
Uses the option to promote jobs along with the associate security rights. Click on Security Settings and select the option.
10.png
  Test Promote: Summary to view the objects to be promoted and the promotion status.
11.png
 
  • Schedule Job: The LCM tool enables you to specify when a job must be promoted, rather than promote it as soon as it is created. It also enables you to schedule promotion at fixed intervals. This feature is useful in promoting large jobs when the load on the server is at its minimum.
12.png
Step 7: Click on Promote
Once the job is promoted you can check the status of the job. To check Status, Click on the History option.
13.png
You can check the job status.
14.png
=======================================================================
Rollback
The Rollback option allows us to check the different versions of a conversion set and, in case of errors, to revert back to a previous stable version and therefore prevent any risk to the project, after a job is promoted.
Before starting a Rollback, we must ensure that the status of the job is one of the following:
  • Success
  • Failure
  • Partial success
You can roll back an entire job or part of the job.
 
Please note that you only can go back to the most recent previous instance. To restore the latest instance, click in the check box and then press Rollback button. You can choose between two rollback options:
Complete Rollback: this will restore the destination system to its previous state before the job was promoted
Partial Rollback: enables you to roll back a set of infoobjects included in a job by selecting them from their objects list.
In the Promotion Job home page, select a job and click Rollback.

15.png

 

Click on Complete Rollback.

16.png

 

=======================================================================

Creating a new job by copying an existing Job

 

Step 1: Log in to the Lifecycle Management console. On home page, click on New Job.

Step 2: Click the Copy an existing job.

17.png

 

 

The list of promotion jobs will be displayed.

 

Step 3: Select a job from the job list, and click Create.

The name, keywords, and description of the job are displayed. You can modify these fields, if required. However, you cannot change the source system.

18.png

 

 

Step 4: Click Create.

===========================================================================================

LCM LOGS

 

Enabling Traces – Web Tier logs

 

  • Go to CMC > Applications and right-click the LifeCycle Management. Then click Trace Log Settings. Set the Log Level to High.

19.png

 

  • Restart Web application server. Logs will be in the default BusinessObjects BI 4.0 logging directory.

 

Enabling Traces - LCM Services

 

  • Go to CMC > Servers and in the Properties for the Adaptive Job Server and Adaptive Processing Server set the Log Levels to High.

20.png

  

  • In the CCM, restart the Adaptive Job Server and Adaptive Processing Server. Logs will be generated in default logging folder.
    • \SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\logging\*.AdaptiveProcessingServer_trace.0xxxx.glf
    • \SAP Business Objects\SAP BusinessObjects Enterprise XI 4.0\logging\*.AdaptiveJobServer_LCMSchedulingService_CHILD0_trace.0xxxxx.glf
Upgrade Management Tool in BI 4.0
Upgrade Management Tool is a new software component that lets you upgrade the content of your BI repository from a previous version of SAP  BusinessObjects BI platform more efficiently.
Improvements in BI 4.0
Some of the improvements made in BI 4.0 are mentioned below.
  1. Universe can now be sourced from multiple datasources.
  2. Universe can access from MOLAP (cubes from Microsoft Analysis Services, Essbase, Mandroin etc.) datasources directly via MDX without having to flatten them out. Prior version, Universe can access only SQL source.
  3. More common look and feel to understand BI products, including Crystal, WebI, Explorer and BEx.
  4. Universe can now be directly accessed by the Dashboards 4.0.
  5. There is a tighter integration with BW via direct exposure of BW metadata (BW query and Infoprovider) to all BO tools.
The previous version’s major limitation is, many components needed a separate installation. But in the new version of BI 4.0, the components don’t need separate installations and these components are directly integrated with SAP BI 4.0.
End of Lives in BI 4.0
      1. Performance Manager
      2. Desktop Intelligence
      3. Import Wizard
One of the first things you will discover when migrating from XI3.1 to BI4 is that the Import Wizard (IW) is gone, and it has been replaced by the Upgrade Management Tool (UMT). This is great, since the UMT is a bit easier to use. However, there are a few things that are helpful to know to make the migrations go more smoothly.
1.png
Upgrade means transport and transform content from previous version to newer version. Content includes all objects.
2.png
Increase the Heap size
By default the UMT uses 2GB of memory. With UMT, the performance will be slow and the migration keeps on failing if the heap size is less. But we can see a drastic improvement in performance by increasing the heap from 2GB to 8GB.
The setting is simple to change. Look in the Start menu and browse to SAP BusinessObjects BI platform 4. Right-click Upgrade management tool and select Properties.

3.png

 

 

Look in the target section for -Xmx2g. If you want to increase the heap to 8GB, simply change the 2 to an 8.
Example:
  “C:\BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\ win64_x64\ jdk\ jre\
  bin\ javaw.exe” -Xmx8g -Djava.library.path=”..\ ..\..\..\win64_x64″ -jar  upgrademanagementtool .jar
4.png

 

 

Temp Directory Redirect

Upgrade Management Tool copies all of the content that is being migrated to the Windows temp directory prior to copying it to the FRS. This means that not only we need enough space in your FRS, but you also need free space in the Windows temp directory.

 

Another option we have is to redirect the temp directory.  To redirect UMT’s temp directory, once again open the properties for the UMT shortcut. Add the following to the target right after javaw.exe” (It can go before or after the memory flag from above): -Djava.io.tmpdir=”TEMP PATH”

 

So, for example, if the new temp directory is located at e:\temp,we have to modify them as -Djava.io.tmpdir=”e:\temp”

Example: “C:\BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\jdk\jre\bin\javaw.exe” -Xmx8g -Djava.io.tmpdir=”E:\Temp” -Djava.library.path=”..\..\..\..\win64_x64″ -jar upgrademanagementtool.jar

 

5.png

 

Migrating Content:    Complete vs. Incremental Migrations

 

What is Complete Upgrade?

  • Upgrade all content at once
  • Only 1 system to maintain
  • Requires lockdown of the entire system
  • Issues affect the entire system
  • Long downtime

 

What is Incremental Upgrade?

  • Upgrade content in stages
  • 2 systems to maintain
  • Requires lockdown of department folder
  • Issues affect only the department upgraded
  • Short downtime

 

Now that UMT is configured, you are ready to start migrating. The first prompt asks if you would like to do a Complete or Incremental Upgrade.

8.png

 

 

The complete upgrade will attempt to copy everything, while incremental will allow you to specifically select what to migrate. If you are migrating a small system, you could try a complete upgrade. However, incremental is suggested because it offers more flexibility and can help identify points of failure if there are problems.

Live or BIAR?

 

Next, we can specify how we want to migrate. Do you want to migrate directly from a live system to another live system, or do you first want to migrate to a BIAR. Our network’s bandwidth and server’s storage will likely influence the decision.

6.png

7.png

 

If you selected the complete upgrade option, there’s not much left to do after specifying the server/BIAR settings. Click Start, and wait for it to finish.However, if you are doing an incremental upgrade, there are just a couple more steps.

9.png

10.png

 

 

Instances

When performing an incremental upgrade, the next decision will be whether or not you should migrate instances. Instances are not always needed, and you may simply be able to back them up to a BIAR for archival purposes. Just know that exporting instances will result in a larger migration.

 

Object instances are migrated by default. To not migrate instances, click Options, and select “Do not export object instances.”

11.png

 

 

Finishing the Migration

At this point, select the content that you want to migrate, click start, and depending on the amount of content being moved, this could take a while. Once it is finished, you will get a message stating that the upgrade is complete.

12.png

13.png

 

 

BI Content that is not upgraded

 

Desktop Intelligence

The Upgrade Management tool does not upgrade DESKI documents as Desktop intelligence has reached end of life. Desktop Intelligence documents will not work in BI4.0. However, you can convert Desktop Intelligence documents to Web Intelligence using the Report Conversion Tool in your existing XI3.x deployment and then bring those Web Intelligence documents with the Upgrade Management tool.

 

Other option is that you can convert your Desktop Intelligence documents residing in your existing XI3.x using BI 4.0 Conversion Tool and then publish them to your new BI4.0 deployment.

 

Auditing DB

The audit database has a new schema, so you can’t upgrade your existing audit database. You can keep it for historical process and start the new database in BI4.0. If you want to create reports from both databases you can use the Information Design Tool to create a multisource universe.

 

Subversion repository (Version Management)

If you are using the version management feature in the LifeCycle Management console in XI3.x, the content in the Subversion repository won't be upgraded by the Upgrade Management Tool as this is an external repository.

 

 

Upgrading to BI 4.0 – Special Considerations

 

Security 

  • Some work will need to be done to adapt migrated content to the new application and role security changes.

 

Dashboard Migration 

  • ‘My InfoView’ and ‘My Dashboard’ objects are migrated to BI Workspaces located in users’ ‘My Favorites’ folders
  • Corporate dashboards are migrated to BI Workspace under the public folders

 

Voyager to Advanced Analysis – OLAP Edition  

  • For MSAS customers, some specific functionality is not available in version 1 – will need to wait until a later server pack.
  • Workspaces from Voyager will be converted to Advanced Analysis - Web but some manual adjustments may be necessary.

 

 

We know that in BI 4.0, we cannot create a Universe using BeX with Information Design Tool(IDT) ,as we were doing it in legacy designer tool.

 

But Using a cube we can build the universe using IDT. Below are the steps for the same.

 

 

Universe creation using InfoCube in IDT

 

 

  1. Insert a relational Connection

 

6.JPG

 

 

2.  Select SAP Java connector Driver from the available list

  2.JPG
3.  Fill in the credentials

 

3.JPG


  4. On Clicking the ellipses highlighted, the below info provider screen appears.

 

4.JPG


5. Under filter dropdown, check CUBE and Click on OK and Click Finish to complete the Wizard to create a connection.

 

5.JPG

6. With the Connection created, create a data foundation with type as multisource-Enabled  and just select single connection created above and build the data foundation layer.

7. Finally build the Business layer and publish it to repository.

8. Use this universe (unx) created for reporting.

 

Universe can be created between Cube and SQL (no BEX) and create an .UNX in IDT.  Few advantages are

  • Direct link to infoprovider level
  • Allows to combine multiple source in a single connection.
  • Allows you to customize the objects.

o

Filter Blog

By author:
By date:
By tag: