Automatically configuring application profiles and tasks

 

Overview

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

 

Procedure

  1. Start the Application Server Toolkit.

  2. Optional: Open the J2EE perspective to work with J2EE projects. Click Window > Open Perspective > Other > J2EE.

  3. Optional: Open the Project Explorer view. Click Window > Show View > Project Explorer. Another helpful view is the Navigator view (Window > Show View > Navigator).

  4. 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:

    1. Select File > Import > EAR file > Next

    2. Select the EAR file.

    3. Create a WAS v6 type of Server Runtime. Select New to open the New Server Runtime Wizard and follow the instructions.

    4. In the Target server field, select WebSphere Application Server V6.0 type of Server Runtime.

    5. Select Finish

  5. Be sure that the application and its modules successfully compile. To include Java Server Pages (JSP) files in the analysis, you must precompile the pages. Also, be sure that you have configured all transactional attributes before analyzing.

  6. In the Project Explorer view of the J2EE perspective, right-click the Deployment Descriptor: Enterprise Application Name under the Enterprise Application, then select Open With > Deployment Descriptor Editor. A property dialog notebook for the Enterprise Application project is displayed in the property pane.

  7. In the property pane, select the Extended Services tab.

  8. Beneath the Application Profiling 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 one 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.

 

See Also


Application profiling: Overview
Automatic configuration of application profiling

 

Related Tasks


Assembling applications for application profiling