Assembling applications for application profiling

 

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. Use the one of the default policies or create your own, as described in the topic, Creating a custom access intent policy.

 

Procedure

  1. Configuring tasks. Declaratively configure tasks as described in the following topics:

    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.

    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 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. We can do this by specifying the -CCDappprofileCompatibility=true option when invoking the launchClient command.

  2. Creating an application profile.

 

See also


Automatic configuration of application profiling
Applying profile-scoped access intent policies to entity beans
Creating a custom access intent policy
Creating an application profile
Configuring container managed tasks for application clients
Configuring container managed tasks for Web components
Configuring container managed tasks for Enterprise Java Beans
Configuring application managed tasks for application clients
Configuring application-managed tasks for Web components
Configuring application managed tasks for Enterprise JavaBeans

 

See Also


Application profiling: Overview

 

Related Tasks


Applying access intent policies to methods
Manage application profiles
Using the TaskNameManager interface
Automatically configuring application profiles and tasks