| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMQ 5.x and WebSphere 5.x JMS/MQ and client mode transport |
« View previous topic :: View next topic » |
| Author |
Message
|
| mdc |
 Posted: Tue Apr 08, 2008 12:37 pm Post subject: WMQ 5.x and WebSphere 5.x JMS/MQ and client mode transport |
 |
|
Novice
Joined: 08 Apr 2008
Posts: 12
|
I have a mix of applications, some of which are standalone Java applications that use MQ 5.x and also a J2EE app on WebSphere 5.x that use the embedded JMS provider.
I would to make the Java applications and WebSphere 5.x JMS/MQ Provider use the client mode of transport instead of the bindings mode when passing MQ messages between them. Eventually I will move the apps on to different systems and requires sockets to communicate.
I noticed that you can call setter methods on the JMS/MQ connection factories to turn on client mode of transport; however, I am looking for a way to set client transport mode as a default for all applications at an administrative configuration level, without having to modify application source.
How is that accomplished and any tips and pointers on how to do it quickly? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Apr 08, 2008 12:40 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
 MQ v5.x is out of support.
Be warned - switching from server to client connections can prevent the application from using an XA Connection, and thus break the transactional needs of the application.
Thirdly, if your client apps are properly written to use JNDI to look up QCF and TCF objects, then you can just adjust those administratively and not have to have any code.
If your client apps are NOT written to use JNDI to look these objects up, then you should change them to do THAT, rather than to manually change the transport properties in the code.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mdc |
| Posted: Tue Apr 08, 2008 3:08 pm Post subject: |
|
|
Novice
Joined: 08 Apr 2008
Posts: 12
|
>if your client apps are properly written to use JNDI to look up QCF and TCF >objects, then you can just adjust those administratively and not have to >have any code.
Is this just a case of writing the QCF into JNDI with the client mode set? What IBM documentation describes this. I am familiar with JNDI lookups of the factory, but not the parameterization of the its properties to set client mode transport.
The point about 5.x is taken and IBM is addressing through their hosting services. |
|
| 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
|
|
|
|
