Use
The
system repository in each system is automatically updated each time that the central server is restarted or that the monitoring segment of the central server is reset (the CCMS monitoring architecture, Transaction RZ21).If you wish, you can explicitly update the local repository. This is sensible if you have just completed configuration changes on the system (new clients, RFC destinations, servers, and the like) and wish to have the changes immediately reflected in the repository. It is also sensible before registering the repository with a central repository if the local system has not been restarted recently.
You can also use this procedure to fill the repository the first time, if the automatic auto-discovery has not filled the repository.
Procedure
The transaction checks to see if there is currently a suitable background job in the state scheduled, released, or running. If there is not, the transaction schedules a job to update the local repository, after first asking you for job start conditions. The job is called CCMS_LOAD_REPOSITORY_LOCDATA. Depending upon the size of your system, such a job runs between 10 and 20 minutes, and except in very large or very busy systems, never more than 30 minutes. The job needs to store data in the database, so avoid this action during periods of peak user activity.
The repository is updated when the job has finished. The transaction does not wait for this event.
See also:
Updating the Central Repository