| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMS/WebSphere Liberty/JSON CCDT |
« View previous topic :: View next topic » |
| Author |
Message
|
| fswarbrick |
 Posted: Thu Jun 04, 2020 11:03 am Post subject: JMS/WebSphere Liberty/JSON CCDT |
 |
|
Apprentice
Joined: 07 Jul 2014
Posts: 42
|
| Before I go on a possibly fruitless search, can JMS applications running under WebSphere Liberty make use of the new JSON CCDT? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jun 05, 2020 3:36 am Post subject: Re: JMS/WebSphere Liberty/JSON CCDT |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| fswarbrick wrote: |
| Before I go on a possibly fruitless search, can JMS applications running under WebSphere Liberty make use of the new JSON CCDT? |
I don't believe that the embedded MQ client is at a version that will allow you to take advantage of this new feature! 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| fswarbrick |
| Posted: Fri Jun 05, 2020 7:59 pm Post subject: Re: JMS/WebSphere Liberty/JSON CCDT |
|
|
Apprentice
Joined: 07 Jul 2014
Posts: 42
|
| fjb_saper wrote: |
| fswarbrick wrote: |
| Before I go on a possibly fruitless search, can JMS applications running under WebSphere Liberty make use of the new JSON CCDT? |
I don't believe that the embedded MQ client is at a version that will allow you to take advantage of this new feature! |
Disappointing!
We have a new application being developed and they want to be able to connect to two sets of queues residing on two different queue managers. We currently only have one prod and one test/dev, but they are pushing for another of each, for obvious reasons. Yet they have developed their application in such a way that a single instance only connects to a single queue manager. Specifically, they get the connection information from a database and the database currently is (in this case) a simply key/value store kind of like the following:
MQ_MGR = <name of a queue manager>
MQ_HOST = <host address of a queue manager>
MQ_PORT = <port for the queue manager>
MQ_CHANNEL = <channel to be used to connect to MQ_MGR>
MQ_SSLPEER = <SSL encryption protocol for MQ_CHANNEL>
My thought at the moment is that they have something like MQ_HOST_1 and MQ_HOST_2, set to the appropriate names, and a CCDT be used for the rest of the configuration. I wa hoping to use a JSON CCDT rather than the binary one for "readability leads to understanding" purporses, but I image the legacy CCDT will work well enough. |
|
| Back to top |
|
|
| fswarbrick |
| Posted: Mon Jun 08, 2020 8:45 am Post subject: |
|
|
Apprentice
Joined: 07 Jul 2014
Posts: 42
|
It looks like JNDI might actually "solve all of my issues". Wish me luck!  |
|
| 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
|
|
|
|
