Consider the points discussed in this section to plan the resource manager. Based on the resource manager that you select and how you use it, the configuration requirements varies for your application.

• Supported Resource Managers
  The transaction participant services may use a resource manager to store application data.
• Supported Drivers for Resource Managers
  It is the application developer's responsibility to select the correct JDBC driver and UCP version, if required, that works with the resource manager that you want to use.
• Optimizations for a Non-XA Resource
  Use the Logging Last Resource (LLR) or Last Resource Commit (LRC) optimization to enable one non-XA resource to participate in a global transaction.
• Common Resource Manager for Multiple Apps
  When you use a common resource manager for multiple participant services, MicroTx can optimize the commit processing resulting in higher throughput and lower latency for XA transactions.
• Configure Multiple Resource Managers for a Single App
  You can use multiple resource managers for a single participant service. Based on the business logic, a participant service can connect to multiple XA-compliant resource managers. However, only one non-XA resource is supported in a transaction.
• About Dynamic Recovery for XA Transactions
  The transaction coordinator server resumes the transactions that were in progress when server the restarts after a failure.