Before you begin
Application profiling enables multiple access intent policies to be configured on the same entity bean, each specified for a particular unit of work. You can use the one of the default policies or create your own, as described in the topic, Creating a custom access intent policy.
Steps for this task
On rare occasions, you might find it necessary to configure tasks programmatically. Application profiling supports this requirement with a simple interface that enables a task name to be set before a unit of work is programmatically initiated. Setting a task name and then initiating a transaction or ActivitySession will cause the task to be associated with the new unit of work. This interface cannot be used within Enterprise Java Beans that are configured for container-managed transactions or container-managed ActivitySessions because units of work can only be associated with a task at the exact time that the unit of work is initiated. The call to set the task name must therefore be invoked before the unit of work is begun. Units of work cannot be named after they are begun. See Using the TaskNameManager interface.
For a Version 6.0 client to interact with applications run under the Application Profiling 5.x Compatibility Mode, you must 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.
Related concepts
Application profiling: Overview
Related tasks
Applying access intent policies to methods
Managing application profiles
Using the TaskNameManager interface
Automatically configuring application profiles and tasks