The Liberty profile provides many of the same transaction services that are provided in the WebSphere® Application Server full profile. If an application uses two or more resources, the Liberty profile transaction manager coordinates the updates to all the resource managers under a global transaction. In the Liberty profile, transaction services are implicitly activated when you specify features that require the use of transactions; for example, jpa-2.0, jdbc-4.0, and wasJmsServer-1.0.
About this task
You can control when database transaction recovery occurs, you can specify configuration settings that determine how database transactions are recovered, and you can choose whether to store your transaction logs as operating system files or in a relational database.
Subtopics
Liberty profile: Configuring the startup of the transaction service
Database transaction recovery can occur either when the transaction service is first used, or at server startup.- Liberty profile: How database transactions are recovered
When recovering any in-doubt database transactions, the Liberty profile transaction manager uses either the unique identifier or the JNDI name to locate the current dataSource element, and then determines the user ID and password to use for recovery. - Liberty profile: Storing transaction logs in a relational database
You can, optionally, choose to store your Liberty profile transaction logs in a relational database rather than as operating system files. In the WebSphere Application Server full profile, this feature provides high availability (HA) support without having to use a shared file system. The feature is provided in the Liberty profile for compatibility and for evaluation and testing purposes.
Task topic