Deploy Web services to the Web services gateway

(Version 5.0 and 5.0.1) Before you deploy a Web service, deploy the resources (channels, filters, and UDDI references) that the Web service uses.

(Version 5.0.2 and later) Before you deploy a Web service to the gateway, deploy the resources (channels, filters, UDDI references and security bindings) that the Web service uses.

For Web services deployed with Java bindings (or EJB bindings where the Web service is on a different server), make the additional classes available to the gateway

To deploy a Web service, complete these steps:

  1. Display the Web services Gateway administrative user interface.

  2. In the navigation pane, click Services.

  3. Click Deploy. A form is displayed for you to specify the deployment details.

  4. Type the following Web service deployment details:
    1. Gateway Service Name. Type the name by which the Web service is known within the Web services gateway. This name must be unique within the Web services gateway and must not contain any spaces.
      Note: If you have several implementations of the same Web service, you can map them all to the same deployed gateway service. You use the Deploy option (this option) to deploy just one instance of a given gateway service. To add more target services to a deployed gateway service, you use the Services and List option.
    2. Choose between the two types of Message part representation. For more information, see Data type representation - choosing between Generic classes and Deployed Java classes:

      • Generic classes
        You can select this option in all cases except the following cases:

        • You cannot select this option if your service has EJB or Java bindings that are used at runtime.
        • You cannot select this option if your service uses Vectors, Enumerations, Hashtables or Maps.

      • Deployed Java classes
        You must select this option if the target services for the gateway service use Vectors, Enumerations, Hashtables or Maps, or contain EJB or Java bindings.
        Note: When you choose this option, ensure that the specific java classes that have been generated for the Web service are deployed to the application server (for example by copying the JAR file into the WAS's /AppServer/lib/app directory, then restarting the application server).
        You can also select this option (as an alternative to selecting "Generic classes"):

        • If the target service uses only supported simple and compound types. For more information, see Web services gateway - supported types
        • If the target service uses complex types, and the specific Java classes that have been generated for the Web service are available to the gateway (but note that if you select "Generic classes", then you do not need to also deploy the associated Java classes locally).

    3. (Optional) Authorization Policy - Control access to this service. If you want to enable operation-level authorization for this Web service, select this check box.
    4. (Optional) 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, and you want it to log requests and responses for this Web service, enable this check box.
    5. In this release of the gateway, the Annotation URL field is not used.
    6. Select the deployed resources that the Web service is to use, from these lists:

      • Channels
        Select one or more deployed channels through which this service is to be available.
      • Request Filters
        Select zero or more deployed filters to apply to the request.
      • Response Filters
        Select zero or more deployed filters to apply to the response.
      • UDDI References
        In this field you can select zero or more deployed UDDI references to UDDI registries in which this service is to be registered. If you select one or more UDDI references in this step, enter a UDDI business key in step 3h below.
        Note: There may be more than one UDDI Reference for the same business in the same UDDI Registry. This is because a business can have more than one entry (each with a different Authorized Name) in the same UDDI registry..

    7. Specify the Target Service Properties for the Web service:

      • WSDL Location
        Type the location of the internal WSDL file that describes the Web service to be deployed. This value is either a URL, or (if the WSDL is located in a UDDI Registry) it is 
        "uddiRefName,serviceKey"

        where uddiRefName is the 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) and 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

        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.
      • Location Type
        Select the type of location (either URL or UDDI) where the internal WSDL file is held.
      • Target Service Name
        If the Web service WSDL contains more than one service, type the target service's name from the target service WSDL.
      • Target Service Namespace
        If the Web service WSDL contains more than one service, type the namespace of the target service's name from the target service WSDL.
      • Target Service Identity Information
        Type the identity by which the Web service is known within the Web services gateway. This identity need not be unique.
        Note: If you later add more target services to this gateway service, and also , you might use the Target Service Identity Information to select a particular target service from the set.

    8. If you want to publish the service to one or more UDDI registries (selected in a previous step), 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

  5. Click OK.

If the processing completes successfully, the list of deployed Web services is updated to include the new Web service. Otherwise, an error message is displayed.

For details on deploying Web services with Java bindings, see Deploy Web services with Java bindings.

For more information on mapping namespaces to packages, see Complex data types - mapping namespaces to packages.