Use this task to assemble an application to use one-phase
and two-phase commit resources in the same transaction.
Before you begin
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 assembling applications, see the topic
about assembling applications.
About this task
To enable an application to use one-phase and two-phase
commit capable resources in the same transaction, you must configure
the deployment attributes of the application to accept the heuristic
hazard, that is, the increased risk of an heuristic outcome. You can
configure the deployment attributes of an application by using an
assembly tool.
You
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, complete the following steps:
Procedure
- Start the assembly tool. For more information,
refer to the Rational Application Developer information.
- Create or edit the application EAR file.
Note: Ensure
that you set the target server as WebSphere Application
Server Version 7.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:
- Click .
- Click Next, then select the EAR
file.
- In the Target server field, select WebSphere Application
Server v7.0.
- Click Finish.
- In the Project Explorer view of the Java EE perspective,
complete the following steps:
- Expand the Enterprise Application instance.
- Right click on the Deployment Descriptor.
- Click .
A property dialog notebook for the component is displayed
in the property pane.
- Complete the following steps to display the Extended Services
tab.
- Close the Enterprise Application Deployment Descriptor
editor.
- In the toolbar, select .
- In the left pane, select Capabilities.
- In the right pane, expand Advanced Java EE and
select the WebSphere PME Development option.
- Click Apply.
- Open the Enterprise Application Deployment Descriptor
editor.
- On the Extended Services tab, in the Last Participant Support
section, select the Last participant support check
box.
- Save your changes to the deployment descriptor.
- Close the Deployment Descriptor Editor.
- When prompted, click Yes to save
changes to the deployment descriptor.
- Verify the archive files. For more information
about verifying files using Rational Application Developer,
refer to the Rational Application Developer information.
- From the popup menu of the project, click Deploy to
generate EJB deployment code.
- 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.
Important: Use Run On Server only for
unit testing. The assembly tool controls the WebSphere Application
Server 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 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 the topic about deploying and administering enterprise
applications.