Showing posts with label Message Broker. Show all posts
Showing posts with label Message Broker. Show all posts

Monday, September 10, 2018

How To Connect To Integration Node/Broker from Java IBM Integration API - How To Override the UDP Using Java Integration API

Ok lets get to the work.

We are going to use the Integration API to achieve this task from 'Java Compute Node' from IIB 10 Toolkit.

Below is sample flow







And code inside java compute  node -




// Add user code below
            BrokerConnectionParameters bcp = new IntegrationNodeConnectionParameters("localhost",4416);
                 BrokerProxy b = BrokerProxy.getInstance(bcp);
               
                 ExecutionGroupProxy e = b.getExecutionGroupByName("default");
                 ApplicationProxy a = e.getApplicationByName("UDPViaJavaApp");
                 MessageFlowProxy m = a.getMessageFlowByName("UDPChangeViaJAVA_MF");
                 m.setUserDefinedProperty("hostName", "localhost:555");

            // End of user code
            // ----------------------------------------------------------


I suggest you to try by yourself but if you don't want here is the code you can download from -

Download Integration PI



Thursday, March 16, 2017

AMQ7017: Log not available | Queue Manager Not Getting Start | Queue Manager Active Log files got deleted

If you are not able to start queue manager and getting the Log Not Available error or if you have accidentally deleted queue manager log files which are there in QM/Active directory then follow the following process.


1. Create Same queue manager in another server with same configuration as your currently stopped queue manager.

Configuration - You can find it qm.ini file in your current queue manager which is not running

2. Copy the log files from new Queue manager / Active and paste them into Old queue manager /active location.

3. Copy amqhlctl.lfh from new queue manager's location - /var/mqm/log/QM and pate/replace it into old queue manager /var/mqm/log/QM location

4. Restart the queue manager using strmqm or restart the broker using mqsistart broker name.



Note - Make sure to take backup of qm.ini , active logs and amqhlctl.lhf file from old queue manager before replacing anything from new queue manager.


If still same error - then please make sure that you have given the correct permission to the log files and amqhlctl.lfh file





Hope it helps. All the best.


Thursday, January 26, 2017

How to Find IIB Message Broker Application Error Logs in Windows

If you are using Message Broker or IIB in Windows Operating System and are facing issue with your applications / Message flows.

In some case you can't figure out the error from your error framework then it's better to check logs in system logs.

Here are the steps you can follow to find the application logs in Windows.