What is a Component?
Components are core to how Iguana X works.
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 also:
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:
Source - receive the message from system A.
Filter - apply any filtering or processing on the message.
Destination - send the processed message to system B.
By separating the tasks between 3 components, we are leveraging https://interfaceware.atlassian.net/wiki/spaces/EC/pages/2089058433 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
The card view shows the use of https://interfaceware.atlassian.net/wiki/spaces/IXB/pages/2500263941 which can be used to change the configuration of the component. You can stop and start the component with the switch in the top left.
By expanding the template section we can get access to it:
Now we see this:
HL7 Server is written in Lua and the source code of the component is stored in https://interfaceware.atlassian.net/wiki/spaces/IXB/pages/2670100487 . There are no built in components in IguanaX. All the components are written in Lua which means you can look at how they are implemented and alter them to meet your specific requirements.