Administering deployed web services applications
You can administer deployed web services applications using the administrative console.
Before you begin
About this task
Procedure
- Administer service providers. You can administer
your service providers using the following ways:
- View service providers at the cell level using the administrative console. You can view the details of your service provider, manage the policy sets for the service, its endpoints and operations, and assign bindings for the policy set attachment at the cell level.
- View service providers at the application level using the administrative console. You can view the details of your service provider, manage the policy sets for the service, its endpoints and operations, and assign bindings for the policy set attachment at the application level.
- Manage policy sets and bindings for service providers. You can view the details of your service provider, manage the policy sets for the service, its endpoints and operations, and assign bindings for the policy set attachment.
- Manage policy sets and bindings for service providers at the application level using the administrative console. You can manage policy sets for the provider, its endpoints, and operations, and assign bindings for the policy set attachment at the application level.
- View WSDL document using the administrative console . You can view the WSDL document for your JAX-WS application.
- Administer service clients. You can administer
your service clients using the following ways:
- View service clients at the cell level . Your application server instance can have one or more applications deployed on it that contain service clients. You can view a list of your service clients at the cell level using the administrative console.
- View service clients at the application level . Your application server instance can have one or more applications deployed on it that contains service clients. You can view the service client names that are referenced in an application.
- Manage policy sets and bindings for service clients. You can view details of your service client reference, manage the policy sets for the service, its endpoints and operations, and assign bindings for the policy set attachment.
- Manage policy sets and bindings for service clients at the application level. You can manage policy sets for your service client applications or its service references, endpoints, or operations and assign bindings for the policy set attachment at the application level.
- 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.
次主題
Overview of service and endpoint listeners
Using the administrative function of this product, you can control throughput by starting and stopping individual service listeners and endpoint listeners. When you stop a service listener, this causes any associated endpoint listeners to stop listening to any new inbound requests and the application server rejects any new incoming requests for that service. Additionally, resources become free that can be used to service requests that are already being processed for the service or to service new incoming requests for other services.Administration of service and endpoint listeners
The administration function of the product is enhanced to support service and endpoint listeners. You can use MBeans such as EndpointManager and the EndpointCentralManager to invoke service and endpoint listeners.Viewing service providers at the cell level using the administrative console
You can use this administrative console page to view and manage your service providers at the cell level.Viewing service providers at the application level using the administrative console
You can use this administrative console page to view and manage your service providers at the application level.Viewing the detail of a service provider and managing policy sets using the administrative console
Use this administrative console task to view the detail of your service provider and to manage the policy sets for the service, its endpoints and operations.Managing policy sets and bindings for service providers at the application level using the administrative console
Use this administrative console task to manage policy sets for an application or its services, endpoints, and operations.Viewing WSDL documents for service providers using the administrative console
You can locate and view a Web Services Description Language (WSDL) document from the administrative console.Viewing service clients at the cell level using the administrative console
You can view all your service clients at the cell level using the administrative console.Viewing service clients at the application level using the administrative console
You can view your installed service clients for an application using this task.Viewing detail of a service client and managing policy sets using the administrative console
Use this administrative console task to view the detail of your service client reference and to manage the policy sets for the service, its endpoints and operations.Managing policy sets and bindings for services references using the administrative console
Use this administrative console task to manage policy sets and bindings for the service reference, its endpoints, and operations.Managing policy sets and bindings for service clients at the application level using the administrative console
Use this administrative console task to manage policy sets for service clients applications or its services, endpoints, or operations.Viewing web services deployment descriptors in the administrative console
You can view the web services client and server deployment descriptors for a deployed web services application. You can view the bindings in the deployment descriptors.Configuring the scope of a JAX-RPC web services port
When a Java API for XML-based RPC (JAX-RPC) 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, client bindings and deployment descriptor information. There are three levels of scope that can be set: application, session and request.暫停補償服務
並非所有的 Web 伺服器都配置成要處理包含 CoordinationContext 元素的 SOAP 訊息。您可以使用 WebSphere Application Server,來配置補償服務的自訂內容,讓它處理預先定義的 Enterprise Java Bean 清單,這些 Enterprise Java Bean 在 Web 服務要求中不應傳送 CoordinationContext。JAX-WS timeout properties
Timeout properties for configuring how long Java API for XML-Based Web Services (JAX-WS) clients wait to read response messages, send request messages, and make connections, can be set in various levels of the application server for JAX-WS applications. These timeout properties can be configured via policy sets, on the org.apache.axis2.context.MessageContext, and the Java virtual machine (JVM). This order of precedence is how the web services runtime environment reads the properties. For example, if the write timeout were set in both the policy set and on the JVM, the runtime environment uses the property value in the policy file and ignore the JVM property. The following tables outline the read, write, and connection timeout properties. Unlike a Java API for XML-based RPC (JAX-RPC) client, timeout properties for JAX-WS clients must not be set on the client binding file, as the runtime environment ignores timeout properties set this way. The read and write timeouts are transport level timeouts that start when writing the request on the wire. The write timeout stops when the request is written. The read timeout includes time spent within the provider and stops when the response is read from the wire. The timeouts do not include the time for web services to marshal or unmarshal the request and response. These timeouts also do not take into account any time required to setup the connection.
Related tasks:


http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=twbs_admindeploy
檔名:twbs_admindeploy.html