Skip to end of metadata
Go to start of metadata

 

Objects that can be added to a Promotion Job

Objects that can be added to a Promotion Job

Objects that can be added to Version Management System

Objects that can be added to Version Management System

Comments

 

XI 3.1

BI 4

XI 3.1

BI 4

 

Public folders (Input File Repository)

Yes *

Yes

Yes

Yes

* empty folders can be promoted from XI3.1 SP3 onwards

Objects within Public folders (Input File Repository)

Yes *

Yes *

Yes *

Yes *

* See list below of included objects, pretty much anything!

Objects and subfolders within Favourate Folders (Input File Repository)

No

Yes *, **

No

No when adding the object directly to VMS.
Yes, when they are part of a Promotion Job that is added to Version Management

There should also be no need to promote individual content.

* See list below of included objects, pretty much anything!

** Can not promote content if the user does NOT have an Enterprise alias.

Instances including re-occurring schedules (public folders and favorite folders) (Output File Repository)

No

Yes (via dependency manager) *, **

No

No when adding the object directly to VMS.
Yes, when they are part of a Promotion Job that is added to Version Management

* to show completed instances enable the option in 'Job Settings' first
** for promoting schedules based off events please refer to KBA 1649684

Promotion Jobs

No

No

No

Yes *

* allows for the contents of a promotion job to be captured and 'frozen'. Can check-in multiple times. Once checked-out no more check-ins are possible as the source of the job becomes the Version Management system.

From the moment the promotion job has been added to Version Management, the job must only be 'moved' and never 'copied', since copying the promotion job object will change its CUID and break the link to its associated contents in Version Management.

Inboxes

No

Yes (1)

No

No when adding the object directly to VMS.
Yes, when they are part of a Promotion Job that is added to Version Management

There should also be no need to promote individual content.

(1) the user must exist in the target, or be promoted with it. See "Users (without an Enterprise Alias)"

Personal Categories

No

Yes (1)

No

No when adding the object directly to VMS.
Yes, when they are part of a Promotion Job that is added to Version Management

There should also be no need to promote individual content.

(1) the user must exist in the target, or be promoted with it. See "Users (without an Enterprise Alias)"

Categories

No

Yes *, ** (requires all objects in the category to be promoted)

No

Yes

* allows for promotion based off category. For example select a category and use the dependency manager to identify objects associated with that category.


** Warning: objects in target can be lost from the category if not promoted at same time. See Note 1868513 (This issue resolved with planned change in BI4.1 SP2)

Users (with an Enterprise Alias)

Yes

Yes

Yes

Yes

In general Users should not be promoted. Users should be defined/created in each environment to prevent 'development' users having 'development' rights in production.

Users (without an Enterprise Alias)

No (1)

Yes, from BI4.1 SP3 via CLI (2) (3)

Yes

Yes

  1. Can not promote a user unless they have an enterprise alias. Users that have been created by a 3rd party authentication plug-in can not be promoted between systems since the CUID on the source and target will be different.
  2. Possible with LCM Command Line Interface (CLI), not possible through the normal CMC User Interface. The target requires the authentication to be setup at a minimum.
  3. BI 4.2 SP4 LCMCLI has ability to promote (or not) 3rd party users/groups

Enterprise Groups

Yes

Yes

Yes

Yes

 

Groups defined by a 3rd party (such as Active Directory etc)

No (1)

Yes, from BI4.1 SP3 via CLI (2) (3)

No

No

  1. Place the 3rd party group inside a normal enterprise group. Place security on the Enterprise group and promote that group. This is best practice anyway for use of 3rd party groups as if there is a problem with the 3rd party group you don't lose the security settings.
  2. Possible with LCM Command Line Interface (CLI), not possible through the normal CMC User Interface. The target requires the authentication to be setup at a minimum. But in general follow note (1) just above where ever possible.
  3. BI 4.2 SP4 LCMCLI has ability to promote (or not) 3rd party users/groups

BusinessViews (including Dynamic Cascading Prompts, Connection, Data Foundation)

Yes (1)

Yes (1)

Yes

Yes

(1) Warning. Although these object types can be prompted there is limited support for mapping the data connection. This means your dynamic cascading prompts will not work in the target if you need to map to a different connection. See wiki page on mapping support

Server Groups

No

Yes (1)

Yes (2)

Yes (1)

  1. Though once in the target still need to explicitly re-link all servers to the server group
  2. From BI 4.2 Support Pack 4

Servers

No

No

No

No

 

Profiles

Yes

Yes

Yes

Yes

 

Universes UNV

Yes

Yes

Yes

Yes

 

Universes UNX

n/a

Yes

n/a

Yes

* Warning. Checking-out a UNX will delete Data Security and Business Security Profiles

Information Design Tool Shared Project: Connection Shortcut

n/a

Yes *

n/a

No

* should only really need to promote the universe. Universe development should typically occur within one environment

Information Design Tool Shared Project: Data foundation

n/a

Yes *

n/a

No

* should only really need to promote the universe. Universe development should typically occur within one environment

Information Design Tool Shared Project: Business Layer

n/a

Yes *

n/a

No

* should only really need to promote the universe. Universe development should typically occur within one environment

Relational Connections

Yes

Yes

Yes

Yes

 

OLAP Connections / OLAP Analysis (1)

Yes

Yes

Yes

Yes

(1) 'OLAP Analysis' has the full product name 'SAP BusinessObjects Analysis, edition for OLAP'. This used to be called 'Voyager'.

SAP BW BICS Connections

n/a

Yes

n/a

Yes

 

Remote Connections

Yes, from SP2

Yes

Yes

Yes

 

Replication Lists

Yes, from SP2

Yes

Yes

Yes

 

Projects (Information Designer Tool)

n/a

 

n/a

 

 

Events

Yes

Yes

No

Yes

 

Calendars

Yes

Yes

Yes

Yes

 

Custom Access Levels

Yes * (needs to be Primary Object)

Yes * (needs to be Primary Object)

Yes

Yes

Warning: When promoting a CAL after the first time and when 'promoting with security' is also specified, the user assignment will be updated in the target only when it is a primary object (not one selected just within the dependency manager).

Applications (the configuration of)

Yes, from SP2 (1) (2)

Yes (1) (2)

No

No when adding the object directly to VMS.
Yes, when they are part of a Promotion Job that is added to Version Management

  1. Warning: ensure the source and target product versions are identical when promoting Applications to avoid errors/issue when using the Application in the target.
  2. 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. 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 Lumira 2 with Application Rights, then Lumira 1 must be present in the target, even if the promotion job has not Lumira 1 content. more

QaaWS (Query as a Web Service, includes BI Web Services)

Yes

Yes

Yes

Yes

 

Access Restrictions 'Overloads' (UNV)

Yes (via dependency manager) , *, **

Yes (via dependency manager) , *, **

No

Yes, when the Universe is added to Version Management directly. Assignment to user/groups is not added to VMS.

Yes, when the Universe is part of a Promotion Job that is added to Version Management. (User group assignment is held **)

* requires universe to be added to job, but can be removed once the overload has been selected.

** Promotion of overload to user/group assignment requires promotion of users/groups within same job and promotion of security (Promote Object Security) set within the job. (The users/groups are not identified by the Dependency Manager, need to manually add the correct users/groups)

Data Security Profile and Business Security Profiles (UNX)

n/a

Yes (via dependency manager) *, from BI4.0 SP6

n/a

No when adding the object directly to VMS.

Yes, when they are part of a Promotion Job that is added to Version Management

* requires universe to be added to job. Promotion of Security Profile to user/group assignment requires promotion of users/groups within same job. Promoting just the UNX (without any Security Profiles) will remove all Security profiles on the target. Promoting the UNX with just 'new' Security Profiles (compared to the target) will add those Security Profiles to the target and will not delete the existing ones. Unlike Overloads for UNVs: There is no need to set within the job to Promote Security and it is not possible to remove the universe from the job having selected the Security Profile, as the Security Profile will also be removed.

Discussion notes

Yes (via dependency manager)

Yes (via dependency manager)

No

No when adding the object directly to VMS.
Yes, when they are part of a Promotion Job that is added to Version Management

 

Encyclopedia

Yes, from SP2

No

n/a

n/a

 

BI Web Services (created within Web Intelligence)

Yes, from SP2

Yes

Yes

Yes

 

MyInfoView

Yes, from SP2

Yes

n/a

n/a

 

License Keys

No

No

No

No

 

Authentication setting

No

No

No

No

 

Cryptographic Keys

No

No

No

No

 

Tenants

n/a

Yes, from BI 4.2 SP3

n/a

No

 
BI Variance (1) Web Intelligence parameter answer 'set'n/aNon/aNo
  1. Variance was added for Web Intelligence documents in BI 4.1 Support Pack 6.  For older product versions: Web Intelligence documents in the target with 'BI Variance' set upon them, will lose the 'BI Variant' association once the Web Intelligence document is prompted into it. This issue has been resolved KBA 2236210
Design Studio 1.x (Analysis Application) Bookmarks (Fragments, Portable Fragment/Smart Object)NoNo (1)NoNo
  1. Planned for a future release. KBA 2286101
Lumira Discovery Version 2 Bookmarks and Lumira Designer Bookmarks Version 2n/aYes  (1)n/a?
  1.  From: BI 4.1 SP08 Patch 09, BI 4.1 SP09 Patch 04, BI 4.2 SP02 Patch 11, BI 4.2 SP03 Patch 07

BI Platform Commentaryn/aYes (1)NoNo
  1. From BI 4.2 Support Pack 3 onwards
Lumira Bookmarksn/aYes     
System Resources (HTML White Lists)n/aYes 
   

List of objects supported within Public and Favorite Folders

All the objects below can be added into a Promotion Job and they can also be added into Version Management System.

Object

XI 3.1

BI 4

Comments

Web Intelligence documents (.WID)

Yes

Yes

 

Desktop Intelligence documents (.REP)

Yes

Yes from BI 4.1

 

Crystal Reports 2008 / 2011 / 2013

Yes

Yes *

* Direct to data connections require the login to the source system of the Promotion Job  to be 'the' Administrator account, unless KBA 1754247 is implemented "Add -systemUserGroupCUID to the source CMS process" 

Crystal Reports for Enterprise

n/a

Yes *

* Direct to data connections require the login to the source system of the Promotion Job  to be 'the' Administrator account, unless KBA 1754247 is implemented "Add -systemUserGroupCUID to the source CMS process"

Publications

Yes *

Yes *

* Warning: objects in target can be lost from the publication if not promoted at same time. See Note 1868513 (This issue was resolved with in BI4.1 SP2)

Hyperlinks

Yes

Yes

 

Agnostic documents (.doc, .xls, .txt, .zip, .anything!)

Yes

Yes

 

Dashboards / Xcelsius (.swf, .xlf)

Yes

Yes

 

BI workspace

n/a

Yes *

* Warning: Any content within the BI workspace must be promoted within the same Promotion Job as the BI workspace. However the content of the BI workspace is not identified as a dependency (product limitation)

InfoView

Yes

n/a

 

Information Space (Explorer)

Yes, from SP2

Yes

 

Exploration View Set

n/a

Yes

 

BusinessObjects Metadata Manager/Information Steward: Integrator Sources and Source Groups

Yes, from SP2

Yes

 

Analysis Office workbookn/a

Yes, from BI4.1

Prior to BI4.1 Analysis Office workbooks where agnostic Microsoft Excel documents.
Design Studio Applications ("Analysis Application")n/a

Yes, from BI4.1 SP 2 (1) (2)

  1. Dependent objects are not currently calculated in the dependency manager.
  2. Even if Lumira 2.x Server add-on (which can process Design Studio 1.x applications) has been installed, Design Studio 1.x applications requires that the Design Studio 1.x BI Platform Server add-on has been installed, on any server in the target cluster, sometime in its history. The target repository/cluster needs to know about the object type and just installing Lumira 2 Server add-on is not sufficient. See KBA 2529186 and this blog
Lumira Documents (when created with Lumira 1.x)n/aYes, from BI4.1 SP 6
  1. Though some limited support may be possible prior to this version.
  2. There are restrictions when promoting Lumira 1.x content into a Lumira 2.x server. See this blog
  3. Version Management of Lumira documents is not supported, however it works very well.
Lumira Documents (when created with Lumira Discovery/Designer 2.x) (1)n/aYes (1)
  1. From: BI 4.1 SP08 Patch 09, BI 4.1 SP09 Patch 04, BI 4.2 SP02 Patch 11, BI 4.2 SP03 Patch 08
  2. Version Management of Lumira documents is not supported, however it works very well.
Web Intelligence Shared Elementsn/aYes 
  • No labels

14 Comments

  1. Unknown User (nlh429x)

    Hi there,

    Are there going to be any plans/ considerations for being able to support Promotion Jobs Objects to be packaged as objects & transported to another system.

    i.e. We have pre-built jobs that contain reports and connections, we would like to transport this to our new environment when we upgrade.

    So far, the option only seem to be recreating the hundreds of jobs we've created when we upgrade.

    Thank you.

    1. Promotion Jobs themselves can not be included within another Promotion Job. They can be exported as a BIAR file, transported to another system and imported.

      There should never be a need to promote a Promotion Job within another Promotion Job. Promotion Jobs should be defined on the source (Development), checked-in to Version Management, then checked-out of Verison Management before being Promoted to Test (for validation) then Promoted again to Production.

      If you find you're recreating Promotion Jobs, then your methodology isn't quite right.

  2. Unknown User (b7ef9ek)

    We have an UNX universe that has a bunch of Data Security Profiles added to it. When the universe was imported to another environment via an LCMBIAR file, the security profiles were promoted too.
    Does this not contradict what this wiki says about packageability of Security Profiles in UNX?

    1. I've updated the Wiki since your post. Depends on the version you're using. BI4.0 SP4 does not promote Security Profiles. This was added into BI4.0 SP6.

       

  3.  

    What about Multitenancy objects ?

    1. Hello Denis, I'm not sure what you mean by "What about Multitenancy objects ?". The wiki correctly reflects on the support status for 'Tenants', but with such little information to go on I don't know if this is helpful or not. Should you mean an 'object' (like a universe or a report) that is associated/created or hosted within a Tenant then there's no difference for those objects to an object that isn't associated/created or hosted within a Tenant. Regards, Matthew

  4. Former Member

    Hi Matt,

    This is really helpful.

    I am on BI4 SP5 Patch 6, but can't see recurring jobs under manage dependencies. All I see is successful instances under that.

    Is it the patch level or am I missing something?

    We have CR and webi and I tried with both, but no go. If there is anything particular, please mention for others as well.

    Cheers

    1. Former Member

      Kindly Disregard.

      They were all corrupt reports. Surprisingly 6-7 of them which I checked.

      Its all fine.

  5. Former Member

    Excellent and useful article. On a related note, for those looking to learn everything they can about Promotion Management and Version Management in BI 4.1 (including little-known best practices such as using a dedicated Promotion Management environment), I found the following slides from Matthew Shaw to be enormously helpful as well:

    http://www.slideshare.net/SAPanalytics/webinar-10-bi-41-upgrade-ceg-promotion-and-version-management-best-practices

  6. Are there any plans to add the Data Services & Information Steward objects to this list, since they also use Promotion Management in the CMC?

    Would only need for BI 4x.

    1. Already added are "BusinessObjects Metadata Manager/Information Steward: Integrator Sources and Source Groups" under "List of objects supported within Public and Favorite Folders". Where you looking for something else? Perhaps it needs more detail?

      1. Matthew,
        Any movement on adding these information Steward & Data services objects to the Matrix?

        • Information Steward - Security (users and user groups)
        • Information Steward - Metadata Management
          • Metadata Management Integrator Sources
          • Metadata Management Source Groups
          • User-created utilities and scheduling information for Information Steward utilities
        • Information Steward - Data Insight
          • Profiling connections
          • Data Insight projects
        • Information Steward - Metapedia
          • Metapedia user security settings
        • Information Steward - Cleansing Package Builder
          • Published cleansing packages
          • Private cleansing packages

        For Data Services, there is probability only "Data Services - Security (users and user groups)" since most Data Services object promotion is done in the DSMC.

         

        Thanks

  7. Thanks Matthew, I guessed I missed that.

    Perhaps rename it as "Information Steward Metadata Manager: Integrator Sources and Source Groups"

    Maybe have 5 rows, a row for each area:

    • Information Steward - Security (users and user groups)

    • Information Steward - Metadata Management
      • Metadata Management Integrator Sources
      • Metadata Management Source Groups
      • User-created utilities and scheduling information for Information Steward utilities

    • Information Steward - Data Insight
      • Profiling connections
      • Data Insight projects

    • Information Steward - Metapedia
      • Metapedia user security settings
    • Information Steward - Cleansing Package Builder
      • Published cleansing packages
      • Private cleansing packages

    For Data Services, there is probability only "Data Services - Security (users and user groups)" since most Data Services object promotion is done in the DSMC.

    Thanks

    Jay

  8. Matthew great information!! Wonderful job on content and display.

    I came across this page because I'm trying to figure out why some objects are not getting included in replication via federation from one system to another.

    I'm not sure if it's appropriate in this document to align replication along with promotion management and version management, but I would love it as we get into the realm of using replication. I'm trying to figure out if this is a defect or limitations of replication.

    But not trying to create more work for you! (smile)