How to restore message from Dead letter queue to original queue

 

How to restore message from Dead letter Queue to original queue for Application processing so that there will not be any impact . 

There are many reasons for the message go into dead letter queue . The actual reason for the message will be seem in the message header . In this we will see how to restore the message back to original queue from DLQ . Will see how to check the reason code later .

Use the dmpmqmsg utility to copy or move the contents of a queue, or its messages, to a file. Formerly the IBM MQ qload utility.

The following command can be used to move the messages from DLQ to original queue:

dmpmqmsg -m <qmgr name> -i <DLQ name> -o <destination queue name> -h
dmpmqmsg used for (queue load and unload)
Note: Please replace <qmgr name>, <DLQ name>, <destination queue name> with real names. The option "-h" is used to remove DLQ header.
-i or -I Input queue name
Note :Using -i browses the queue, whereas using -I gets messages from the queue.

For more options refer link dmpmqmsg help

How to enable SSL for JBOSS App Port

Find the below clear steps for enabling SSL for App Port on JBOSS EAP 7.X version . 

1.edit host or standalone.xml and add below JKS 
<security-realms>
    <security-realm name="httpsrealm">
        <server-identities>
            <ssl>
                <keystore path="/app/ssl/keystore.jks" keystore-password="xxxx" alias="site"/>
            </ssl>
        </server-identities>
        <authentication>
            <truststore path="/app/ssl/truststore.jks" keystore-password="xxxxxx"/>
        </authentication>
    </security-realm>
</security-realms>

2. Add below under undertow with in the respective profile for domain setup and in standalone.xml for standalone mode setup 
<subsystem xmlns="urn:jboss:domain:undertow:3.1">
    <buffer-cache name="default"/>
    <server name="default-server">
        <http-listener name="default" socket-binding="http" redirect-socket="https"/>
        <https-listener name="https" secure="true" enabled-protocols="TLSv1.1,TLSv1.2" security-realm="httpsrealm" socket-binding="https"/>
		.....
3.Restart and verify the App Https port to see if it reflects configured https certificate

Steps to enable SSL to JBOSS Console

 Now a days SSL is a mandatory security check for all the websites to encrypt the data transfer . Also called Data Encrypt at Transit .

Steps to enable SSL to JBOSS Console
------------------------------------------
1. Add below Server-idntities tag and truststore in both Host and Domain controller config giles

<security-realm name="ManagementRealm">
<server-identities>
<ssl protocol="TLS">
<keystore path="D:\JBC\hostname1a.jks" keystore-password="hostname1a" alias="hostname1a"/>
</ssl>
</server-identities>
<authentication>
<truststore path="D:\JBC\hostname1a.jks" keystore-password="hostname1a"/>


2. In the below management-interfaces replace port with secure-port (NOTE: Below change is only on domain-controller file )

<management-interfaces>
<native-interface security-realm="ManagementRealm">
<socket interface="management" port="${jboss.management.native.port:9999}"/>
</native-interface>
<http-interface security-realm="ManagementRealm">
<socket interface="management" secure-port="9990"/>
</http-interface>
<!-- <http-interface security-realm="ManagementRealm">
<socket interface="management" port="${jboss.management.http.port:9990}"/>
</http-interface> -->
</management-interfaces>

3. Restart Domain controller and Host controller .Check console wether the cert is browsing or not and also check wether Host is able to connect to Domain .