|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ Series for Two Phase Commit |
« View previous topic :: View next topic » |
Author |
Message
|
vivekkooks |
Posted: Tue Jul 08, 2003 10:42 pm Post subject: MQ Series for Two Phase Commit |
|
|
 Voyager
Joined: 11 Jun 2003 Posts: 91
|
Hello,
I have Installed MQSeries for Linux/Intel.
Can I use unixODBC driver manager as database resource manager in MQ Series Two Phase Commit Protocol.?
thanks, |
|
Back to top |
|
 |
bduncan |
Posted: Wed Jul 09, 2003 4:12 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
|
What database are you using, what driver are you using (be more specific than ODBC), and what language are you planning on writing your app in? Plus, who do you need the transaction coordinator to be, MQ or the database? _________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
Back to top |
|
 |
vivekkooks |
Posted: Wed Jul 09, 2003 9:15 pm Post subject: |
|
|
 Voyager
Joined: 11 Jun 2003 Posts: 91
|
I am planning to write the application in C++. The application design is required to be database independent(it may be oracle, DB2, sybase or any other database). The scenario is as follows:
App1+ db1(linux/intel)
|
|
|
|
App2 + db2(linux/intel)
App1 retrieves the data from db1(it may be any database), forms the message, send it to app2 ,update db1 tables and commits this global unit of work so that message will be available for App2.
App2 will retrieve the message, update db2(it may be any database) and commit this unit of work so that message is removed from the queue.
I am planning to use MQ as transaction coordinator on both the systems.
So, in this case can I use ODBC driver manager(eg unixODBC) for the database operations on both the systems or I have to use the embedded SQL as given in the samples of MQ Series? |
|
Back to top |
|
 |
bduncan |
Posted: Thu Jul 10, 2003 9:51 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
|
You can't use the standard ODBC driver. You must use an XA compliant driver, which is database specific. In other words, to have MQ and Oracle do XA transactions, you'll have to get a special XA driver from Oracle. Also, you must define all the possible databases you'll be doing XA transactions with in the queue manager itself, at design time. You can have the same queue manager do XA with Oracle and DB2 for instance. You'll just have to define those connections ahead of time. So your application won't be able to connect to an arbitrary database at run-time and do XA if it wasn't defined in the queue manager beforehand. _________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|