Skip to main content

Accessing the DB (database) from a compute node in a message flow in WMB

Accessing the DB from a compute node in a message flow in WMB

1. Add the datasource name in the oracle ini files

2. Run the mqsetdbparms command
Read syntax diagramSkip visual syntax diagram >>-mqsisetdbparms--BrokerName-- -n --ResourceName---------------> >-- -u --UserId-------------------------------------------------> >--+- -p --Password------------------------------+--+-----+----><    '- -i --SSHIdentityFile--+------------------+-' '- -f-'        '- -r --Passphrase-'    


3. Configure the DSN name in the compute node and run the sql query through the compute node



Comments

Post a Comment

Popular posts from this blog

Communication between Queue Managers

Communication between Queue Managers in MQ 7.5 Creating MQ connection between two queue managers, QMA & QMB 1. Creating queue manager QMA ALTER QMGR + *  ALTDATE(2018-05-19) + *  ALTTIME(15.19.41) +    CCSID(437) +    CLWLUSEQ(LOCAL) + *  COMMANDQ(SYSTEM.ADMIN.COMMAND.QUEUE) + *  CRDATE(2018-05-19) + *  CRTIME(15.19.41) +    DEADQ('QMA.DLQ') +    DEFXMITQ('QMA') + *  PLATFORM(WINDOWSNT) + *  QMID(QMA_2018-05-19_15.19.41) +    SSLCRYP(' ') +    SSLKEYR('C:\Program Files\IBM\WebSphere MQ\qmgrs\QMA\ssl\key') +    SUITEB(NONE) + *  VERSION(07050002) +    FORCE DEFINE LISTENER('LISTENER.TCP') TRPTYPE(TCP) CONTROL(QMGR) +    PORT(1424) + *  ALTDATE(2018-05-19) + *  ALTTIME(15.20.15) +    REPLACE 2. Creating queue manager QMB ALTER QMGR + *  ALTDATE(2018-05-19) + *  ALTTIME(15.21.08)...
Post a Comment
Read more
Managing High load failure scenarios for the Aggregation node in WMB message flows A common scenario in WMB message flows is when the aggregation message flows call multiple validation  services which are supposed to return a reply within 2 minutes. In normal scenarios, 10 to 50 requests are handled per minute. In high volume load scenarios, more than 100 requests are received per minute which leads to the failure of aggregation message flows. The aggregate replies from validation services will pile up on the aggregation reply queues making any new requests impossible. The piled up requests have to be cleared and only then the failed requests can be retried using a retry message flow which reads the aggregation requests from the input backout queue and processes them once again. This issue requires attention from IBM and can be fixed by having queue depth monitors and triggers on the aggregate request and reply queues. I would like to bring this issue to the notice of...
Post a Comment
Read more