Version Control for BUSINESS OBJECTS repository

[Former Member]

Hi,

Do we have any version control for business objects repository?

Thanks

[Former Member]

Hi

I am hoping someone can answer my Version Control queries. The LCM document is limited in its detail on VM.

I am currently testing the BO LCM 3.1 and while it appears very easy to use especially for promotion, the Version Control Manager seems to be lacking in controls and a clear promotion path from dev to test to uat to prod.

We have set up 2 identical environments for UAT and PROD.

And using the Version Control part of LCM creating version control for a universe.

Logged into VM in UAT

We have selected a universe

Added it to VM

Made a change to the universe in Designer

Exported it

Then Checked it in

Can now see 2 versions in the history and the VMS Version. All good

I then click on swap system and log into PROD

The VM history is also there in PROD

I have a number of concerns and questions and can't seem to find the solution to them anywhere.

1. VM seems to be lacking a controlled process from all the environments. Basically we want to deploy following this path;

Dev - Test - UAT - PROD

There does not seem to be any controls or security which would stop you from GET VERSION from the DEV environment and putting that straight into PROD. Obviously we would not want that to happen.

We would only want to GET VERSION from UAT

Similarly for UAT We would only want to GET VERSION from TEST

And for TEST We would only want to GET VERSION from DEV.

Granted, we currently only have 2 identical environments.

But Is there controls that would stop you when in PROD from getting versions from any other system other than UAT?

Also is there any reason why no promotion is required when using VM.

This seems to negate the Promotion Function of the LCM

Any advise would be greatly appreciated with this.

Many thanks

Eilish

[Maheshwar_Singh]

Hi Eilish,

When you version an object in LCM using the Version Management workflow, the versioned object is system specific. A versioned object checked in from the DEV system cannot be checked out on a PROD system.

Version management workflow is of use to a developer who would want to version an object before he modifies the report. The user can have multiple versions of the same object in the VMS repository.

Promotion workflow is to copy contnets from DEV > TEST or from TEST > PROD.

You can stop users to promote from DEV > PROD by using the different rights available.

- Maheshwar

[Former Member]

Lifecycle Manager? It's not strictly version control but can be used for controlling the promotion of content.

https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/90433257-bfa8-2b10-5e8c-e6d9764622e4

[dennis_scoville4]

Lifecycle Management (LCM), which is part of SAP Business Objects Enterprise suite of tools, doesn't currently handle version control, or any other kind of object management, for anything related to Data Services (Data Integroator / Data Quality). In the several times that I've asked SAP Business Objects about this, it's in the development pipeline, but there was some inconsistency as to whether it would be in a future relase of LCM or as part of Enhanced Change and Transport System (CTS+) in NetWeaver.

LCM will act as a version management tool for, but not limited to:

Crystal Reports

Web Intelligence

Web Intelligence Full Client (formerly Desk Intelligence)

Xcelsius

Office, PDF, Text Files

Users and User Groups

Folders

Universes

To date, there really isn't anything for version control on repositories but as I stated further, stay tuned.

[Former Member]

Hi James,

This is a helpfull document.

Thank You.

[Henry_Banks]

that document is extremely old, and you should seek out the newer ones!  for example:

http://scn.sap.com/docs/DOC-28446

http://wiki.sdn.sap.com/wiki/display/BOBJ/Object+support+for+Promotion+and+Version+Management