Componentsss

This shows three connected components represented in the flow chart of the dashboard:

You can see these components in the list view on the side of the dashboard:

Components should be designed to handle a single task. For example, when building an interface between two systems that requires some message processing, this integration should be made up of at least 3 components:

1. Source - receive the message from system A.

2. Filter - apply any filtering or processing on the message.

3. Destination - send the processed message to system B.

By separating the tasks between 3 components, we are leveraging Separation of Concerns which will help:

• Embrace reusability of components. The more simple the task, the more likely you are able to reuse that component for a future interface.

• The team understand and manage the components

• Quickly locate and troubleshoot errors that may come up

Double click on a component’s name in the list or graphical view to open up their card. See Component Cards

Click on the component card to see the code the component is running on (read only format):

Click at the bottom of the component card or in the list view to read and edit the code:

Git is an integral part of how IguanaX works. Every component is implemented as a Translator component and the source code for these components is stored in Git repositories.  All the components are written in Lua script so you can use them as is, or you can go into the translator to customize the source code to decide how it behaves.

For convenience of deployment it’s helpful to store these components on a platform like http://bitbucket.org or http://github.com. Currently we use bitbucket.

If Git is new to you, see What is Source Control?.