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 Enterprise JavaBeans (EJB) module,
including client bindings.
Before you begin
Deploy a web service into your WebSphere Application
Server instance. Read about deploying web services applications
onto application servers.
You must know the topology of the
URL endpoint address of the web services servers and which web service
the client depends upon. You can view the deployment descriptors in
the administrative console to find the topology information. To learn
more, see the View web services server deployment descriptors information.
About this task
The client bindings define the Web Services Description
Language (WSDL) file name and preferred ports. The relative path of
a web service in a module is specified within a compatible WSDL file
that contains 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, you need to 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, you must configure the client bindings to
access the downstream web service.
You
can also configure client bindings with the wsadmin tool. Read about
configuring a web service client deployed WSDL file name with the
wsadmin tool.
To configure client bindings through the administrative
console:
Procedure
- Open the administrative console.
- Click Applications > Enterprise Applications > application_instance > Manage
Modules > module_instance > Web services client
bindings.
- Find the web service you want to update.
The
web services are listed in the Web Service field.
- Select the WSDL file name from the drop down box in the
WSDL file name field.
- Click Edit in the Preferred port mappings field
to configure the default port to use.
- Specify the port type and the preferred ports in the
Port type and Preferred ports fields.
Configuring the
preferred port enables you to select an optimal port implementation
use non-SOAP protocols. See the RMI-IIOP web services using JAX-RPC
information to learn more about using non-SOAP protocols.
- Click Apply and OK.
- Click Edit in the Port information field to configure
the request timeout, the overridden endpoint, and the overridden binding
namespace for a port.
Configuring the request timeout
accommodates complex topologies that can have multiple cascaded Web
services that involve multiple hops or long-running services.
You
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 you have applications containing
web services clients that timeout, you can change the request time
out values for the clients.
You 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. You can specify the Overridden endpoint URL value for
both Java™ API for XML-Based Web Services (JAX-WS)
clients and Java API for XML-based RPC (JAX-RPC)
clients.
Supported configurations: 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.
Avoid trouble: Overridden endpoint URL settings do not persist when a
module or application is replaced in an update operation.
- Click Apply and OK.
Results
Your web service client bindings are configured.
What to do next
Now you can finish any other configurations, start or restart
the application, and verify the expected behavior of the web service.