The Central Management Server (CMS) Repository

Posted by Manikandan Elumalai
Comments (1)
December 17th, 2010

Introduction

The content of the Business Objects Enterprise (BOE) system consists of the physical files and the metadata information about the physical files.

For a Crystal Report, the physical file as well as the metadata about the file should exist in the BOE system. The Crystal report is stored as a file on File Repository Server (FRS) with an extension of .rpt . The Metadata information such as report name, type, report ID, path, etc is stored as an InfoObject in the CMS Repository.

I will discuss about the CMS repository in this article.

The CMS Repository Database Tables

The CMS metadata is physically stored on a database as InfoObjects.   There are six tables, the purpose of which is given below.

Sno Physical Table Name Purpose
1 CMS_VersionInfo Contains the current version of BOE.
2 CMS_InfoObjects6 Each row in this table stores a single InfoObject.  This is the main table in the repository.
3 CMS_Aliases6 Maps the user alias(es) to the corresponding user ID. For example, a user may have both a Win NT alias and an LDAP alias. Regardless of the number of aliases a user may have, in the BI Platform each user has only one user ID. The map is stored in a separate table to enable fast logins.
4 CMS_IdNumbers6 The CMS uses this table to generate unique Object IDs and Type IDs. It has only two rows: an Object ID row and a Type ID row. The CMSs in a cluster use this table when generating unique ID numbers.
5 CMS_Relationships6 Relationship tables are used to store the relations between InfoObjects. Each row in the table stores one edge in the relation. For example, the relation between a Web Intelligence document and a Universe would be stored in a row in the WebI – Universe Relation table. Each relationship table has these columns: Parent Object ID, Child Object ID, Relationship InfoObject ID, member, version, ordinal, data.
6 CMS_LOCKS6 This is an auxiliary table of CMS_RELATIONS6.

The CMS repository tables cannot be queried directly. Query builder is the tool to be used to retrieve Business Objects metadata information using the virtual tables such as ci_systemobjects, ci_infoobjects and ci_appobjects.

In the forthcoming posts, I will discuss on query builder and file repository server.

Comments (1)

CMS Application - March 24th, 2011

Awesome post! It really helped me a lot! Thanks for sharing it.

Comments are closed.