Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata
 

Following is the quick summary of the number of iterations and their scope (what’s actually included in that iteration to migrate from source BOE XI 3.1 to target BI 4.2):

 

Iteration

Scope

Iteration #1

In this iteration, the following objects were migrated with their   dependencies:

  •   User groups
  •   Access Levels
  •   Applications

The same approach can be used for all user groups, all access levels   in a single iteration. However, this can be time consuming based on the   number of objects etc. Therefore it’s recommended to decide the number of   iterations based on your repository objects.

Iteration #2

The following objects were considered for upgrade with dependencies.   You can select these objects for migration in the Object selection screen:

  •   Folders and Objects
  •   Repository Objects
  •   Universes

For this pattern book, we have done the migration in a single   iteration. However, depending upon the number of objects, this iteration can   be time consuming. Therefore it’s recommended to decide the number of   iterations based on your repository objects.

Iteration #3

In the initial “Select Filter” screen, the time filter was set   according to the requirement. In our pattern book, we are selecting the start   date as 02/01/2016 and the end date as 02/05/2016. So, only the following   objects will be listed and migrated:

  •   Universe – Universe modified between the start   date and end date mentioned in the select filter
  •   Web Intelligence Reports – Reports modified   between the start date and end date mentioned in the select filter

Iteration #4

The following objects were considered for upgrade with dependencies.   These are the objects selected for migration in the Object selection screen:

  •   Applications
  •   Calendars
  •   Corporate Categories
  •   Profiles
  •   Remote Connections and Replication Jobs
  •   Repository Objects
  •   Universes

In this iteration, all the content dependencies (related to all the   documents) were set to be upgraded first. However, this can also be done in   increments.

Note that any objects that have already been migrated will not be   listed in the object selection screen. Again, in this iteration as we are using   the feature “Hide objects which are already upgraded” from the selection   filter screen.

Iteration #5

The following objects were selected for upgrade with dependencies:

  •   Public folders and their objects, except those   objects that were upgraded in iteration 2
  •   QaaWS objects
  •   Events
  •   Mobile Subscriptions
  •   Object dependencies will be listed in UMT, but   will be unselected later

For this pattern book, we have done the migration in a single   iteration. However, depending upon the number of objects, this iteration can   be time consuming. Therefore it’s recommended to decide the number of   iterations based on your repository size and number of objects.

 

Next Section: Iteration 1

Previous Section: New Features in UMT SAP BusinessObjects BI 4.2

  • No labels