Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop Transactions > Develop components to use transactions > Use one-phase and two-phase commit resources in the same transaction


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 in the same transaction. This task description assumes that we have an EAR file for an application component that can be deployed in WAS. For more details about assembling applications, see the topic about assembling applications.

To enable an application to use one-phase and two-phase commit capable resources in the same transaction, configure the deployment attributes of the application to accept the heuristic hazard, that is, the increased risk of an heuristic outcome. We can configure the deployment attributes of an application by using an assembly tool.

We can also configure an application to accept the heuristic hazard after deployment, by using the administrative console and the Last participant support extension settings. Alternatively, you can configure the transaction service for an application server to accept the heuristic hazard.

This topic describes the use of Rational Application Developer to configure the deployment attributes of an application.

To configure an application to indicate that you accept the increased risk of an heuristic outcome...


Procedure

  1. Start the assembly tool. For more information, refer to the Rational Application Developer information.

  2. Create or edit the application EAR file.

    Ensure that you set the target server as WAS v7.0.

    For example, to change attributes of an existing application, use the Import wizard to import the EAR file into the assembly tool.

    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 WAS v7.0.

    4. Click Finish.

  3. In the Project Explorer view of the Java EE perspective...

    1. Expand the Enterprise Application instance.
    2. Right click on the Deployment Descriptor.

    3. Click Open With > Deployment Descriptor Editor.

    A property dialog notebook for the component is displayed in the property pane.

  4. Complete the following steps to display the Extended Services tab.

    1. Close the Enterprise Application Deployment Descriptor editor.

    2. In the toolbar, select Windows > Preferences.

    3. In the left pane, select Capabilities.

    4. In the right pane, expand Advanced Java EE and select the WebSphere PME Development option.

    5. Click Apply.

    6. Open the Enterprise Application Deployment Descriptor editor.

  5. On the Extended Services tab, in the Last Participant Support section, select the Last participant support check box.

  6. Save your changes to the deployment descriptor.

    1. Close the Deployment Descriptor Editor.

    2. When prompted, click Yes to save changes to the deployment descriptor.

  7. Verify the archive files. For more information about verifying files using Rational Application Developer, refer to the Rational Application Developer information.

  8. From the popup menu of the project, click Deploy to generate EJB deployment code.

  9. Optional: Test your completed module on a WAS installation. Right-click a module, click Run on Server, and follow the instructions in the displayed wizard.

    Use Run On Server only for unit testing. The assembly tool controls the WAS installation and, when an application is published remotely, the assembly tool overwrites the server configuration file for that server. Do not use the Run On Server option on production servers.


What to do next

After assembling the 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 the topic about deploying and administering enterprise applications.


Related


Last participant support extension settings
Coordination of access to one-phase commit and two-phase commit capable resources in the same transaction
Assembly tools
Assembling applications
Deploy and administering enterprise applications
Use one-phase and two-phase commit resources in the same transaction


Related


Transaction service settings
Rational Application Developer documentation

+

Search Tips   |   Advanced Search