Can Oracle Tuxedo repalce IBM mq connectivity from mainframe

Question

Hi all,
I am new to Oracle Tuxedo i have some basic question we are facing some issues with the IBM MQ with mainframe .
Can we repalce IBM MQ and can we use oracle tuxedo . How end systems that are connecting to MQ will connect to Tuxedo did they use JMS?
Thanks
Phani

Answer 1

Hi Phani,
You don't need to use JMS to use Tuxedo's /Q facility. It is an option if you already are using JMS.
Any system that supports Tuxedo client install can access Tuxedo /Q queues. On the mainframe this could be done with the zLinux version of Tuxedo. Other systems such as AIX, Linux, Windows, etc., also have client kits that can enqueue and dequeue messages from Tuxedo /Q.
The WebLogic Tuxedo connector can:
1) take messages from a JMS queue and place them on a Tuxedo /Q queue
2) take messages from a Tuxedo /Q queue and place them on a JMS queue
3) take message from a JMS queue and directly call a Tuxedo service with that message
The performance of /Q is good, although how good depends upon the quality of service chosen. /Q supports both persistent (disk based) and transient (memory based) queues, and it also supports XA so /Q queues can be part of a distributed transaction (syncpoint in mainframe terminology.)
zLinux is not a widely used Tuxedo platform. However Tuxedo /Q is used quite a bit in projects where customers are moving their mainframe applications off of the mainframe and onto Tuxedo due to cost and performance concerns. Many customers headed down this path use our Application Runtime for Tuxedo (ART) which besides supporting the rehosting of CICS applications, also provides a JES-2 like batch subsystem that heavily uses /Q.
I believe you are currently doing:
non-mainframe MQ Series mainframe
application using MQ <====> Queue <=====> application using
API (MQI) Manager MQ API
What I'm suggesting is:
non-mainframe Tuxedo mainframe application
application using Tuxedo <====> /Q Queue <=====> using Tuxedo API
API to access /Q Manager to access /Q
Although the more common scenario when dealing with mainframes is to use the Tuxedo Mainframe Adapter (TMA). TMA provides a bi-directional transactional gateway between mainframe applications and Tuxedo applications. Using TMA, CICS applications see Tuxedo services as DPL or APPC based transactions, and Tuxedo sees CICS transactions as Tuxedo services. Thus a Tuxedo service (or client) can directly invoke a CICS transaction in exactly the same manner that it invokes another Tuxedo service. The service/client is unaware that the provider of the service invoked is actually some transaction running on CICS. Likewise a CICS application simply uses DPL or APPC to invoke a remote transaction, and that transaction actually ends up being a Tuxedo service running somewhere on Tuxedo. If using the SNA version of the gateway, one can use syncpoint level 2 for guaranteed integrity of updates made both on CICS and Tuxedo.
Regards,
Todd Little
Oracle Tuxedo Chief Architect