[Version 5.0.2 and later]Creating a custom access intent policy

Why and when to perform this task

Define a custom access intent policy which can be configured for 2.0 entity beans.

Steps for this task

  1. Start the Assembly Toolkit.
  2. (Optional)   Open the J2EE perspective to work with J2EE projects. Click Window > Open Perspective > Other > J2EE.
  3. (Optional)   Open the J2EE Hierarchy view. Click Window > Show View > J2EE Hierarchy. Other helpful views include the Project Navigator view (Window > Show View > Other > J2EE > Project Navigator) and the Navigator view (Window > Show View > Navigator).
  4. Create a new application EAR file or edit an existing one.

    Note: Ensure that you have Enabled Server Target support for J2EE projects and that you set the target server as Integration Server v5.1 or WebSphere Application Server EE v5.0.

    For example, to change attributes of an existing application, use the import wizard to import an EAR file. To start the import wizard:

    1. Select File > Import > EAR file > Next
    2. Select the EAR file.
    3. In the Target server field, select Integration Server v5.1 or WebSphere Application Server EE v5.0
    4. Select Finish

  5. In the J2EE Hierarchy view of the J2EE perspective, right-click the EJB module, then select Open With > Deployment Descriptor Editor.
    A property dialog notebook for the Enterprise Java Bean (EJB) project is displayed in the property pane.
  6. In the property pane, select the Extended Access tab.
  7. Beneath the Defined Access Intent Policies panel, select Add.
  8. Specify a unique name by which the policy is referenced when applied to entity beans.
  9. (Optional)   Specify a description of the policy.
  10. Specify an access type.
  11. 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.
  12. 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.
  13. 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.




Searchable topic ID:   tapp_axicus
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/tasks/tapp_axicus.html

Library | Support | Terms of Use | Feedback