Replications

Learn how replication provides the ability to federate with third-party UDDI-compliant registries, extending the governance capabilities of the Workbench to a distributed development organization.

Table of Contents

About Replications

Replication provides the ability to federate with third-party UDDI-compliant registries, thereby extending the governance capabilities of the Workbench to a distributed development organization. Services defined in external registries are pulled into the Workbench and made available to users of the Policy Manager Management Console in the same way as other physical services.

To make use of the Replication feature, the third-party registry must support the UDDI v3 standard, including Subscriptions. Steps:

  • First, define a subscription in the third-party registry to define the subset of services that must be replicated with the Workbench.
  • Once defined, the subscription will be assigned a UDDI key of the form: uddi:665e237e-b4c3-11dc-a5b9-96cca7393881.
  • The Replication can then be configured in the Workbench using the UDDI key and a set of remote credentials acceptable to the third-party registry.

To view the Replications Summary page, go to Configure > Registry and then click the Replications tab.

Add Replications

  1. Go to Configure > Registry.
  2. Click the Replications tab.

    The Replication Summary page is displayed, showing a list of registry subscriptions current defined in Policy Manager.

  3. Click Add Replications.

    The Add Replication page is displayed.

  4. Enter the Properties of the remote system required to create a successful connection and replication relationship:
    • Name—A name for the replication. It should be descriptive of the nature of the replication in some way.
    • Subscription Key—The UDDI key for the subscription created in the remote system. The subscription is the saved search that is used to drive the set of services and other information that is replicated across to the local system.
    • Security QName—The Local System QName for the remote system's UDDI v3.0 Security API. In other words, the remote system's UDDI v3.0 Security API must be registered in the local system and the associated unique QName must be provided.
    • Username & Password—The username and password used to connect to the remote system. This username must have sufficient rights to use the UDDI v3.0 Inquiry and Subscription APIs and must have visibility of the scope of results that need to be replicated into the local system.
    • Subscription QName—The Local System QName for the remote system's UDDI v3.0 Subscription API. In other words, the remote system's UDDI v3.0 Subscription API must be registered in the local system, and the associated unique QName must be provided.
    • Inquiry QName—The Local System QName for the remote system's UDDI v3.0 Inquiry API. In other words, the remote system's UDDI v3.0 Inquiry API must be registered in the local system and the associated unique QName must be provided.
    • Polling Interval—The interval at which the local system will poll the remote system for new services and other information that needs to be replicated. The format of this interval follows the xsd:duration syntax (PnYnMnDTnHnMnS).
  5. Enter Local Username & Password used by the replication process to replicate information into the local system. This credential must have sufficient rights to use the UDDI v3.0 Publish API and must have create, update, and delete permissions within the scope of the replicated results.
  6. Click Apply.

Modify Replications

  1. Go to Configure > Registry.
  2. Click the Replications tab.

    The Replication Summary page is displayed, showing a list of registry subscriptions current defined in Policy Manager.

  3. Select the line item for the replication you want to update.
  4. Click Modify Replication. The Modify Replication page is displayed.
  5. Follow steps #4 through #6 of Add Replications above.

Delete Replications

  1. Go to Configure > Registry.
  2. Click the Replications tab.

    The Replication Summary page is displayed, showing a list of registry subscriptions current defined in Policy Manager.

  3. Select the line item for the replication you want to delete.
  4. Click Delete Replication.
  5. At the confirmation message, click OK.