+

Search Tips   |   Advanced Search

Deploy web services client applications

After we have created an EAR file for the web services client application, we can deploy the web services client application into the Application Server.

To deploy a Java-based web services client, we need an EAR file configured and enabled for web services.

A 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 JAX-RPC web services application requires additional bindings and deployment descriptors. JAX-WS is 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 administrative console or the wsadmin scripting tool to deploy an EAR file. If we are installing an application containing web services 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 we are installing an application containing web services 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.


Deploy the with the wsadmin command

  1. Start install_root/bin/wsadmin from a command prompt.

      install_root/bin/wsadmin.sh

  2. Deploy the EAR file.

    For JAX-WS web service applications...

      $AdminApp install EARfile "-usedefaultbindings"

    For JAX-RPC web service applications...

      $AdminApp install EARfile "-usedefaultbindings -deployws"

We have a deployed a web service client in the application server runtime environment.


What to do next

Test the web services client. We can now test a web services-enabled managed client EAR file or an unmanaged client JAR file.

  • Implement static JAX-WS web services clients
  • Implement JAX-RPC web services clients
  • Testing web services-enabled clients
  • Task overview: Implementing web services applications
  • Install enterprise application files with the console
  • wsdeploy command