Compare Iguana 6 Channel Configurations with IguanaX

This exercise is intended to help you understand the difference in design philosophy of IguanaX with Iguana 6.

Create a new repository:

Make the name DemoImport
Select Protocol HTTPS
Copy paste the repository url:
https://bitbucket.org/interfaceware/export

In IguanaX we have:

Versus in Iguana 6:

What is different and why?

Iguana 6 looks like the complex dashboard of a 747 plane - there are lots of different options which most customers leave on the defaults.

With IguanaX a design goal was to make the operation of interfaces simpler by soft coding the components in Lua but giving each component a lot less configuration fields so that more attention can be given to what actually matters.

When you need to customize components we have made that simple.

Hint - look in the source code of the importer.

Look at the CHAN/CHANllpSource.lua file. This defines the mapping of configuration information from Iguana 6 to IguanaX.

Also look at the calls to CHANcreateStandardComp in CHAN/CHANmain.lua:

CHANcreateStandardComp(Dir, C, "from_llp_listener", "#source #llp",
                 "git@bitbucket.org:interfaceware/hl7_server.git")

These calls define the mapping of Iguana 6 components to IguanaX components.

Currently this could mean making the current components more complicated. Or making another secure LLP component and mapping those LLP interfaces using secure sockets into the new component which supports SSL/TLS.