Creating a Central Repository (SAP Library

Creating a Central Repository

Use

A central CCMS System Component Repository (SCR) contains data from more than one system. Setting up a central repository has the advantages that a single repository can display data from multiple SAP R/3 Systems and other components.

To create a central repository, you must explicitly register the other CCMS System Repositories with the central repository. A central repository is not automatically created. By registering a system with a central repository, the two repositories are combined. This means that:

Data for the registering system is added to the central repository. For example, information about the clients and RFC destinations of the registering system is added to the central system.
In the case of a conflict (the different repositories each have their own version of certain data), the data from the repository of the system to which the data refers is used. If the contradictory data refers to another system, the data from the central repository is used.
No data is added to the repository of the registering system; only an object exchange takes place. The display options in the central repository are used instead of those in the registering system.

Technically, this means the combination of repositories; that the repositories share a namespace for the objects contained within them.

You should create a central repository if one of the following applies to you:

You want to use the CCMS Repository Browser to access data from the remote repository directly, to obtain information about the SAP R/3 Systems in your IT landscape. For example, you can display the configuration properties for clients of application servers or data for the versions of systems that have registered their repositories with the central system.
An SAP component that you are using requires a central repository. A requirement of this type is documented in the installation or Customizing guidelines for the component.

Some components that use the SCR deal with their own information requirements themselves without the need to combine the repositories. You only need to combine repositories if this is noted as a requirement in the documentation of the component.

Prerequisites

You must decide which system is to be the central system for the SCR. Note that SCRs with SAP Basis 4.6X cannot be subordinate to an SCR with SAP Web Application Server 6.X. In general, the central system should either be the central monitoring system or the system on which the Solution Manager is running.

The selection of the central system should be carefully considered, as to change the central system you must delete the contents of the central and the registered subordinate repositories and then fill them again.

Decide which systems should register with your repository in the central system.

You must Create the CSMREG User in the central system. This user is used by the registered systems for RFC logons, with which the system transfer the data to the central repository.

Define Central Repository

Log on to the system that is to contain the central repository.

Choose CCMS ® Configuration ® Alert Monitor, or call transaction RZ21.

Choose Technical Infrastructure ® System Repository ® Set Repository Role.

The system displays the Set Repository Role in Central System Administration screen. Choose Central Repository.

It is not mandatory to define a central repository. If you define subordinate repositories, the repository of the system that you specify as the central system is defined as the central repository. The above procedure is therefore presented here only for completeness.

Define Subordinate Repository

Log on to the system that is to be registered with the central repository. To do this, you require administrator authorizations (profiles S_RZL_ADM, S_RFC, and S_BTCH_JOB with release authorization).

Choose CCMS ® Configuration ® Alert Monitor, or call transaction RZ21.

Choose Technical Infrastructure ® System Repository ® Set Repository Role.

The system displays the Set Repository Role in Central System Administration screen. Choose Subordinate Repository and enter the name of the central system. Enter administration information for the system, if desired. You can save this information and the system role setting separately.

Choose Goto ® Maintain RFC Destinations.

On the next screen, enter the data required to create an RFC destination through which the subordinate repository can reach the central system and to create destinations in the central system for the registering systems. The destinations are created automatically for you with the following default names:

RFC Destination	Created in System
CCMS_CSM_CEN_DEST_<central system>	Registering system
CCMS_CSM_MNT_DEST_<registering system>	Central system
CCMS_CSM_QRY_DEST_<registering system>	Central system

The destination CEN_DEST in the registering system has the fixed user CSMREG and requires a password. This destination represents a security risk if the authorizations of CSMREG are not restricted (see Creating the CSMREG User).

We recommend that you set up the registering system so that it automatically regularly updates the central repository. To do this, the destination CEN_DEST must be active and usable. If there are security considerations, you can, however, deactivate the destination by deleting the password. This also deactivates the automatic updates of the central system repository. You must then update the central system repository manually (see Update Central Repository).

The destination MNT_DEST in the central system is a default destination for access to the registered system using dialog users. QRY_DEST is intended for automatic access by the central repository to the subordinated repository for data queries. Both destinations are saved without user ID or password and therefore do not represent a security risk. QRY_DEST is not yet used; it is reserved for later use.

Choose ENTER () to return to the main screen for registration.

Choose ENTER (), to perform the registration.

Result

The registration procedure creates the required local RFC destination and schedules the job CCMS_REPOSITORY_RECONCILIATION, which runs under your authorization. This job compares the data in the repositories of the subordinate systems and the central system and combines the repositories. The registration is complete when the job finishes. As long as it is not running on an extremely large system, the runtime for this job is less than five minutes.

After the job is complete, the data from the subordinate system is available to you in the central system, for example using the Repository Browser.

The job is only scheduled for execution once. You can, however, manually schedule it to run regularly using transaction SM37 (Simple Job Selection). You should schedule a daily or weekly repetition of the job, depending on how often you make system configuration changes in the subordinate systems (new clients, new application servers, new RFC destinations).

Note that the SCR does not allow you to change the roles of the central repository or of the registered subordinate repositories. If you want to change the central repository or if a subordinate system is to report its data to a different central repository, you must delete the central repository and all of the repositories registered there.