The transaction object store can be configured with JDBC. Then transactional data is stored in database.

The object store has to be configured to have a link to an non-xa non-jta datasource. These data are then used for connection to database where transaction log is stored.

The way of definition of the tx object store as jdbc has two variants.

• Either to use JDBC_STORE_JNDI_NAME which reuses already existing datasource.
• Using `TX_DATABASE_PREFIX_MAPPING` which should work in the same way as `DB_SERVICE_PREFIX_MAPPING` works (see doc at https://doc-stage.usersys.redhat.com/documentation/en-us/jboss_enterprise_application_platform_continuous_delivery/18/html-single/getting_started_with_jboss_eap_for_openshift_container_platform/index#datasources). It creates the datasource and defines the object store to use it.

If the datasource creation with `TX_DATABASE_PREFIX_MAPPING` is used then only mysql and postgresql driver names are permitted to be used. The code has to allow to use the '`PREFIX`_DRIVER' as name of driver which is linked for the created datasource.