| Author |
Message
|
| RaviSavi |
 Posted: Mon Apr 20, 2015 2:41 am Post subject: How to Configure JMSInput Node |
 |
|
Novice
Joined: 20 Apr 2015
Posts: 14
|
Request to All,
Please help me how to Configure JMSinput node.....Post that I need to read the message and send it to message queue(MQ).
Also,please tell me how to post the message to JMSinput node...Any tool / medium?
Replies to this post is highly helpful and appreciable. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Apr 20, 2015 3:52 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you looked to see if any of the Sample Flows use JMS nodes?
What have you tried?
What were the problems?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| MB Developer |
| Posted: Mon Apr 20, 2015 5:21 am Post subject: |
|
|
Disciple
Joined: 03 Feb 2014
Posts: 179
|
Hi RaviSavi,
work with this JMSInput Node sample and configure properties
JMS
_________________
Thanks.... |
|
| Back to top |
|
|
| RaviSavi |
| Posted: Mon Apr 20, 2015 11:26 pm Post subject: |
|
|
Novice
Joined: 20 Apr 2015
Posts: 14
|
Hi,
Thanks for ur link..I tried but resulted with error while debugging.
Error :
Failure to obtain JMS Connection JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'IB9QMGR' with connection mode 'Client' and host name 'localhost(1410)'. JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED'). |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Apr 21, 2015 12:50 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| RaviSavi wrote: |
Hi,
Thanks for ur link..I tried but resulted with error while debugging.
Error :
Failure to obtain JMS Connection JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'IB9QMGR' with connection mode 'Client' and host name 'localhost(1410)'. JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED'). |
What does ('MQRC_NOT_AUTHORIZED') tell you?
What does the AMQERR01.LOG file tell you?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| RaviSavi |
| Posted: Tue Apr 21, 2015 1:27 am Post subject: |
|
|
Novice
Joined: 20 Apr 2015
Posts: 14
|
AMQ9777: Channel was blocked
EXPLANATION:
The inbound channel 'SYSTEM.DEF.SVRCONN' was blocked from address '127.0.0.1'
because the active values of the channel matched a record configured with
USERSRC(NOACCESS). The active values of the channel were 'CLNTUSER(SYSTEM)'.
ACTION:
Contact the systems administrator, who should examine the channel
authentication records to ensure that the correct settings have been
configured. The ALTER QMGR CHLAUTH switch is used to control whether channel
authentication records are used. The command DISPLAY CHLAUTH can be used to
query the channel authentication records. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Apr 21, 2015 3:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| RaviSavi wrote: |
AMQ9777: Channel was blocked
EXPLANATION:
The inbound channel 'SYSTEM.DEF.SVRCONN' was blocked from address '127.0.0.1'
because the active values of the channel matched a record configured with
USERSRC(NOACCESS). The active values of the channel were 'CLNTUSER(SYSTEM)'.
ACTION:
Contact the systems administrator, who should examine the channel
authentication records to ensure that the correct settings have been
configured. The ALTER QMGR CHLAUTH switch is used to control whether channel
authentication records are used. The command DISPLAY CHLAUTH can be used to
query the channel authentication records. |
great!
now you can resolve it.
This is standard MQ stuff.
The 'security' forum on this site has a number of posts on this subject. There are some really good Developerworks articles by Morag Hughson that are also worth reading and understanding.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
