Publishing a Web service to a UDDI registry for deployment to the gateway

Why and when to perform this task

The gateway interacts with UDDI registries as described in UDDI registries - Web service directories that integrate with the Web services gateway. When you deploy a Web service to the gateway, you enable UDDI interaction by entering a UDDI reference, and (depending upon what you are trying to do) either or both of the following pieces of information:

You get these two keys from the UDDI registry. To help you understand what UDDI service keys and business keys are, and where you find them in a UDDI registry, this topic describes how to publish a Web service to a UDDI registry.

The following description of the UDDI publication process requires that you specify 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. The gateway makes no use of Technical model information because it only interacts with UDDI registries at the level of specific Web services.

The following task steps include specific navigation instructions. These instructions 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.

Steps for this task

  1. Specify a business:
    1. 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.
    2. 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.
  2. Add a technical model:
    1. Select Add a technical model on the Advanced Publish section of the Publish pane.
    2. Enter the name as specified for the target namespace of your binding (or interface) WSDL file, then add a description (if required).
    3. Add a category of Type unspsc and value wsdlSpec (the Key name field can be left blank).
    4. 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.

    5. Click Publish Technical Model.
  3. Add a service:
    1. Select Show owned entities on the Advanced Publish section of the Publish pane.
    2. Select Add a Service for your business.
    3. Enter the name as specified for the target service in your WSDL file, then add a description (if required).
    4. 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).
    5. 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.
    6. Click Publish Service.

Results

The UDDI registry assigns a service key to your service, and publishes the service.

Related tasks
Deploying Web services to the Web services gateway



Searchable topic ID:   twsg_admin_uddipub
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/twsg_admin_uddipub.html

Library | Support | Terms of Use | Feedback