Many customers implement UDDI as either a stand-alone service directory or in conjunction with a service registry. Layer 7 SecureSpan XML Gateways are designed to integrate natively into a variety of registries like HP Systinet, Software AG Centrasite, Oracle Service Registry and IBM WSRR. In some instances this can be implemented using pre-canned API level integrations. However with all there is a simple out-of-the-box option to leverage UDDI directly. This tutorial shows the set up for HP’s UDDI directory using their open Governance Interoperability Framework (GIF).
Step 1: Publish a service
Publish a SOAP Web Service in the Layer 7 SOA Gateway by selecting a WSDL from Systinet UDDI using the Layer 7 UDDI wizards.
Following the publishing of the SOAP Web Service the Layer 7 SOA Gateway has a record of which BusinessSerivce and original bindingTemplate (endpoint) the service was published from. This can be seen via the Published Services properties dialog on the UDDI tab inside the Policy Manager.
Note: The check box 'WSDL under UDDI control' is not checked. This means that we can publish to and update this business service.
Step 2: Publish a Systinet UDDI GIF endpoint
The option to publish a GIF endpoint is available as the Layer 7 XML Gateway Policy Manager because the Gateway knows the service was published from a BusinessSerivce in a Systinet UDDI.
GIF transparently replaces the functional (original) bindingTemplate in UDDI with a proxy bindingTemplate. A choice of HTTP or HTTPS endpoint must be selected as GIF requires a single proxy bindingTemplate.
Following this operation Systinet will be updated and the proxy bindingTemplate will contain the bindingKey of the functional endpoint. All required meta data will be added to the proxy and functional endpoints. Any meta data added via the 'Manage Meta Data' dialog will also be added to the proxy bindingTemplate. In addition any meta data associated with the functional bindingTemplate will also be associated with the proxy bindingTemplate. Any searches for the functional endpoint will now also return the proxy.
Step 3 – Update
While the GIF endpoint has been published the Layer 7 SOA Gateway will keep the bindingTemplate up to date inside of Systinet. If the Layer 7 SOA Gateway is reconfigured to listen on a different port for example, then the gateway's endpoint in UDDI will be updated to contain the correct URL.
Step 4 – Unpublish
When it is time to no longer proxy the functional endpoint this can be done by selecting “Don't Publish” inside the Layer 7 SOA Gateway Policy Manager like so
This will remove the proxy bindingTemplate and any GIF meta data added to the functional bindingTemplate. In addition the GIF specific meta data added to the functional bindingTemplate will also be removed.