Central Management Server ( CMS )

Card Puncher Data Processing


The aptly named Central Management Server (CMS) is the main server in the BO XI collection.

The CMS maintains a database of information about your BusinessObjects Enterprise system. This is known as the CMS database. All the platform services are managed and controlled by the CMS.

The CMS handles communication with the RDBMS tables that store the metadata about the BO XI objects. Any commands issued by the SDK to the servers are communicated via the CMS.

CMS is also known as :

  • In Application Foundation 6.x versions and earlier, BusinessObjects repository
  • Before the rebranding effort, the Crystal Management Server,
  • and before that as the Automated Process Scheduler (APS).

There are still a few active properties that are named for the old APS designation. One of these APS references is found in the ServerKind property of the Server class. The CMS ServerKind designation of the Central Management Server is still “aps”.

The CMS also manages :

  • the auditing database
  • all schedule and custom events.

The CMS can also maintain an optional auditing database of information about user actions, and files with the File Repository Servers.

File events alone are handled by the Event Server.

The CMS manages :

  • security and controls authentication of all users
  • as well as license management.

Because the Central Management Server is the principal server, it cannot be stopped from within the SAP BOBJ - Central Management Console (CMC). You must use the Central Configuration Manager.

In a production environment, it’s a good idea to disable all servers first so they can finish any pending requests before shutting them down, with the CMS being the last to close. If you’re working with a cluster, shutting down one CMS will shift the workload to the other active ones—a feature that allows maintenance without causing downtime.

The CMS also manages access to the system file store where the physical documents are managed.

CMS data includes information about :

  • users and groups,
  • security levels,
  • content,
  • services.
  • license.

Main tasks

This data allows the CMS to perform four main tasks:

  • Maintaining security

The CMS enforces the application of rights at both the folder and object level, and supports inheritance at the user and group level. It also supports aggregation through a flexible, group-user membership model. An integrated security system is available for customers who do not currently use an entitlement database, although BusinessObjects Enterprise is designed for integration with multiple concurrent third-party security systems, such as LDAP, Siteminder, or Microsoft Active Directory.

When a change is made to a user in the entitlement database, the change is then propogated to BusinessObjects Enterprise.

  • Managing objects

The CMS keeps track of the object location and maintains the folder hierarchy. InfoObjects are system metadata objects that contain contain index information, and the actual documents or objects are stored in a file store. The separation of the object definition (metadata) from the document allows for fast object processing as only the required information is retrieved from the system’s repository. The CMS also runs scheduled report jobs.

  • Managing servers

Server process are monitored by the CMS and allocates work to less busy processes. It will also add or remove service instances as work loads change or services become unavailable. The CMS handles load balancing and automated clustering to avoid bottlenecks and maximize hardware efficiency. In some multi-server environments, BusinessObjects Enterprise may not require a separate third-party load balancing system.

  • Managing auditing

User actions can be monitored and written to a central audit database. This information allows system administrators to better track and manage their BusinessObjects Enterprise deployment. The auditing functionality allows administrators to better understand which users accessed the enterprise system, which documents they interacted with, and the overall system metrics for system optimization. Usage data is collected from the system interactions recorded in the auditing database. A sample universe and sample auditing reports are also available to provide fast access to information such as the most accessed reports, peak system use times, and average user session times.

It is strongly recommended that you back up and audit the CMS system database frequently.

The CMS database should not be accessed directly. System information should only be retrieved using the calls that are provided in the BusinessObjects Enterprise software development kit (SDK).

Discover More
Bobj Pm Bubble Pie Char Analytics
BOBJ - Analytics

Analytics are templates into which you insert the data that you want to view in your . Some of the most commonly used analytics are: Gauges such as and traffic lights A Navigation List or Web Page...
Card Puncher Data Processing
BOBJ - Joins (Home)

The Joins in BOBJ. You have several approaches to creating joins in : Tracing joins manually in the schema (Drag and drop) Defining join properties directly ( Menu Select Insert > Join ) ....
Bobj Pm Bubble Pie Char Analytics
Deploy Xcelsius template-based analytics with Analytic Template Publisher

You use the “Analytic Template Publisher” to publish your Crystal Xcelsius templates to the BusinessObjects Enterprise . This allows you to use them in to create new . The Data Exploration analytics,...
Bobj Pm Architecture Overview
Deploy the Performance Manager repository

A Dashboard and Analytics deployment includes two repositories: The database – stores user security information, documents, dashboards, analytics, performance models, schedules and the semantic layer...
Card Puncher Data Processing
Event Server

The manages file-based events. When you set up a file-based event within BusinessObjects Enterprise, the monitors the directory that you specified. When the appropriate file appears in the monitored...
Card Puncher Data Processing
Job servers

A job server processes scheduled actions on objects at the request of the (CMS). When you add a job server to the BusinessObjects Enterprise system, you can configure the job server to: Process reporting...
Card Puncher Data Processing
Multi-Dimensional Analysis Server (MDAS)

The registers itself with the (CMS), and its services are available for consumption by other servers or client applications that communicate via the BusinessObjects Enterprise framework. The MDAS provides...
Card Puncher Data Processing
Report Conversion Tool

The converts reports to the format and publishes the converted reports to the . It retrieves reports from the CMS, in the Public, Favorites, or Inbox folders. Once converted, you can publish to the...
Card Puncher Data Processing
Report and Processing servers

The processing tier includes the following servers: Web Intelligence Report Server Desktop Intelligence Report Server (RAS) Crystal Reports Processing Server Web Intelligence Processing Server...

Share this page:
Follow us:
Task Runner