When a Web service 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 JavaBean (EJB) module, including client bindings.
Deploy a JAX-RPC 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. View Web services server deployment descriptors for more information.
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 wsadmin.
To configure client bindings through the administrative console:
In this information ...Subtopics
Related tasks
| IBM Redbooks, demos, education, and more |