| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Database access from WMB - ODBC vs. Adapter |
« View previous topic :: View next topic » |
| Author |
Message
|
| 4integration |
 Posted: Tue Oct 31, 2006 1:54 pm Post subject: Database access from WMB - ODBC vs. Adapter |
 |
|
Disciple
Joined: 04 Sep 2006
Posts: 197
Location: Gothenburg, Sweden
|
Hello,
We have a need for accessing a database from a message flow in WMB 6.
What is your experience in using ODBC versus WBI Adapter?
Performance?
Stability?
Functionality?
...? |
|
| Back to top |
|
 |
| msukup |
| Posted: Sat Nov 04, 2006 4:07 pm Post subject: |
|
|
Acolyte
Joined: 11 Feb 2002
Posts: 56
|
Here is our experience with ODBC through WMB (merant drivers):
* if you are connecting to DB2, you might consider configuring db for loopback, as it allows more numerous conns. Each thread of msg flow requires a connection.
* conn to db over a firewall may cause timeout and restart of e.g. because of firewall settings
* conn to Sybase databases do not have as many fixes to Merant ODBC drivers as those for DB2 and Oracle. Disconnect errors seem to persist rather than having a reconnect after first failed message.
Generally stable as long as db itself is configured correctly, obviously not as high performance as a client conn (OCI client, for instance), but comparable to JDBC thin client (someone might correct me on that)
I'm not sure if WBI Adapters use configurable thin or thick clients with JDBC? If there is a thick client configuration, I imagine that you might have some performance savings with an adapter, but ODBC through WMB is dependable with a properly configured db. |
|
| Back to top |
|
|
| sr_aguilar |
| Posted: Wed Nov 22, 2006 10:33 am Post subject: |
|
|
Newbie
Joined: 11 Apr 2006
Posts: 4
|
| This is an casually db, because you can use JDBC with a java compute too. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 23, 2006 6:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The WBI adapters are an additional layer of complexity that are almost always unnecessary.
The two cases when they are necessary are as follows: 1) When you need to start a message flow when someone makes a change to a database table, b) when you need to interact with a database that is not supported from WMB.
One can make arguments for using the WBI Adapters to interact with databases as a means of isolating the database logic. But one can counter those arguments with the performance and complexity hits of having to build new MQ messages and etc.
And certainly, if the customer is already using them - then you might as well leverage that for anything even modestly complicated.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
