Author |
Message
|
broker_new |
Posted: Wed Jan 09, 2013 9:08 am Post subject: WMBv8.0.0.1-> Oracle Messaging Gateway with MQ Integratio |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
Hi Guys,
We were using support pac ma0i in the past to integrate the oracle with mq using the MQ client and CCDT file on oracle. As it is no longer supported we are looking for the alternatives of achieving this.
i know implementing this using the other methods using message broker, but we would like to use OMG to replace this support pac..
Did anyone successful in configuring the OMG?
If yes, how does it support the multi instance queue managers?
 _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Jan 09, 2013 9:22 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
The reason the support pak was discontinued was that it was no longer needed. Since all products you mentioned can read/write JMS queues, there is no longer a need for a gateway. JMS is the gateway. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
broker_new |
Posted: Wed Jan 09, 2013 9:42 am Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
If an oracle stored procedure or oracle job needs to integrate with JMS..it has to go through the OMG which will create the links between the Oracle Advance Queues to MQ queues, without OMG it can't directly interface with MQ. _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jan 09, 2013 9:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
The point is to configure OMG to use a JMS configuration to talk to MQ. |
|
Back to top |
|
 |
broker_new |
Posted: Tue Jan 22, 2013 12:49 pm Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
Hi Guys,
After following the following instructions from Oracle creating the agent
http://docs.oracle.com/cd/B28359_01/server.111/b28420/mg_work.htm
and actual message propagation and creating the links using
http://www.ibm.com/developerworks/websphere/library/techarticles/0807_tuli/0807_tuli.html
encountered the following exception during enqueueing the message in Oracle AQ queues.
15:44:21 ORA-24033: no recipients for message
Here is the command used for Enqueuing the message
DECLARE
queue_options DBMS_AQ.ENQUEUE_OPTIONS_T;
message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
message_id RAW(16);
p_xmlstring varchar2(3000);
queue_name_val varchar2(100);
v_agent sys.aq$_agent := sys.aq$_agent(' ', null, 0);
v_jms_message sys.aq$_jms_text_message;
enqueue_options dbms_aq.enqueue_options_t;
msgid raw(16);
BEGIN
queue_name_val := 'OMG_SAMPLE_QUEUE';
v_jms_message := sys.aq$_jms_text_message.construct;
v_jms_message.set_replyto(v_agent);
v_jms_message.set_type('mcd://xmlns');
v_jms_message.set_text(p_xmlstring);
DBMS_AQ.ENQUEUE(
queue_name => queue_name_val,
enqueue_options => queue_options,
message_properties => message_properties,
payload => v_jms_message,
msgid => message_id);
END;
Any inputs?  _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Jan 23, 2013 5:36 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
The article was written in 2008, well before the modern incarnations of all these products. Contact the article's author to get an update.
In the mean time, as was previously stated, JMS is the way to go. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
broker_new |
Posted: Wed Jan 23, 2013 6:32 am Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
I agree with you.
We have looked at the other option by loading the MQclient class files and all other related dependent jars using the loadjava which doesn't work (as classpath is not helping in this case),will contact the author as suggested!! _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Jan 23, 2013 7:44 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
broker_new wrote: |
I agree with you.
We have looked at the other option by loading the MQclient class files and all other related dependent jars using the loadjava which doesn't work (as classpath is not helping in this case),will contact the author as suggested!!
---------------------------------
IBM ->On Demand Business
|
You seem dense.
No where in this would you use MQclient jars.
WMQ can read+write jms queues without any additional software.
Oracle products can read+write jms queues without any additional software.
MQclient jars are neither needed or desired.
Since you are having so much difficulty, you might like to attend a training class or two. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Jan 23, 2013 9:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
lancelotlinc wrote: |
broker_new wrote: |
I agree with you.
We have looked at the other option by loading the MQclient class files and all other related dependent jars using the loadjava which doesn't work (as classpath is not helping in this case),will contact the author as suggested!!
---------------------------------
IBM ->On Demand Business
|
You seem dense.
No where in this would you use MQclient jars.
WMQ can read+write jms queues without any additional software.
Oracle products can read+write jms queues without any additional software.
MQclient jars are neither needed or desired.
Since you are having so much difficulty, you might like to attend a training class or two. |
I'm going to have to disagree with your police work.
Any application that is establishing a JMS connection to an MQ queue manager needs the corresponding MQ JMS Provider classes available to it.
Just like any application that is establishing a JMS connection to an Oracle AQ system needs the corresponding Oracle JMS Provider classes available to it.
And any application that is establishing a JMS connection to a WebLogic JMS system needs the corresponding WebLogic JMS Provider classes available to it.
So an Oracle Messaging Gateway that is going to read messages from an Oracle AQ and forward them to a WebSphere MQ (or the other way, or both directions) needs both the Oracle AQ JMS Provider classes and the WebSphere MQ JMS Provider classes available to that application.
This is JMS 101... did you attend training on JMS, lancelotlinc?
The only supported way to use the MQ JMS Provider classes is to install either the MQ Server or the MQ Client on the relevant machine.
Then the necessary jar files need to be added to the relevant classpath for the relevant classloader. How you configure Oracle Messaging Gateway to do this, I don't know. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Jan 23, 2013 10:59 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
Back to top |
|
 |
smdavies99 |
Posted: Wed Jan 23, 2013 11:06 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
lancelotlinc wrote: |
I'll read it more carefully after my meeting.
|
Is this your belated new years resolution by any chance?  _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Jan 23, 2013 12:38 pm Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
The answer is to install the wmq.jmsra.rar resource adpater that is shipped with WMQ as a JCA 1.5 resource adapter on any J2EE application server you choose, including those from Oracle, Sun, or Apache. Then, you can configure jms reads and writes to use that resource and the resulting transactions will show up in WMQ queues, which can then be read by WAS or WMB.
Again, not rocket science, and with a little digging using Google, an easy answer. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
broker_new |
Posted: Wed Jan 23, 2013 3:19 pm Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
Atlast we fixed the problem...queue was subscribed incorrectly which was causing that error.
Removed all the configuration and started from scratch again.
1. remove_subscriber
2.unschedule_propagation
3.unregister_foreign_queue
4.remove_msgsystem_link
5.Shutdown gateway agent
6.Start gateway agent
The following link was very useful to configure the OMG for inbound and outbound messages to Oracle.
http://haiyanliang.wordpress.com/2008/09/23/oracle-11g-message-gateway-testing-with-ibm-websphere-mq-v7/ _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
broker_new |
Posted: Fri Jan 25, 2013 8:16 am Post subject: |
|
|
 Yatiri
Joined: 30 Nov 2006 Posts: 614 Location: Washington DC
|
MGW (Messaging gateway ) has limitation when working with cluster queue managers, queue manager groups as it maintains a inbound and outbound log queues which basically keeps track of the previous message propagated from the AQ queue to MQ local queue. The log queue is maintained at MQ level.
So when the client connection fails over to other active queue manager in the group or other cluster local queue on other queue manager the stranded message in the log queue is not available for the other queue manager...the propagation fails from oracle.
it applies to load balancing of the messages across multiple queue managers in the queue manager group. _________________ IBM ->Let's build a smarter planet |
|
Back to top |
|
 |
|