Assembling applications for application profiling
To enable application profiling, you must configure tasks, create an application profile, and declaratively configure a unit of work on necessary methods.
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. To create your own access intent policy, see the topic, Creating a custom access intent policy, in the assembly tool information center.
Procedure
What to do next
- Automatic configuration of application profiling
The assembly tool includes a static analysis engine that can assist you in configuring application profiling. The tool examines the compiled classes and the deployment descriptor of a Java EE application to determine the entry point of transactions, calculate the set of entities enlisted in each transaction, and determine whether the entities are read or updated during the course of each identified transaction.
- Automatically configure application profiles and tasks.
Automatically configure application profiling for an application through static analysis.
- Apply profile-scoped access intent policies to entity beans.
Configure entities with access intent for an application profile.
- Create a custom access intent policy.
Define a custom access intent policy, which can be configured for Enterprise JavaBeans (EJB) 2.x and 3.0 entity beans.
- Create an application profile.
An application profile contains a set of access intent policies applied to an application's entity beans. The access intent policies are only applied for requests that are associated with tasks configured on the application profile.
- Configure container-managed tasks for application clients.
For application clients that programmatically begin either a transaction or ActivitySession only, you must configure an application client's container-managed task to associate requests from the client with an application profile.
- Configure container-managed tasks for Web components.
For Web components that programmatically set the configured task and then programmatically begin either a transaction or ActivitySession only, you can configure Web components application-managed tasks to associate requests from a servlet or JavaServer Pages (JSP) file with application profiles.
- Configure container-managed tasks for Enterprise JavaBeans.
For methods that cause a new transaction or ActivitySession to be started either by the container or programmatically by the EJB developer, you can configure an enterprise bean's container-managed tasks to associate requests from the bean with application profiles.
- Configure container-managed tasks for application clients.
For application clients that programmatically begin either a transaction or ActivitySession only, you must configure an application client's container-managed task to associate requests from the client with an application profile.
- Configure application-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 JSP file with an application profile.
- Configure application-managed tasks for Enterprise JavaBeans.
For Enterprise JavaBeans that programmatically set the configured task and then programmatically begin either a transaction or ActivitySession only, you can configure EJB application-managed tasks to associate requests from the bean with application profiles.