MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  How do I set my IIB app to allow parallel processing

    Posted 06/01/18 08:27 AM

    I am new to working on webservices and want to work on implementing Parallel processing of webservices using IIB v10. So, If a message is sent to message flow via MQ Input node, IIB processes the message till completion before processing another message coming from the input node. 

     The setup I am trying to build will be as follows-

    1. IIB app should accept webservice requests from multiple applications .
    2. As soon as the webservice request comes in from any application, IIB should start processing the request. It should not wait on previous request to be completed first.
    3. Each request should have a unique response for that request i.e, using correlation id to make sure the response is sent back for a specific request.

     

    In short, I want  my IIB app to allow parallel processing. I was going through IBM knowledge center and couldn't find any sample on IIB allowing parallel processing. Per project requirement, I am leaning on using REST nodes.  

    It would be great to have a message flow sample that will help me in implementing such a setup.

    Thank you !



    ------------------------------
    Nikita
    ------------------------------


  • 2.  RE: How do I set my IIB app to allow parallel processing

    Posted 06/01/18 12:47 PM
    You can use Asyn nodes, it won't wait for response, threads get released.

    ------------------------------
    HariHaran Ganesan
    ------------------------------



  • 3.  RE: How do I set my IIB app to allow parallel processing

    Posted 06/07/18 11:23 AM
    The previous recommendation on using Async nodes deals with outbound work but I think the original question was how to process multiple inbound web services requests in parallel.

    The answer is to increase the number of additional instances associated with either the input node or the flow. The total number of instances (threads) will be the maximum number of flow invocations that you can run in parallel.

    Additionally you can tweak the maxThreads parameter in the HTTPConnector in either the node level or server level listener so that you can control the maximum total HTTP connections coming in to the listener.

    Typically with a fast flow you do *not* necessarily require a message flow instance for every concurrent client but can instead allow the listener to distribute work to a smaller number of message flow threads. 


    ------------------------------
    DAVID CRIGHTON
    ------------------------------



Related Content