Use this task to assemble an application to use one-phase
and two-phase commit resources within the same transaction.
Before you begin
You must have an EAR file for an application component that
can be deployed in WebSphere Application Server. For more details
about assembling applications, see
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 increased
risk of an heuristic outcome. You can configure the deployment attributes
of an application by using an assembly tool.
Alternatively, you can configure the
transaction service for an application server to accept the heuristic
hazard so that last participant support (LPS) is enabled for all applications
that run on that server.
This topic describes how to configure
the deployment attributes of an application using the Application
Server Toolkit. To configure an application to accept the increased
risk of an heuristic outcome, use the following steps.
Procedure
- Start the assembly tool. For more information
about starting the Application Server Toolkit, refer to the Application
Server Toolkit information in the navigation pane of this information
center.
- Create or edit the application EAR file.
Note: Ensure that you set the target server as WebSphere
Application Server version 6.
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 File-> Import-> EAR file
- Click Next, then select the EAR
file.
- In the Target server field, select WebSphere
Application Server v6.0
- Click Finish
- In the J2EE Hierarchy view, complete the following steps:
- Expand the Enterprise Application instance.
- Right click on the Deployment Descriptor.
- Click Open With > Deployment Descriptor Editor.
A property dialog notebook for the component is displayed
in the property pane.
- In the property pane, select the Extended Services tab.
If you are using an IBM Rational Software Development Platform and
do not see the Extended Services tab, complete the following steps:
- Close the Enterprise Application Deployment Descriptor
editor.
- In the toolbar select .
- In the left pane, select Capabilities.
- In the right pane, expand Advanced J2EE and
select the WebSphere PME Development option.
- Click Apply.
- Open the Enterprise Application Deployment Descriptor
editor and you should see the Extended Services page.
- 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 indicate
that you want to save changes to the deployment descriptor.
- Verify the archive files. For more information
about verifying files using the Application Server Toolkit, refer
to the Application Server Toolkit information in the navigation pane
of this information center.
- 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 for unit testing
only. 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 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
Deploying and administering J2EE applications.