Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services
Deploy web services
- Deploy web services applications onto application servers
After assembling the artifacts required to enable the web module for web services into an EAR file, you can deploy the EAR file into the application server.
- Use 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, set up a third-party JAX-WS web services engine if deploy applications that use a single runtime across various application servers such as WAS, JBoss, and WebLogic, or to build JAX-WS web services applications using third party JAX-WS run-times such as CXF, Axis2, and Metro.
- Deploy web services client applications
After we have created an EAR file for the web services client application, you can deploy the web services client application into the Application Server.
- Make deployed web services applications available to clients
We 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.
- Run an unmanaged web services JAX-RPC client
WAS v8.0 and the Application Client for WAS v8.0 provides a thin Java Platform, Standard Edition 6 (Java SE 6) web services client runtime implementation that is based on the JAX-RPC 1.1 specification. The Thin Client for JAX-RPC with WAS 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.
- Run an unmanaged web services JAX-WS client
WAS 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 WAS 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.
- Test web services-enabled clients
Once we have developed, assembled, deployed and configured your web service, you can test to confirm your web service runs in the application server environment.