Configure container-managed tasks for Web components

For Web components that programmatically begin either a transaction or ActivitySession only, you can configure a Web component's container-managed task to associate requests from a servlet or JavaServer Pages file with an application profile.

Overview

If a unit of work is not begun, then the configured task is ignored. For more information about using tasks, see Application profiling tasks and Tasks and units of work considerations.

Note: If you select the 5.x Compatibility Mode attribute on the Application Profile Service's console page, then tasks configured on J2EE 1.3 applications are not necessarily associated with units of work and can arbitrarily be applied and overridden. This is not a recommended mode of operation and can lead to unexpected deadlocks during database access. Tasks are not communicated on requests between applications that are running under the Application Profiling 5.x Compatibility Mode and applications that are not running under the compatibility mode.

For a V6.0 client to interact with applications run under the Application Profiling 5.x Compatibility Mode, set the appprofileCompatibility system property to true in the client process. You can do this by specifying the -CCDappprofileCompatibility=true option when invoking the launchClient command.

Procedure

1. Start the Application Server Toolkit.

2. Optional: Open the J2EE perspective to work with J2EE projects. Click Window > Open Perspective > Other > J2EE.

3. Optional: Open the Project Explorer view. Click Window > Show View > Project Explorer. Another helpful view is the Navigator view (Window > Show View > Navigator) .

4. Create a new application EAR file or edit an existing one. For example, to change attributes of an existing application, use the import wizard to import an EAR file. To start the import wizard:

   1. Select File > Import > EAR file > Next

   2. Select the EAR file.

   3. Create a WebSphere Application Server v6.0 type of Server Runtime. Select New to open the New Server Runtime Wizard and follow the instructions.

   4. In the Target server field, select WebSphere Application Server v6.0 type of Server Runtime.

   5. Select Finish

5. In the Project Explorer view of the J2EE perspective, right-click the Deployment Descriptor: Web Module Name under the web module, then select Open With > Deployment Descriptor Editor. A property dialog notebook for the web project is displayed in the property pane.

6. Select the Servlets tab.

7. Select the servlet or JSP that you want to change.

8. Expand the WebSphere Programming Model Extensions section.

9. Enter the name and description of the task in the Container-Managed Task section. The task name is mapped to application profiles and used by the run time to determine the appropriate access intent to use for enlisted entities. Task names do not have to be unique within an application. However, task names should be shared consciously and conservatively. At run time, all tasks with the same name are treated the same way, regardless of where you configured the task.

   The description is provided for your convenience; it is not used by the runtime environment.

10. Select OK.

Related tasks