Configure web services client bindings

When a web services application is deployed into WebSphere Application Server, an instance is created for each application or module. The instance contains deployment information for the web module or EJB module, including client bindings.

Deploy a web service into our WAS instance.

We must know the topology of the URL endpoint address of the web services servers and which web service the client depends upon. We can view the deployment descriptors in the administrative console to find the topology information.

The client bindings define the WSDL file name and preferred ports. The relative path of a web service in a module is specified within a compatible WSDL file containing the actual URL to be used for requests. The address is only needed if the original WSDL file did not contain a URL, or when a different address is needed. For a service endpoint with multiple ports, define an alternative 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, configure the client bindings to access the downstream web service.

We can also configure client bindings with the wsadmin tool.

Configure client bindings with the admin console

1. Open the administrative console.

2. Click...
   Applications | Enterprise Applications | application_instance | Manage Modules | module_instance | Web services client bindings

3. Find the web service we want to update.

   The web services are listed in the Web Service field.

4. Select the WSDL file name from the drop down box in the WSDL file name field.

5. Click Edit in the Preferred port mappings field to configure the default port to use.

   1. Port type and the preferred ports in the Port type and Preferred ports fields.

      Configuring the preferred port enables us to select an optimal port implementation use non-SOAP protocols.

   2. Click Apply and OK.

6. Click Edit in the Port information field to configure the request timeout, the overridden endpoint, and the overridden binding namespace for a port.

   Configure the request timeout accommodates complex topologies that can have multiple cascaded Web services that involve multiple hops or long-running services.

   We can configure Timeout values based on observed behavior of the overall system as integration proceeds. For example, a web service client might time out because of changing network conditions or the performance of an external web service. When we have applications containing web services clients that timeout, we can change the request time out values for the clients.

   We can specify an endpoint URL to override the current endpoint. A client invoking a request on this port uses this endpoint instead of the endpoint specified in the WSDL file. We can specify the Overridden endpoint URL value for both JAX-WS clients and Java API for XML-based RPC (JAX-RPC) clients.

   The Overridden endpoint URL field is applicable for both JAX-WS and JAX-RPC clients. The other fields on this administrative console page are only applicable for JAX-RPC clients.

   Overridden endpoint URL settings do not persist when a module or application is replaced in an update operation.

   1. Click Apply and OK.

Your web service client bindings are configured.

What to do next

Now we can finish any other configurations, start or restart the application, and verify the expected behavior of the web service.

Subtopics

• Web services client bindings
  
• Preferred port mappings
  
• Web services client port information
  

Related:

RMI-IIOP using JAX-RPC Configure web service client-preferred port mappings
Configure web service client port information
Deploy web services applications onto application servers
Configure a web service client deployed WSDL file name

View web services server deployment descriptor