Develop Web services clients
Overview
Locate the WSDL file that defines the Web service that you want to access from the services provider using e-mail, URL or by looking it up in a UDDI registry.
For a Java application to act as a Web service client, a mapping between the WSDL file and the Java application must exist. The mapping is defined by the JAX-RPC specification. Use a Java component to implement a Web service by specifying the component interface and binding information in the WSDL file and designing the application server infrastructure to accept the service request. This entire process is based on the Web Services for J2EE specification. The JAX-RPC specification defines the mapping between a WSDL file, Java code and XML Schema types.
Create the client code and artifacts that enable the application client to access a Web service by following the steps provided:
Procedure
- Develop client bindings from a WSDL file.
The client-side bindings and deployment descriptors are generated.
- Complete the client implementation.
- Assemble a Web services-enabled client JAR file.
Complete this step if you are developing a managed client that runs in the J2EE client container. (Optional)
- Assemble a Web services-enabled client WAR file.
Complete this step if you are developing a managed client that runs in the J2EE client container. (Optional)
- Configure the client deployment descriptor.
Complete this step if you are developing a managed client that runs in the J2EE client container. (Optional)
- Configure the ibm-webservicesclient-bnd.xmi deployment descriptor.
Complete this step if you are deploying a managed client that runs in the J2EE client container and you want to override the default client settings.
- Test the Web services-enabled client application.
This task explains how to test an unmanaged client JAR file and an unmanaged client application.
Result
You have created and tested a Web services client application. For step-by-step information see Example: Developing Web services clients.
What to do next
After you develop a Web services application client, and the client is statically bound, the service endpoint used by the implementation is the one that is identified in the WSDL file that you used during the development process. During or after installation of the Web services application, you might want to change the service endpoint. We can change the endpoint with the administrative console or the wsadmin scripting tool.
See also
Example: Developing Web services clients
Developing client bindings from a WSDL file
Assembling a Web services-enabled client JAR file into an EAR file
Assembling a Web services-enabled client WAR file into an EAR file
Testing Web services-enabled clients
See Also
Web services
Related Tasks
Implementing Web services applications
Developing Web services applications
Configuring the Web services client bindings in the ibm-webservicesclient-bnd.xmi deployment descriptor
Configuring the client deployment descriptor
Configuring the client deployment descriptor for handler classes with an assembly tool
See Also
Artifacts used to develop Web services
ibm-webservices-bnd.xmi assembly properties