Configuring and customizing
You can configure and customize the features of IBM® WebSphere® Service Registry and Repository (WSRR) after installation.
Note: For information about configuring and customizing
WSRR by using the WSRR Studio application, see the WebSphere Service
Registry and Repository Studio documentation.
- Customizing and configuring the dashboard
The dashboard interface to WSRR can be configured and customized to meet your requirements. - Configuration profiles
A WSRR configuration profile contains a complete set of WSRR configuration files. Configuration profiles are used for backup, restore and management of entire sets of WSRR configuration. - Configuring access control
WebSphere Service Registry and Repository (WSRR) makes use of role based access control for J2EE roles and for access control policies at a fine grained level. Both these depend on defining roles based on principals drawn from a user registry such as LDAP or the underlying operating system. - Configuring classification systems
Classification classes are used to organize and find artifacts in WSRR. WSRR allows you to create and modify classification systems that contain these classes. - Configuring business models
You can load a business model system into WSRR by using the Configuration perspective. You can also export an existing business model system to another location, or delete it. - Configuring templates
Templates are now deprecated. The preferred method is to create business models based on OWL rather than templates based on XML schema. Schema-based templates will still operate if required. - Configuring the governance lifecycle
This topic describes how to configure the governance lifecycle and set up WSRR to support governance. - Configuring the WebSphere MQ integration feature
The WebSphere MQ Integration feature extends the existing WSDL shredding capabilities of WebSphere Service Registry and Repository (WSRR) to provide WebSphere MQ WSDL parsing. This feature is provided in the governance enablement profile. - Configuring the WSRR provided plug-ins
Some of the WSRR provided plug-ins are required for correct WSRR behavior, and some are optional. All are installed by default. - Promotion
Using the promotion feature, you can manage content, relating to multiple deployment environments, in a central WSRR instance and have subsets of that content copied automatically to environment-specific WSRR instances in response to lifecycle transitions. - Text Search
Text search provides an enhanced search facility. Use text search to search metadata and document content in WSRR. - Scheduler framework
The scheduler framework is an EJB component that provides the ability to configure different types of scheduled tasks. The tasks are controlled by scheduler configuration XML files. - Service discovery
The service discovery mechanism automatically searches a target application environment for services and then loads the corresponding WSDL documents into WSRR. - UDDI synchronization
The UDDI synchronization feature in WSRR provides a means of mapping entities in a WSRR repository to corresponding entities in one or more UDDI V3.0.2 registries (your UDDI registries must support UDDI V3.0.2). - Named queries
You can define named queries, and then call these queries from any of the WSRR APIs. - Policy analytics
The policy analytics feature stores event data relating to the enforcement of policies that have been defined in the governance policy validator. You can then view this data graphically, by using the dashboard. You can, for example, see the percentage policy pass and failure rates over a specified period. - Atom plug-in framework
You can use the WSRR Atom plug-in framework to deploy Atom Publishing Protocol (APP) API implementations to WSRR. Then, WSRR will return Atom feeds in response to appropriate HTTP requests. - Subscription notifier
You use a subscription notifier to send a notification message automatically when a user operation takes place in relation to a WSRR object, Saved Search, or Named Query; for example, loading a WSDL document, transitioning a business service to a new lifecycle state. You can also specify conditions to filter the objects for which notification messages are sent; for example, all version 1.0 entities that are classified as being in the "Created" state. - Policy sets
A policy set is defined as a collection of assertions about how services are defined, which can be used to simplify security configurations. - Developing a custom action
You can develop a custom action, and configure it to be displayed in the web UI in several different ways: as a button, a link on a detail view, a menu bar item, an item in the navigation tree, or as a directory entry on the Home page. When a user clicks the action, the results are displayed in the web UI. - Configuring Tivoli Access Manager WebSEAL and WSRR
If you are using Tivoli® Access Manager WebSEAL with WSRR you must create transparent path junctions for the context roots of the components that you are using. - Configuring the web UI
The web user interface for WebSphere Service Registry and Repository (WSRR) is displayed in a screen divided into four areas.
Related information: