iNTERFACEWARE™ Inc.

Migrating From Version 3.1 To Version 3.2

The notion of "Incoming" and "Outgoing" channels was removed in Iguana 3.2, replaced by the idea of channel components. In version 3.2, each channel requires one source component, such as an LLP Listener, and one destination component, such as a Database. You can have any combination of source and destination components, such as an LLP Listener connecting directly to an LLP Client. These different combinations are the reason why the "Incoming" and "Outgoing" labels are obsolete. In future versions of Iguana, you will be able to have any number of source and destination components, and also any number of filters between those components.

If you have existing channels from Iguana 3.1, and you installed Iguana 3.2 into the same directory, Iguana 3.2 will read the existing channel configurations and create new channel configurations based on the Iguana 3.2 structure. The existing channel configurations from Iguana 3.1, may be found in the files "ClientConfiguration.xml" and "ServerConfiguration.xml" for outgoing and incoming channels, respectively. If you wish to install Iguana 3.2 in a different directory and also import the existing Iguana 3.1 channels, you may simply copy those files into the Iguana 3.2 directory. In Iguana 3.2, the channel configuration is stored in the file "ChannelConfiguration.xml". The channel import procedure is started only if that file does not exist in the Iguana 3.2 directory.

Because of the obsolescence of the "Incoming" and "Outgoing" labels, the naming of the error log tables was changed. Some error log tables were combined into a single table for certain components in order to prevent confusion as to where certain errors occurred.

The table name changes are summarized in the following table:

Furthermore, the column names in the "log_indices_[channel_name]" table should be changed to reflect the above table name changes.