| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSeries and weblogic: which interaction way prefer? |
« View previous topic :: View next topic » |
| Author |
Message
|
| preich |
 Posted: Fri Oct 14, 2005 5:09 am Post subject: MQSeries and weblogic: which interaction way prefer? |
 |
|
Novice
Joined: 12 Oct 2005
Posts: 15
|
Hello.
I need to interact from application running on weblogic 8.1sp5 with mqseries6. Which way of interaction you prefer and why?
So, application should receive messages from MQSeries topic, skip and clear invalid messages and put messages back to queue.
I know next variants of interaction with mqseriss:
1.weblogic integration provides event generator that can acquire messages from mqseries. Which transaction-related issues are bad in that variant, by your opinion? Another issue, that on incorrect (non-XML in my case) messages i can (with event generator settings) only throw message to another queue, but i can't create queue on mqseries server (i'm not admin on that server)
2.Foreign JMS provider
With JMSAdmin application from websphere mqseries/win32 i have created File JNDI context (fscontext) and define queuemanager, queue items.
So, in weblogic i create foreign JMS provider that connects to FS context and acquire queuemanager, queue (strange - not ask for channel). In event generator i have create JMS Event Generator, but on start weblogic i have problem:
javax.jms.JMSSecurityException: MQJMS2013: for MQQueueManager used incorrect authentication credentials.
But no passwords setted for fscontext/mqseries. What's problem here?
3.Java Connector architecture adapter for MQSeries.
Provided by BEA
Which way is most preferred and why? As easiest i choose first, but what's about perfomance, security, transaction and other params of choose a best deal?
Thanks! |
|
| Back to top |
|
 |
| preich |
| Posted: Thu Oct 20, 2005 3:03 am Post subject: answer |
|
|
Novice
Joined: 12 Oct 2005
Posts: 15
|
http://www.topsecurity.dk/examples/servlet/View?id=2249
/**
* Setting up authorisation username. Used by classes in com.ibm.mqjms.jar
* Setting up queue connection factory (QCF)
* Setting up name of queue, as defined in the MQ setup
* Setting up url for file-based, external JNDI provider
* Setting up context factory to use with external JNDI
*/
public String mq_username = "Administrator";
public String mq_qcf = "TOPSECURITY_QCF";
public String mq_qname = "TOPSECURITY.QUEUE";
public String mq_url = "file:/C:/jms-jndi-directory";
public String mq_jndi = "com.sun.jndi.fscontext.RefFSContextFactory";
And problem resolved |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Oct 20, 2005 9:39 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
That's not security, your're just expoiting a security hole.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| preich |
| Posted: Fri Oct 21, 2005 5:50 am Post subject: |
|
|
Novice
Joined: 12 Oct 2005
Posts: 15
|
Of course, not Administrator, but low privelleged user.
btw, how can you resolve that problem without changing of user.name?
Thanks. |
|
| 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
|
|
|
|
