[Version 5.0.2 and later]Applying profile-scoped access intent policies to entity beans

Why and when to perform this task

Configure entities with access intent for an application profile

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 for the application profile instance, then select Open With > Deployment Descriptor Editor.
    A property dialog notebook for the EJB project is displayed in the property pane.
  6. Select the Extended Access tab.
  7. Select the application profile for which you want to specify the access intent.
  8. Beneath the Access Intent for Entities 2.x (Profile Level) panel, select Add...
  9. Select the entities to configure and click Next....
  10. Select the access intent policy to apply. Select Read Ahead Hint if a read ahead hint is desired.
  11. Select Next.
  12. (Optional)   Specify the collection scope
    Transaction
    This is the default. Collections of entities cannot be used beyond the scope of the transaction in which you create the collection.
    ActivitySession
    Collections of entities cannot be used beyond the scope of the ActivitySession in which you create the collection. The collection can be used in a new transaction if that transaction is nested under the original ActivitySession, although you might have to reload the object by querying the underlying data store.
  13. (Optional)   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 for access types that result in U locks is 1. Otherwise, the default is 25.
  14. (Optional)  
  15. Specify the resource manager prefetch increment.
    Specify a valid integer to set as the fetch size on the JDBC statement when you execute queries for a bean type. The default is 0.
  16. Select Next.
  17. If you selected read ahead, choose the preload path.
  18. Select Finish to apply.
  19. Select OK.

Related tasks
Automatically configuring application profiles and tasks



Searchable topic ID:   tapp_entaxiapp
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_entaxiapp.html

Library | Support | Terms of Use | Feedback