Deploy a Web services client application
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.
To deploy a Java-based Web services client, we need an enterprise application, also known as an enterprise archive (EAR) file that is configured and enabled for Web services. For Java API for XML-based RPC (JAX-RPC) Web services clients, configure the client deployment descriptors.
Overview
You can use either the 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.
If you are installing an application containing Web services by using the console, select Deploy WebServices in the Install New Application wizard. For more information about installing applications using the console see Installing a new application. The following actions deploy the EAR file with the wsadmin command:
Procedure
- Start install_root/bin/wsadmin from a command prompt. If you are using Linux or Unix platforms, start install_root/bin/wsadmin.sh.
- Enter the $AdminApp install EARfile "-usedefaultbindings -deployws" command at the wsadmin prompt.
Results
You have a deployed a Web service client in the appserver runtime environment.
What to do next
Test the Web services client. You can now test a Web services-enabled a managed client EAR file or an unmanaged client JAR file.
Testing Web services-enabled clients
Task overview: Implementing Web services applications
Related Reference
wsdeploy command