WSDL  Locate

This describes how to publish a WSDL file to BEA AquaLogic Service Registry. The implementation reflects the OASIS UDDI technical note Using WSDL in a UDDI Registry, Version 2.0. As shown in Figure 1, the technical note suggests a mapping between WSDL and UDDI.

Figure 1. WSDL TO UDDI

WSDL TO UDDI

WSDL PortTypes  Locate

As shown in Table 1, “WSDL portType:UDDI Mapping”, each WSDL portType maps to a tModel having the the same name as the local name of the portType in the WSDL specification. The overviewURL of the tModel becomes the URL of the WSDL specification. The tModel contains a categoryBag with a keyedReference for the type of WSDL artifact and the namespace of the WSDL definitions element containing the portType, as follows:

  • The type is categorized as portType.

  • The namespace is categorized as the WSDL binding namespace.

Table 1. WSDL portType:UDDI Mapping

WSDLUDDI
portType tModel (categorized as portType)
Namespace of portType keyedReference in categoryBag
Local name of portTypetModel name
WSDL locationoverviewURL

WSDL Bindings  Locate

In similar fashion, as summarized in Table 2, “wsdl binding:UDDI mapping”, WSDL bindings are mapped to tModels created for each binding, with name of the tModel gathered from the WSDL binding local name and the overviewURL again being the URL of the WSDL specification. Again, the tModel contains a categoryBag, this time with the following keyedReferences:

  • The type is categorized as binding.

  • The namespace is categorized as the WSDL binding namespace.

  • A portType category on the binding is used to refer to the portType tModel that was created for the WSDL portType (as described above).

  • The protocol and transport categories are set to the same attributes as described in the WSDL binding, such as SOAP and HTTP, respectively.

Table 2. wsdl binding:UDDI mapping

WSDLUDDI
Binding tModel (categorized as binding and wsdlSpec)
Namespace of binding keyedReference in categoryBag
Local name of bindingtModel name
WSDL locationoverviewURL
portType bindingkeyedReference in categoryBag
ProtocolkeyedReference in categoryBag
TransportkeyedReference in categoryBag

WSDL Service  Locate

WSDL services are represented as UDDI businessServices. The name is a human readable name. The tModel again contains a categoryBag which this time contains the following keyedReferences:

  • The type is categorized as service

  • The namespace is again categorized as the WSDL binding namespace.

  • The local name is categorized as the local name of the service.

The businessService also contains a bindingTemplate:

  • The access type is categorized as the access point of the service.

  • The portType is categorized as the tModel of the portType.

  • The binding is categorized as the tModel of the binding information.

  • The local name is categorized as the local name of the port.

Table 3. wsdl service:UDDI mapping

WSDLUDDI
Service businessService (categorized as service)
Namespace of servicekeyedReference in categoryBag
Local name of servicekeyedReference in categoryBag; optionally used name of service

Use Cases  Locate

BEA AquaLogic Service Registry supports the following use cases:

  • Publishing a WSDL file You can also specify how artifacts of the WSDL file will be mapped to the existing UDDI structures.

  • Search for a WSDL You can search for the WSDL file by WSDL location (URI).

  • Unpublish and republish the WSDL You can unpublish and republish the WSDL

For more information, also see: