App Connect

App Connect

Join this online user 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.


#Applicationintegration
#App Connect
#AppConnect
#Integration
#Automation
 View Only
  • 1.  Changing Environment Variables

    Posted 08/21/17 07:34 PM

    It looks like if you are only changing Environment Variables, then it appears the only choice is to choose a Compute Mode = Exception. Please confirm...



  • 2.  RE: Changing Environment Variables

    Posted 08/24/17 08:46 AM

    Hi Anne

    Yes, and No.

    If you want to use a compute node, then yes, that is what you need to do.

    But, if you only want to update something in the environment then you can use one of the other nodes that takes ESQL code, like the Filter node or the Database node. 

    I've done some performance tests on a very basic simple flow.  I've found on my laptop the following TPS: 

    • Compute Node with mode set to exception:   about 56 000 transactions per second
    • Filter node:                                                      about 72 600 transactions per second
    • Database node                                                 about 76 800 transactions per second

    So, for updating only the environment it might be better to use a database node. Strange but true.



  • 3.  RE: Changing Environment Variables

    Posted 08/25/17 02:13 PM

    Thanks Francois!



  • 4.  RE: Changing Environment Variables

    Posted 09/06/17 09:47 AM

    I usually use a Filter node if I'm just changing the Environment,  People unfamiliar with this technique will argue against it but now I see it is faster than a Compute node.  This is good stuff.

    Scott