The client bindings define the Web service, WSDL file name, and preferred ports. A Web service can specify the relative path, within the module, of a compatible WSDL file containing the actual URL to be used for requests. This is needed only if the original WSDL file did not contain a URL or when a different URL is needed. For a service endpoint with multiple ports, define an alternative Web service WSDL file name.
The following steps describe how to edit bindings for a Web service after these bindings are deployed on a server. When one Web service communicates with another Web service, you must configure the client bindings to access the downstream Web service.
Perform the following steps in the WebSphere administrative console:
Click Applications --> Enterprise Applications --> application_instance --> Web Modules --> module_instance --> Web Services Client Bindings, where application_instance is the name of your Web service application, and module_instance is the name of your Web archive (WAR) file.
In the Web Service field, locate the Web service that you want to update.
In the WSDL Filename field, enter the WSDL file name. The path must be relative to the module.
(Version 5.1.1 and later) In the Preferred Port Type Mappings field, click Edit to configure the ports that the client uses.
(Version 5.1) In the Default Port Type Mappings field, click Edit to configure the ports that the client uses.
For each port type that is listed, select the preferred or default port.
Click Apply and OK.