How to use Tuxedo's services from an EJB: Jolt x JET ?

Question

Hi.
Can anyone tell me if an EJB MUST use JET (instead Jolt) to access Tuxedo services
Suppose the following case:
We have a client using JNDI service to obtain an EJB.
In my client i invoke the appropriate methods to create a jolt session and to
start a jolt transaction. My EJB Bean only call Tuxedo services (using Jolt).
Will this application work ? Will EJB code use the transaction created by the
client code ? Will a transaction context exist ?
Thanks in advance.

Answer 1

Hi Daniel,
If you mean WebLogic Server 5.1 by WL 5.1 (instead of WebLogic Enterprise), then
yes, you need to use Jolt until you upgrade to a later release of WebLogic Server.
WTC wasn't fully supported until WebLogic Server 6.1 and later.
The transaction context of the container Jolt is being used in is not extended
to the Tuxedo system. Jolt can be used to start a new and separate transaction
in Tuxedo, but that transaction and the containers current transaction will not
be coordinated.
I'm not sure what you mean when you say:
The transaction management when using Jolt is realized for Jolt API.
There is no relantionship between Jolt transactions and Tuxedo transactions.
Is this rightThe transaction management when using Jolt is transaction management of
the Tuxedo system you are talking to. Jolt is a client side API that uses a
delegated model for transactions. So a transaction started with Jolt starts
a transaction in Tuxedo, but does not affect the transaction context of the
environment the client, i.e., the place where the Jolt call was made. So if
you are using Jolt inside an EJB hosted in the EJB container of WebLogic
Server, the Jolt calls will have no impact or effect on the transaction state
of the EJB.
Regards,
Todd
"Daniel" <[email protected]> wrote:
>
Ok.
We have EJBs running in Weblogic and they are using Tuxedo services.
We have used Jolt instead WTC because we are running WL 5.1. Can i
use WTC with WL 5.1 ?
The transaction management when using Jolt is realized for Jolt API.
There is
no
relantionship between Jolt transactions and Tuxedo transactions. Is this
right
Thanks in advance.
"Todd Little" <[email protected]> wrote:
"Daniel" <[email protected]> wrote:
Hi.
Can anyone tell me if an EJB MUST use JET (instead Jolt) to access
Tuxedo
services
? You can use either Jolt or preferably use WTC and JATMI.
Suppose the following case:
We have a client using JNDI service to obtain an EJB.
In my client i invoke the appropriate methods to create a jolt session
and to
start a jolt transaction. My EJB Bean only call Tuxedo services (using
Jolt).Why is the client creating a Jolt session and transaction? They will
not be associated
with the EJB's execution. The client's Jolt context is not propogated
to the
EJB. Can you explain what it is you want to do? What do you want included
in
the transaction?
Will this application work ? Will EJB code use the transaction created
by the
client code ? Will a transaction context exist ?Well I suppose it depends upon what you mean by work. It comes down
to what are
you trying to accomplish. The client is a WLS client? Is the EJB a
client of
some Tuxedo service? If those are both true, then you would be best
served by
controlling the transaction with the EJB's deployment descriptor and
having the
EJB use WTC to access Tuxedo. WTC will take of propagating any required
transaction
state to Tuxedo.
Regards,
Todd