[Version 5.0.2 and later]Automatically configuring application profiles and tasks

Why and when to perform this task

You can automatically configure application profiling for an application through static analysis.

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. Be sure that the application and its modules successfully compile. To include Java Server Pages (JSPs) in the analysis, you must precompile the JSPs. Also, be sure that you have configure all transactional attributes before analyzing.
  6. In the J2EE Hierarchy view of the J2EE perspective, right-click the Enterprise Application to configure, then select Open With > Deployment Descriptor Editor.
    A property dialog notebook for the application project is displayed in the property pane.
  7. In the property pane, select the Extended Services tab.
  8. Beneath the Application Profiles table, select Auto....
  9. Select the projects to be analyzed and configured. Select Next.
  10. To limit the returned results of the analysis, choose closed world analysis.
    Closed world analysis generates application profiles only if a client entry point in a message driven bean (MDB), servlet, JSP, or application client is resolved that begins a transaction and enlists entities. If closed world is not selected, the analysis returns the set of application profiles for all possible transactions represented by the application.

    Note: At this point you can also choose the Clean attribute. If you set this attribute, the existing configuration of selected modules is removed and the new configuration is applied fresh. If you do not select this option, the new configuration is merged into the existing configuration.

  11. Choose the concurrency for the default configuration of the access intent for generated application profiles.
  12. Select Analyze > Next.
  13. Examine the results of the analysis.
    Each top-level entry in the table represents a transaction identified by the analysis. The nested entries represent the callers of the transaction, the entities enlisted by the transaction, and the attributes read or modified during the course of the transaction.
  14. Select Finish to automatically configure the container-managed tasks and application profiles represented by the analysis.

Related concepts
Application profiling: Overview
Automatic configuration of application profiling
Related tasks
Assembling applications for application profiling



Searchable topic ID:   tapp_autoconfig
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_autoconfig.html

Library | Support | Terms of Use | Feedback