When you configure an inbound or outbound service, you enable UDDI
interaction by associating the service with a UDDI reference, and (depending
upon what you are trying to do) either or both of the following pieces of
information: The business key that identifies the UDDI business
category under which you want your service to appear in the UDDI registry,
and the service-specific part of the service key that the UDDI
registry assigns to your service. To help you understand what UDDI business
keys and service keys are, and where you find them in a UDDI registry, here
is a description of how to publish a Web service to a UDDI registry.
About this task
Service integration technologies interact with UDDI registries
as described in
UDDI registries - Web service directories that can be referenced by bus-enabled Web services. When you publish
a Web service to a UDDI registry, you:
- Specify the type of business that your Web service supports. This usually
means choosing an existing business type from a list, but you can also create
a new business type. For each type of business there is an associated business
key. Service integration bus Web services use this key, in combination with
the service key, to find the Web service in the registry.
- Add a Technical model. Technical models are generic categories. Using
these models, a UDDI registry user can search for a type of service, rather
than needing to know the access details for a specific service. Bus-enabled
Web services makes no use of Technical model information because it only interacts
with UDDI registries at the level of specific Web services.
- Add the Web service. The UDDI registry assigns a service key to your service,
and publishes the service. Bus-enabled Web services use this key, in combination
with the business key, to find the Web service in the registry.
The following steps describe how you publish a Web service to
the IBM
WebSphere UDDI Registry.
If you are working with a different UDDI registry, then the specific navigation
is different but the underlying principles are the same.
Procedure
- Specify a business:
- To get a list of valid business keys, look up businesses in
the UDDI registry. Here is an example of a UDDI business key: 08A536DC-3482-4E18-BFEC-2E2A23630526.
- If you do not find an appropriate existing business in the UDDI
registry, then use the Add a business option on the Advanced Publish section
of the Publish pane to add a new one.
- Add a technical model:
- Select Add a technical model on the Advanced Publish section
of the Publish pane.
- Enter the name as specified for the target namespace of your
binding (or interface) WSDL file, then add a description (if required).
- Add a category of Type unspsc and value wsdlSpec (the
Key name field can be left blank).
- Add an overview URL specifying the Web address for your binding
WSDL file, then add a description (if required).
Note: The binding
and the service definition for your Web service might be held in separate
WSDL files, therefore be careful to type the Web address of the WSDL file
that defines the binding.
- Click Publish Technical Model.
- Add a service:
- Select Show owned entities on the Advanced Publish section
of the Publish pane.
- Select Add a Service for your business.
- Enter the name as specified for the target service in your WSDL
file, then add a description (if required).
- For the Access point verify that the correct Web address
type is selected (for example http for an HTTP access point),
then enter the value of the soap:address location (or its
equivalent) from your service definition WSDL file (for example http://yourhost:80/SimpleTest/servlet/rpcrouter).
- For the Technical model select Add, then find
the required Technical model by entering a suitable prefix and selecting Find
technical models, then enable the check box for the required Technical
model and click Update.
- Click Publish Service.
Results
The UDDI registry assigns a service key to your service,
and publishes the service.
What to do next
After the service has been published you can get the service
key from the target UDDI registry.
Here is an example of a full UDDI service key:
uddi:blade108node01cell:blade108node01:server1:default:6e3d106e-5394-44e3-be17-aca728ac1791
The service-specific part of this key is the final part:
6e3d106e-5394-44e3-be17-aca728ac1791.