Set the persistence in message level :

                SET OutputRoot.Properties.ExpirationTime=600;
SET OutputRoot.MQMD.Expiry = -1; --Non expiry message
SET OutputRoot.MQMD.Expiry = 1; -- expiry message
SET OutputRoot.MQMD.Persistence = 0; --Non peristent
SET OutputRoot.MQMD.Persistence = 1; --peristent

IV Questions :

1. Folders create when we deploy file nodes ?

file input node ::  mqsitransitin , mqsibackout
file output node ::    mqsitransitout

2. MAXIMUM HEAP SIZE IS .... 256 MB.

3. WMQ GROUP --- MQM
    WMB GROUP --- MQBRKRS

Command to check entire execution group information:

mqsireportproperties ESS_NODE -e TEST -o HTTPSConnector -r

Command to know the execution group port number :

mqsireportproperties ESS_NODE -e TEST -o HTTPConnector -n port

Command to know the broker level port Number :

mqsireportproperties ESS_NODE -b httplistener -o HTTPConnector -n port

Command to deploy the bar file :

mqsideploy brokername -e execution -a barfilenamewithpath -d todeleteanythinginexecutingroup

Command to read Bar file :

mqsireadbar -b barpathlocation

Command to override bar property files : 

mqsiapplybaroverride -b barfilelocattion -p propertyfilelocation -o newbarlocation

Command to Stop Execution Group : 

mqsistopmsgflow brokername -e execution

Command to Stop Message Flow :

mqsistopmsgflow brokername -e execution -m flowname -w300

Command to change the Port Number EG:

mqsichangeproperties brokername -e execution -o Httpconenctor -n explicitysetportnumber -v newportnumber

Tracing Commands :

 1. Start trace.

mqsichangetrace EssiConnectSIT -t -e NGAMERAAPPTEST -l debug -r -c 100000

2. Put a message on the queue to cause the failure to occur.  (In this step we need to create the order via RAINBOW)

3. Stop trace.

mqsichangetrace EssiConnectSIT -t -e NGAMERAAPPTEST -l none

4. Retrieve the trace log for the specified component.

mqsireadlog EssiConnectSIT -t -e NGAMERAAPPTEST -f -o flowtrace.xml

5. Format the XML trace file.

mqsiformatlog -i flowtrace.xml -o serviceflowtrace.txt



Email Output Node Configuration Commands :

mqsicreateconfigurableservice brokername -c SMTP -o configurableservicename

mqsichangeproperties brokername -c SMTP -o configurableservicename -n servername -v smtpserverport

mqsisetdbparms brokername -n securityidentity -u username -p password


mqsichangeproperties brokername -c smtp -o configurableservicename -n securityidentity -v securityidentityname


Command to set mqsi path : 

mqsiprofile

Command to Start the Message Flow : 

mqsistartmsgflow brokername -e execution -m flowname

FTP Configurable Service Commands :

Create Configurable Service:

mqsicreateconfigurableservice EssiConnectSIT -c FtpServer -o Server01 -n serverName,scanDelay,transferMode,connectionType,securityIdentity -v SGDC2FTPS001T:21,60,BINARY,ACTIVE,ftpredhat2

Set Username and Password:

mqsisetdbparms EssiConnectSIT -n ftp::ftpredhat2 -u iibuser -p iibuser

mqsireload ESS_NODE   or  mqsistop ESS_NODE  and mqsistart ESS_NODE

Delete the FTP Configurable Service :

mqsideleteconfigurableservice ESS_NODE -c FtpServer -o Server01

Deployment Issues :

    When we do deployment directly from the IIB Toolkit. It will what we mentioned in the code.
Such as like :

Queue names ,
User Defined Properties,
SOAP Url,
Http Url  etc .. all the data take from the code level , It will not take from Property file.


Attlasian :

   If we deploy the code through bamboo or scripts or any other auto deployment tool.
It will take all the required information from property file. We have to update Property file based on the Environment.

ESQL Time Stamp Changes : 

Code : 

DECLARE target TIMESTAMP;

SET now = CAST(CURRENT_TIMESTAMP AS CHARACTER FORMAT 'yyyy/MM/dd-h:mm:ss a');

Output :

 

Related IBM Links for Time Stamp :

https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ak05616_.htm

CAST Function: 

https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ak05610_.htm