Application profiling: Overview
Application profiling enables you to identify particular units of work
to the WebSphere Application Server run time environment. The run time can
tailor its support to the exact requirements of that unit of work. Access
intent is currently the only run time component that makes use of the application
profiling functionality. For example, you can configure one transaction to
load an entity bean with strong update locks and configure another transaction
to load the same entity bean without locks.
Application profiling introduces two new concepts in order to achieve this
function: tasks and profiles.
- Tasks
- A task is a named unit of work within a distributed application. Unit
of work in this case means a unique path within the application that may
or may not correspond to a transaction or activity session. The name of the
path is typically assigned declaratively to the method of an enterprise bean,
to a J2EE client or servlet. This point of configuration marks the head of
a graph or subgraph identified by the name of the task; the task name flows
from the head of the graph downstream on all subsequent IIOP requests, identifying
each subsequent invocation along the graph as belonging to the developer-configured
task.
- Profiles
- A profile is simply a mapping of a task to a set of access intent policies
that are configured on entity beans. When an invocation on a bean (whether
by a finder method, a CMR getter, or a dynamic query) requires data to be
retrieved from the back end system, the current task associated with the request
is used to determine the exact requirement of the transaction. The same bean
loads and behaves differently in the context of the task-to-profile mapping.
Each profile provides the developer an opportunity to reconfigure the application's
access intent. If a request is operating in the absence of a task, the run
time environment uses either a method-level access intent (if any) or a bean-level
default access intent.

Application profiles
Application profiling performance considerations

Assembling applications for application profiling
Managing application profiles
Using the TaskNameManager interface
Searchable topic ID:
capp_overview
Last updated: Jun 21, 2007 8:07:48 PM CDT
WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/appprofile/concepts/capp_overview.html