This was sorted. Thanks.
IBM documentation says by-default access is provided for test accounts to
only those Queues which have names starting with DEV*
Cheers
Reji Mathews
On Fri, 15 May 2020, 14:45 Reji Mathews, wrote:
> My current configuration of
> com.ibm.msg.client.jms.JmsConnectionFacto
My current configuration of
com.ibm.msg.client.jms.JmsConnectionFactory looks like follows
{
"XMSC_WMQ_SSL_KEY_RESETCOUNT": 0,
"XMSC_WMQ_APPNAME": "testapp",
"XMSC_WMQ_CHANNEL": "CLOUD.APP.SVRCONN",
"failIfQuiesce": 1,
"XMSC_WMQ_USE_CONNECTION_POOLING": true,
"XMSC_WMQ_BROKER_CONTROLQ
Oh i see what you mean!
Indeed, I need to establish a jms connection. I decided to use camel-jms
component. Referred this official ibm git example here ->
https://github.com/ibm-messaging/mq-cloud-demo/blob/master/aws-backend-request/JMSLambdaFunction/src/main/java/com/example/lambda/ibmmq/JMSLamb
Hi,
What you are describing is direct MQ channel, no MQ JMS.
It’s possible to use JMS with IBM MQ but using JMS channel.
So, you create the connection factory like this:
> class="com.ibm.mq.jms.MQQueueConnectionFactory">
>
>
>
>
>
>
>
