Deploying web services

You can deploy, run, and test web services client applications.

Deploying web services applications onto application servers
After assembling the artifacts required to enable the web module for web services into an enterprise archive (EAR) file, you can deploy the EAR file into the application server.
Using a third-party JAX-WS web services engine
In certain situations you might need to set up a third-party JAX-WS web services engine. For example, you must set up a third-party JAX-WS web services engine if you need to deploy applications that use a single run time across various application servers such as WebSphere® Application Server, JBoss, and WebLogic, or if you want to build JAX-WS web services applications using third party JAX-WS run time such as CXF, Axis2, and Metro.
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.
Making deployed web services applications available to clients
You can publish WSDL files to the file system. If you are a client developer or a system administrator, you can use WSDL files to enable clients to connect to web services.
Running an unmanaged web services JAX-RPC client
WebSphere Application Server Version 8.5 and the Application Client for WebSphere Application Server Version 8.5 provides a thin Java Platform, Standard Edition 6 (Java SE 6) web services client runtime implementation that is based on the Java™ API for XML-based RPC (JAX-RPC) 1.1 specification. The Thin Client for JAX-RPC with WebSphere Application Server is a stand-alone Java SE 6 client environment that enables running unmanaged JAX-RPC web services client applications in a non-WebSphere environment to invoke web services that are hosted by the application server.
Running an unmanaged web services JAX-WS client
WebSphere Application Server provides a thin Java Platform, Standard Edition 6 (Java SE 6) web services client runtime implementation that is based on the Java API for XML-based Web Services (JAX-WS) 2.2 specification. The Thin Client for JAX-WS with WebSphere Application Server is a stand-alone Java SE 6 client environment that enables running unmanaged JAX-WS web services client applications in a non-WebSphere environment to invoke web services that are hosted by the application server.
Testing web services-enabled clients
Once you have developed, assembled, deployed and configured your web service, you can test to confirm your web service runs in the application server environment.