List and managing gateway-deployed Web services

Use this task to list the Web services that are deployed to the Web services gateway, and modify their deployment details.

 

There is no point in deploying multiple target services to the same gateway service unless you have a filter implementation that is capable of selecting the required target service. To list the Web services that are currently deployed to the Web services gateway, and view and modify their deployment details (including adding or removing multiple target services) complete the following steps:

 

  1. Display the Web services gateway administrative user interface.

  2. In the navigation pane, click the following link:

    Services

    • List
    The main pane is updated with a list of all the Web services that are deployed to the Web services gateway.

  3. Click the name of a Web service in the list. A form is displayed through which you can view and modify the current deployment details for this Web service, and add or remove multiple target services.

  4. At the level of the gateway service itself (in the Gateway Service Properties section) you can change the following settings. When you have finished making changes, click Apply Changes.

    1. Authorization Policy - Control access to this service. Use this check box to enable or disable operation-level authorization for this gateway service.

    2. Audit Policy - Log requests to this service.

      The Audit policy indicates whether the MessageWarehouse object, if present, should be used to log requests and responses for this service. If you have a Message Warehouse implementation, use this check box to enable or disable logging of requests and responses for this Web service.

    3. In this release of the gateway, the Annotation URL field is not used.

    4. If you want to publish the service to one or more UDDI registries (selected in the UDDI References section below), enter the UDDI business key in the field provided under UDDI Publication Properties. This key identifies the business category under which you want your service to appear in UDDI. To get a list of valid business keys, look up businesses in a UDDI registry. This is an example of a UDDI business key: 08A536DC-3482-4E18-BFEC-2E2A23630526 . For more information about UDDI business keys see Publishing a Web service to a UDDI registry for deployment to the gateway.

    5. If you want to enable or disable Service Security, select or clear the Enable service security check box. If you choose to enable service security, then use the Edit service security configuration option to configure secure communication for this gateway service between the service requester (the client) and the gateway. For more information see Editing the service security configuration.

  5. In the Target Services section you can add, modify or remove services from a list of target services for this single gateway service. Every service on this list provides exactly the same service, and they are presented by the gateway to the service requesters as a single gateway service. To add a new target service, complete the following steps:

    1. WSDL Location. Type the location of the "internal" WSDL file that describes the Web service to be deployed. The WSDL file is either located at a URL, or through a UDDI registry.

      If the WSDL location is a URL, type the URL (if the binding and service definition for this Web service are held in separate WSDL files, then type the URL of the WSDL file that defines the binding).

      If the WSDL is located through a UDDI registry, type uddiReference,serviceKey where

      • uddiReference is the reference name by which a currently-deployed UDDI reference is known within the gateway (and by which it is listed using the UDDI References -> List option)

      • serviceKey is the service key that the UDDI registry has assigned to the service. This is an example of a UDDI service key: 34280367-0ECF-46CE-B804-14C21D6D0FB1 . For more information about UDDI service keys see Publishing a Web service to a UDDI registry for deployment to the gateway.

      Note:

      • When the Web services gateway deploys the Web service, it generates a matching "external" WSDL file that it makes available to gateway users. This "external" WSDL file also describes the service, but is located at a new URL and is generated and maintained by the Web services gateway itself.

      • If the Web service is also published to one or more UDDI registries, then the "internal" WSDL file is required to remove the service from the gateway.

    2. Location Type. Select the type of location (either URL or UDDI) where the "internal" WSDL file is held.

    3. Target Service Name. If the Web service WSDL contains more than one service, or the WSDL is located through a UDDI registry, type the target service's name from the target service WSDL.

    4. Target Service Namespace. If the Web service WSDL contains more than one service, or the WSDL is located through a UDDI registry, type the namespace of the target service's name from the target service WSDL.

    5. Target Service Identity Information. Type the identity by which the target service is known within the Web services gateway. This identity need not be unique.

    6. Click add. The target service is added to a list of target services.

    To modify the deployment details for an existing target service, click on the name of the service in the list of target services. A form is displayed, containing the same fields that you filled in when you added the service, and also the following additional fields:

    • Started. Enable this check box option if you want the gateway to offer this Web service to service requesters.

    • Enable target service security. Enable this check box if you want the gateway to use secure communication between the gateway and the target service.

    • Edit target service security configuration. If you choose to enable target service security, then use this option to configure secure communication between the gateway and the target service. For more information see Editing the target service security configuration.
    When you have finished making changes, click Apply Changes.

  6. In the Channels section, you can add or remove channels from the list of deployed channels through which this service is available.

  7. In the Request Filters section, you can add or remove filters from the list of deployed filters that are applied to the request.

    Note: The filters are executed in the order shown. To add a filter into the list at a particular position, use the at position menu.

  8. In the Response Filters section, you can add or remove filters from the list of deployed filters that are applied to the response.

    Note: The filters are executed in the order shown. To add a filter into the list at a particular position, use the at position menu.

  9. In the UDDI References section, you can add or remove UDDI references from the list of deployed UDDI references to UDDI registries in which this service is published. If you select one or more UDDI references in this step, also enter a UDDI business key in the field provided under UDDI Publication Properties as described above. For more information about how the gateway works with UDDI registries, see UDDI registries - Web service directories that integrate with the Web services gateway.

  10. In the Exported WSDL definitions section there are two pairs of WSDL links. Both pairs link to (a) the external WSDL implementation definition, and (b) the external WSDL interface definition.

    • To view details of the associated external WSDL for the service, use the first pair.

    • To return the WSDL for use by application programs that need the WSDL definitions for the service, use the second pair.

    If there is an error generating the WSDL then a blank page is returned.

    Note: To help your service users locate the WSDL documents for services that are deployed to the Web services gateway, the gateway also supports the  

     

    WS-Inspection specification . To open a WS-Inspection document which contains references to the WSDL documents for all of the gateway-deployed services, you issue an HTTP GET against 

    http://host:port/wsgw/wsinspection.wsil
    where host and port are the host name and port number that your HTTP server is listening on.

Working with Web services
Deploying Web services to the Web services gateway
Removing Web services from the Web services gateway
Publishing a Web service to a UDDI registry for deployment to the gateway
Enabling Web Services Security (WS-Security) for the gateway
Configure the gateway security bindings
Editing the service security configuration
Editing the target service security configuration