Deploy a Web services client application
After we have created an EAR file for the Web services client application, we can deploy the Web services client application into the appserver.
To deploy a Java -based Web services client, we need an enterprise application, also known as an EAR file configured and enabled for Web services.
A JAX-WS application is packaged as a WAR file or a WAR module within an EAR file. A JAX-WS application does not require additional bindings and deployment descriptors for deployment whereas a JAX-RPC Web services application requires you to add additional bindings and deployment descriptors for application deployment. JAX-WS is much more dynamic, and does not require any of the static data generated by the deployment step required for deploying JAX-RPC applications. For JAX-RPC Web services clients, configure the client deployment descriptors.
Use either the admin console or the wsadmin scripting tool to deploy an EAR file. If installing an application containing Web services by using the wsadmin command, specify the -deployws option for JAX-RPC applications.
Use the wsdeploy command only with JAX-RPC applications. The wsdeploy command is not applicable for JAX-WS applications.
If installing an application containing Web services by using the admin console, select Deploy WebServices in the Install New Application wizard. Read about installing a new application for more information on using the admin console.
The following actions deploy the EAR file with the wsadmin command:
- Start install_root/bin/wsadmin from a command prompt.
On operating systems such as AIX or Linux, start install_root/bin/
./wsadmin.sh.- Deploy the EAR file.
- For JAX-WS Web service applications, enter the $AdminApp install EARfile "-usedefaultbindings" command at the wsadmin prompt.
- For JAX-RPC Web service applications, enter the $AdminApp install EARfile "-usedefaultbindings -deployws" command at the wsadmin prompt.
Results
we have a deployed a Web service client in the appserver runtime environment.
Next steps
Test the Web services client. We can now test a Web services-enabled managed client EAR file or an unmanaged client JAR file.
Related tasks
Implementing JAX-WS Web services clients
Implementing JAX-RPC Web services clients
Testing Web services-enabled clients
Task overview: Implement Web services applications
Install enterprise application files with the console
Related
wsdeploy