[Version 5.0.2 and later]Configuring application-managed tasks for web components

Why and when to perform this task

Configure web components' application managed tasks to associate requests from a servlet or Java Server Page (JSP) with application profiles.

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 Web module for the web component instance, then select Open With > Deployment Descriptor Editor.
    A property dialog notebook for the web project is displayed in the property pane.
  6. In the property pane, select the Extended Services tab.
  7. Select the servlet or JSP that you want to change.
  8. Beneath the Application-Managed Tasks table, select Add....
  9. Specify the name of the task reference.
    The task reference name is used programmatically by the servlet or JSP. The task reference is the logical representation of the task that is used by the run time environment.
  10. Enter the name and description of the task.
    The task name is mapped to application profiles and used by the run time to determine the appropriate access intent to use for enlisted entities. Task names do not have to be unique within an application. However, task names should be shared consciously and conservatively. At run time, all tasks with the same name are treated the same way, regardless of where you configured the task.

    The description is provided for your convenience, it is not used by the run time environment.

  11. Select OK.

Related tasks
Configuring container managed tasks for web components
Using the TaskNameManager interface
Creating an application profile



Searchable topic ID:   tapp_webamtask
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_webamtask.html

Library | Support | Terms of Use | Feedback