For information email info@jumpcointegrator.com
The IIB pattern is a template for a specific integration scenario e.g.: MQ iin-> webservice out, MQ in -> Mq out etc

IIB patterns configure meta-data (queues names, database names, eSql procs etc.) in Message Flows whereas JumpCo Integrator configures metadata in the database. New pattern instances are instantiated for every integration scenario with IIB patterns, whereas with the JumpCo Integrator there is a static amount of flows. There are a number of pros to the JumpCo Integrator that far outweigh IIB Patterns that can be summarized as follows:

JumpCo Integrator

GUI driven meta data + ESQL and Message Sets in Toolkit. Rate: 3

Fixed number of flows. e.g.: 500 integrations = 15 flows. e.g.: 500 integrations = 15 flows. Rate: 5

Same as IIB i.e. logs and debugging. Debugging happens through generic flows used by other integrations so it can be a little more difficult. JumpCo Integrator has comprehensive logging and GUI event reporting – pinpoints troubleshooting easily. Easier for Developer to use GUI than to step through code Rate: 5

Available through new IIB web GUI. Shows message performance, message throughput. This is general message performance and not integration scenario specific. Rate: 3

IIB 10

Single Development environment. Rate: 5

A flow/pattern instance for each integration scenario e.g.: 500 integrations = 500 flows Rate: 2

This is done through viewing log files and debugging. An IIB API exists to query logs and display through custom web GUI, monitoring tool etc. Debugging is easier than the JumpCo Integrator as you step through individual flows. Rate: 2.5

GUI allows business to draw reports from Event DB on business transactions

Message throughput, message performance available for fine tuning where necessary. This is available per integration scenario. Intelligent tuning can then be done based on the priority of the service/integration scenario. Rate: 4

Could not resolve host: urls.api.twitter.com