Use this task to configure the transactional deployment descriptor attributes associated with an EJB or Web module, to enable a J2EE application to use transactions.
Why and when to perform this task
This topic describes the use of the Assembly Toolkit to configure the deployment attributes of an application. 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 set transactional attributes in the deployment descriptor for an application component (enterprise bean or servlet), complete the following steps:
Steps for this task
This setting specifies the containment boundary at which all contained resource manager local transactions (RMLTs) must be completed. Possible values are Bean method or ActivitySession.
Note: The ActivitySession option is not supported in the web container.
This setting specifies the component responsible for initiating and ending RMLTs. Possible values are Application or ContainerAtBoundary.
Specifies the direction that the container requests RMLTs to take, if they are unresolved at the end of the LTC boundary scope and the Resolver is set to Application. Possible values are Rollback or Commit.
If the application uses ActivitySessions, how the container manages transaction boundaries when delegating a method invocation depends on both the Transaction attribute attribute, set here, and the ActivitySession kind attribute, as described in Setting EJB module ActivitySession deployment attributes with the Assembly Toolkit. For more detail about the relationship between these two properties, see Combining transaction and ActivitySession container policies.
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.
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.