WebSphere Application Server Enterprise assembly settings for Web components

Use this page to configure Enterprise functions for Web components (servlets and JSPs).

Own task
A J2EE component's own task defines the task that can be used to identify a unit of work begun by this component to application profile-configured policies on downstream requests.
Name
The name of the task to be propagated on requests from this J2EE component.
Datatype String
Description
The description of the task.

An optional field provided as a convenience to the developer.

Datatype String
Task references
Task references enable developers to programmatically set the current task under which a component is executing.
Task
The task that the run-time environment will associate with execution of the current component.
ActivitySession control kind
The action to be taken by the TransactionControl collaborator that runs in the web container.
Default None
Range
Application
Access to UserActivitySessions is provided. Any HttpSession started by a servlet does not have an ActivitySession automatically associated with it by the container. The container associates any ActivitySession started by the servlet with an HttpSession already available to the servlet. An ActivitySession started before any HttpSession is created is not associated with any HttpSession and must be completed by the application before dispatch-end; otherwise it is cleaned up by the container. Servlets with this attribute cannot be included or forwaded to.
Container
A servlet has no access to UserActivitySessions. Any HttpSession started by the servlet has an ActivitySession automatically associated with it by the container, and this ActivitySession is put onto the thread of execution. If such a servlet is dispatched by a request that has an HttpSession containing no ActivitySession, then the container starts an ActivitySession and associates it with the HttpSession and the thread.
None
A servlet has no access to UserActivitySessions, and no participation in an ActivitySession is tolerated. Any HttpSession containing an ActivitySession that is associated with a request dispached on such a servlet is rejected with a ServletException.
Internationalization type
The Internationalization type of a servlet indicates whether the servlet or the hosting J2EE Web container will manage internationalization context on lifecycle method invocations. For servlets, the Internationalization type setting can be configured to Application or Container, and defaults to Container. The setting applies to all lifecycle methods of a servlet.

Select whether the servlet will employ Application or Container internationalization context management using the Internationalization type drop-down menu.

Default Container
Range
Application

Under Application-managed Internationalization (AMI) servlets are responsible to manage (set) invocation context elements using the internationalization context API. The container suspends internationalization context imported from the calling process on lifecycle method invocations, including HTTP servlet requests; to continue propagating this context on subsequent business method requests, the method must use the API to transfer caller context elements to the invocation context scoped to the method. Invocation context elements not set using the API default to the respective elements of the current process when accessed using the API or when propagated on outgoing business method requests.

Specify Application-managed Internationalization for servlets having internationalization context management requirements not supported by Container-managed Internationalization.

Container

Under Container-managed Internationalization (CMI) servlets have read-only access to the internationalization context API and rely solely on the Web container to manage invocation context in accordance with the Run as field of the applicable Container Internationalization attribute. On a service method invocation, the container scopes the context indicated by the Run as field to the method; when the method has completed, the container removes this context from scope. If the servlet is not indicated within a Container Internationalization attribute, the container scopes the caller context by defualt. Invocation context elements unavailable to the container default to the respective elements of the server JVM when accessed using the API or when propagated on outgoing business method requests.


Related tasks
Assembling applications for application profiling
Setting the internationalization type for servlets
Related reference
Internationalization assembly properties for Web modules[5.0 only][Version 5.0.1][Version 5.0.2]



Searchable topic ID:   uaat_servlettab
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/../aat_pme/ui/uaat_servlettab.html

Library | Support | Terms of Use | Feedback