Author |
Message
|
thindk00 |
Posted: Fri Sep 16, 2005 8:25 am Post subject: MQSeries as a JMS provider on Siebel |
|
|
Voyager
Joined: 16 May 2001 Posts: 75 Location: UK
|
Hi,
We're trying to use a JMS enable application to send messages to our MQSeries queues on a Sun Solaris platform. We're on WMQ 5.3. This is the first time I'm using the JMS interface so I apologise in advance if the questions are basic or sound silly.
I understand that WMQ qill act as a JMS server for the application, which will act as a JMS client. I understand there is some configuration that needs to be done. Could someone highlight what the main steps are? If there is a really useful guide that will cover this topic I would be grateful if you could pass a link on to that.
Many thanks,
Kulbir. |
|
Back to top |
|
 |
bower5932 |
Posted: Fri Sep 16, 2005 11:56 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Aug 2001 Posts: 3023 Location: Dallas, TX, USA
|
|
Back to top |
|
 |
Michael Dag |
Posted: Fri Sep 16, 2005 12:08 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
|
Back to top |
|
 |
Tibor |
Posted: Sat Sep 17, 2005 2:57 pm Post subject: |
|
|
 Grand Master
Joined: 20 May 2001 Posts: 1033 Location: Hungary
|
Michael Dag wrote: |
I thought Siebel supported MQSeries natively... |
MQ is supported by Siebel, but this is a very basic implementation and slow and buggy and ...
Tibor |
|
Back to top |
|
 |
thindk00 |
Posted: Sun Sep 18, 2005 2:22 pm Post subject: interesting |
|
|
Voyager
Joined: 16 May 2001 Posts: 75 Location: UK
|
interesting response. We're going with the Siebel 7.7 and Siebel 7.8 apps with the Siebel EAI JMS component for MQ integration. If you have any thing that we should be wary of I would appreciate any comments.
Thanks. |
|
Back to top |
|
 |
Tibor |
Posted: Mon Sep 19, 2005 2:54 am Post subject: |
|
|
 Grand Master
Joined: 20 May 2001 Posts: 1033 Location: Hungary
|
Perhaps my post was not quite true because Siebel (v7.5) MQSeries Server Transport works, but I am very discontent with it. Why? e.g. you can not:
- handle message desriptor on demand but only specific fields
- connect to any local/remote qmgr but only the *default* local qmgr
I hope the Java/JMS support is fine in the newer versions of Siebel. You can solve *anything* with Java/JMS MQ interface.
Tibor |
|
Back to top |
|
 |
|