Administering deployed web services applications

You can administer deployed web services applications using the administrative console.

Before you begin

Before you can administer a web service application, you need to deploy your web service application.

About this task

You can use the administrative console to administer Java™ API for XML-Based Web Services (JAX-WS) service provider or service client applications or Java API for XML-based RPC (JAX-RPC) web services.

Procedure

  • Administer service providers.
    You can administer your service providers using the following ways:
  • Administer service clients.
    You can administer your service clients using the following ways:
  • View the deployment descriptors..
    View the web services server and client deployment descriptors for a deployed web services application. You can view the bindings in the deployment descriptors. The deployment descriptors are required for JAX-RPC web services. You can optionally use the webservices.xml deployment descriptor to augment or override application metadata specified in annotations within your JAX-WS web services.
  • Configure the scope of a web service port..(JAX-RPC applications only)
    When a web service application is deployed into WebSphere Application Server, an instance is created for each application or module. The instance contains deployment information for the web module or enterprise bean module, including implementation scope and client bindings information. There are three levels of scope that you can set: application, session and request.
  • Suppress the compensation service
    Not all web servers are configured to handle SOAP messages containing CoordinationContext elements. WebSphere Application Server allows you to configure a custom property for the compensation service which processes a predefined list of Enterprise Java Beans for which no CoordinationContext should be sent on web service requests.