Use this task to list the Web services that are deployed to the Web services gateway, and modify their deployment details.
Before you begin
Do not deploy multiple target services to the same gateway service unless you have a filter (or similar mechanism) that can select the required target service, because without filtering the gateway always picks the first target service in the list.
Why and when to perform this task
To list the Web services that are currently deployed to the Web services gateway, and to view and modify their deployment details (including adding or removing multiple target services) complete the following steps:Steps for this task
Services
The Audit policy indicates whether the MessageWarehouse object, if present, is 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.
Note:
If the location for the internal WSDL file is a Web address, type the Web address. If the binding and service definition for this Web service are held in separate WSDL files, then type the Web address of the WSDL file that defines the binding.
If the WSDL is located through a UDDI registry, type uddiReference,serviceKey where
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:
When you have finished making changes to the target service deployment details, click Apply Changes.
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.
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.
WSDL documents are XML documents, and two pairs of links are supplied in order to display the same external WSDL in two different document formats. The pair of links labelled View external WSDL implementation definition display the XML source for the WSDL, whereas the pair of links labelled External WSDL implementation definition (WSDL only) display the WSDL as it appears in a Web browser.
For example, in XML notation the ampersand character ("&") is reserved for use in encoding special characters such as the quotation mark ("""). The ampersand character itself is encoded as "&". When you select either of the View external WSDL implementation definition links, you view the literal XML source and the ampersand character is represented as "&". When you select either of the External WSDL implementation definition (WSDL only) links, your Web browser parses the XML source, converts the special characters back into their normal form, and the ampersand character is represented as "&".
Note: The "&" encoding is required only within the WSDL XML source document. You should not use it in any endpoint address that you supply to a service client. If you get the endpoint address from the WSDL programatically, then the XML parser handles the conversion. If you manually copy and paste the address into the properties file, you should copy the address from one of the External WSDL implementation definition (WSDL only) links.
If there is an error generating the WSDL then a blank page is returned.
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 Web services inspection document that contains references to the WSDL documents for all of the gateway-deployed services, you issue an HTTP GET against
http://host:port/wsgw/wsinspection.wsilwhere host and port are the host name and port number on which your HTTP server is listening.
Note: When you use the Web address provided in Testing the installation to list the services that are deployed to the SOAP over HTTP channel, you see a link labeled WSDL next to each service in the list. Do not use these links. To get the WSDL location for your service, open a Web services inspection document.