[Version 5.0.2 and later]Assembling an application to use one-phase and two-phase commit resources in the same transaction

Use this task to assemble an application to use one-phase and two-phase commit resources within the same transaction.

Why and when to perform this task

To enable an application to use one-phase and two-phase commit capable resources within the same transaction, you must configure the deployment attributes of the application to accept the increased risk of an heuristic outcome.

You can configure the deployment attributes of an application by using the Deployment Descriptor Editor of WebSphere Studio Application Developer or the Assembly Toolkit.

This task description assumes that you have an EAR file for an application component, that can be deployed in WebSphere Application Server. For more details about using the Assembly Toolkit, see Assembling applications with the Assembly Toolkit.

To configure an application to indicate that you accept the increased risk of an heuristic outcome, complete the following steps:

Steps for this task

  1. Starting the Assembly Toolkit
  2. Create or edit the application EAR file.

    Note: Ensure that you set the target server as WBI Server Foundation v5.1.

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

    1. Click File-> Import-> EAR file
    2. Click Next, then select the EAR file.
    3. In the Target server field, select WBI Server Foundation v5.1
    4. Click Finish
  3. In the J2EE Hierarchy view, right-click the Enterprise Application instance, then click Open With > Deployment Descriptor Editor.
    A property dialog notebook for the component is displayed in the property pane.
  4. In the property pane, select the Extended Services tab.
  5. In the Last Participant Support section, select the Last participant support checkbox.
  6. Save your changes to the deployment descriptor.
    1. Close the Deployment Descriptor Editor.
    2. When prompted, click Yes to indicate that you want to save changes to the deployment descriptor.
  7. Verify the archive files.
  8. Generate code for deployment for EJB modules or for enterprise applications that use EJB modules.
  9. (Optional)   Test your completed module on a WebSphere Application Server installation. Right-click a module, click Run on Server, and follow the instructions in the displayed wizard. Note that Run on Server works on the Windows, Linux/Intel, and AIX operating systems only; you cannot deploy remotely from the Assembly Toolkit to a WebSphere Application Server installation on a UNIX operating system such as Solaris.

    Important: Use Run On Server for unit testing only. Assembly Server Toolkit controls the WebSphere Application Server installation and, when an application is published remotely, the Toolkit overwrites the server configuration file for that server. Do not use on production servers.

    For instructions on remote testing, see the article "Setting Up a Remote WebSphere Application Server in WebSphere Studio V5" at http://www7b.boulder.ibm.com/wsdd/techjournal/0303_yuen/yuen.html .

What to do next

After assembling your application, use a systems management tool to deploy the EAR file onto the application server that is to run the application; for example, using the administrative console as described in Deploying and managing applications.

Related concepts
Coordinating access to 1-PC and 2-PC-capable resources within the same transaction
Related tasks
Using one-phase and two-phase commit resources in the same transaction
Assembling applications with the Assembly Toolkit
Related reference
Last participant support extension settings



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

Library | Support | Terms of Use | Feedback