Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer web services (generally applicable) > Administer deployed web services applications
View web services deployment descriptors in the administrative console
We can view the web services client and server deployment descriptors for a deployed web services application. We can view the bindings in the deployment descriptors. Before you can view the deployment descriptors, complete all tasks required to implement a JAX-RPC web service, create the deployment descriptor templates that were generated by the WSDL2Java command-line tool, configure the deployment descriptors and bindings, and deploy the Web service application into WAS. Review the implementing web services application documentation for more information on developing and implementing web services.
Deployment descriptors contain the information that is needed by a web services client to communicate with the server for which the Web services is installed. This information is added to the deployment descriptor templates after a web service is developed or an existing web service is located. The data that you can view in the deployment descriptor includes the following:
- The web service description including the name, WSDL file, WSDL file location and the mapping file.
- The port description, including the port component name, the WSDL port, the service endpoint interface that indicate the service's bindings, and the EJB used to implement the web service.
After we have developed a web service that contains all the necessary artifacts, created the deployment descriptors from the deployment descriptor templates, configured the deployment descriptors, and deployed the web services application into WAS; now you can view the deployment descriptors and bindings in the administrative console.
Similar to JAX-RPC web services, you can use deployment descriptors to describe JAX-WS web services. For JAX-WS web services, the use of the webservices.xml deployment descriptor is optional because you can use annotations to specify all of the information that is contained within the deployment descriptor file. We can use the deployment descriptor file to augment or override existing JAX-WS annotations. Any information that you define in the webservices.xml deployment descriptor overrides any corresponding information specified by annotations.
Procedure
- Open the administrative console.
- Click Applications > Application Types > WebSphere enterprise applications > application_name > Manage Modules.
- Click View web services client deployment descriptor extension.
- Click View web services server deployment descriptor.
- Click View web services server deployment descriptor extension.
- Click Expand All to view the deployment descriptor contents.
- Verify deployment descriptor and bindings configurations.
What to do next
You have viewed and verified the deployment descriptors and bindings for the web services application.
Develop a webservices.xml deployment descriptor for JAX-WS applications
Configure the webservices.xml deployment descriptor for JAX-RPC web services
Configure the ibm-webservices-bnd.xmi deployment descriptor for JAX-RPC web services
Configure the webservices.xml deployment descriptor for handler classes
Configure the JAX-RPC web services client deployment descriptor with an assembly tool
Configure the JAX-RPC client deployment descriptor for handler classes
Task overview: Implementing web services applications