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 JavaBeans (EJB) module, including the client bindings.
You should have the Web service application ready for deployment or already deployed the Web service into WebSphere Application Server before starting this task.
To complete this task, you need to 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 topology information. To learn more, see the viewing Web services server deployment descriptors in the administrative console information.
For more information about the wsadmin tool options, see the information on options for the AdminApp object install, installInteractive, edit, editInteractive, update, and updateInteractive commands.
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 use the WebServicesClientBindDeployedWsdl command-line option in this task to change the endpoint. One of the benefits to using the command-line option is that you can avoid uninstalling, modifying enterprise archive (EAR) files and reinstalling applications to make binding configuration changes. Another benefit is the ability to customize the Web service bindings applications for different environments during installation, and to avoid the need to create different application EAR files for each version.
Several versions of WSDL files, each with different service endpoints, can be provided during the development and assembly of a Web service module that is acting as a client to a Web service. During or after the installation, when you are configuring the installed application, the WebServicesClientBindDeployedWsdl option can be used to specify which of the WSDL files to use.
Because the WSDL file defines all the service endpoints or implementations for all of the port types and ports that the client can use, the deployed WSDL file can group a set of choices into one WSDL. You can override the endpoint by port.
You can use Jacl or Jython scripts, but this task assumes that you are using Jacl. For more information about deploying and managing using scripting, see the getting started with scripting information.
To configure client bindings with the wsadmin tool, proceed with the following steps:
$AdminApp edit MultiEjbJar {-WebServicesClientBindDeployedWSDL {{ejbclientonly.jar Exchange service/StockQuoteService META-INF/wsdl/AlternateStockQuoteFetcher.wsdl}...}}
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |