Administration of WebSphere Service Registry and Repository

Administration refers to the tasks that you carry out to manage your WSRR configuration.

The administration of WSRR is described in detail in the following subsections:

Overview of Administration
You can administer WSRR by using either the web UI Configuration perspective, WSRR Studio, or the JMX interface.
Service registry configurations
Service Registry components use configuration documents stored in the registry to determine their runtime behavior. The management interfaces allow administrators to retrieve, create, update, and remove configurations to meet their business requirements.
Security considerations for administration
When WebSphere® Application Server global security is enabled, you can invoke the operations of the ServiceRegistryRepository MBean only if you are a user in a WebSphere Application Server administrative role.
Updating WSRR system user and password settings
You might want to periodically change settings for WSRR system user IDs and passwords.
Managing WSRR with the web UI
You can manage your WSRR configuration with the web UI, by using the Configuration perspective.
Managing WSRR with wsadmin
WSRR administrative operations are performed by invoking the WSRR MBean by using standard wsadmin commands. You must know the type of the WSRR MBean, and the cell, node and server for the WSRR you want to configure.
Managing WSRR with a Java JMX client
WebSphere Service Registry and Repository (WSRR) can be managed programmatically by any remote Java™ client. A client proxy class in ServiceRegistryClient.jar allows you to easily connect to the WSRR MBean and invoke operations by invoking corresponding methods on the proxy, without your classes needing to know about JMX classes or the WSRR MBean.
Managing WSRR with the command line interface
Interactive and scripted administration of WSRR is possible with the Jython-based command line interface. The command line interface provides full support for all the WSRR programmatic APIs, including all administrative operations. It can be used from a stand-alone Jython or Jacl interpreter, or it can be run inside wsadmin and used with the facilities available there. Several example scripts show you how to perform governance tasks such as promoting entities from one WSRR to another, or transitioning entities through different lifecycle states.
Access control policy administration
Fine-grained access control to WSRR artifacts is applied if WebSphere global security is enabled. The WSRR authorization component will initially try to find a policy in the WSRR configuration files. If successful it will load and use that policy. If no policy is found a default policy is generated at runtime and stored in WSRR for use when the application starts next.
Governance lifecycle administration
You can manage lifecycles by using WSRR Studio, the web UI, or administration scripts.
Configuration profile administration
Back up entire sets of WSRR configurations as a configuration profile. These saved profiles can be applied to other WSRR installations. Configuration profiles are a convenient way to apply pre-configured access control, UI customization, governance life cycles and other configurations in one operation.
Backup and restore
To perform a complete backup and restore of your WSRR configuration information, ontology data, and entity data, you must back up and restore the WSRR database, by using the standard procedures for your database type.
Import and export
WebSphere Service Registry and Repository (WSRR) provides a facility for exporting collections of entities, with their associated metadata, to a compressed file archive, and importing that file archive back into another WSRR instance. Both instances of WSRR must be at the same release if you want to use this facility.
Administration scripts (wsadmin)
A number of wsadmin scripts are provided for common administration functions. These can be used as is, or modified to suit specific environments.
Read-only mode
WSRR can be placed in read-only mode; the read-only protection applies to objects in WSRR, and their metadata. It does not apply to configuration items or profile actions.