IBM MQ Errors - Solutions

-
FAQ's Error:
0000008a SystemErr     R com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for 
QueueManager 'MYQM' with connection mode 'Client' and host name 'MYLAPTOP(1414)'.
Please check if the supplied username and password are correct on the QueueManager to which you are connecting.
00000080 SystemErr     R Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' 
('MQRC_NOT_AUTHORIZED').

00000080 MDBListenerIm W   WMSG0019E: Unable to start MDB Listener MDB, JMSDestination MYQUEUE : com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'MYQM' with connection mode 'Client' and host name 'MYLAPTOP(1414)'.
Please check if the supplied username and password are correct on the QueueManager to which you are connecting.



Few Basic Commands of MQ Setup:
1] Navigate to installed path of MQ server
e.g. 
Window: C:\Program Files (x86)\IBM\WebSphere MQ\bin\
UNIX: /usr/IBM/MQ/bin/

2] Run below commands:

runmqsc MYQM
ALTER QMGR CHLAUTH(DISABLED)

runmqsc REFRESH SECURITY(*)

SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY)


C:\>runmqsc MYQM
5724-H72 (C) Copyright IBM Corp. 1994, 2011.  ALL RIGHTS RESERVED.
Starting MQSC for queue manager MYQM.

REFRESH SECURITY(*)
     1 : REFRESH SECURITY(*)
AMQ8560: WebSphere MQ security cache refreshed.
SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY)
     2 : SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY)
AMQ8877: WebSphere MQ channel authentication record set.
REFRESH SECURITY(*)
     3 : REFRESH SECURITY(*)
AMQ8560: WebSphere MQ security cache refreshed.
ALTER QMGR CHLAUTH(DISABLED)
     4 : ALTER QMGR CHLAUTH(DISABLED)
AMQ8005: WebSphere MQ queue manager changed.
REFRESH SECURITY(*)
     5 : REFRESH SECURITY(*)
AMQ8560: WebSphere MQ security cache refreshed.

ALTER CHL('WAS.CLIENTS') CHLTYPE(SVRCONN) MCAUSER('MYLAPTOP')



C:\>runmqsc MYQM
5724-H72 (C) Copyright IBM Corp. 1994, 2011.  ALL RIGHTS RESERVED.
Starting MQSC for queue manager MYQM.

SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(BLOCKUSER) USERLIST('nobody')
     1 : SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(BLOCKUSER) USERLIST('nobody')
AMQ8877: WebSphere MQ channel authentication record set.
SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP) ADDRESS(*) ACTION(REMOVE)
     2 : SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP) ADDRESS(*) ACTION(REMOVE)
AMQ8877: WebSphere MQ channel authentication record set.
SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP) ADDRESS(localhost) USERSRC(CHANNEL)
     3 : SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP) ADDRESS(localhost) USERSRC(CHANNEL)
AMQ9778: IP address is invalid.

       :
DISPLAY QMGR CHLAUTH
     4 : DISPLAY QMGR CHLAUTH
AMQ8408: Display Queue Manager details.
   QMNAME(MYQM)                          CHLAUTH(DISABLED)
ALTER QMGR CHLAUTH(DISABLED)
     5 : ALTER QMGR CHLAUTH(DISABLED)
AMQ8005: WebSphere MQ queue manager changed.
END
     6 : END
5 MQSC commands read.
No commands have a syntax error.
One valid MQSC command could not be processed.

C:\>


set MQSERVER=SYSTEM.DEF.SVRCONN/TCP/hostname(1414)

Comments

Post a Comment

Popular posts from this blog

PUTTY - The server's host key is not cached in the registry cache

-
Error: "The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server's rsa2 key fingerprint is: [SSH KEY FINGERPRINT] If you trust this host, enter "y" to add the key to PuTTY's cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, enter "n". If you do not trust this host, press Return to abandon the connection. Store key in cache? (y/n) y" Answer: Simply run this command in your windows preferred terminal (cmd.exe etc) and agree to accept the host and store the cache: C:\Program Files (x86)\PuTTY\plink.exe -ssh [SSH USERNAME]@[SSH HOST] -P [SSH PORT] echo y | pscp -i /path/to/key/file user@remote:/tmp/file  . echo y | plink -i /path/to/key/file scripts.sh Usually you would hit “y” here, assuming the host key is correct, in order to store it in future connection.  The storage of this goes into the Registry under ...
Read more

OIM-12c Installation - FMW - SOA - IDM

-
Image
Oracle Identity Manager (OIM) 12c Installation Prerequisites: The Oracle Identity Manager software includes the following: 1] Oracle's Java Development Kit (JDK) 1.8 (jdk-8u311-linux-x64.tar.gz) 2]  Fusion Middleware 12.2.1.4.0 3]  SOA Suite 12.2.1.4.0 4] Oracle Identity and Access Management  12.2.1.4.0 What Do You Need? For completing Oracle IDM Setup you will need, Environment as below: Oracle Enterprise Linux 6 or similar, with access to the Internet At least 8GB RAM (16GB recommended) An Oracle Database Enterprise Edition 12 or superior installed and running. Note: Installing a Database for Identity and Access Management (IDM) Suite provides instructions on how to install an Oracle Database that is suitable for Oracle Identity and Access Management Suite. oracle and root user credentials SYS database user credentials Basic understanding of Linux An Oracle Technology Network (OTN) account OIM-11g PS3 Installation Steps: Just for reference https://www.oracle.com/webfol...
Read more

Apache Kafka - Zookeeper

-
Apache Kafka - Zookeeper Tutorial Topics covered in this article as below: Need of Messaging System What is Kafka? Kafka Features Kafka Components Kafka Architecture Installing Kafka Working with Single Node Broker Cluster 1. Need of Messaging System Data pipelines - Communication is required between different systems in the real-time scenario, which is done by using data pipelines Chat Server -----------Data Pipeline---------------> Database server Many services are communicating with various internal systems like front-end, back-end Api, database server, security system, real-time monitoring, chat server etc. Messaging systems helps managing complexity of above pipelines. so Kafka helps here to decouples data pipelines Key entity involved in Kafka Producer (Publisher) Consumer (Subscriber) 2. What is Kafka? (High throughput distributed messaging system) Apache Kafka is a distributed publish-subscribe messaging system It was originally developed at Linked-In and later became part ...
Read more