Why are there restrictions using JNDI as the connection type when using JDBC activities in the transaction group?

Why are there restrictions using JNDI as the connection type when using JDBC activities in the transaction group?

book

Article ID: KB0091081

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks -
Not Applicable -

Description

Resolution:
Description:
============
Why are there restrictions using JNDI as the connection type when using JDBC activities in the transaction group?

Environment:
==========
TIBCO ActivMatrix BusinessWorks 5.7.x, 5.8.x,5.9.x,5.10.x,5.11.x.
All Operating Systems

Symptoms:
========
In TIBCO ActiveMatrix BusinessWorks Process Design Guide -- > Chapter 11 Transactions -- > Configuring JTA User Transaction Transactions.

==================================
JDBC Connections used by JDBC activities in the transaction group must be configured to use JNDI as the connection type and specify the data source in the application server.
==================================

Reason:
=========
With JTA UserTranscations, transaction manager takes care of enlisting  and delisting resources. For this,  transaction resources (like JDBC connections) need to be available through JNDI lookup. If you do not have JNDI lookup, the application needs to do most of transaction manager's work.

Issue/Introduction

Why are there restrictions using JNDI as the connection type when using JDBC activities in the transaction group?