Deploying web services client applications
After you have created an enterprise archive (EAR) file for the web services client application, you can deploy the web services client application into the Application Server.
Before you begin
To deploy a Java-based web services client, you need an enterprise application, also known as an enterprise archive (EAR) file that is configured and enabled for web services.
A Java™ API for XML-Based Web Services (JAX-WS) application is packaged as a web application archive (WAR) file or a WAR module within an Enterprise Archive (EAR) file. A JAX-WS application does not require additional bindings and deployment descriptors for deployment whereas a Java API for XML-based RPC (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, you must configure the client deployment descriptors.
About this task
You can use either the administrative console or the wsadmin scripting tool to deploy an EAR file. If you are 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 you are installing an application containing web services by using the administrative console, select Deploy WebServices in the Install New Application wizard. Read about installing a new application for more information on using the administrative console.
The following actions deploy the EAR file with the wsadmin command: