Operating Systems: i5/OS
             Personalize the table of contents and search results
Create a custom access intent policy
You can define a custom access intent policy, which can be configured
for 2.x entity beans.
Procedure
- Start the Application Server Toolkit.
- Optional: Open the J2EE perspective to work with J2EE
projects. Click Window > Open Perspective > Other > J2EE.
- Optional: Open the Project Explorer view. Click Window
> Show View > Project Explorer. Another helpful view is the Navigator
view (Window > Show View > Navigator).
- Create a new application EAR file or edit an existing one.
For example, to change attributes of an existing application, use
the import wizard to import an EAR file. To start the import wizard:
- Select File > Import > EAR file > Next
- Select the EAR file.
- Create a WebSphere Application Server V6.0
type of Server Runtime. Select New to open the New Server Runtime Wizard
and follow the instructions.
- In the Target server field, select WebSphere Application Server
V6.0 type of Server Runtime.
- Select Finish
- In the Project Explorer view of the J2EE perspective, right-click
the Deployment Descriptor: EJB Module Name under the EJB module for
the bean instance, then select Open With > Deployment Descriptor Editor.
A property dialog notebook for the EJB project is displayed in the property
pane.
- In the property pane, select the Extended Access tab.
- Beneath the Defined Access Intent Policies panel, select Add.
- Specify a unique name by which the policy is referenced
when applied to entity beans.
- Optional: Specify a description of the policy.
- Specify an access type.
- Specify the collection scope.
- Transaction
-
This is the default. Collections of entities cannot be used beyond the
scope of the transaction in which the collection is created.
- ActivitySession
-
Collections of entities cannot be used beyond the scope of the ActivitySession in
which the collection is created. The collection can be used in a new transaction
if that transaction is nested under the original ActivitySession, although
you might need to reload the object by querying the underlying data store.
- Specify the collection increment. Specify a valid
integer to define the chunks that populate a remote collection. This value
only applies to remote collections and is ignored by local collections.
The default value for access types that result in U locks is 1. Otherwise,
the default is 25.
- Specify the resource manager prefetch increment.
Specify a valid integer to set as the fetch size on the JDBC statement
when executing queries for a bean type. The default value is 0.
What to do next
Applying
access intent policies to entity beans.
}
Access intent assembly settings
Access intent policies
Access intent service
  Â