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.

Before you begin

Deploy a web service into the WebSphere Application Server. To learn more, read about deploying web services applications onto application servers.

About this task

The Web Services for Java Platform, Enterprise Edition (Java EE) specification states that web services implementations must be stateless. Therefore, to maintain specification compliance, the scope can remain at the application level because the state relevant to the individual sessions level or the requests level is not supposed to be maintained in the implementation. If you want to deviate from the specification and want to access a different JavaBeans instance, because you are looking for information that is located in another JavaBeans implementation, the scope settings need to change.

The setting that you configure for the scope determines how frequently a new instance of a service implementation class is created for the web services ports in a module. Use this task to configure the scope of a web services port.

This task applies only to Java API for XML-based RPC (JAX-RPC) web services.

To change the scope setting in the administrative console:

Procedure

  1. Open the administrative console.
  2. Click Applications > Application Types > WebSphere enterprise applications application_name > Manage Modules > module instance > Web services implementation scope
  3. Set the scope to application, session or request. The application scope causes the same instance of the implementation to be used for all requests on the application. The session scope causes the same instance to be used for all requests in each session. The request scope causes a new instance to be used for every request. For example, with the scope set to application, every message that comes to the server accesses the same JavaBeans instance because that is the way the scope settings are configured.
  4. Click Apply.
  5. Click OK.

Results

The scope for a web services port is configured.

What to do next

Now you can finish any other configurations, start or stop the application, and verify the expected behavior of your web service.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jan 30, 2014 9:17:32 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-iseries&topic=twbs_scope
File name: twbs_scope.html