Custom Nodes

Custom Nodes

We not only provide custom solutions but also develop custom nodes which fulfills features not available in IIB by default. These custom nodes are easy to use and all you need to do is just connect the terminals and fill the properties.

Exception Handler

Every project has its own exception handler. But do they capture every exception?

Our exception handler can do the following:

  • Read from exception list only the required information like error code, exception type and exception description
  • Capture the error location where exactly error occurred
  • Capture the complete error path similar to Java stack trace
  • Capture flow name, application name, library name, server name, node name and time of failure
  • Prepare exception message according to the input message type. For example if the input message is of type JSON error message also prepared in JSON format. For non-self defined messages like CSV the error message is prepared in XML format.
  • For soap messages the error message is prepared in soap Fault
  • Capture exception message from catch terminal, failure terminal, soap fault terminal, http error terminal and http timeout terminals
  • Write the error message to file system or failure queue which are completely configurable
  • Propagate the failed message for further processing
  • Send email to support group. Give them all required details in HTML table format
  • Attach the failed message in gzip format if configured (java is required for this)
  • Available as both user defined node or as a subflow
  • No Java. Completely written in ESQL

Compression and Decompression Ndoes

These two nodes can compress and decompress any messages using GZIP algorithm.

Key Features
  • Simple to use; Just connect the terminals
  • Works for all kinds of message types
  • Available both as subflow and node
  • No additional jar files are required

Encryption and Decryption Cryptography Nodes

There are certain circumstances where we need to either encrypt/decrypt the message but there is no built-in nodes available by default. There are nodes publicly available for this but those are not simple to use or needs several configurations before you start using. Ours is simple and does not require any configuration.

Key Features
  • Simple to use; Just connect the terminals
  • Works for all kinds of message types
  • Available both as subflow and node
  • No additional jar files are required
Recursive File Read Node

The File Read node currently available in tookit allows to read one file at a time but if we need to read multiple files in the middle of a flow there is no direct way to do it. This custom node can recursively read files from all subdirectories and also according to the pattern you wish. You can also read files based on their age too. Want to read file by records ? Yes that too available

Key Features
  • Simple to use; Just connect the terminals
  • Recursively reads from all subdirectories
  • Follows GLOB pattern
  • Allows to read files by age and by type
  • All features of records and elements of File Read node are available
  • Works for all kinds of message types
  • Available both as subflow and node
  • No additional jar files are required
Recursive File Delete Node

There is no direct way to delete files in IIB. File Read node currently available in tookit allows to indirectly delete one file at a time but if we need to delete multiple files in the middle of a flow there is no direct way to do it. This custom node can recursively delete files from all subdirectories and also according to the pattern you wish. You can also delete files based on their age too.

Key Features
  • Simple to use; Just connect the terminals
  • Recursively deletes from all subdirectories
  • Follows GLOB pattern
  • Allows to delete files by age and by type
  • Works for all kinds of message types
  • Available both as subflow and node
Split Node

There are certain cirumstances where we need to split the messages into multiple chunks. This is possible when it is coming from a file node but if this is from MQ node there is no direct way to do it. There is also possibility of some special cases like send N records at a time or some repeating segments N times or send N bytes of data or group records based on a field and then send. All these can be done using this Split Node

Key Features
  • Split the messages into multiple chunks
  • Split by any way you need whether that is by size, count, delimeter or segments
  • Simple to use; Just connect the terminals
  • Works for all messages and all protocols
  • Purely written in ESQL

Group Node

Are you looking for an alternativce to Collector node? Want to control the message grouping as you want? Then this is the node for you

Key Features
  • Simple to use; Just connect the terminals
  • Works for all kinds of message types
  • Available both as subflow and node

Sleep Node

Do you want to stop processing the message for some time? This node can do it for you

  • Simple to use; Just connect the terminals
  • Works for all kinds of message types
  • Available both as subflow and node

Stop and Start Nodes

There are certain cirumstances where we need to stop processing the message flow. To do this generally commands are issued but there is no dynamic way to do it. These nodes can stop and start any application, library and message flow. You can configure the name in the node property and pass the valid path which has the name

Key Features
  • Can stop and start any application, library and message flow
  • Completely configurable. You can hard code the name or pass in valid ESQL path
  • Works for all kinds of message types
  • Available both as subflow and node

Logger Nodes

A developer spends lot of time not for development but for debugging. This is the most frustrating part when the issue could not be identifed or diagnosed or no access to connect to the remote server or takes time to conenct/disconnect. Usually every project has log4j or special custom node or subflow or use Flow exerciser but all these are not with flaws. Each has its own pros and cons. So we decided to create set of custom nodes which should give every detailed information a developer is interested and it must be controlled and configurable . It has to show him not only the message payload and headers but also what type of message, sender and receiver details, what protocol is it, time to complete and status of the transaction


  • Log files are written to a common directory as configured
  • Log files are written to physical file system where Node is installed
  • Can easily move to Database if needed to store audit messages
  • Dynamically change what level of log is required
  • Log files can be compressed and decompressed as configured
  • key business elements can also be captured
  • Additional information like Sender, Receiver, Interface Name, MessageId,Node details,Additional Instances,Message type and protocol can also be captured
  • Want to see Environment and LocalEnvironment too? Yes everything is availble as you confgured
  • Time of failure and Time of success are also captured
  • Elasped time for each message is also captured in log messages
  • Automatically rolling of files for every 10 minutes.
  • Every flow has its own unique log files
  • Works for all kinds of message types
  • Available both as subflow and node
Looking for a solution which doesn't exist in IIB?

If you see something which doesn't exist in IIB or wanted to convert all your reusable subflows into Nodes by which you can simply drag and drop from pallete to canvas, chat with our representative and we would be glad to assist you.