This blog is part of the SAP BI Version Management series. My previous blog in this series was about need for SAP BI version management, Terminologies used, options available and VMS workflow. In this blog I will throw light on VMS architecture, installation and configuration.
SAP BI Version Management application is delivered as part of the platform and it supports the following software’s for versioning repository (LCM repository)
- Subversion – Delivered as the default option and bundled with SAP BI installer. No additional steps involved in configuration (most scenarios)
- Clearcase – Third party component that can be used as an alternative for subversion. Needs additional configuration
Subversion option will be covered in this blog as it is part of the default installation
Subversion software will be installed as part of the installation (if selected) and it will run as a service. Version Management tool within Business Objects will connect to this service and will store versions of objects added to VM in the VMS repository.
LCM Service (Life cycle Management Service) is responsible for handling version management requests. If Clearcase is used for versioning, LCM Clearcase service should be enabled along with core LCM services.
Scenario 1 – New Install
Installation of SAP BI Version Management System is fairly simple and straight forward. Since subversion is bundled with SAP BI installer it does not involve complex steps.
During installation process, while prompted for the selection of version control software select “Configure and Install Subversion” option
Next step is to select a password for the LCM user
When SAP BI platform installation is completed, subversion will be installed and Version Management System will be configured automatically.
Scenario 2 – Existing Installation
Adding subversion to an existing system is also relatively simple. Go to Control Panel -> Add or Remove Programs -> “Select SAP BI platform Installation” -> “Select Change/Remove” option. Once the installer loads, select “Modify” option and select “subversion” in the list
Complete the “Modify” process after selecting subversion. Subversion will be added to existing platform
Version Management configuration is simple. In a new install scenario, it is configured by default. While adding it to an existing installation, following should be validated
Check if “LCMSubversion” service is running. Or else start the service
Go to CMC -> Applications -> Version Management -> VMS Settings, ensure that the required information is in place.
Required information for subversion – Server Name-where subversion is running, Port used by service, LCM username, Password, Install path/repo location and Repo name.
Most cases this information is filled up by installer.
Validate the settings using “Test VMS” option – If it is reachable, then following message is displayed
In a clustered system, configuration part is little tricky. There will be multiple servers and the LCM Repository must be shared among all servers, otherwise, the checkouts won’t be consistent across systems and will result in in-consistent repository.
Once the VMS is installed and configured, Version Management can be accessed from CMC -> Manage -> Version Management.
Stay tuned for the next blog in this series where the actual VMS operations are discussed in detail with examples.
Got questions? Click here to get in touch.