Task overview: Application profiling
Use application profiling to configure multiple access intent policies on the same entity bean.
Application profiling reflects different units of work that have different use patterns for enlisted entities. Support from the server runtime can vary for these units of work and use patterns. See topic Application profiling.
Tasks
- Assemble applications for application profiles. See the topic Assemble applications for application profiles to learn how to configure tasks, create application profiles, and configure tasks on profiles.
- Manage application profiles. See the topic Managing application profiles to learn how to add and remove tasks from application profiles using the administrative console.
- Use the TaskNameManager API. See the topic Using the TaskNameManager API to learn how to programmatically set the current task name; use this technique sparingly. Wherever possible, use the declarative method instead, which results in more portable function.
Subtopics
- Application profiling
Use application profiling to identify particular units of work to the product runtime environment. The run time can tailor its support to the exact requirements of that unit of work.- Application profiling tasks
Tasks are named units of work. They are the mechanism by which the runtime environment determines which access intent policies to apply when an entity bean's data is loaded from the back end system.- Assemble applications for application profiling
To enable application profiling, configure tasks, create an application profile, and declaratively configure a unit of work on necessary methods.- Manage application profiles
Using the administrative console, we can add tasks to or remove tasks from application profiles.- Application profiling interoperability
Using application profiling with 5.x compatibility mode or in a clustered environment with mixed product versions and mixed platforms can affect its behavior in different ways.
Use the TaskNameManager interface