Version 4.5 Build 8: April 16, 2012

Bug Fixes

#19924 - Iguana may not always retry accessing it's log files when they are locked by backup software

1) [Problem]
   In Iguana 4.1.13, changes were introduced so that if external software locked
   Iguana's log files while Iguana was attempting to access them, Iguana would
   reattempt accessing the log files for 30 seconds instead of immediately going
   into a panic state and stopping all channels.

   In Iguana 4.1.23, 4.5.7, and 5.0.9 the retry period was extended to 30
   minutes to further accomodate enterprise environments where it may be
   difficult to to adhere to the recommended best practice of omitting Iguana's
   log files from back-ups.

   Despite these changes, there were still some circumstances where Iguana would
   immediately go into a panic state when back-up software locked it's log
   files.

   This has been fixed in Iguana 4.1.24, Iguana 4.5.8, and Iguana 5.0.13.

   [Affected Releases]
   Iguana 4.0,
   Iguana 4.1.1 through 4.1.23,
   Iguana 4.5.1 through 4.5.7,
   Iguana 5.0.1 through 5.0.12

   [Tracking Numbers]
   #19924, #19930

back to top

#19090 - Leaving Table View mode displayed for a long time may cause a crash

2) [Problem]
   In previous versions of Iguana, if you are viewing a message in the log 
   browser where you have the option of viewing the message in Table View mode, 
   if you leave the message displayed for longer than 5 minutes, Iguana may have
   crashed if activity was resumed in this mode (for example, if you chose to 
   view a different table in the Graphical Table View mode when there is more 
   than one table to choose from).

   This has been fixed in Iguana 4.5.8 and Iguana 5.0.13.

   [Affected Releases]
   Iguana 4.5.1 through 4.5.7,
   Iguana 5.0.1 through 5.0.12

   [Tracking Numbers]
   #19090, #19839

back to top

Version 4.1 Build 24: April 16, 2012

Bug Fixes

#19924 - Iguana may not always retry accessing it's log files when they are locked by backup software

1) [Problem]
   In Iguana 4.1.13, changes were introduced so that if external software locked
   Iguana's log files while Iguana was attempting to access them, Iguana would
   reattempt accessing the log files for 30 seconds instead of immediately going
   into a panic state and stopping all channels.

   In Iguana 4.1.23, 4.5.7, and 5.0.9 the retry period was extended to 30 
   minutes to further accomodate enterprise environments where it may be 
   difficult to to adhere to the recommended best practice of omitting Iguana's
   log files from back-ups.

   Despite these changes, there were still some circumstances where Iguana would
   immediately go into a panic state when back-up software locked it's log 
   files.

   This has been fixed in Iguana 4.1.24, Iguana 4.5.8, and Iguana 5.0.13.

   [Affected Releases]
   Iguana 4.0,
   Iguana 4.1.1 through 4.1.23,
   Iguana 4.5.1 through 4.5.7,
   Iguana 5.0.1 through 5.0.12

   [Tracking Numbers]
   #19924, #19930

back to top

Version 4.5 Build 7: January 19, 2012

Additions

#15045 - New configuration option in the To Database component to retry on a specific non-fatal database error

1) [Feature Description]
   You can now configure the To Database component to retry on specific 
   non-fatal database errors. 

   A new configuration option is available in the To Database component that 
   allows you to specify the text of the non-fatal database error, and how 
   often to retry when that error happens.

   This feature has been added to Iguana 4.1.23, 4.5.7, and 5.0.10.

   [Affected Releases]
   Iguana 4.1.23, 
   Iguana 4.5.7, 
   Iguana 5.0.10

   [Tracking Numbers]
   #15045

back to top

#19078 - Iguana will retry accessing it's log files for 30 minutes

2) [Feature Description]
   In Iguana 4.1.13, changes were introduced so that if external software 
   locked Iguana's log files while Iguana was attempting to access them, 
   Iguana would reattempt accessing the log files for 30 seconds instead of
   immediately going into a panic state and stopping all channels.

   In Iguana 4.1.23, 4.5.7, and 5.0.9 the retry logic has been enhanced to 
   retry for 30 minutes.  This is to accommodate enterprise environments where
   it may be difficult to follow best practices with respect to not having 
   Iguana's index files included in back-ups.
   
   [Affected Releases]
   Iguana 4.1.23, 
   Iguana 4.5.7, 
   Iguana 5.0.9

   [Tracking Numbers]
   #19078, #19109
	   

back to top

#19657 - Iguana will attempt to recover from index or meta log file corruption automatically on startup

3) [Description]
   In previous versions of Iguana, during startup if Iguana detected corruption
   in any of it's index or meta log files, Iguana would abort it's startup 
   sequence, report the corruption, and indicate which file(s) needed to be 
   moved out of the way to recover from the corruption before restarting Iguana.

   In Iguana 4.1.23, 4.5.7, and 5.0.11, Iguana has been enhanced such that it 
   will now attempt to automatically move the corrupted files out of the way 
   during it's startup sequence in an attempt to recover from the corruption.

   Iguana will report the corruption recovery as a Service Error in Iguana's 
   logs upon successful startup, as well as in it's ServiceErrorLog.txt file 
   located in Iguana's working directory.

   [Affected Releases]
   Iguana 4.1.23,
   Iguana 4.5.7,
   Iguana 5.0.11

   [Tracking Numbers]
   #19657

back to top

Bug Fixes

#19001 - Some versions of the Windows ODBC driver do not properly handle deallocation of null handles causing Iguana to crash

1) [Problem]
   In previous versions of Iguana, with some versions of the Windows ODBC driver 
   the driver would not properly handle deallocation of null handles, causing 
   Iguana to crash when attempting to free a null database handle.

   This has been fixed in Iguana 4.1.23, 4.5.7, and 5.0.8 such that Iguana no 
   longer asks the ODBC driver to free a null handle.

   [Affected Releases]
   All previous versions of Iguana

   [Tracking Numbers]
   #19001

back to top

Version 4.1 Build 23: January 19, 2012

Additions

#15045 - New configuration option in the To Database component to retry on a specific non-fatal database error

1) [Feature Description]
   You can now configure the To Database component to retry on specific 
   non-fatal database errors. 

   A new configuration option is available in the To Database component that 
   allows you to specify the text of the non-fatal database error, and how 
   often to retry when that error happens.

   This feature has been added to Iguana 4.1.23, 4.5.7, and 5.0.10.

   [Affected Releases]
   Iguana 4.1.23, 
   Iguana 4.5.7, 
   Iguana 5.0.10

   [Tracking Numbers]
   #15045

back to top

#19078 - Iguana will retry accessing it's log files for 30 minutes

2) [Feature Description]
   In Iguana 4.1.13, changes were introduced so that if external software 
   locked Iguana's log files while Iguana was attempting to access them, 
   Iguana would reattempt accessing the log files for 30 seconds instead of
   immediately going into a panic state and stopping all channels.

   In Iguana 4.1.23, 4.5.7, and 5.0.9 the retry logic has been enhanced to 
   retry for 30 minutes.  This is to accommodate enterprise environments where
   it may be difficult to follow best practices with respect to not having 
   Iguana's index files included in back-ups.
   
   [Affected Releases]
   Iguana 4.1.23, 
   Iguana 4.5.7, 
   Iguana 5.0.9

   [Tracking Numbers]
   #19078, #19109
	   

back to top

#19657 - Iguana will attempt to recover from index or meta log file corruption automatically on startup

3) [Description]
   In previous versions of Iguana, during startup if Iguana detected corruption
   in any of it's index or meta log files, Iguana would abort it's startup 
   sequence, report the corruption, and indicate which file(s) needed to be 
   moved out of the way to recover from the corruption before restarting Iguana.

   In Iguana 4.1.23, 4.5.7, and 5.0.11, Iguana has been enhanced such that it 
   will now attempt to automatically move the corrupted files out of the way 
   during it's startup sequence in an attempt to recover from the corruption.

   Iguana will report the corruption recovery as a Service Error in Iguana's 
   logs upon successful startup, as well as in it's ServiceErrorLog.txt file 
   located in Iguana's working directory.

   [Affected Releases]
   Iguana 4.1.23,
   Iguana 4.5.7,
   Iguana 5.0.11

   [Tracking Numbers]
   #19657

back to top

Bug Fixes

#19001 - Some versions of the Windows ODBC driver do not properly handle deallocation of null handles causing Iguana to crash

1) [Problem]
   In previous versions of Iguana, with some versions of the Windows ODBC driver 
   the driver would not properly handle deallocation of null handles, causing 
   Iguana to crash when attempting to free a null database handle.

   This has been fixed in Iguana 4.1.23, 4.5.7, and 5.0.8 such that Iguana no 
   longer asks the ODBC driver to free a null handle.

   [Affected Releases]
   All previous versions of Iguana

   [Tracking Numbers]
   #19001

back to top

Version 4.5 Build 6: September 6, 2011

Bug Fixes

#18724 - Iguana may not stop cleanly if it's in the middle of sending an email during shutdown

1) [Problem]
   In Iguana 4.5 and later, if Iguana was shutting down while it was in the 
   middle of sending out an email, Iguana would not stop cleanly.

   This has been fixed in Iguana 4.5.6 and Iguana 5.0.7.


   [Affected Releases]
   Iguana 4.5.1 through 4.5.5, 
   Iguana 5.0.1 through 5.0.6

   [Tracking Numbers]
   #18724

back to top

Version 4.1 Build 22: September 6, 2011

Bug Fixes

#17547 - Iguana may not always retry accessing it's log files when they are locked by an external application

1) [Problem]
   In Iguana 4.1.13 and later, changes were introduced so that if external 
   software locked Iguana's log files while Iguana was attempting to access 
   them, Iguana would reattempt accessing the log files for 30 seconds instead 
   of immediately going into a panic state and stopping all channels.  In 
   subsequent versions of Iguana, there was still the chance that Iguana would 
   immediately panic when attempting to access log files that were locked by an 
   external process.

   This has been fixed in Iguana 4.1.22, Iguana 4.5.6, and Iguana 5.0.7.


   [Affected Releases]
   Iguana 4.1.13 through 4.1.21,
   Iguana 4.5.1 through 4.5.5,
   Iguana 5.0.1 through 5.0.6

   [Tracking Numbers]
   #17547

back to top

Version 4.5 Build 5: June 17, 2011

Additions

#18088 - Serialization of ODBC database connections now controllable via an environment variable

1) [Feature Description]
   In Iguana 4.1.15, if more than one channel connected to the same database
   using ODBC, the database connections were serialized to prevent issues
   on some versions of Windows.

   In Iguana 4.5.5 and Iguana 5.0.5 this behaviour is now controllable via an
   environment variable IGUANA_USE_ODBC_LOCK.  Setting this environment
   variable to "no" (without the quotes) will disable the serialization 
   of ODBC database connection calls.
                                   
   
   [Affected Releases]
   Iguana 4.1.15 and later, 
   Iguana 4.5.1 through 4.5.4, 
   Iguana 5.0.1 through 5.0.4

   [Tracking Numbers]
   #18073, #18088

back to top

Bug Fixes

#17947 - IGC_csharp.dll would not load correctly on 64-bit Windows

1) [Problem]
   In previous versions of Iguana, when using Client Executables or Iguana
   Plugins written in either C#.NET or VB.NET on 64-bit Windows, IGC_csharp.dll
   would not load properly.
   
   This has been fixed in Iguana 4.5.5 and Iguana 5.0.5.
   
   [Affected Releases]
   Iguana 4.5.4 and earlier, 
   Iguana 5.0.1 through 5.0.4
   
   [Tracking Numbers]
   #17947

back to top

Version 4.5 Build 4: April 7, 2011

Additions

#17482 - SSL and STARTTLS connection encryption now supported for email notification

1) [Feature Description]
   Email notification messages can now be sent through STMP servers
   that require SSL or STARTTLS connection encryption for
   authentication.

   In previous versions of Iguana, the workaround was to configure
   email notification settings to not require authentication.


   [Affected Releases]
   Iguana 4.5.4, 5.0.2

   [Tracking Numbers]
   #17482

back to top

#17097 - FTP debug output now available for channels

2) [Feature Description]
   A new environment variable, IGUANA_ENABLE_FTP_DEBUG, has been added
   to enable you to debug problems with channels that read files from
   or write files to remote FTP servers.

   When IGUANA_ENABLE_FTP_DEBUG is set to "yes" (without the quotes),
   FTP debug output will appear on the console if you are running
   Iguana from a Command Prompt window or a command line. If you are
   running Iguana as a service or daemon, the FTP debug output will be
   added to the ServiceErrorLog.txt file.


   [Affected Releases]
   Iguana 4.5.4

   [Tracking Numbers]
   #17097

back to top

Bug Fixes

#17018 - Uploaded FTP files sometimes cannot be renamed properly

1) [Problem]
   In Iguana 4.5.2 and later, a problem may occur if you create a
   channel whose destination component is To File, select the "Upload to
   FTP" check box to upload files to an FTP server, and use the "FTP
   path" field to specify a directory into which files are to be written
   on the FTP server.

   When this problem occurs, a temporary copy of the file being uploaded
   is written to the FTP server, but the attempt to rename the file to
   its proper name the fails, and a "450 Rename Failed" error message is
   sent by the server. The Iguana channel then stops.

   This problem has been fixed in Iguana 4.5.4.


   [Affected Releases]
   Iguana 4.5.2 and later

   [Tracking Numbers]
   #17018

back to top

#17217 - Database tables cannot be exported to MySQL 5.5

2) [Problem]
   Version 4.5.3 of Iguana could not export database tables to a
   database created using version 5.5 of MySQL. This is because the
   SQL queries generated by Iguana used the TYPE keyword to specify
   the storage engine, which is not supported in MySQL 5.5.

   SQL queries generated by Version 4.5.4 of Iguana use the ENGINE
   keyword, which is supported in all versions of MySQL.


   [Affected Releases]
   Iguana 4.5.3

   [Tracking Numbers]
   #17217

back to top

#17334 - GUID generator can generate access violations in multi-threaded environments

3) [Problem]
   Internal testing of the Chameleon Python library's GUID
   generator function, guid.generate_guid(), revealed that an
   access violation could occur in multi-threaded environments
   in unusual circumstances.

   This has been fixed in version 4.5.4 of Iguana and
   version 5.3.4 of Chameleon.


   [Affected Releases]
   Chameleon 5.0 and later

   [Tracking Numbers]
   #17334

back to top

#17540 - VMD files in database components now no longer pre-populated

4) [Problem]
   In previous versions of Iguana, when a new channel is created
   with a From Database source component, the "Full generator
   VMD path" field is pre-populated with the location of the VMD
   file used by the last channel created with a From Database
   source component. Similarly, when a new channel is created
   with a To Database destination component, the "Full parser VMD
   path" field is pre-populated with the location of the VMD file
   used by the last channel created with a To Database destination
   component.

   In some environments, pre-populating these VMD file fields
   may create the risk of a potential HIPAA violation. For this
   reason, pre-populating VMD files has been removed from
   version 4.5.4 of Iguana.


   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #17540

back to top

#17609 - Problem with Save Changes button in Database Settings screen in IE8

5) [Problem]
   If you are using Iguana on Internet Explorer 8, and you are using the
   Database Settings screen to change a shared library preference, the
   Save Changes button may sometimes not work properly.

   This has been fixed in version 4.5.4 of Iguana.


   [Affected Releases]
   Iguana 4.5.3 and earlier

   [Tracking Numbers]
   #17609

back to top

#17428 - List of channels not saved in To Channel destination component

6) [Problem]
   If you are creating a channel whose destination component is To
   Channel and you create a list of one or more destination
   channels, this list is not saved when the channel is created.

   You can work around this problem by editing the channel after
   it has been created and rebuilding the list of destination
   channels. When you save the changes to your edited channel,
   the list of channels is properly saved.

   This problem has been fixed in versions 4.5.4 and 5.0.2 of
   Iguana.


   [Affected Releases]
   Iguana 4.5, Iguana 5.0.1

   [Tracking Numbers]
   #17428

back to top

#13089 - Chameleon now remembers the last format used to save a VMD file

7) [Problem]
   In previous versions of Chameleon, if you saved a VMD file, the
   default file format was always "Message Definition File". If you
   saved a file in XML format, and then wanted to save it again, you had
   to remember to select "XML Message Definition File" each time.

   In Chameleon 5.3.4, if you save a VMD file in XML format, this format
   becomes the default format when you save the file again.


   [Affected Releases]
   All previous releases of Chameleon

   [Tracking Numbers]
   #13089

back to top

#17319 - Leaving Segment View mode or Segment Grammar View mode displayed for a long time may cause a crash

8) [Problem]
   In version 4.5 of Iguana, if you are viewing log message details in
   either Segment View mode or Segment Grammar View mode, and you leave
   the message displayed for longer than 5 minutes, Iguana may crash if
   activity is resumed in this mode (for example, if a segment is
   expanded).

   This problem has been fixed in versions 4.5.4 and 5.0.2 of Iguana.


   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #17319

back to top

Version 4.5 Build 3: January 31, 2011

Additions

#16618 - Parsing of Python scripts can now be serialized across channels

1) [Feature Description]
   For some customers that make extremely heavy use of Python, it has
   been observed that performance issues could occur.  This is due to
   multiple channels being in contention for the Python "global
   interpreter lock".

   For customers facing this problem, an optional switch has been added
   to Iguana to allow parse execution to be serialized across all the
   channels in an Iguana instance.  In some cases, this can
   significantly improve performance.

   To use this lock, set the IGUANA_USE_PARSE_MESSAGE_LOCK environment
   variable to "yes" (without the quotes) and restart at least one
   channel whose destination component is To Database.

   [Affected Releases]
   Iguana 4.5.3

   [Tracking Numbers]
   #16618

back to top

#16880 - Version 5.5 of the MySQL shared library now supported

2) [Feature Description]
   Iguana now supports version 5.5 of the MySQL shared library. This
   means that Iguana can interact with any database that uses this
   library.

   [Affected Releases]
   Iguana 4.5.3

   [Tracking Numbers]
   #16880

back to top

#16938 - passive_llp_consumer_plugin now has "--ack_verification none" option

3) [Feature Description]
   The passive_llp_consumer_plugin utility program now supports the
   "--ack_verification none" option. When this option is set, waiting
   for acknowledgment messages is disabled. Any acknowledgment messages
   that are received are ignored and are logged to standard output.

   [Affected Releases]
   Iguana 4.5.3

   [Tracking Numbers]
   #16938

back to top

#13909 - Channel start time now included with channel inactivity email notification

4) [Feature Description]
   In Iguana 4.5.3, if you have created an email notification rule to
   send a notification message if a channel has been inactive for a
   specified amount of time, the sent message now includes the channel
   start time as part of the message text. This makes it easier to
   determine the sequence of events that led to the channel becoming
   inactive.

   [Affected Releases]
   Iguana 4.5.3

   [Tracking Numbers]
   #13909

back to top

Bug Fixes

#16809 - Control characters now removed when message received using Log Query API

1) [Problem]
   Previous versions of Iguana did not strip control characters from log
   messages that were retrieved using the Log Query API. This caused
   XML-related exceptions.

   In Iguana 4.5.3, when a message is retrieved using the Log Query API,
   control characters will be removed.

   In addition, if the login username or password is changed, a
   reconnection is performed.

   [Affected Releases]
   Iguana 4.1 and later

   [Tracking Numbers]
   #16809

back to top

#16646 - Edit channel changes no longer lost when a channel group name is clicked

2) [Problem]
   In previous versions of Iguana, when you are editing a channel and
   are viewing the Channel tab, clicking any channel group specified in
   the Groups field displays the Edit Channel Group screen. Any changes
   that you have made while editing the channel are lost.

   In version 4.5.3 of Iguana, the channel groups in the Groups field
   cannot be clicked.

   [Affected Releases]
   Iguana 4.1 and later

   [Tracking Numbers]
   #16646

back to top

#16923 - Unicode prefixes now only provided with string values in database queries when needed

3) [Problem]
   In previous versions of Iguana, interaction with a SQL Server or
   Oracle database may be slower than expected.  This is because the
   database queries generated by Iguana use Unicode ("N") prefixes for
   any string values included as part of these queries.  This
   particularly affects index lookups for the Database components in
   Iguana.

   Versions 4.5.3 and 4.1.21 of Iguana have been updated to no longer
   use the Unicode prefix for string values that consist only of ASCII
   characters.  Any string values that contain values outside of the
   ASCII range will continue to use the Unicode prefix. 


   [Affected Releases]
   Iguana 4.5.2 and earlier; Iguana 4.1.20 and earlier

   [Tracking Numbers]
   #16923

back to top

#16789 - Log Query API now works with older versions of Iguana

4) [Problem]
   The Log Query API provided with version 4.5.2 of Iguana cannot
   connect properly to older versions of Iguana.

   This problem has been fixed in version 4.5.3 of Iguana.

   [Affected Releases]
   Iguana 4.5.2

   [Tracking Numbers]
   #16789

back to top

Version 4.1 Build 21: January 28, 2011

Bug Fixes

#13044 - Problems with plugins in Java on HPUX

1) [Problem]
   In versions of Iguana prior to 4.1.21, plugins written in Java for
   the HPUX operating system do not link properly to the IGC shared
   library.

   This has been fixed in versions 4.5 and 4.1.21 of Iguana.

   [Affected Releases]
   Iguana 4.1.20 and earlier

   [Tracking Numbers]
   #13044

back to top

Version 4.5 Build 2: December 15, 2010

Additions

#15971 - Iguana daemon on Linux, Unix and Mac OS X now issues SIGQUIT on timed out stop attempt

1) [Feature Description]
   In previous versions of Iguana for Linux, Unix and Mac OS X, if you
   attempt to stop an Iguana server that is running as a daemon and the
   daemon is unable to stop during the time period specified in the
   service_kill_timeout field of the iguana_service.hdf configuration
   file, Iguana issues a SIGKILL signal. This signal stops Iguana but
   does not generate a core dump.

   In Iguana 4.5.2, if the daemon is unable to stop during the time
   period specified in the service_kill_timeout field, a SIGQUIT signal
   is issued. This enables the Linux, Unix or Mac OS X system to
   generate a core dump.

   If you do not want the Iguana daemon to issue a SIGQUIT signal, you
   can specify the signal that Iguana is to use. To do this, add the
   "unix_kill_signal" field to the iguana_service.hdf configuration
   file. For example, if Iguana is to issue a SIGKILL signal, add the
   following:

      unix_kill_signal=9

   
   [Affected Releases]
   Iguana 4.1 and later

   [Tracking Numbers]
   #15971

back to top

#16446 - 8-bit characters in outgoing messages can be preceded by escape characters

2) [Feature Description]
   In the LLP Listener channel source component, and in the LLP Client
   and To File channel destination components, you can now specify that
   8-bit characters in outgoing HL7 messages or acknowledgment messages
   are to be preceded by escape characters.
   
   [Affected Releases]
   Iguana 4.1 and later

   [Tracking Numbers]
   #16446

back to top

Bug Fixes

#16057 - Permissions problems when performing an action on multiple channels

1) [Problem]
   In Iguana 4.5.1, if you use the Dashboard's search capability to
   display a subset of the defined channels, clear the search to display
   all of the channels again, then select an action from the Channel
   Action list box located at the bottom left of the Dashboard, an
   incorrect error message appears. This message states that you cannot
   perform the selected channel action on some of the specified channels
   because you lack the necessary permissions.

   This message appears whether or not your user account is a member of
   the Administrators role.

   This problem has been fixed in version 4.5.2 of Iguana.


   [Affected Releases]
   Iguana 4.5.1

   [Tracking Numbers]
   #16057

back to top

#16289 - Permissions problems when performing an action on all channels

2) [Problem]
   In Iguana 4.5.1, if you have more channels than can be displayed on
   the Dashboard, you select all of the channels using the check box in
   the Dashboard's heading row, and you select an action from the
   Channel Action list box located at the bottom left of the Dashboard,
   an incorrect error message appears. This message states that the
   action will not be performed because you lack the necessary
   permissions. 

   This message appears whether or not your user account is a member of
   the Administrators role.

   This problem has been fixed in version 4.5.2 of Iguana.


   [Affected Releases]
   Iguana 4.5.1

   [Tracking Numbers]
   #16289

back to top

#16192 - SMS address cleared when editing user information

3) [Problem]
   In Iguana 4.5.1, if you are editing information for a user, any
   existing SMS address is cleared. If you save your changes without
   retyping the SMS address, the address is lost.

   Any new address typed in the SMS Address field is saved correctly.

   This problem does not occur in versions of Iguana prior to 4.5.1,
   and has been fixed in version 4.5.2 of Iguana.


   [Affected Releases]
   Iguana 4.5.1

   [Tracking Numbers]
   #16192

back to top

#15228 - Error message generated when connection to LLP Client dropped and reestablished while acknowledgment is being validated

4) [Problem]
   If a channel whose destination component is LLP Client has been
   configured to use a VMD file to validate acknowledgment messages,
   Iguana may generate an incorrect error message if the connection to
   the receiving application is dropped and then re-established while
   an acknowledgment message is being validated.

   If the acknowledgment message is re-sent by this application after
   the connection is re-established, Iguana may generate an error
   message indicating that the acknowledgment timeout timer has already
   been started.

   This problem has been fixed in version 4.5.2 of Iguana.


   [Affected Releases]
   Iguana 4.5.1

   [Tracking Numbers]
   #15228

back to top

#16282 - Starting and stopping a channel from a web browser only works if "start" or "stop" is in lower case

5) [Problem]
   In version 4.5.1 of Iguana, starting and stopping a channel from a
   web browser does not work properly if the channel action is specified
   with a word containing uppercase letters (such as "Start", "START",
   "Stop" or "STOP"):

      http://localhost:6543/status.html?UserName=admin&Password=password
      &ChannelAction=Stop&ChannelName=TestChannel

   If a word containing an uppercase letter is specified, all channels
   are stopped or started.

   Starting or stopping a channel works properly if you use a lowercase
   word ("start" or "stop") in the ChannelAction field:

      http://localhost:6543/status.html?UserName=admin&Password=password
      &ChannelAction=stop&ChannelName=TestChannel

   This problem has been fixed in version 4.5.2 of Iguana.


   [Affected Releases]
   Iguana 4.5.1

   [Tracking Numbers]
   #16282

back to top

#16234 - enqueue_message() does not allow enqueueing when source is From Channel and destination is not To Channel

6) [Problem]
   The enqueue_message() Python scripting function no longer allows you
   to enqueue a message for a channel whose source component is From
   Channel and whose destination component is something other than To
   Channel. Messages sent to these channels could not be processed.


   [Affected Releases]
   Iguana 4.5.1

   [Tracking Numbers]
   #16234

back to top

#16281 - active_llp_producer_plugin and passive_llp_consumer_plugin now work in the 64-bit Windows environment

7) [Problem]
   The active_llp_producer_plugin utility, which was released with
   version 4.1.8 of Iguana, did not work in the 64-bit Windows
   environment. The passive_llp_consumer_plugin utility, which was
   released with version 4.5.1 of Iguana, also did not work in the
   64-bit Windows environment.

   These utilities did work properly if the 32-bit version of Iguana
   for Windows was installed in a 64-bit environment.

   In version 4.5.2 of Iguana, the 64-bit versions of these utilities
   can now be run successfully.


   [Affected Releases]
   Iguana 4.1.8 and later

   [Tracking Numbers]
   #16281

back to top

#15539 - Database Table Importing Wizard now supports DB2 and Filemaker

8) [Problem]
   In previous versions of Chameleon, the Database Table Importing
   Wizard did not include the DB2 and Filemaker database APIs as options 
   that could be selected from the Database API list box.

   This problem has been fixed in version 5.3.2 of Chameleon.


   [Affected Releases]
   Chameleon 5.1.10 and later

   [Tracking Numbers]
   #15539

back to top

#16441 - Escaped extended ASCII characters in incoming messages now handled properly

9) [Problem]
   If an incoming message contains escaped extended ASCII characters,
   Iguana 4.5.2 will now undo the escape sequences before converting
   the characters into the UTF-8 format that Iguana and Chameleon use
   internally. This ensures that a generated message will not contain
   incorrect escape sequences if the characters in the message are
   converted to an encoding format other than UTF-8.


   [Affected Releases]
   Iguana 4.0 and later

   [Tracking Numbers]
   #16441

back to top

#16260 - Iguana may crash if database removed from system while channel is generating messages

10)[Problem]
   Previous versions of Iguana may crash if a database is removed from
   the system while a channel whose source component is From Database
   is generating messages. This is because Iguana uses a status table,
   stored in the database, to determine the database table rows from
   which messages are to be generated. Iguana was not checking whether
   the database connection still existed before attempting to update
   the status table.

   This problem has been fixed in version 4.5.2 of Iguana.


   [Affected Releases]
   Iguana 4.0 and later

   [Tracking Numbers]
   #16260

back to top

#16556 - Iguana may crash if Oracle database turned off for maintenance

11)[Problem]
   If you are using Iguana with an Oracle database, your Iguana server
   may crash if you turn off the Oracle database for maintenance while
   a database operation is being performed. This is because Iguana is
   attempting to free the descriptors that Oracle has already freed.

   This crash is unlikely to occur, as it can only happen if the Oracle
   database is turned off at the very instant that an SQL statement is
   executing.

   This problem has been fixed in version 4.5.2 of Iguana.


   [Affected Releases]
   Iguana 4.0 and later

   [Tracking Numbers]
   #16556

back to top

#16515 - ADRA19 message definitions now handled properly in older HL7 library files

12)[Problem]
   Some of the older HL7 library files that are included with
   Chameleon contain an ADRA19 message definition. In this message
   definition, the table grammar uses the Group1 table group name more
   than once. This means that stubcode generated from this message
   definition will contain errors, as the stubcode generator uses the
   group names to create unique identifiers in the generated output.

   This problem occurs in the library files for HL7 versions 2.2, 2.3,
   2.3.1 and 2.4. These files can be found in the Libraries
   subdirectory of the directory in which Chameleon is installed, and
   have the following names:

      HL7_2.2.vmd
      HL7_2.3.vmd
      HL7_2.3.1.vmd
      HL7_2.4.vmd

   Library files that are older than HL7 version 2.2 or newer than HL7
   version 2.4 do not have this problem, as the ADRA19 message
   definition is not included in these files.

   The library files have been corrected in version 4.5.2 of Iguana
   and version 5.3.2 of Chameleon. To fix this problem in older
   versions of Iguana and Chameleon, use Chameleon to edit the library
   files shown above. Change the second group name in the ADRA19 message
   definition table grammar from "Group1" to "Group2".
   

   [Affected Releases]
   Version 4.1.18 and earlier of Iguana; version 4.5.1 of Iguana;
   version 5.2.18 and earlier of Chameleon; version 5.3.1 of Chameleon.

   [Tracking Numbers]
   #16515

back to top

#16585 - Segment View does not work when log message displayed in separate window

13)[Problem]
   When you are displaying a log message in a separate window, the
   Segment View mode does not display properly.

   This problem has been fixed in version 4.5.2 of Iguana.

   [Affected Releases]
   Version 4.1 and later

   [Tracking Numbers]
   #16585

back to top

#15896 - Channel becomes unselected if name changed

14)[Problem]
   If you are using the Dashboard to start and stop multiple channels,
   clear or mark multiple channel errors, or clear one or more channel
   queues, a problem may occur when you are selecting one or more
   channels on which to perform your specified operation.

   If you have selected one or more channels from the Dashboard and you
   rename a selected channel, the selected channel becomes unselected.
   If you then change the name of the channel back to its original name,
   the channel becomes selected again.

   This problem has been fixed in version 4.5.2 of Iguana.

   [Affected Releases]
   Version 4.0 and later

   [Tracking Numbers]
   #15896

back to top

Version 4.1 Build 20: January 7, 2011

Additions

#16618 - Optional switch allows serialization of parse execution

1) [Feature Description]
   For some customers that make extremely heavy use of Python, it has
   been observed that performance issues could occur.  This is due to
   multiple channels being in contention for the Python "global
   interpreter lock".

   For customers facing this problem, an optional switch has been added
   to Iguana to allow parse execution to be serialized across all the
   channels in an Iguana instance.  In some cases, this can
   significantly improve performance.

   To use this lock, set the IGUANA_USE_PARSE_MESSAGE_LOCK environment
   variable to "yes" (without the quotes) and restart at least one
   channel whose destination component is To Database.

   [Affected Releases]
   Iguana 4.1.20

   [Tracking Numbers]
   #16618 

back to top

Version 4.1 Build 19: December 7, 2010

Additions

#16446 - 8-bit characters can now be preceded by escape characters

1) [Feature Description]
   In the LLP Listener channel source component, and in the LLP Client
   and To File channel destination components, you can now specify that
   8-bit characters in outgoing HL7 messages or acknowledgment messages
   are to be preceded by escape characters.
   
   [Affected Releases]
   Iguana 4.1 and later

   [Tracking Numbers]
   #16446

back to top

Version 4.1 Build 18: November 1, 2010

Additions

#16017 - Filters can now perform no message ignoring or transforming

1) [Feature Description]
   For any channel, you can now create a filter that ignores no messages
   and performs no transformations. This enables you to create a VMD
   file for this channel that executes global Python scripts.

   In previous versions of Iguana, for any filter, you were required to
   specify either a transformation mode or the names of one or more
   messages to be ignored.

   
   [Affected Releases]
   Iguana 4.1.18

   [Tracking Numbers]
   #16017

back to top

Bug Fixes

#16055 - Channel conversion from Iguana 3.3.2 incorrect in rare circumstances

1) [Problem]
   If you are upgrading from version 3.3.2 or earlier of Iguana to the
   latest version, some of your channels may not be converted properly
   if the following are all true:

     * A channel receives messages from a local port P.
     * A second channel sends messages to the same local port P.
     * A third channel sends messages to a remote host on the same
       port, P.

   In this case, during upgrading, the source component of the first
   channel is correctly converted to From Channel, and the destination
   component fo the second channel is correctly converted to To
   Channel. However, the destination component of the third channel is
   incorrectly converted to To Channel, as Iguana is converting the
   channel even when the specified host is not "localhost".

   This upgrading problem has been fixed in version 4.1.18 of Iguana.


   [Affected Releases]
   Iguana 4.1

   [Tracking Numbers]
   #16055

back to top

Version 4.5 Build 1 (Beta): October 13, 2010

Additions

#11413 - HL7 Listener and HL7 Simulator now use Courier New font

1) [Feature Description]
   In the HL7 Listener and the HL7 Simulator, the text that appears in
   the Main Display window is now displayed in the Courier New font.
   Text in this font is easier to read, and the O, 0 and o characters in
   this font are easily distinguishable from one another.

   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #11413

back to top

#13166 - Iguana no longer dynamically linked to CHM_LIB3.dll

2) [Feature Description]
   As of version 4.5, Iguana is no longer dynamically linked to the
   CHM_LIB3.dll library file. All links to this library are static.
   This change enables the Iguana executable to perform more efficiently.

   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #13166

back to top

#10208 - Plugin error messages have been improved

3) [Feature Description]
   In this version of Iguana, plugin error messages have been improved.
   The message text is more meaningful, and each error message now
   indicates which channel component has detected the error.

   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #10208

back to top

#14136 - Iguana 4.5 logins disabled on IE6

4) [Feature Description]
   If you are using Iguana 4.5, you will not be able to log in to or
   access Iguana if you are using Internet Explorer 6. This is because
   this browser is obsolete and does not provide the features that
   Iguana needs to be able to work properly.

   Although Internet Explorer 6 was not supported for Iguana 4.1, there
   was no mechanism in place to disable logging in from this browser.

   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #14136

back to top

#13880 - active_llp_producer_plugin relocated

5) [Feature Description]
   In Iguana 4.5, the active_llp_producer_plugin utility program has
   been moved into the plugins subdirectory of the directory in which
   Iguana is installed. This change ensures that all plugins included
   with Iguana can be found in the same directory.

   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #13880

back to top

Performance Improvements

#13428 - Database connections can remain inactive for 5 seconds

1) [Feature Description]
   If a channel has a To Database destination component, and the channel
   becomes inactive, the connection to the database is now disconnected
   only after the channel has remained inactive for 5 seconds. This
   ensures more efficient interaction with the database in situations
   where a new message arrives almost immediately after the last message
   has been processed.

   In previous versions of Iguana, the channel was disconnected as soon
   as it became inactive.

   [Affected Releases]
   Iguana 4.5 

   [Tracking Numbers]
   #13428

back to top

#13641 - VMD file loading has been optimized

2) [Feature Description]
   The amount of time required to load VMD files has been optimized.
   Depending on the content of the file, load time can be as much as 25%
   faster.

   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #13641

back to top

#13631 - Less CPU time required for database reconnection

3) [Feature Description]
   If you have created a large number of channels that have a From
   Database source component or a To Database destination component,
   less CPU time is now needed to reconnect to a database after a
   connection is lost.

   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #13631

back to top

#13888 - Message browser handles large messages better

4) [Feature Description]
   The Chameleon message browser now features improved handling of
   messages that contain a large number of segments.

   [Affected Releases]
   Iguana 4.5 and Chameleon 5.3

   [Tracking Numbers]
   #13888

back to top

#13666 - From File handles large numbers of files better

5) [Feature Description]
   In Iguana 4.5, the From File source component handles a large number
   of input files much more efficiently.

   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #13666

back to top

#15999 - Log files now checked for matching index files

6) [Feature Description]
   Iguana 4.5 now contains a low-priority thread that checks whether
   each log file has had an index file defined for it. These index files
   improve log search speed.

   Log files are searched in reverse chronological order, from newest
   to oldest.


   [Affected Releases]
   Iguana 4.5

   [Tracking Numbers]
   #15999

back to top

Bug Fixes

#12987 - Plugins now work properly on Unix, Linux and Mac OS X

1) [Problem]
   In previous versions of Iguana, if you used Chameleon to build a
   source or destination plugin, the generated code would not compile
   properly in the Unix, Linux and Mac OS X environments.

   This has been fixed in version 4.5 of Iguana.

   [Affected Releases]
   Iguana 4.1

   [Tracking Numbers]
   #12987

back to top

#13344 - Channel stopping while From File processing a file

2) [Problem]
   In Iguana 4.1, if Iguana is stopped when a channel whose source
   component is From File is in the middle of processing a file, the
   channel starts processing the file from the beginning again when
   Iguana is restarted. This means that some messages may be duplicated.

   In addition, if a channel is stopped when in the middle of processing
   a file, and the file is moved, renamed or deleted before the channel
   is restarted, Iguana 4.1 does not notify you that the file has been
   moved, renamed or deleted.

   These problems have been fixed in version 4.5 of Iguana.

   [Affected Releases]
   Iguana 4.1

   [Tracking Numbers]
   #13344

back to top

#14178 - Channel group names cannot contain tab characters

3) [Problem]
   In previous versions of Iguana, channel groups could not be deleted
   if tab characters were embedded in the group name.

   In Iguana 4.5, channel group names cannot contain embedded tab
   characters.

  
   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14178

back to top

#12914 - Only unmarked errors displayed when multiple message types selected

4) [Problem]
   In the Logs screen, if you select "Errors - Unmarked" from the Type
   list box to display unmarked errors, then select another message
   type from the list box, only the unmarked errors are displayed.

   This problem has been fixed in Iguana 4.5.

  
   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #12914

back to top

#14162 - Screen timeout problems in Iguana

5) [Problem]
   In previous versions of Iguana, some screens will not time out even
   if they have been idle for longer than the specified session timeout
   period.

   In Iguana 4.5, session timeout behavior is consistent. All screens
   will time out after the session timeout period has expired.

  
   [Affected Releases]
   Iguana 4.0 and 4.1


   [Tracking Numbers]
   #14162

back to top

#15361 - ACK messages no longer parsed multiple times

6) [Problem]
   If you create a channel whose destination component is LLP Client,
   and you specify strict verification checking by setting the "ACK
   verification" list box to "Verified ACK Message", the ACK message
   is parsed multiple times. This means that any Python scripts
   created in a custom ACK verification VMD file are executed more
   than once. This may produce undesirable results if the Python
   scripts have "side effects" (if they perform other tasks).

   In Iguana 4.5, this problem has been fixed: ACK messages are
   parsed only once.

  
   [Affected Releases]
   All previous versions of Iguana


   [Tracking Numbers]
   #15361

back to top

#15821 - Global Inbound Post-Process now part of global Python overview

7) [Problem]
   In previous versions of Chameleon, the Global Inbound Post-Process
   Script was not included as part of the Global Python Overview.

   This has been fixed in this version of Chameleon.


   [Affected Releases]
   Iguana 4.0.12 and later, Chameleon 5.1.12 and later


   [Tracking Numbers]
   #15821

back to top

#14041 - Channel edit collision problems fixed

8) [Problem]
   In previous versions of Iguana, if two users are editing a channel at
   the same time, one user's changes may be discarded when the other
   user's changes are saved.

   This problem has been fixed in this version of Iguana.


   [Affected Releases]
   All previous versions of Iguana


   [Tracking Numbers]
   #14041

back to top

#13909 - Channel inactivity notification not affected by starting and stopping channel

9) [Problem]
   In previous versions of Iguana, starting and stopping a channel did
   not reset the timer for channel inactivity email notification rules.

   This meant that, for example, an email notification rule that is
   triggered when a channel has been inactive for the past hour would
   be sent even if the channel was stopped for part of that hour.

   This problem has been fixed in this version of Iguana.


   [Affected Releases]
   Version 4.0 and later of Iguana


   [Tracking Numbers]
   #13909

back to top

Version 4.1 Build 17: August 24, 2010

Bug Fixes

#15209 - Log browser may generate unexpected assertion

1) [Problem]
   If your Iguana server has large log files, you are examining several
   days' worth of log information for a specific channel, and the log
   information is very sparse for that channel, the server may detect an
   unexpected assertion and crash.

   This has been fixed in version 4.1.17 of Iguana.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #15209

back to top

#15206 - Deadlock may occur if multiple channels write to overlapping tables in a database

2) [Problem]
   If multiple channels whose destination component is To Database are
   writing to the same database, and are writing into an overlapping set
   of tables in a different order, a deadlock may occur.

   In version 4.1.17 of Iguana, you can ensure that this problem does
   not occur by setting the IGUANA_USE_INSERT_LOCK environment variable
   to "yes".

   If you are using an older version of Iguana, you must upgrade to
   version 4.1.17 to be able to set IGUANA_USE_INSERT_LOCK.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #15206

back to top

#15482 - Messages treated as successfully processed even if MessageProcessedFlag set to false in plugin

3) [Problem]
   If you have written a plugin that receives messages from an Iguana
   server, and your plugin calls the SetMessagedProcessedFlag() method
   to set the MessageProcessedFlag variable to "false" (to indicate that
   the received message was not successfully processed), Iguana may
   incorrectly generate a log message that states that the message was
   successfully processed.

   In version 4.1.17 of Iguana, if MessageProcessedFlag is set to
   "false" and ResendMessageFlag is set to "true", a warning message is
   written to the logs. If MessageProcessedFlag is set to "false" and
   ResendMessageFlag is set to "false", an error message is written to
   the logs.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #15482

back to top

Version 4.1 Build 16: August 3, 2010

Additions

#14784: Delphi 2010 now supported

1) [Feature Description]
   The Delphi 2010 development environment is now supported. Iguana
   plugins can now be created in Delphi 2010, and Chameleon can now
   generate stubcode for it.


   [Affected Releases]
   Iguana 4.1.16


   [Tracking Numbers]
   #11413

back to top

Bug Fixes

#15262 - Scripted transformation not selected properly in filter

1) [Problem]
   In previous versions of Iguana, if you are specifying a filter when
   creating or editing a channel and you select "Scripted
   transformation" from the "Transformation mode" list box, the filter
   always uses the configuration that was last selected in the VMD file.
   The scripted transformation specified in the "Configuration name"
   field is ignored.

   This has been fixed in version 4.1.16 of Iguana.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #15262

back to top

Version 4.1 Build 15: July 9, 2010

Bug Fixes

#14718: GTS composite definition fixed in HL7_2.6 library

1) [Problem]
   In previous versions of Iguana and Chameleon, the HL7_2.6.vmd file
   that is shipped with Chameleon and Iguana contains an empty
   definition for the GTS composite.

   The version of HL7_2.6.vmd that is shipped with Iguana 4.1.15 and
   Chameleon 5.2.15 includes the correct definition of the GTS
   composite.


   [Affected Releases]
   All releases that include HL7_2.6.vmd.


   [Tracking Numbers]
   #14718

back to top

#15081: msgtransform crashes on unexpected file format

2) [Problem]
   In previous versions of Iguana and Chameleon, the msgtransform
   utility crashed when it was unable to autodetect the format of the
   file to be transformed. It would also crash if an invalid argument
   was specified for the --forceformat option.

   In the version of msgtransform that is included with Iguana 4.1.15
   and Chameleon 5.2.15, an error message is displayed indicating
   either that msgtransform is unable to detect the file format or
   that the --forceformat option is invalid.
   

   [Affected Releases]
   All previous versions of Iguana and Chameleon


   [Tracking Numbers]
   #15081

back to top

#14490: 8-bit hexadecimal escape sequences now handled

3) [Problem]
   Previous versions of Iguana did not properly handle 8-bit \Xxx\
   hexadecimal escape sequences in HL7 messages. This has been fixed in
   Iguana 4.1.15.
   

   [Affected Releases]
   All previous versions of Iguana


   [Tracking Numbers]
   #14490

back to top

#15123: Input file encoding for arbitrary text now handled properly

4) [Problem]
   In version 4.1 of Iguana, if you are creating a channel whose source
   component is From File and you select "Arbitrary Text" as the input
   file, the input file encoding is incorrectly assumed to be UTF-8.
   The file encoding specified in the From File component definition is
   ignored.

   In Iguana 4.1.15, input file encoding for arbitrary text is handled
   properly.
   

   [Affected Releases]
   Version 4.1


   [Tracking Numbers]
   #15123

back to top

#15099: Single machine ID now generated for 64-bit Windows 7 environment

5) [Problem]
   In previous versions of Iguana, in the 64-bit Windows 7 environment,
   Iguana generated separate Iguana IDs for 32-bit and 64-bit
   installations.  This is because of how Windows 7 handles its
   registry.

   In Iguana 4.1.15, a single machine ID is generated for both 32-bit
   and 64-bit versions of Iguana. This means that if you are using a
   64-bit version of Iguana on Windows 7, your machine ID may change
   when you upgrade to version 4.1.15. This is a one-time change;
   future versions of Iguana will use the same machine ID as existing
   versions.

   [Affected Releases]
   Version 4.1


   [Tracking Numbers]
   #15099

back to top

#14413: Problems using SQL Server with ODBC on Windows 2003

6) [Problem]
   In previous releases of version 4.1 of Iguana, problems were detected
   when using SQL Server with ODBC in the Windows 2003 environment.

   These problems have been fixed in version 4.1.15 of Iguana, and
   Iguana now works reliably in this environment.

   [Affected Releases]
   Version 4.1


   [Tracking Numbers]
   #14413

back to top

#14879: Timezone offset now specified for DateTime fields obtained from a database

7) [Problem]
   In Iguana 4.1, when a message was being generated by a channel whose
   source component is From Database, timestamps created from database
   fields would not include timezone offsets.

   Before Iguana 4.1, "+0000" would be appended if the date/time format
   for the timestamp required an offset. This behavior has been
   restored in Iguana 4.1.15.

   [Affected Releases]
   Version 4.1


   [Tracking Numbers]
   #14879

back to top

#14990: Invalid datetime stamp in Python code may crash Iguana

8) [Problem]
   If a Python script in a VMD file creates or processes a date-time
   whose "hour" field is greater than 23, Iguana may crash. This is
   because the Windows strftime() utility that processes dates and
   times generates an assertion when it is passed an invalid time.

   This has been fixed in version 4.1.15 of Iguana. If you are using an
   earlier version of Iguana, you can work around this problem by adding
   code to your Python script that checks that the date and time fields
   it is working with are accurate.

  [Affected Releases]
  Iguana 4.1


  [Tracking Numbers]
  #14990

back to top

Version 4.1 Build 14: May 19, 2010

Bug Fixes

#13451: Rare date range problems in logs screen in AIX

1) [Problem]
   During internal testing of Iguana 4.1, the AIX version of Iguana
   crashed when attempting to search the logs using a specified date
   range. Scrolling the log browser or attempting to export the logs
   may have been contributing factors that caused the crash.

   Continued testing failed to produce a scenario in which a crash would
   consistently occur, so it is highly unlikely that this crash would
   happen in a customer environment. The problem that caused this crash
   to occur has been located, and the problem has been fixed in version
   4.1.14 of Iguana.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13451

back to top

#14446: Deleting a locked log file

2) [Problem]
   Internal testing of Iguana revealed that a problem may occur if it
   tries to delete a log file that is locked by an anti-virus program or
   other external application.

   The likelihood of this problem occurring is extremely rare, and no
   customers have ever encountered it.

   Iguana 4.1.14 now retries a log file deletion if an attempt to delete
   failed because the file was locked.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14446

back to top

#14105: Chameleon crashes when monitor setup changed

3) [Problem]
   Previous versions of Chameleon may crash if you add or disconnect a
   monitor, resize your primary display, or switch from a multi-screen
   machine to a remote session. This is due to a problem in one of the
   underlying Delphi libraries that Chameleon uses.

   This problem has been fixed in version 5.2.14 of Chameleon.


   [Affected Releases]
   All previous versions of Iguana and Chameleon


   [Tracking Numbers]
   #14105 

back to top

#14664: Fast ACK causes lockup if MSH is missing fields

4) [Problem]
   In previous versions of Iguana, a channel whose source component is
   LLP Listener may lock up if the Fast ACK capability is being used to
   acknowledge receipt of a message whose MSH segment contains fewer
   fields than expected.

   This problem has been fixed in version 4.1.14 of Iguana.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14664

back to top

#14639: Message resubmission fails in rare circumstances

5) [Problem]
   In previous versions of Iguana, in rare circumstances, when you
   attempt to resubmit a message, the text "loading..." may be
   resubmitted instead of the message.

   This problem has been fixed in version 4.1.14 of Iguana.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14639

back to top

Version 4.1 Build 13: April 26, 2010

Additions

Python library now includes timestamp functions

1) [Feature Description]
   The Python library that is included with Iguana and Chameleon now
   includes functions that create, validate and process timestamps,
   which are the date/time values that are included in HL7 messages.


   [Affected Releases]
   Iguana 4.1.13 and Chameleon 5.2.13

back to top

Bug Fixes

#14182: Type column in Dashboard incorrectly displays filter icon

1) [Problem]
   In previous versions of Iguana, the Type column in the Dashboard
   sometimes incorrectly displays filtering information. The filter icon
   appears when no filter has been specified for a channel, or vice
   versa.

   If you hover over a filter icon that is displaying incorrect
   information, the correct filter icon appears.

   This has been fixed in version 4.1.13 of Iguana.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14182

back to top

#14163: Errors column not updated when log files purged

2) [Problem]
   If you have sorted your channels using a criterion other than
   alphabetical order by channel name, and the channel sort order has
   recently changed, clicking the value in the Errors column may
   display error log entries for the wrong channel.

   This problem has been fixed in version 4.1.13 of Iguana.

   
   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14163

back to top

#14173: Service error count not updated when log files purged

3) [Problem]
   In previous versions of Iguana, if log files containing service
   error log messages are purged, the Service Error count on the
   Dashboard is not updated to only count the service errors that
   remain.

   This problem has been fixed in version 4.1.13 of Iguana.

   
   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14173

back to top

#14313: Error message generated if log file locked

4) [Problem]
   In previous versions of Iguana, if external software such as
   anti-virus software had locked a log file when Iguana is trying to
   access it, Iguana would immediately generate an error message and
   stop all channels.

   When Iguana 4.1.13 detects that a log file is locked, it will
   re-attempt to access the log file for 30 seconds. If the log file
   remains locked after that, an error message is generated and all
   channels are stopped.
   
   The generated error message contains text similar to the following:
   
   The log index commit system has failed. Possible reasons:
   - The disk has run out of space.
   - An external process (such as antivirus or backup software) is
     locking files in the log system, or has changed the file
     permissions.
   - Some other unknown I/O error occurred, please provide this error
     to iNTERFACEWARE.
   
   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14313

back to top

Known Issues

#14105: Chameleon crashes when monitor setup changed

1) [Description]
   Chameleon may crash if you add or disconnect a monitor, resize your
   primary display, or switch from a multi-screen machine to a remote
   session. This is due to a problem in one of the underlying Delphi
   libraries that Chameleon uses.

   This problem will be fixed in the next release of Iguana and
   Chameleon.


   [Workaround]
   Close Chameleon before adding or removing a monitor.


   [Severity]
   Moderate


   [Affected Releases]
   All existing versions of Chameleon


   [Tracking Numbers]
   #14105

back to top

Version 4.1 Build 12: March 19, 2010

Bug Fixes

#14069: Iguana unresponsive while SSL connections shut down

1) [Problem]
   Iguana 4.1.11 on Windows, and older versions of Iguana on other
   platforms when used with the recently released OpenSSL 0.9.8m, may
   become unresponsive for several seconds while SSL connections are
   being shut down.

   This problem has been fixed in version 4.1.12 of Iguana. 


   [Affected Releases]
   All previous versions of Iguana


   [Tracking Numbers]
   #14069

back to top

Version 4.1 Build 11: March 17, 2010

Additions

#13506: Improvements to active_producer_llp_plugin

1) [Feature Description]
   The following improvements have been added to the
   active_producer_llp_plugin utility:

    * A "component" parameter has been added to make this utility's
      parameters consistent with the parameters supplied to other
      plugins.

    * The --stop_channel_on_error flag tells Iguana to stop the channel
      if the utility detects an error.

    * The --verbose flag indicates that incoming messages and outgoing
      acknowledgment messages will be written to the standard output
      file.

   The active_producer_llp_plugin utility is now located in the
   directory in which Iguana is installed (not in the plugins
   subdirectory).


   [Affected Releases]
   Iguana 4.1.11


   [Tracking Numbers]
   #13506

back to top

value() in Database Result Set object now accepts column name or index

2) [Feature Description]
   The Database Result Set object's value() method now accepts either a
   column name or a column index as its second parameter.


   [Affected Releases]
   Iguana 4.1.11 and Chameleon 5.2.11

back to top

Bug Fixes

#13333: Creating and starting all licensed channels simultaneously generates error

1) [Problem]
   In previous versions of Iguana, if you had created all of the
   channels that your license entitled you to, and you attempted to
   start all of the channels simultaneously when at least one channel
   was already running, Iguana would incorrectly generate an error
   message stating that you were attempting to create more channels than
   was allowed.

   This problem has been fixed in Iguana 4.1.11.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13333

back to top

Version 4.1 Build 10: March 1, 2010

Additions

/DIRECTORY flag added to command-line installer

1) [Feature Description]
   If you are installing Iguana on Windows from the command line prompt,
   you can now use the /DIRECTORY="directory" flag to specify the
   directory into which Iguana is to be installed.


   [Affected Releases]
   Iguana 4.1.10

back to top

Bug Fixes

#13851: Users with administrative permissions unable to update environment variables

1) [Problem]
   In previous versions of Iguana, users other than "admin" who have
   administrative permissions were not able to add or edit
   environment variables.

   This has been fixed in version 4.1.10 of Iguana. 


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13851

back to top

#13857: Newline character no longer required to separate one message from another

2) [Problem]
   In previous versions of Iguana, if you are reading HL7 messages from
   a file, a newline character is required to separate one message from
   another.

   In Iguana 4.1.10, the only requirement is that a new message must
   begin with an MSH segment.


   [Affected Releases]
   Iguana 4.1

   [Tracking Numbers]
   #13857

back to top

#13862: Automatic uninstall sometimes fails on Windows 2000

3) [Problem]
   When version 4.1 of Iguana or version 5.2 of Chameleon was installed
   on Windows 2000, the install.log file was sometimes not successfully
   created. In these situations, automatically uninstalling Iguana and
   Chameleon did not work properly, and they had to be uninstalled
   manually.

   This problem has been fixed in Iguana 4.1.10 and Chameleon 5.2.10.


   [Affected Releases]
   Iguana 4.1 and Chameleon 5.2

   [Tracking Numbers]
   #13862

back to top

#13287: "Legacy database logging" check box not working properly on IE7 and IE8

4) [Problem]
   In version 4.1 of Iguana, if you are using Internet Explorer 7 or 
   Internet Explorer 8, the "Legacy database logging" check box in the
   To Plugin destination component of a channel does not work properly.

   This problem has been fixed in Iguana 4.1.10.


   [Affected Releases]
   Iguana 4.1

   [Tracking Numbers]
   #13287

back to top

#13868: _IGCexceptionGetCode not located when creating a plugin using Borland Delphi

5) [Problem]
   In some earlier versions of Iguana 4.1, you may see the following
   error message when you use Borland Delphi to create a plugin in the
   Windows environment:

     _IGCexceptionGetCode@8 could not be located in IGC.dll

   This error occurs because a symbol was missing from the IGC.dll file.
   This problem has been fixed in Iguana 4.1.10.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13868

back to top

#13866: client_exe and iguana_log_verify not working if Visual Studio 9 DLLs missing

6) [Problem]
   In versions 4.1.8 and 4.1.9 of Iguana, the client_exe and
   iguana_log_verify utility programs do not work properly on versions
   of Windows that are missing the runtime C programming language DLLs
   that Visual Studio 9 uses (such as MSVCR90.dll).

   These DLLs are not normally provided on Windows 2000 or on versions
   of Windows XP for which service packs have not been installed. The
   DLLs can be obtained from Microsoft and installed in your
   environment if needed.

   This issue has been resolved in Iguana 4.1.10.


   [Affected Releases]
   Iguana 4.1.8, Iguana 4.1.9


   [Tracking Numbers]
   #13866

back to top

Version 4.1 Build 9: February 10, 2010

Additions

#13615: Iguana now uses Open SSL0.98l, which patches a plaintext injection vulnerability

1) [Feature Description]
   Version 4.1.9 of Iguana for Windows is built and shipped with the
   latest version of OpenSSL, which is 0.98l. This version of OpenSSL
   patches a vulnerability to potential plaintext injection
   ("man-in-the-middle") attacks.

   If you are using Iguana on Unix, Linux or Mac OS X, you must ensure
   that your system has upgraded to version 0.98l of OpenSSL.
  

   [Affected Releases]
   Iguana 4.1.9


   [Tracking Numbers]
   #13615

back to top

#13741: Show Debug Output window in Chameleon now uses Courier New font

2) [Feature Description]
   The Show Debug Output window in Chameleon now uses the Courier New
   font to display text.  This ensures that this text is easier to
   read.


   [Affected Releases]
   Iguana 4.1.9, Chameleon 5.2.9


   [Tracking Numbers]
   #13741

back to top

#13686: Crash reporting system improved

3) [Feature Description]
   In Iguana 4.1.9, the scope of the crash reporting system has been
   increased and reliability has been improved.


   [Affected Releases]
   Iguana 4.1.9


   [Tracking Numbers]
   #13606

back to top

Bug Fixes

#13110: Encrypt() method in Log Query API may crash

1) [Problem]
   If your application is using the Log Query API, it may crash if it
   calls the Encrypt() method to indicate that HTTPS processing is to be
   used.

   This has been fixed in Iguana 4.1.9.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13110

back to top

#13682: Problems with regular expressions and Unicode character strings fixed

2) [Problem]
   The problems with regular expressions and Unicode character strings
   (strings that are not in Latin-1 format) in Python scripts have been
   resolved in Iguana 4.1.9.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13682

back to top

#13662: On Windows 7 or Vista, Program Compatibility Assistant may appear after program is closed

3) [Problem]
   If you are using Chameleon on a system that is running Windows 7 or
   Windows Vista, or you have started Iguana from the command line,
   the Program Compatibility Assistant window may appear after the
   program is closed. This window appears because Chameleon and Iguana
   are trying to access MSVCP50.DLL, which is not included with
   Windows 7 and Windows Vista.

   Internal testing has determined that Chameleon and Iguana work
   properly even when this DLL file is missing. If the Program
   Compatibility Window appears, click "This program worked correctly"
   to close it.

   Version 4.1.9 of Iguana and version 5.2.9 of Chameleon have been
   modified to no longer look for this library.

   [Affected Releases]
   Iguana 4.1.8, Chameleon 5.2.8


   [Tracking Numbers]
   #13662

back to top

#13314: Filename collision checks improved for To File destination components

4) [Problem]
   In the To File destination component, when you are using
   custom identifiers to generate output file names, the checks for
   potential file name collisions have been improved.

   The following problems have been identified and fixed in
   Iguana 4.1.9:

    * Some custom identifers (such as "%Y_%B_%d_%A_%H_%M.txt") were
      being incorrectly identified as causing a file collision.

    * Some of the generated warning messages referred to format
      specifiers that differed from the ones that were included in
      the custom identifier.

    * A warning message was not generated when a custom identifier
      consisted of "%I", "%f" or "%p" (by itself).


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13314

back to top

#11351: SetCurrentTranslationLocale() method does not allow UTF-8 locale

5) [Problem]
   In version 5.2 of Chameleon, the SetCurrentTranslationLocale()
   method, defined in the ChameleonEncoding class, does not allow you to
   set the locale to "UTF-8".  UTF-8 is required for the correct
   translation of international characters in XML files.

   This problem has been fixed in Chameleon 5.2.9. If you use
   SetCurrentTranslationLocale() to set the locale to "UTF-8", the
   translation codepage is set to use UTF-8 encoding and the current
   locale is set to "C".

 
   [Affected Releases]
   Iguana 4.1, Chameleon 5.2


   [Tracking Numbers]
   #11351

back to top

#13725: Error generated when returning a database table for which column names not specified

6) [Problem]
   If your channel is performing a database query that returns a table
   for which column names have not been specified, you may see the
   following error:

     Error while processing message:
     Failed precondition: ColumnName.size() > 0

   In Iguana 4.1.9, this problem has been fixed.


   [Affected Releases]
   Iguana 4.1

   [Tracking Numbers]
   #13725

back to top

#13617: From File component may stop processing files under very rare circumstances

7) [Problem]
   Under very rare circumstances, the From File component may abruptly
   stop processing files. No errors are reported, and the channel is
   still indicated as running.

   This problem has been fixed in Iguana 4.1.9. All issues with files
   are now handled appropriately.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13617

back to top

#14625: Matching and searching functions allow comparison of an object with zero

8) [Problem]
   In some versions of Iguana, on the Windows platform, the matching and
   searching functions in the Python regular expression library will
   return meaningful results when comparing an object with zero.  In
   Iguana 4.1.9, this is no longer the case.

   It is important to note that comparing an object with zero when
   matching or searching is not supported and will always yield
   unpredictable results. If your code relies on this behaviour, it will
   not function properly.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #14625

back to top

Version 4.1 Build 8: January 19, 2010

Additions

#13284: LLP Listener connection rules modified to allow greater flexibility

1) [Feature Description]
   The connection rules for connecting to channels with an LLP Listener
   source component have been modified to allow greater flexibility.

   The new connection rules are:

    * Channels with an LLP Listener source component now accept a new
      connection from the same IP address if the last processed
      transaction has been completed.

    * If a new connection is from a different IP address, it is accepted
      if the existing connection has been inactive for 5 minutes.
   

   [Affected Releases]
   Iguana 4.1.8


   [Tracking Numbers]
   #13284

back to top

Bug Fixes

#13528: Iguana may crash when processing a message with an unterminated escape sequence

1) [Problem]
   In previous versions of Iguana, attempting to process an HL7 message
   that contains an unterminated escape sequence (for example, "\Xff"
   instead of "\Xff\") could potentially cause Iguana to crash.

   This has been fixed in Iguana 4.1.8.


   [Affected Releases]
   All previous releases of Iguana

   [Tracking Numbers]
   #13528

back to top

#13472: To File destination components may generate filename collisions after forced shutdown

2) [Problem]
   In earlier versions of Iguana, if the Iguana server is shut down
   forcefully due to a crash or other system error and is unable to
   perform its shutdown procedures, channels with To File destination
   components would sometimes generate filename collisions. This
   occurred when the file was completed and Iguana was attempting to
   change the file name from its Iguana temporary name (which has its
   internal channel GUID appended to it) to the file name specified in
   the channel definition.

   In Iguana 4.1.8, this problem no longer occurs, as Iguana now checks
   for potential filename collisions.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13472

back to top

#13461: Header segment no longer required for incoming messages in X12 format

3) [Problem]
   In previous versions of Chameleon, if you specified that incoming
   messages are in X12 format, Chameleon still required a header
   segment to be defined for each message. This was the case even though
   header segments are not always needed for X12 messages. (An X12
   message can consist of one or more sets of segments which are
   bracketed by ST and SE segments. Such messages do not have a header
   segment.)

   In Chameleon 5.2.8, which is included with Iguana 4.1.8, a header
   segment is not required for incoming messages in X12 format.


   [Affected Releases]
   All


   [Tracking Numbers]
   #13461

back to top

#13460: Segments can now be imported if existing segments of the same name already exist

4) [Problem]
   Previous versions of Chameleon did not allow you to import a segment
   definition from the Segment Library if a segment of the same name
   already existed in the VMD file. This restriction was too limiting
   for VMD files that process incoming messages in X12 format: these
   messages can have multiple definitions of segments with the same
   name. The context in which a segment appears is used to determine
   which of the segments of the same name is to be applied.

   In Chameleon 5.2.8, which is included with Iguana 4.1.8, you can
   import a segment definition from the Segment Library even if a
   segment of the same name already exists in the VMD file.

   [Affected Releases]
   All


   [Tracking Numbers]
   #13460

back to top

#13492: Definition of FT composite for NTE segment was empty in HL7 2.6 library file

5) [Problem]
   In the HL7_2.6.vmd file that is shipped with Chameleon and Iguana,
   the definition of the FT composite for the NTE segment was empty.
   In this composite, one field of data type String is required.

   The NTE segment definition in the HL7_2.6.vmd file has been
   updated to include the correct definition of the FT composite.

   [Affected Releases]
   All releases that include HL7_2.6.vmd.


   [Tracking Numbers]
   #13492

back to top

#13622: Iguana may crash if multiple database transactions repeatedly performed at the same time

6) [Problem]
   In high-volume environments in which Iguana is writing large
   quantities of message data to a MySQL database, Iguana may crash if
   multiple database transactions are repeatedly performed at exactly
   the same time. This problem was discovered during in-house quality
   assurance testing, and is extremely unlikely to happen in a normal
   production environment.

   This problem has been fixed in Iguana 4.1.8. If you are using
   a MySQL database in an Iguana production environment, we recommend
   that you upgrade to the latest version of Iguana.


   [Affected Releases]
   All


   [Tracking Numbers]
   #13622

back to top

#13437: Error message displayed if you log in to Iguana after the server runs out of space

7) [Problem]
   If your server runs out of disk space, you may see the following
   error message when you attempt to log in to Iguana the day after the
   disk space is exhausted:

     Failed precondition: PushResult

   This is due to an internal problem in the Iguana logging system.
   This problem has been fixed in Iguana 4.1.8.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13437

back to top

Version 4.1 Build 7: January 6, 2010

Bug Fixes

#13479: Iguana crashes when script accesses message.log_id while previewing resubmit

1) [Problem]
   If you are attempting to preview a resubmitted message to a channel
   whose destination component is To Database, and the VMD file for the
   channel contains a Python script that is accessing the message.log_id
   field, previous versions of Iguana will crash.

   This has been fixed in Iguana 4.1.7.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13479

back to top

#13448: Iguana 4.1.6 does not work on Windows 2000

2) [Problem]
   Due to changes to the compiler optimization settings, Iguana 4.1.6
   does not work in the Windows 2000 environment.

   Versions of Iguana prior to 4.1.6 should work in Windows 2000.

   The problem has been fixed in version 4.1.7, and this version has
   been confirmed to work in the Windows 2000 environment.


   [Affected Releases]
   Iguana 4.1.6


   [Tracking Numbers]
   #13448

back to top

#13408: %f format specifier does not yield consistent results

3) [Problem]
   In previous versions of Iguana, the %f format specifier, which
   includes the milliseconds portion of the current time in a custom
   file ID generated by a To File destination component, did not yield
   consistent results. The %f specifier could be replaced by anywhere
   from 1 to 3 digits, depending on the number of milliseconds in the
   current time.

   In Iguana 4.1.7, the %f format specifier always returns a 3-digit
   value. If the number of milliseconds in the current time is less than
   100, zeroes are added at the left (for example, 43 becomes 043).

   This change ensures that the sort order of the files generated by
   this To File destination component matches the order in which the
   files were generated.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13408

back to top

#13481: Users with SMS address but no email address cannot receive email notifications

4) [Problem]
   In Iguana 4.1.7, when you are creating a new email notification
   rule, users with an SMS address but no email address are now
   included in the list of possible recipients.

   In addition, the tooltip that appears when you hover over the
   recipient of an email notification now includes the user's SMS
   address only if this address has been specified. In previous
   versions of Iguana, the SMS address was displayed as blank.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13481

back to top

#12871: Environment variables with non-alphanumeric characters not created properly

5) [Problem]
   In earlier versions of Iguana, environment variables whose name and
   value consist of characters that are non-numeric and non-alphabetic
   are sometimes not created properly.

   This problem has been fixed in Iguana 4.1.7.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #12871

back to top

#12940: Environment variables containing environment variable values not working properly

6) [Problem]
   In earlier versions of Iguana, attempting to define an environment
   variable whose value includes a previously defined environment
   variable did not always work properly.

   This problem has been fixed in Iguana 4.1.7.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #12940

back to top

#13484: Database connection problems when previewing a message resubmitted to a To Database channel

7) [Problem]
   In earlier versions of Iguana, database connection problems could
   occur when previewing a message that is being resubmitted to a
   channel whose destination component is To Database. These problems
   may occur when the channel's data source entry includes an
   Iguana-defined environment variable specification.

   This problem has been fixed in Iguana 4.1.7. Note that the problem
   only occurred when the message was being previewed: messages that
   are resubmitted to this channel are processed normally.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13484

back to top

#13434: Iguana may crash if MySQL database stopped while checking for incoming messages

8) [Problem]
   If a channel whose source component is From Database is checking a
   MySQL database for incoming messages, Iguana may crash if the
   database is unexpectedly stopped.

   This has been fixed in version 4.1.7 of Iguana.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13434

back to top

Version 4.1 Build 6: December 10, 2009

Additions

#12928: New fields added to log query API classes

1) [Feature Description]
   New fields have been added to the classes defined for the log query
   API.

   The following methods have been added to the LogQuery class:

   Encrypt
   IncludeMarkedErrorMessages
   IncludeUnmarkedErrorMessages

   The following methods have been added to the LogMessage class:

   Deleted
   IsResubmission
   MarkedError
   Resubmitted
   ReferenceLogId


   [Affected Releases]
   Iguana 4.1.6


   [Tracking Numbers]
   #12928

back to top

#13402: New channel information included with Dashboard data export

2) [Feature Description]
   In Iguana 4.1.6, the following channel information is now included
   whenever Dashboard data is exported in either XML format or text
   format:

   TotalProcessed
   CurrentProcessed
   LastActivityTime

   These fields can also be found on the channel's Control Panel. The
   values of these fields are identical to the values displayed there.


   [Affected Releases]
   Iguana 4.1.6


   [Tracking Numbers]
   #13402

back to top

#13196: Legacy database logging in To Plugin now improved

3) [Feature Description]
   In Iguana 4.1.6, the legacy database logging feature of the To Plugin
   destination component has been improved. If the Iguana channel is
   unable to connect to the legacy database, you can now specify how
   often to attempt to reconnect and how long to wait between
   reconnection attempts.

   The log messages that are generated have also changed. Iguana now
   generates an Informational log message when the plugin has processed a
   message, and generates a Success log message when the message has been
   successfully logged in the legacy database.


   [Affected Releases]
   Iguana 4.1.6


   [Tracking Numbers]
   #13196

back to top

Bug Fixes

#12521: Some preview text is not displayed if an environment variable is included

1) [Problem]
   In previous versions of Iguana, if the text in a text field includes
   an environment variable and is only a few characters long, the
   preview field for this text is not displayed in the expected
   location. (The preview field displays the contents of the text field
   after the environment variable is replaced by its value.)
 
   This has been fixed in Iguana 4.1.6.

   Note that this is only a cosmetic issue. The text field has always
   contained the correct expanded value of the environment variable.
 

   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #12521

back to top

#13285: Data corruption possible in large character strings in C# or VB.NET Log Query API

2) [Problem]
   Internal quality assurance testing has detected that when the Log
   Query API is being accessed from an application written in C# or
   VB.NET, data corruption may occur in large character strings because
   of a problem with memory allocation and deallocation.

   This problem has not appeared at any customer sites to date, and has
   been fixed in Iguana 4.1.6.
 

   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13285

back to top

Version 4.1 Build 5: December 3, 2009

Additions

#13349: Stop channel now default option for some To Database radio buttons

1) [Feature Description]
   If you are creating a channel whose destination component is To
   Database, the default value for the "On database error" and "On
   VMD parse error" radio buttons is now "Stop channel". This is because
   stopping the channel when an error occurs is the safer alternative in
   many environments.
   

   [Affected Releases]
   Iguana 4.1.5


   [Tracking Numbers]
   #13349

back to top

Bug Fixes

#13264: Open file socket limit in Windows increased from 256 to 2048

1) [Problem]
   In version 4.1.4 of Iguana and earlier, the number of open file
   sockets in the Windows environment was restricted to 256. This
   imposed a limit on the number of channels that could be created with
   a source component of LLP Listener and a destination component
   of To Database - less than 150 of these channels could be created.

   In Iguana 4.1.5, the limit on the number of open file sockets in the
   Windows environment has been increased from 256 to 2048. This makes
   it possible to create and run 150 or more channels whose source
   component is LLP Listener and whose destination component is To
   Database.
   

   [Affected Releases]
   Iguana 4.0 and Iguana 4.1


   [Tracking Numbers]
   #13264

back to top

#13292: Problems displaying log message with multiple destinations in Safari

2) [Problem]
   In Iguana 4.1, if you are using Safari, a problem exists with parsing
   a message from within the log browser.  If the message has been
   routed to two or more channels whose destination component is To
   Database, the list box that displays the list of channels also
   provides an extra meaningless option.

   This extraneous option has been removed in Iguana 4.1.5.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13292

back to top

#11111: Iguana may crash when in panic mode if date changes

3) [Problem]
   When Iguana detects that the drive on which its logs are stored is
   running out of space, it switches into an internal "panic mode" in
   which it limits the amount of disk space that it uses.

   In earlier versions of Iguana, if it is in panic mode, a crash could
   occur when the current date changes. This crash never occurs if there
   is sufficient log message space available.

   This problem has been fixed in Iguana 4.1.5.


   [Affected Releases]
   Iguana 4.0 and Iguana 4.1


   [Tracking Numbers]
   #11111

back to top

#13298: Email notification not disabled until Iguana restarted

4) [Problem]
   Email notification messages were being sent even after email
   notification had been explicitly disabled via the Disable Email
   Notification button in the E-mail Notification screen. Disabling of
   email notification did not take effect until Iguana had been
   restarted. 

   This problem has been fixed in Iguana 4.1.5.


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13298

back to top

Version 4.1 Build 4: November 26, 2009

Additions

#13205: Database and Database Result Set objects now provide better error messages

1) [Feature Description]
   The Database and Database Result Set objects that are included in the
   Chameleon Python API now provide more informative error messages when
   problems are detected.


   [Affected Releases]
   All previous versions of Iguana in which these objects are defined.


   [Tracking Numbers]
   #13205

back to top

#12960: Log re-indexing now much faster

2) [Feature Description]
   In Iguana 4.1.4, re-indexing of the logs after an unexpected server
   crash is now approximately five times faster than in previous
   versions of Iguana. For any site with more than 500 MB of log data
   per day, this is a significant improvement.


   [Affected Releases]
   Iguana 4.0 and 4.1


   [Tracking Numbers]
   #12960

back to top

#13215: Error message changed if From Database component cannot read from its database

3) [Feature Description]
   In Iguana 4.1.4, when a channel whose source component is From
   Database is unable to read a message from its database, the error
   message that is generated has been changed. The text "Error While
   Generating" is now added to the beginning of the error message before
   it is written to the Status column of the status table entry. This
   makes it easier to detect that a problem has occurred.

   As in previous versions of Iguana, the text that is written to the
   Status column is truncated if it is longer than 255 characters. 


   [Affected Releases]
   Iguana 4.0 and 4.1


   [Tracking Numbers]
   #13215

back to top

#13241: Log messages for From Database component Status column update now improved

4) [Feature Description]
   In Iguana 4.1.4, when a channel whose source component is From
   Database updates the Status column of the status table field, the
   log messages that are added to the Logs to report this event now
   provide an improved description of the update.
   

   [Affected Releases]
   Iguana 4.0 and 4.1


   [Tracking Numbers]
   #13241

back to top

#11517: Log message for plugin message write now of type Informational

5) [Feature Description]
   In Iguana 4.1.4, when a channel whose destination component is To
   Plugin sends a message to a plugin, a log message of type
   Informational is written to the logs. This message contains the
   text "Message written to plugin".

   In previous versions of Iguana, this log message was of type
   Debug.
   

   [Affected Releases]
   Iguana 4.0 and 4.1


   [Tracking Numbers]
   #11517

back to top

Bug Fixes

#13074: Legacy plugin API for C# and VB.NET sometimes does not handle acknowledgment properly

1) [Problem]   
   In versions of Iguana prior to version 4.1.4, the legacy plugin API
   for C# and VB.NET may not handle message acknowledgment properly
   under extraordinary circumstances, such as when insufficient disk
   space makes it impossible for Iguana to enqueue the message generated
   by the plugin.

   When Iguana cannot enqueue the message under these circumstances, the
   MessageSucceeded flag passed to the plugin's MessageRequestCompleted
   event handlers may be erroneously set to true, even though the
   message was not enqueued.

   This potential problem was detected during internal QA testing and
   has yet to occur in any application that uses the legacy plugin API.
   This problem has been fixed in version 4.1.4 of Iguana.

   
   [Severity] 
   Minor


   [Affected Releases]
   All versions of Iguana prior to 4.1.4 that support the C# and VB.NET
   legacy plugin API.


   [Tracking Numbers] 
   #13074

back to top

#13199: Page Help sidebar for channel configuration page not displayed properly

2) [Problem]   
   In version 4.1.3 of Iguana, when you click on a channel name in the
   Dashboard to display the channel configuration page, the Page Help
   sidebar is missing its external border and proper coloring (though
   the links themselves are still correct). These appearance issues
   have been fixed in version 4.1.4.

   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1.3


   [Tracking Numbers] 
   #13199

back to top

#13201: Channel Groupings screen displays wrong help link in Page Help sidebar

3) [Problem]   
   In version 4.1 of Iguana, the Page Help sidebar for the Channel
   Groupings screen displays the wrong help link. This has been fixed in
   Iguana 4.1.4.

   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers] 
   #13201

back to top

#11194: Screens not displayed properly when browser page cache not cleared after upgrade from 4.0

4) [Problem]   
   If you upgrade from version 4.0 of Iguana to any version of Iguana
   from 4.1 to 4.1.3 and you do not clear your browser's page cache,
   some screens may not be displayed as expected. This is because some
   of the Javascript files have become stale.

   In Iguana 4.1.4, a unique GET parameter is associated with each
   Javascript file request, which avoids this problem.

   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers] 
   #11194

back to top

#13192: Browse buttons in HTTPS Channel Settings screen not working

5) [Problem]   
   In Iguana 4.1, if you are in the HTTPS Channel Settings screen and
   you select the "Use dedicated port" radio button, the Browse buttons
   in the Certificate File and Private Key File fields do not work.
   This has been fixed in Iguana 4.1.4.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers] 
   #13192

back to top

#13212: Heading row in Environment Variables page not displayed properly in IE7

6) [Problem]   
   In Iguana 4.1, if you are using Internet Explorer 7, the heading row
   in the Environment Variables page is not displayed properly: it is
   too wide for the page. This has been fixed in Iguana 4.1.4.

   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers] 
   #13212

back to top

#13232: Information in Log Usage screen not displayed properly

7) [Problem]   
   In Iguana 4.1, the information on the Log Usage screen is accurate
   but is not displayed properly in its window. In Iguana 4.1.4, this
   information is displayed more clearly.

   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers] 
   #13232

back to top

#13202: Python errors difficult to diagnose because of stack dumps

8) [Problem]
   In Iguana 4.1.3, certain error messages caused stack dumps to be
   generated, which made it difficult to diagnose some Python errors.
   This problem has been fixed in Iguana 4.1.4.

   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13202

back to top

#13245: Channel status flickers from green to yellow and back again

9) [Problem]
   In Iguana 4.0 onwards, on busy servers, the status square
   for channels whose destination is To Database may occasionally
   change briefly from green to yellow and back again. This is because
   Iguana was changing the status of the channel while it was checking
   whether the database connection was still valid.  This would be only
   noticeable at sites with slow-responding database servers.

   In Iguana 4.1.4, the status square remains green while Iguana
   checks whether the database connection is still valid. The status
   only changes if the connection to the database fails and Iguana is
   retrying the connection. This means that the brief changes in
   color should no longer appear.

   Note that the interaction between the channel and the database
   connection has not been changed. This fix is simply a cosmetic
   issue.


   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13245

back to top

#13231: Text field containing environment variable value not displayed properly

10)[Problem]
   If a text field contains a directory path, and the value of an
   environment variable is included as part of the text in this field
   (as in, for example, "${iguana_dir}/autoack.vmd"), clicking Browse
   does not properly display the directory in which the file is
   contained.

   This has been fixed in Iguana 4.1.4.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13231

back to top

#13193: Port in use warning now links to the screen in which the port is defined

11)[Problem]
   In Iguana 4.0, if you were creating an LLP Listener source component
   for a channel and a Warning appeared that indicates that the port
   that you have selected is in use, the Warning contained a link to the
   Iguana screen in which the port was previously defined.  In Iguana
   4.1, the link was not provided.
 
   This has now been corrected in Iguana 4.1.4.

  
   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13193

back to top

#13250: Connection parameters cannot be exported if incorrect in one component

12)[Problem]
   In Iguana 4.1, if you create a channel whose source component is From
   Database and whose destination component is To Database, and the
   connection parameters for one of the components are incorrect, the
   tables for the other component cannot be exported either.

   This problem only occurs when connection parameters for a component
   are incorrect. If the connection parameters for both components are
   correct, both the source and destination components can be
   successfully exported.

   This problem has been fixed in Iguana 4.1.4.

  
   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #13250

back to top

#12967: Bookmark Search now generates a popup dialog box on all browsers

13)[Problem]
   In Iguana 4.1, in the Logs screen, using the Bookmark Search button
   in the Search Criteria panel generated a Javascript Alert message
   on these browsers:

    * Google Chrome 3.0.1 on Windows
    * Safari 4.0.3 on Mac OS X
    * Mozilla Firefox 3.0.7 and 3.5.3 on Windows
    * Mozilla Firefox 3.0 on Mac OS X

   In Iguana 4.1.4, the Bookmark Search button now consistently
   generates a popup dialog box on all browsers. This makes this
   functionality more generic and flexible.

  
   [Affected Releases]
   Iguana 4.1


   [Tracking Numbers]
   #12967

back to top

#13101: Duplicate file IDs may be generated if system time is rolled back

14)[Problem]
   If you have created a channel whose destination component is To
   File, and you have selected "Unique ID" from the "Use as file ID"
   list box, the file ID generator that is used to create unique file
   IDs may generate duplicate file IDs when the system time is rolled
   back. For example, this may occur when clocks are changed from
   Daylight Savings Time to Standard Time.

   If a duplicate file ID is generated, the channel will stop due to
   the filename error. No data will be overwritten or lost.

   This problem has been fixed in Iguana 4.1.4.

  
   [Affected Releases]
   Iguana 4.0 and Iguana 4.1


   [Tracking Numbers]
   #13101

back to top

#13224: SGMstringPool error message generated in 64-bit Windows environments

15)[Problem]
   In 64-bit Windows environments, some Python scripts may cause the
   following error to be generated:

     TypeError: SGMstringPool index must be integer

   This error occurred because some internal values were being stored
   as 32-bit integers instead of 64-bit integers.

   This problem has been fixed in Iguana 4.1.4.

  
   [Affected Releases]
   Iguana 4.0 and Iguana 4.1


   [Tracking Numbers]
   #13224

back to top

Version 4.1 Build 3: November 16, 2009

Additions

back to top

#13079: LLP Listener now uses fewer threads

1) [Feature Description] 
   The performance of the LLP Listener source component has been
   improved in Iguana 4.1.3. Each LLP Listener component now uses two
   fewer threads than were used in Iguana 4.1.2.


   [Affected Releases] 
   Iguana 4.1.3
 

   [Tracking Numbers] 
   #13079

back to top

#13156: Log indexing system now optimized to minimize memory usage

2) [Feature Description] 
   In Iguana 4.1.3, the log indexing system has been optimized to ensure
   that, over a long period of time, the amount of memory used is
   contained.


   [Affected Releases] 
   Iguana 4.1.3
 

   [Tracking Numbers] 
   #13156

back to top

#12964: Interaction with the Environment Variables screen has been improved

3) [Feature Description] 
   Interaction with the Environment Variables screen has been improved
   in Iguana 4.1.3:

     * In Iguana 4.1.2, in some browsers, the table header did not stay
       in place when the screen was scrolled. In Iguana 4.1.3, the table
       header stays in place on all browsers.

     * In Iguana 4.1.2, if you clicked on an environment variable to
       edit it, the cursor was always positioned in the Name field. If
       you wanted to edit the value of the environment variable, you
       needed to use your mouse or the Tab character to position your
       cursor in the Value field.

       In Iguana 4.1.3, environment variable editing has become more
       precise. If you click on the name of an environment variable, the
       cursor is positioned in the Name field. If you click on the value
       of an environment variable, the cursor is positioned in the Value
       field.


   [Affected Releases] 
   Iguana 4.1.3
 

   [Tracking Numbers] 
   #12946

back to top

#13120: From File components now write a debug log message when reading a message

4) [Feature Description] 
   Channels that have From File as their source component now write a
   log message of type Debugging to the logs whenever a message is read
   from a file. This log message contains the name of the file and the
   position of the message in the message queue. This log message is
   helpful if you are having trouble with reading from files.

   To view this log message, you must set your channel's logging level
   to Debug. See "Changing the Logging Level" in the iNTERFACEWARE
   Products Manual for details on how to change the channel logging
   level.

  
   [Affected Releases] 
   Iguana 4.1.3
 

   [Tracking Numbers] 
   #13120

back to top

Bug Fixes

#13012: Permission errors when reading or writing files not appearing in the logs

1) [Problem]   
   In version 4.1.2 of Iguana, if a From File channel source component
   is attempting to read a file and is unable to do so because it does
   not have the necessary permissions, the resulting error does not
   appear in the logs.

   Similarly, if a To File destination component is attempting to write
   a file but does not have the necessary permissions, the resulting
   error does not appear in the logs.

   This has been fixed in version 4.1.3 of Iguana.


   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.1.2


   [Tracking Numbers] 
   #13012

back to top

#13152: Logs screen does not stretch properly on some browsers

2) [Problem]   
   In version 4.1.2 of Iguana, on some browsers, the Logs screen does
   not stretch to the bottom of the window in which it is contained.

   This has been fixed in version 4.1.3 of Iguana.


   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1.2


   [Tracking Numbers] 
   #13152

back to top

#13052: Source Type list box not displayed in IE8

3) [Problem]   
   In Iguana 4.1.2, if you are using Internet Explorer 8 and you are
   creating an email notification rule, the Source Type list box is
   not displayed. The source type is assumed to be Channel.

   This problem has been fixed in Iguana 4.1.3.


   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1.2


   [Tracking Numbers] 
   #13052

back to top

#13045: Logging API documentation pages for Delphi are missing

4) [Problem]   
   In Iguana 4.1.2, some of the logging API documentation pages
   were missing from the documentation pages for Delphi users.
   These have been added in Iguana 4.1.3.


   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.1.2


   [Tracking Numbers] 
   #13045

back to top

Version 4.1 Build 2: November 3, 2009

Known Issues

#13029: Plugins not supported for Borland Delphi 3.0

-----------------------------------------------------------------------
#13029
-----------------------------------------------------------------------


[Description]
At this time, iNTERFACEWARE does not plan to support plugins in
Borland Delphi 3.0.

If this is a significant requirement for your organization, please
contact us. 


[Workaround]
Use a supported version of Delphi. Borland Delphi 4.0 is supported, as
are more recent versions of Delphi up to and including CodeGear
Delphi 2009.


[Severity]
Moderate


[Affected Releases]
Iguana 4.1

back to top

#12559: Problems with environment variable screen shortcut keys

-----------------------------------------------------------------------
#12559
-----------------------------------------------------------------------


[Description]
The following known issues exist for the environment variable screen
shortcut keys in Iguana 4.1:

 * If you are using Safari or Google Chrome, the environment variable
   screen does not scroll properly when you use the Ctrl+UpArrow and
   Ctrl+DnArrow shortcut keys.

 * If you are using the shortcut keys to navigate the environment
   variable screen, you may occasionally see two environment variables
   highlighted at the same time.

 * If you have defined your own shortcut key mappings, using the
   shortcut keys defined for the environment variable screen may not
   produce the result that you expect. User-defined shortcut key
   mappings normally override the environment variable screen shortcut
   keys.


[Workaround]
Use the mouse to navigate the environment variable screen.


[Severity]
Minor


[Affected Releases]
Iguana 4.1

back to top

#12998: Small memory leak when using ODBC to connect to a PostgreSQL database

-----------------------------------------------------------------------
#12998
-----------------------------------------------------------------------


[Description]
If you are using Iguana on Unix, Linux or Mac OS X and you have created
a channel that uses ODBC to connect to a PostgreSQL database, you may
notice a memory leak of 60 bytes every time you connect to the channel.
This is due to a bug in some versions of PostgreSQL.


[Workaround]
No workaround needed, as the memory leak is very small.


[Severity]
Minor


[Affected Releases]
Iguana 4.1

back to top

#12938: Environment Variables tooltip not displayed properly in Safari

-----------------------------------------------------------------------
#12938
-----------------------------------------------------------------------


[Description]
If you are using Safari, you are in the Environment Variables screen,
and you hover over the value of an environment variable whose value has
been changed, the tooltip that is displayed might not fit on the screen
if the new value of the environment variable is very long.

This is because Safari does not allow word wrapping on any
character other than a white space character (spaces or tabs).


[Workaround]
Use a different browser.


[Severity]
Minor


[Affected Releases]
Iguana 4.1

back to top

Version 4.0 Build 12: September 10, 2009

Known Issues

#12997: Iguana may crash if logging in with unknown username

-----------------------------------------------------------------------
#12997
-----------------------------------------------------------------------


[Description]
If your Iguana session expires and you are asked to log in again,
versions 4.0 to 4.0.12 of Iguana could crash if you type a username
that does not exist. This will be fixed in version 4.1 of Iguana.


[Workaround]
None


[Severity]
Moderate


[Affected Releases]
Iguana versions 4.0 through 4.0.12

back to top

#12826: Changing "Attempt to reconnect?" in LLP Client not always working

-----------------------------------------------------------------------
#12826
-----------------------------------------------------------------------

[Description]
If you have created a channel whose destination component is LLP
Client and you have selected "Yes (unlimited)" from the "Attempt to
reconnect?" list box, and then you edit the channel to change the value
of this list box to "No", this change does not appear in the channel.

Changing the value of the "Attempt to reconnect?" list box from
"Yes (unlimited)" to "Yes, with limit" works properly, as does
changing it from "Yes, with limit" to "No".

This problem will be fixed in Iguana 4.1.

[Workaround]
Edit the channel and change the value of the "Attempt to reconnect"
list box from "Yes (unlimited)" to "Yes, with limit". Then, edit the
channel again and change it from "Yes, with limit" to "No".


[Severity]
Moderate


[Affected Releases]
Iguana 4.0

back to top

#12577: Dashboard flicker in Firefox 3.5 on Mac OS X

-----------------------------------------------------------------------
#12577
-----------------------------------------------------------------------


[Description]
If you are using Firefox 3.5 on Mac OS X, you may notice that the
Dashboard flickers occasionally if you have created a number of
channels. This is due to a problem in this version of Firefox.

Optimizations will be added to Iguana 4.1 to work around this problem
and ensure that flickering does not occur.

[Workaround]
Download and install a different version of Firefox for Mac OS X.


[Severity]
Minor


[Affected Releases]
Iguana 4.0

back to top

#11138: Iguana desktop shortcut on Vista always points to localhost:8081

------------------------------------------------------------------------
#11138
------------------------------------------------------------------------


[Description] 
If you are installing Iguana on Windows Vista, the URL specified in the
Desktop shortcut file always points to localhost:8081, regardless of
what port you have specified in the installation. This is due to a
problem in Windows Vista.


[Severity of Problem] 
Minor


[Workaround]
Edit the shortcut file to point to the proper port.


[Affected Releases] 
Iguana 4.0

back to top

Version 4.0 Build 11: August 21, 2009

Additions

#12339: HL7 2.6 and 2.5.1 library files now include example tables

1) [Feature Description] 
   The VMD library files for version 2.6 and version 2.5.1 of the HL7
   standard now include example tables. These example tables are similar
   to those found in the other VMD library files that are included as
   part of the Chameleon and Iguana installation.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #12339

back to top

Bug Fixes

#12381: Export Database Tables not working properly with Interbase

1) [Problem]   
   In version 4.0.10 of Iguana, if a channel is interacting with an
   Interbase database, the Export Database Tables feature does not work
   properly. This is because the command that this version of Iguana
   uses to create the tables includes the DEFAULT keyword, which is not
   supported in Interbase.

   This has been fixed in version 4.0.11 of Iguana.

   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0.10


   [Tracking Numbers] 
   #12381

back to top

Version 4.0 Build 10: August 7, 2009

Additions

#12109: HL7 2.5.1 and 2.6 library files now included

1) [Feature Description] 
   VMD library files for version 2.6 and version 2.5.1 of the HL7
   standard have been included with this release. They are located in
   the Libraries subdirectory of the directory in which Chameleon is
   installed, and are named "HL7_2.6.vmd" and "HL7_2.5.1.vmd".


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #12109

back to top

#12092: Support added for Interbase, DB2, Filemaker Pro, Informix

2) [Feature Description] 
   In Iguana 4.0.10, support has been added for the following ODBC-based
   database APIs:

      Interbase
      DB2
      Filemaker Pro
      Informix
   

   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #12092, #12243

back to top

#11972: OCI driver now more stable

3) [Feature Description] 
   Minor enhancements have been added to the OCI driver to provide
   greater stability.
   

   [Affected Releases] 
   Iguana 4.0.10
 

   [Tracking Numbers] 
   #11972

back to top

Bug Fixes

#11950: Executable path in To Client Executable not split properly in upgrade

1) [Problem]   
   When you are upgrading from Iguana 3.3 to Iguana 4.0, and you have
   defined a channel whose destination component is To Client
   Executable, the "Executable Path" field defined in Iguana 3.3 is not
   split properly into the "Full executable path" and "Executable
   parameters" fields defined in Iguana 4.0 if the executable path
   contains a space.

   For example, if the executable path is
   "C:\Program Files\myprog.exe myparam", the "Full executable path"
   field is incorrectly set to be "C:\Program", and the "Executable
   parameters" field is set to "Files\myprog.exe myparam".

   This has been fixed in Iguana 4.0.10: when splitting the "Executable
   Path" field, everything up to ".exe" is now always included in the
   "Full executable path" field.

   This problem will never occur in channels that have been created
   using Iguana 4.0.
   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #11950

back to top

#11300: Pasted text now written as multiple lines

2) [Problem]   
   In previous versions of Iguana 4.0, if you copied a message from the
   logs and pasted it into a file or into an application such as
   Chameleon, the pasted text appeared as a single long line.

   In Iguana 4.0.10, this problem has been fixed: messages that are
   copied from the logs and pasted into a file or other application
   are written as multiple lines of text. Each message segment is on
   a separate line.

      
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #11300

back to top

Known Issues

#12021: Table Inbound Script can now assign 0 to "value" variable

-----------------------------------------------------------------------
#12021
-----------------------------------------------------------------------

[Description]
In previous versions of Chameleon that support the version 5.0
parser engine, if a Table Inbound Script assigned 0 to the "value"
variable, the parser engine converted 0 to None. This meant that
the null value was written to the database field that corresponded
to the table column.

In Chameleon 5.1.10, this has been fixed: if a Table Inbound Script
assigns 0 to "value", 0 is written to the corresponding database
field.

[Workaround]
Use the following Segment Inbound Script for the segment field
that is mapped to the table entry:

if value == '':
	value = '0'


[Severity]
Moderate


[Affected Releases]
Chameleon 5.0 and 5.1

back to top

#12243: Cannot specify primary key for Filemaker Pro using ODBC

------------------------------------------------------------------------
#12243
------------------------------------------------------------------------
[Description] 
If you are using the ODBC client with Filemaker Pro, you cannot specify
a primary key when creating a table, as Filemaker Pro does not support
this.

When you create a table in Filemaker Pro, it will attempt to
determine the primary key for you. You can use the Filemaker client to
specify the primary key in a table after it has been created.

[Severity of Problem] 
Moderate


[Workaround]
Use the Filemaker client to specify the primary key for the table.


[Affected Releases] 
Iguana 4.0.10

back to top

#11073: Must set TCP.CONNECT_TIMEOUT when using OCI Oracle

------------------------------------------------------------------------
#11073
------------------------------------------------------------------------
[Description] 
If you are using OCI Oracle in an Iguana channel, you must set the
following value in the sqlnet.ora file that is defined for your Oracle
client:

TCP.CONNECT_TIMEOUT=5

This tells the Oracle client to time out if a connection to the Oracle
server cannot be obtained within 5 seconds. If sqlnet.ora does not
exist, create it in the directory that contains the tnsnames.ora file
that is defined for your Oracle client.

The Oracle default is to never time out if a connection cannot be
established. This can cause problems if the server is down or cannot be
reached.


[Severity of Problem] 
Moderate


[Workaround]
Update sqlnet.ora as defined above.


[Affected Releases] 
Iguana 4.0

back to top

Version 4.0 Build 9: July 2, 2009

Additions

#11957: SocketHandle and IsValidSocketHandle properties added

1) [Feature Description] 
   The SocketHandle and IsValidSocketHandle properties have been added
   to the connection interface classes.
   

   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #11957

back to top

Bug Fixes

#11862: Header information repeatedly included in CSV log file output

1) [Problem]
   When log files are exported in CSV format, the header information is
   repeatedly included in the output.

   This has been fixed in Iguana 4.0.9.
   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #11862

back to top

#11937: Incoming message streams not handled properly if fields missing

2) [Problem] 
   Previous versions of Chameleon 5.1 did not correctly handle incoming
   message streams where fields in a message segment are mapped to
   fields in a table, but may or may not be present. If a message from
   this stream contains a segment that is missing a field, an error is
   incorrectly generated. This has been fixed in Chameleon 5.1.9.
   
   [Severity] 
   Moderate


   [Affected Releases]
   Chameleon 5.1


   [Tracking Numbers] 
   #11937

back to top

#11949: Iguana may crash if error encountered when stopping

3) [Problem] 
   Under certain circumstances, Iguana 4.0 will crash if a channel
   encounters an error when it is about to stop.  This is related to
   the queuing system.  It is a reasonably rare race condition that
   has not been seen in the field.

   The issue has been fixed in Iguana 4.0.9.  It is recommended for this
   reason that customers upgrade to Iguana 4.0.9 or above.
   
   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #11949

back to top

Version 4.0 Build 8: June 17, 2009

Bug Fixes

#11567: Permission errors with network shares may generate an exception

1) [Problem] 
   In previous versions of Iguana 4.0, permission issues with network
   shares could generate an exception when attempting to edit a channel.
   This has been fixed in version 4.0.8 of Iguana.
   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #11567

back to top

Known Issues

#11392: SSL connections dropped if Iguana unable to send data for 5 seconds

------------------------------------------------------------------------
#11392
------------------------------------------------------------------------
[Description] 
In Iguana 4.0, SSL connections are dropped if Iguana is unable to send
data for approximately five seconds. In Iguana 4.1, data is cached and
is sent as soon as possible.

Iguana 4.0 also had difficulty sending secure exports when used in the
Safari browser. This problem will be fixed in Iguana 4.1.

[Severity of Problem] 
Moderate


[Workaround]
None


[Affected Releases] 
Iguana 4.0

back to top

Version 4.0 Build 7: May 4, 2009

Version 4.0 Build 6: April 20, 2009

Additions

#11143: New radio buttons added to To Database component

1) [Feature Description] 
   Two new sets of radio buttons have been added to the "To Database"
   destination component of an Iguana channel:

   * The "On database error" radio buttons control whether you want your
     channel to be stopped when a database error occurs. Select "Skip
     message" if you want the message causing the error to be skipped,
     or select "Stop channel" if you want the channel to be stopped when
     a database error occurs.

   * The "On VMD parse error" radio buttons control whether you want
     your channel to be stopped when an error is detected during the
     parsing of the VMD file specified in the "Full parser VMD path"
     field. Select "Skip message" if you want the message causing the
     error to be skipped, or select "Stop channel" if you want the
     channel to be stopped when a parse error occurs.
   

   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #11143

back to top

Bug Fixes

#11244: Iguana ID now set during registration process

1) [Problem] 
   Previous versions of Iguana 4.0 had a problem with the registration
   process for users who did not yet have a free member's account. In
   the Iguana Registration form, the "Iguana ID (AKA Machine ID)" field
   was not automatically set to the Iguana ID for the Iguana
   installation. It had to be supplied manually before a member's
   account could be created. This has been fixed in Iguana 4.0.6.
   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #11244

back to top

#11237: Ignored message in From Database sometimes causes Iguana to stop

2) [Problem] 
   In a channel that contains a From Database source component and that
   defines a filter that ignores messages, an ignored message sometimes
   caused the channel to generate an "Invalid Message Id: 0-0" log
   message and then stop.  This problem has been fixed in Iguana 4.0.6.
   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #11237

back to top

#11044: Iguana sometimes unable to recover from log file corruption due to disk failure

3) [Problem] 
   Quality assurance testing of Iguana revealed that, in certain
   circumstances, Iguana might not able to recover from log file
   corruption resulting from disk failure. This has been fixed in Iguana
   4.0.6.
   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #11044

back to top

Version 4.0 Build 5: March 31, 2009

Bug Fixes

#10410: Dashboard tooltip for destination component is sometimes missing information

1) [Problem] 
   In previous versions of Iguana 4.0, the tooltip that is displayed on
   the Dashboard when you hover over the destination component of a
   channel is sometimes missing some information. This problem occurs
   when one or more channels use this channel as a source channel (in a
   From Channel component). This has been fixed in Iguana 4.0.5.

   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.0


   [Tracking Numbers] 
   #10410

back to top

Version 4.0 Build 4: March 23, 2009

Bug Fixes

#11089: vmd_tool sometimes processes files more than once if --overwrite specified

1) [Problem] 
   When using vmd_tool with the --overwrite option, files can get
   processed more than once. This has been fixed in Iguana 4.0.4.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0.3


   [Tracking Numbers] 
   #11089

back to top

#11098: Email authentication always checked for, even if not being used

2) [Problem] 
   Iguana 4.0.3 always checks for supported authentication methods
   before sending an email message, even if authentication is not being
   used to send the message. This has been fixed in Iguana 4.0.4.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0.3


   [Tracking Numbers] 
   #11098

back to top

Version 4.0 Build 3: March 15, 2009

Bug Fixes

#11036: Iguana crashes when resubmitting a message

1) [Problem] 
   In Iguana 4.0.2, attempting to resubmit a message caused Iguana to
   crash. This has been fixed in Iguana 4.0.3.

   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 4.0.2


   [Tracking Numbers] 
   #11036

back to top

#10929: Oracle deadlock error could occur

2) [Problem] 
   If you are using version 4.0.1 of Iguana with an Oracle database, an
   Oracle deadlock error can occur.

   While this error has only been reproduced internally by
   iNTERFACEWARE's Quality Assurance team, this problem could occur if
   you are obtaining message data from an Oracle database. If you are
   using Oracle to do this, you should update to version 4.0.2
   immediately.

   
   [Severity] 
   High


   [Affected Releases]
   Iguana 4.0.1


   [Tracking Numbers] 
   #10929

back to top

#10903: Automatic installer for Iguana may abort while installing Chameleon

3) [Problem] 
   In some Windows environments, the automatic installer for Iguana
   4.0.1 may abort while installing Chameleon. This happens because
   the Iguana installer is terminating if either of the following
   conditions occurs:

    * The Chameleon installer returns a non-zero return code;
    * The Chameleon installer cannot be deleted after the Chameleon
      installation is completed.


   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.0.1


   [Tracking Numbers] 
   #10903

back to top

#10944: Invalid dates in Date fields of Search Criterial panel not handled properly

4) [Problem] 
   In Iguana 4.0.1, invalid dates entered in the Date fields in the
   Search Criteria panel of the Logs screen were not handled properly.
   In Iguana 4.0.2, invalid dates are ignored.

   
   [Severity] 
   Minor


   [Affected Releases]
   Iguana 4.0.1


   [Tracking Numbers] 
   #10944

back to top

Known Issues

#10977: Integer indexing changed in To File destination component

------------------------------------------------------------------------
#10977
------------------------------------------------------------------------
[Description] 
In Iguana 4.0, if you are using To File as a destination component in a
channel and specifying an integer index as the unique identifier for
the files generated by the component, the indexing method is different
from that used in Iguana 3.3.

In Iguana 4.0, the integer index is set to be one greater than the
highest index currently in use. This means that integer indexes can be
reused. In Iguana 3.3, the integer index for output files is stored in
the configuration file and is always incremented; each integer index is
only used once.

If you have created a channel with From File as its source component
that uses the files generated by the To File destination component as
input, and this channel is expecting unique and constantly increasing
integer indexes, the behavior of this channel may be affected.

In Iguana 4.1, a persistent integer index for the To File destination
component will be implemented. 


[Severity of Problem] 
Moderate


[Workaround]
None


[Affected Releases] 
Iguana 4.0

back to top

#10901: Iguana may stop working if URL used to start channel before it is stopped

------------------------------------------------------------------------
#10901
------------------------------------------------------------------------
[Description] 
If a channel is stopping due to an error, Iguana may stop working if you
try to use a URL address to start the channel before it has been
completely stopped.

This cannot happen if you are starting the channel from the Iguana
web-based GUI interface, as the Start button does not become
available until the channel has completely stopped.

This problem will be fixed in an upcoming patch release of Iguana.


[Severity of Problem] 
Minor


[Workaround]
Ensure that the channel has stopped before attempting to restart it, or
use the web-based GUI.


[Affected Releases] 
Iguana 4.0

back to top

#11616: Error messages in Python scripts in custom VMD ACK files not added to logs

------------------------------------------------------------------------
#11616
------------------------------------------------------------------------

[Description] 
If you have created a custom VMD file for generating acknowledgment
messages and this VMD file uses Python scripts, errors detected in these
scripts are not being added to the logs. This will be fixed in Iguana
4.1.


[Severity of Problem] 
Minor


[Workaround]
Enclose your script in an exception handler:

try:
    # your code goes here
except Exception, error:
    print error


[Affected Releases] 
Iguana 4.0

back to top

Version 4.0 Build 2: March 10, 2009

Known Issues

#10730: Iguana now shipped with its own copy of the Python libraries

------------------------------------------------------------------------
#10730
------------------------------------------------------------------------
[Description] 
Iguana 4.0 is shipped with its own copy of the Python libraries. These
libraries are located in the lib subdirectory of the Iguana installation
directory.

Previous versions of Iguana used the Python libraries that were shipped
with Chameleon, which were located in the Chameleon\lib subdirectory of
the iNTERFACEWARE installation directory.

To specify the location of the Python libraries that you are using, add
the directory to the CHM_PYTHON_LIB_PATH environment variable. You may
need to reboot your computer before the update to this environment
variable is recognized.


[Severity of Problem] 
Minor


[Workaround]
Define CHM_PYTHON_LIB_PATH as described above.


[Affected Releases] 
Iguana 4.0

back to top

#10241: Multiple Iguana servers could use the same log files

------------------------------------------------------------------------
#10241 
------------------------------------------------------------------------
[Description] 
If you are running an Iguana server on Solaris, and you start a second
Iguana server that uses a different web port from the first server but
uses the same log directory, both Iguana servers could end up using the
same log files. This may lead to log file corruption.

The problem will be fixed in either Iguana 4.1 or Iguana 4.2.


[Severity of Problem] 
Minor


[Workaround]
You should never use the same log directory for multiple Iguana
servers.


[Affected Releases] 
Iguana 4.0

back to top

#10676: Cannot delete log data in Iguana 4.0

------------------------------------------------------------------------
#10676 
------------------------------------------------------------------------

[Description] 
You cannot delete log data in Iguana 4.0.  This feature will be added in
either Iguana 4.1 or Iguana 4.2.


[Severity of Problem] 
Minor


[Workaround]
None


[Affected Releases] 
Iguana 4.0

back to top

#10864: Idle Iguana servers may still write log data

------------------------------------------------------------------------
#10864
------------------------------------------------------------------------

[Description] 
If an Iguana server is idle, it may still write log data, thus using up
some disk space every day. This problem is not severe, and will be fixed
in an upcoming patch release of Iguana that will likely be available by
the end of March.


[Severity of Problem] 
Minor


[Workaround]
None


[Affected Releases] 
Iguana 4.0

back to top

#10809: 64-bit C++ plugins not supported in Iguana 4.0

------------------------------------------------------------------------
#10809
------------------------------------------------------------------------

[Description] 
64-bit C++ plugins are not supported in Iguana 4.0. They will be
supported in Iguana 4.1.


[Severity of Problem] 
Moderate


[Workaround]
None


[Affected Releases] 
Iguana 4.0

back to top

#10813: Channel Configuration screen slow to load if there is a large number of channels

------------------------------------------------------------------------
#10813
------------------------------------------------------------------------

[Description] 
If you have defined a large number of channels for your Iguana server
and you need to edit a channel whose source component is From Channel,
the Channel Configuration screen for that channel will take some time
to load. This is because the page needs to build HTML for each possible
channel that you might use as a source.


[Severity of Problem] 
Moderate


[Workaround]
None


[Affected Releases] 
Iguana 4.0

back to top

#10788: Viewing a channel with a filter may interrupt Iguana message processing

------------------------------------------------------------------------
#10788
------------------------------------------------------------------------

[Description] 
When a user attempts to view a channel that uses a VMD file as a filter
and the file takes a while to load, the processing of messages through
Iguana will be briefly interrupted while the file is loading.

This performance issue will be resolved in a future version of Iguana.


[Severity of Problem] 
Minor


[Workaround]
Use vmd files which load quickly within Iguana.


[Affected Releases] 
Iguana 4.0

back to top

#10763: C++ plugin support only verified for Windows

------------------------------------------------------------------------
#10763
------------------------------------------------------------------------

[Description] 
In Iguana 4.0, support for C++ plugins has been fully tested and
verified for the Windows environment, but has not yet been
thoroughly tested in other environments.

Complete support for C++ plugins for Mac OS X and Linux environments
will be provided in Iguana 4.1. Support for Java plugins will also be
provided.


[Severity of Problem] 
Moderate


[Workaround]
None


[Affected Releases] 
Iguana 4.0

back to top

#10728: From Channel generates corrupted configuration file in some beta versions

------------------------------------------------------------------------
#10728
------------------------------------------------------------------------

[Description] 
Some beta versions of Iguana 4.0 generate a corrupted configuration
file when the server is running one or more channels that specify
From Channel as a source component.

When the Iguana 4.0 server is restarted using this configuration file,
the following error appears:
 
  * ERROR:  Channel "MyChannelName" has an unknown source. 

This error occurs because the source_guid field in the  tag for
this channel was incorrectly specified as zero. Configuration files
generated by recent beta versions of Iguana 4.0 and by the release
version of Iguana 4.0 do not define this source_guid field and therefore
do not generate this error.

In Iguana 4.1, this error will not appear: if a source_guid field of zero
is encountered, the source will be dropped and a warning message will be
generated when the channel is loaded.


[Severity of Problem] 
Moderate


[Workaround]
Edit the IguanaConfiguration.xml file and search for tags that are
similar to the following:

  

Delete these tags, save the file, and restart the Iguana server. The
server should now start normally.


[Affected Releases] 
Iguana 4.0 beta

back to top

#10473: Large log files have size displayed incorrectly on Mac Power PC

------------------------------------------------------------------------
#10473
------------------------------------------------------------------------

[Description] 
On the Mac Power PC, a large log file - 2GB or greater - will have its
size displayed as 16.0EB.


[Severity of Problem] 
Minor


[Workaround]
Iguana installations of this size should be running on the Mac Intel
platform.


[Affected Releases] 
Iguana 4.0

back to top

Bug Fixes

#3045: Iguana not starting because of invalid ComponentVisibility.xml file

------------------------------------------------------------------------
#3045
------------------------------------------------------------------------

[Description] 
There was an issue in which Iguana would fail to start because of an 
invalid ComponentVisibility.xml file. This issue has now been resolved.


[Severity of Problem] 
Moderate


[Affected Releases] 
Iguana 4.0 and below

back to top

Version 4.0 Build 1: March 3, 2009

Additions

#7606: Iguana user interface completely redesigned

1) [Feature Description] 
   The Iguana User Interface has been completely redesigned, offering a 
   more modern look and feel.  Along with several graphical
   enhancements, the new interface is also now more intuitive to use.
   For example, cookie crumb trails have been added to the user
   interface to make navigation easier. To make these changes possible,
   some tabs have been removed and some functionality has been merged in
   with other tabs.
   

   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #7606, 7654, #7656

back to top

#7514: Control Panel now displays active database connection count

2) [Feature Description] 
   Iguana now displays the number of active database connections
   directly from the Dashboard's Control Panel. This feature provides
   you with a quick summary of connected databases, which allows you to
   monitor the overall health of Iguana.
   

   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #7514

back to top

#7506: Channel Status Summaries now available from Control Panel

3) [Feature Description] 
   The Channel Status Summaries are now available directly from the
   Dashboard's Control Panel. This is useful for determining if the
   Iguana process has stopped, and which channels are currently running
   or have stopped.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #7506

back to top

#7582: HTTP channel components have been added

4) [Feature Description] 
   A new pair of HTTP channel components have been added to Iguana.
   These new components allow you to send and receive data using the
   HTTP protocol. When the HTTPS Server is turned on, these components
   allow you to send and receive encrypted HL7 messages over an Internet
   connection.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #7582

back to top

#7277: Can now translate between HL7 and XML within a message filter

5) [Feature Description] 
   It is now possible to translate between HL7 and XML from within the
   source Message Filter component. In previous versions of Iguana, you
   had to send the HL7 XML messages to a "To XML" file component, and
   then use a "From XML" file component to read them and send to another
   target, such as a database. In addition to the overhead of creating
   and reading the XML files, the temporary files were never
   automatically removed. When you use the Message Filter components,
   this ensures that messages are purged after processing when they are
   moved into a log table. This log table can then be purged
   automatically by Iguana.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #7277

back to top

#4752: Email notification settings have been significantly improved

6) [Feature Description] 
   The Email Notification Settings have been significantly improved: 
    * Error notifications no longer contain sensitive HL7 message data.
      Instead, email messages just contain basic information about the
      error message like the channel name, error type and timestamp. A
      link to the log entry is also included in each email. This
      requires users to log in to Iguana in order to view the log entry.

    * A new option, called "Iguana Host Name for Email Links", has been
      added to the Email Notification Settings in Iguana. Any email
      notification errors are sent to specific recipients when errors
      occur for a given channel. Included in the emails are links to the
      log entries containing the error. This option allows you to
      specify which domain name will be used in the links contained 
      in the emails.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #4752, #7578

back to top

#7472: Iguana can be started from a command prompt

7) [Feature Description] 
   Running "Iguana --run" from a command prompt is very useful for
   diagnosing problems with Iguana. This allows you to run Iguana
   manually and diagnose issues quickly when the Iguana service will not
   start. Issues you can diagnose include incompatible versions of
   Chameleon and port conflicts.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #7472

back to top

#7670: URLs to a specific location now displayed after logging in

8) [Feature Description] 
   Iguana will now display URLs to a specific location after logging in.
   In previous versions of Iguana, if you pasted a URL into  your web
   browser and logged in, you would be taken to the Dashboard. In Iguana
   version 4.0, you are taken to the URL location instead. This feature
   becomes especially important when clicking email notification error
   links to log entries.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #7670

back to top

#7657: Last Activity column added to Dashboard

9) [Feature Description] 
   The "Source" and "Destination" columns have been removed from the
   Dashboard.  Those columns have been replaced by a new column called
   "Last Activity". This column displays the timestamp of the last known
   message transaction for that channel. Clicking the "Channel Name" in
   the Dashboard will display the source and destination information,
   last recorded activity and error count. In addition, you can stop the
   channel, or view its configuration.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #7657

back to top

#1577: Null values now handled more correctly in Iguana 4.0

10)[Feature Description] 
   "Null" (also referred to as "Present But Null"), "Empty" and "Invalid" 
   values are now handled more correctly in Iguana 4.0. depending on the
   selected parser version in the VMD file, the input data, and the data
   type. For details, see "Null, Empty and Invalid Values" in the Iguana
   manual.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #1577, #3567

back to top

#4014: Failover documentation now provided

11)[Feature Description] 
   Documentation has been added to Iguana to show you how to set up an 
   effective failover strategy. A failover cluster is an effective strategy 
   for improving the availability of the Iguana service running on a server.
   For details, see "Setting Up a Failover Cluster for Iguana" in the Iguana
   manual. 


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #4014

back to top

#6784: Iguana --run now outputs its IP address and port number

12)[Feature Description] 
   When starting Iguana from the command line (i.e. "Iguana --run"), Iguana 
   will now output the IP address and port number it is listening on in the 
   Command Prompt window, as well as saving this information to the 
   "ServerErrorLog.txt" file. This makes it easy to see which port Iguana is
   listening on when starting it from Mac or Unix platforms.


   [Affected Releases] 
   Iguana 4.0
 

   [Tracking Numbers] 
   #6784

back to top

Changes

#7511: Configuration information now located in IguanaConfiguration.xml

1) [Description]
   The information found in the configuration files (ChannelConfiguration.xml,
   ComponentVisibility.xml, AdminConfiguration.xml and UserConfiguration.xml)
   has been merged into one file called IguanaConfiguration.xml. If you are 
   upgrading, Iguana will automatically merge the settings found in the 
   configuration files into the new file. 

   Note: If you downgrade from Iguana 4.0 to 3.3 and lower, you will lose any
   changes you made in Iguana 4.0. 
   

   [Severity] 
   Moderate


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #7511, #7581, #7636

back to top

#7581: Python Settings feature removed from Iguana 4.0

2) [Description]
   The "Python Settings" feature has been removed from Iguana 4.0 and is 
   no longer supported. It was removed because it had the potential to 
   cause a few issues with regards to logging and ACK generation.


   [Severity] 
   Moderate


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #7511, #7581, #7636

back to top

#7654: Tab names and link names have changed

3) [Description]
   The "Configuration" tab has been removed from the user interface. Its
   functionality is still available from the "Add Channel" button.

   The "Advanced" tab is now referred to as the "Settings" tab. Some of 
   the link names have also been changed, as described below:

    * "Change Password for admin" > "Change Password"
    * "Add a User, Add a Group, Edit Users/Groups" > "Users & Groups"
    * "Registration Information" > "License Entitlement"
    * "Email Server Settings" > "E-mail Notification"
    * "Log/Status Purge Settings" > "Logging"
    * "Web Server Settings" > "Web Server Configuration"

   In addition, the "Channel Status Summaries (Text and XML)" have been 
   moved to the Dashboard's "Control Panel."


   [Severity] 
   Moderate


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #7654

back to top

#7242: Iguana web pages now redesigned

4) [Description]
   All of the Iguana web pages have been redesigned. For example, the "Log 
   Pages", "Routing tab" and "Dashboard" now feature a smaller font size. 
   This provides you with more detailed information at a glance.


   [Severity] 
   Moderate


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #7242

back to top

#6099: Export Tables screen has been significantly improved

5) [Description]
   The "Export Tables" screen has been significantly improved:
    * A warning will be displayed in red if drop SQL statements are being
      issued.
    * Semi-colons have been added to the end of SQL-create statements.
    * '1s' have been inserted in the insert statements in place of '?s' since
      some databases do parameter binding on the generated SQL. 


   [Severity] 
   Moderate


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #6099

back to top

Iguana provides notification if plugin communication server port is busy

6) [Description]
   If the plugin communication server fails to start because another
   application is listening on its port, Iguana will notify you that
   this problem has occurred. (Iguana 3.3.2 does not start if the RPC
   port is being used by another application.)


   [Severity] 
   Moderate


   [Affected Releases] 
   Iguana 4.0

back to top

#9260: To File integer indexing now starts with next unused value

7) [Description]
   If you have created a channel that uses the To File destination
   component, writes messages to separate files, and uses an integer
   index as the file ID, indexing now starts with the value one
   greater than the largest index that is currently defined. (If no
   file exists in the message directory, indexing starts from 0.)
   In previous versions of Iguana, the index number was stored in
   the configuration file, and indexing always started with the last
   index number assigned.


   [Severity]
   Moderate


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #9260

back to top

#7649: Directories specified in source and destination components must exist

8) [Description]
   In Iguana 4.0, whenever you specify a directory as part of the
   definition of a source component or destination component of a
   channel, the directory must exist. In addition, any slash
   characters ("/") or backslash characters ("\") in the directory
   are converted to whichever character is correct for the
   operating system on which Iguana is running. A trailing slash
   or backslash character is added to the directory name if needed.

   In previous versions of Iguana, the requirements were not
   consistent: some components would create the directory if it
   did not exist, and most components would not convert
   slash/backslash characters or add a trailing slash/backslash
   character.


   [Severity]
   Minor


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #7649

back to top

#9755: Stopped channels not automatically restarted if configuration changed

9) [Description]
   In Iguana 3.3, if a channel is configured to automatically start
   when Iguana is started, and you stop the channel to change its
   configuration, the channel automatically restarts when the
   changed channel configuration is saved. In Iguana 4.0, if you stop
   a channel to change its configuration, and you have not restarted
   Iguana, the channel will not start until you press its Start button.


   [Severity]
   Moderate


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #9755

back to top

#9818: Python module search now includes python_lib subdirectory

10)[Description]
   When Iguana 4.0 is running in a POSIX environment and is searching
   for Python modules, its search now includes the python_lib
   subdirectory of the Iguana installation directory.


   [Severity]
   Moderate


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #9818

back to top

Bug Fixes

#5604: In From File, files without extensions or containing asterisks can now be read

1) [Problem] 
   When using the "From File" component, files without extensions and files
   containing asterisks would not be read. This only affected Iguana versions
   running on Linux operating systems. This bug has now been fixed.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 3.3 and below


   [Tracking Numbers] 
   #5604

back to top

#5826: Message status erroneously changed to P if client executable throws exception

2) [Problem] 
   When you have a "Message Filter" to "Client Executable" setup and send a message,
   the message status will be erroneously changed to "P" (partially processed) if the 
   client executable throws an exception. This bug has been resolved.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 3.3 and below


   [Tracking Numbers] 
   #5826

back to top

#6292: From Executable component incorrectly logs error

3) [Problem] 
   The "From Client Executable" component would incorrectly log an error when the error
   actually occurred in the "To Client Executable" component. This bug has now been fixed.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 3.3 and below


   [Tracking Numbers] 
   #6292

back to top

#6293: Stopping client executable channel creates a log that only displays debug output

4) [Problem] 
   After stopping a "From Client Executable" to "To Client Executable" 
   channel, the source client executable would create a log that only 
   displays debug output (i.e. just the stdout, not the message text 
   and debug text areas). This bug has been fixed so that error messages
   are output into the 'Debug Output' and 'Trace Output' fields instead.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 3.3 and below


   [Tracking Numbers] 
   #6293

back to top

#7067: Database triggers preventing Iguana inserts and updates due to ODBC bug

5) [Problem] 
   Any database triggers that were run from Iguana inserts and updates 
   would prevent the insert or update from occurring. In addition, no 
   errors would be reported. This issue was caused by a bug in ODBC, 
   which is described here: http://support.microsoft.com/kb/293901. 

   This bug has now been fixed.

   
   [Severity] 
   Moderate


   [Affected Releases]
   Iguana 3.3 and below


   [Tracking Numbers] 
   #7067

back to top

#9368: Performance problems when using OCI Oracle to retrieve hundreds of records

6) [Problem]
   In versions of Iguana prior to 4.0, channels that used OCI to
   generate HL7 messages from an Oracle database occasionally
   encountered performance problems if hundreds of records
   needed to be retrieved to generate the message. (This could
   happen if a message contains segment groups consisting
   of large numbers of segments.) When using Iguana 4.0, no such
   performance problems occur.


   [Severity]
   Moderate


   [Workaround]
   Use ODBC to interact with the Oracle database.


   [Affected Releases] 
   Iguana 4.0


   [Tracking Numbers]
   #9368

back to top

Known Issues

#9627:

------------------------------------------------------------------------
#9627
------------------------------------------------------------------------

[Description]
Iguana occasionally crashes when a client executable application shuts
down.

[Symptom]
If Iguana is connected to a client executable application and the
application shuts down due to an error, Iguana occasionally crashes
due to threading problems.

[Severity] 
Moderate

[Workaround] 
None

[Affected Releases] 
All Iguana releases

back to top

#3045:

------------------------------------------------------------------------
#3045
------------------------------------------------------------------------

[Description]
Iguana fails to start because of an invalid XML file.

[Symptom]
Running Iguana results in the error:

    "Error while running service: xml error on line 1 column 0. 
     not well-formed (invalid token)"

in the ServiceErrorLog.txt file.

[Severity] 
Low

[Workaround] 
Back up and delete the "ComponentVisibility.xml" file in the Iguana 
installation directory.

[Affected Releases] 
All Iguana releases

back to top

#3043:

-----------------------------------------------------------------------
#3043
-----------------------------------------------------------------------

[Description] 
MySQL 'uniqueidentifier' type not supported.

[Symptom]
Using a table with the 'uniqueidentifier' in MySQL causes an 'unknown 
data type'.

[Severity]
Low

[Workaround]
Use an alternate data type.

[Affected Releases] 
All Iguana releases

back to top

#7025:

------------------------------------------------------------------------
#7025
------------------------------------------------------------------------

[Description]
Error message appears when Iguana is started from the command line when
MySQL 5.0.45 is installed.

[Symptom]
Running Iguana from the command line causes Iguana to:

 1. Start up normally.
 2. Then pause for a few seconds as it shuts down.
 3. When Iguana does shut down the following error message is output to 
    standard out:

        "Error in my_thread_global_end(): 2 threads didn't exit"

Note that this error will not be visible in the "ServiceErrorLog.txt"
file in Iguana's install directory.

[Severity]
Low

[Workaround]
Use MySQL 5.0.41 or earlier.

[Affected Releases] 
Iguana 3.3-3.3.2

back to top

Version 3.3 Build 2: September 27, 2007

Changes

#6814: Username and password now optional in Email Notification Settings

1) [Description]
   The UserName and Password for the "Email Notification Settings" have
   been made optional. These fields can now be left blank, in which case
   Iguana will not use SMTP authentication when sending email
   notifications.

   [Severity] 
   Minor

   [Affected Releases] 
   Iguana 3.3.2

   [Tracking Numbers]
   #6814

back to top

Version 3.3 Build 1: August 17, 2007

Additions

#4753: HTTPS support added

1) [Feature Description] 
   HTTPS Support has been added to Iguana, which allows you to easily 
   secure confidential data such as log messages, as well as any changes 
   made within the Dashboard. Using HTTPS, you can secure and encrypt 
   connections to the web server via a specified port.
   
   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #4753, #5450 

back to top

#6284: Global Web Server Settings page added

2) [Feature Description] 
   A global "Web Server Settings" page has been added to Iguana, which
   allows you to change the session timeout, specify a new web server 
   port and turn on HTTPS support. In addition, you can also specify which 
   private/public key and certificate files to use.

   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #6284

back to top

#5613: Global Purge Log Settings page added

3) [Feature Description] 
   A global "Purge Log Settings" page has been added to Iguana. This 
   setting allows you to determine the time of day that the logs will be 
   purged. This means that you can purge logs for all the active channels 
   at the same time.

   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #5613

back to top

#5849: Contextual information provided for database API in channel configuration page

4) [Feature Description] 
   New helpful contextual information appears when you set up your database 
   API in the channel configuration page. Varying information will appear 
   beside the Data source field, depending on the type of database selected 
   (ODBC or non-ODBC). This will make it easier to set up your data source.
   
   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #5849

back to top

#6272: Auto-Refresh Rate option added

5) [Feature Description] 
   An "Auto-Refresh Rate" option has been added to Iguana. The auto-refresh 
   rate allows you to view the updated status of channels in near real-time 
   without having to explicitly refresh the entire page.
   
   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #6272

back to top

#5548: The web port that Iguana uses can now be specified

6) [Feature Description] 
   It is now possible to change the default port that Iguana is run on 
   via the Web Interface. For more information, see "Changing the Web 
   Port Via the Web Interface" in the Iguana manual.
    
   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #5548

back to top

#5671: Iguana now supported on 64-bit Linux platforms

7) [Feature Description]
   Iguana is now supported on 64-bit Linux platforms. Although 64-bit 
   Windows is not supported at this time, iNTERFACEWARE plans to offer 
   support for it once there is a demand from customers.

   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #5671

back to top

#6173: Advanced Python Settings functionality added

8) [Feature Description] 
   Advanced "Python Settings" functionality has been added to Iguana. 
   This allows you to set up custom methods for handling error and/or 
   success logs. To use the functionality, you need to write a simple 
   Python module for handling log events. Examples of what you can do 
   include sending email notifications for certain events and logging
   to a file.

   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #6173, #6259

back to top

#6230: Browse file buttons added to source and destination components configuration pages

9) [Feature Description] 
   Convenient "Browse" file buttons have been added to the source and
   destination components configuration page. Rather than entering the 
   VMD path manually, the "Browse" button allows you to quickly locate 
   the file path you want to add to your configuration from a local
   machine. 

   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #6230

back to top

Changes

#5298: Email notification settings moved to Email Server Settings page

1) [Description]
   The "Email Notification Settings" have been moved from the channel
   configuration page to a separate page called "Email Server Settings."
   This page allows you to set up a list of recipients who will receive 
   emails when errors occur for a given channel. By making this setting 
   global, this means that you only have to configure the settings once.

   If you are upgrading from a version prior to 3.3 and already have 
   existing email settings, Iguana will use the first enabled email 
   setting and make it the new global setting. Other existing email 
   settings will be stored in the ChannelConfiguration.xml backup file.

   [Severity] 
   Moderate

   [Affected Releases] 
   Iguana 3.3

   [Tracking Numbers]
   #5298

back to top

#6167: ChannelConfiguration.xml file backed up when upgrading

2) [Description] 
   When you upgrade your Iguana installation, a backup of your 
   "ChannelConfiguration.xml" file will be automatically created, 
   if any automatic migration has been performed by Iguana during the 
   upgrade. The backup file will have the following naming convention: 
   "ChannelConfiguration.xml.X", where "X" is the sequence number (0 
   will be the first sequence number). Note that if you are downgrading 
   from version 3.3 to pre-3.3, you will have to re-enter any previously 
   set email server and database password settings.

   [Severity] 
   Moderate

   [Affected Releases] 
   Iguana 3.3

   [Tracking Numbers]
   #6167

back to top

#6204: User password algorithm changed

3) [Description] 
   The User Password Algorithm has changed in Iguana. If you are upgrading 
   from Iguana pre-3.3 to 3.3, you will not be affected by the change. 
   However, if you are downgrading from version 3.3 to 3.2.155 and below, 
   your password will no longer function. As such, you will need to reset 
   your password. For more information, see "Resetting User Passwords" in 
   the Iguana Troubleshooting section.
   
   [Severity] 
   Moderate

   [Affected Releases] 
   Iguana 3.3

   [Tracking Numbers]
   #6204

back to top

#6256: Default RPC port changed to 6123

4) [Description] 
   The default "RPC port" for client executables has been changed from "5123" 
   to "6123" to avoid conflicts. Note that this change will not affect any 
   existing channel configurations.


   [Severity] 
   Low

   [Affected Releases] 
   Iguana 3.3

   [Tracking Numbers]
   #6256

back to top

#5717: Iguana Monitor functionality merged with Iguana Service

5) [Description] 
   The "Iguana Monitor" has been removed from the Iguana installation. All of its 
   functionality has been merged with the "Iguana Service." If you are upgrading 
   from Iguana pre-3.3 to version 3.3, no action is required.

   [Severity] 
   Low

   [Affected Releases] 
   Iguana 3.3

   [Tracking Numbers]
   #5717, #6043

back to top

#4143: Logs page now displays most recent entries first

6) [Description] 
   The default view for the "Logs" page has been changed so that the most recent
   entries are always displayed on the first page.
   
   [Severity] 
   Low

   [Affected Releases] 
   Iguana 3.3

   [Tracking Numbers]
   #4143

back to top

#6271: DB Direct support removed

7) [Description] 
   Support for "DB Direct", a legacy version of Iguana, has been 
   removed.

   [Severity] 
   Low

   [Affected Releases] 
   Iguana 3.3

   [Tracking Numbers]
   #6271

back to top

#6178: Log purging implemented for Client Executable error and success logs

8) [Feature Description] 
   Log purging for "Client Executable" error and success logs has been 
   implemented for Iguana. This allows you to specify in days when logs 
   are stale and can be automatically deleted. 

   [Affected Releases] 
   Iguana 3.3
 
   [Tracking Numbers] 
   #6178

back to top

Bug Fixes

#3531: Log table purging not performed during requested interval

1) [Problem] 
   There was a bug in Iguana in which the log table purging functionality
   would not be performed at the requested interval. This bug was fixed 
   when the "Purge Log Settings" page was added. 

   [Severity] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #3531

back to top

#5884: All logs exported after search

2) [Problem] 
   After performing a logs search, there was a bug in Iguana when attempting 
   to export any other logs page besides the first page. Instead, all the logs 
   would be exported. This bug has now been resolved.
 
   [Severity] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #5884

back to top

#5909: Resubmitted messages not logged when "Disconnect between retries" set in LLP Client

3) [Problem] 
   There was an issue in Iguana where resubmitted messages were not being
   properly logged when using the "LLP Client" component and the "Disconnect
   between retries" option was set to "true." This bug has now been fixed.

   [Severity] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #5909

back to top

#6220: Connection hangs when logs exported after database error

4) [Problem] 
   There was an issue in Iguana when trying to export the logs after the logs
   page displayed a database error. This would cause the connection to hang and
   Iguana would not return the "Export tables complete" page.
  

   [Severity] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #6220

back to top

#6080: Leading and trailing white space not stripped in channel name

5) [Problem] 
   There was an issue in Iguana where leading and/or trailing white space
   would not be stripped when entering a channel name. This bug has been 
   fixed.

   [Severity] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #6080

back to top

#5699: Log tables in MySQL cannot handle input messages larger than 64 KB

6) [Problem] 
   There was a bug in Iguana where log tables within MySQL would not handle
   large input messages beyond 64 KB. This bug has now been fixed. 
   

   [Severity] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #5699

back to top

#6177: Client Executable message success logs displayed in Errors column

7) [Problem] 
   There was a minor issue in Iguana in which the "Client Executable's" message 
   success logs would be displayed in the "Errors" column. This bug has now been 
   fixed so that the logs appear in the "Success" column.

   [Severity] 
   Low

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #6177

back to top

#5651: Channel Status Summary page does not return a useful file if database not available

8) [Problem] 
   There was a bug in Iguana in which the "Channel Status Summary" page did
   not return a useful XML/text file if the database was not available. The 
   problem was resolved with the use of a "-1" value. A "-1" value beside the 
   "Success", "SourceError" or "DestinationError Logs" denote errors with the 
   channel's associated database.

   [Severity] 
   Low

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #5651

back to top

#5683: Messages not ignored if multiple messages specified

9) [Problem] 
   There was a bug in Iguana when using the "Ignore Messages" field in the
   "From Message Filter" source component. When entering multiple messages
   that contained a space after the comma, the second message would not
   be ignored. This bug was resolved by stripping both the leading and 
   trailing spaces of ignored messages.

   [Severity] 
   Low

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #5683

back to top

#5683: Problem with registering Iguana on Unix-based machines

10)[Problem] 
   There was a bug that occurred when registering Iguana on Unix-based machines. 
   When registering Iguana initially, you would receive an error message 
   stating that the host machine did not have a valid Chameleon license 
   after registering Iguana. 

   [Severity] 
   Low

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #5231

back to top

#5982: Iguana crashes if "Disconnect between retries" and "Verified ACK message" set

11)[Problem] 
   There was a bug in Iguana where setting the "Disconnect between retries
   option" to "true" would cause Iguana to crash if the "Verified ACK message"
   option was set.

   [Severity] 
   Low

   [Affected Releases]
   Iguana Pre-3.3

   [Tracking Numbers] 
   #5982

back to top

Version 3.2 Build 155: April 16, 2007

Fixed Iguana Issues

#2367: Some resubmitted messages not appearing in logs page

-----------------------------------------------------------------------
#2367, #5463
-----------------------------------------------------------------------

[Description] 
There was an issue in Iguana with resubmitting a single message with 
Sybase ASA 7. When resubmitting a single message, the logs page did not 
indicate that the new message was resubmitted (missing log record). This 
did not occur for every resubmit. This issue has now been resolved.

[Severity of Problem] 
Moderate

[Affected Releases] 
Iguana 3.2.155

back to top

Additions

#3572: Arbitrary text can now be read from source File component

1) [Feature Description] 
   New functionality has been added to Iguana that allows you to read
   arbitrary text from the source "file" component. This allows Iguana to 
   read and process arbitrary data such as XML, CSV and other text files.
  
   [Severity] 
   Moderate
   
   [Affected Releases] 
   Iguana 3.2.155
 
   [Tracking Numbers] 
   #3572, #4932

back to top

#4979: Temporary file extension option added to destination File and XML components

2) [Feature Description] 
   A "Temporary file extension" option was added to the destination "file" 
   and "xml" components. This allows users to specify a temporary file 
   extension that Iguana will use while writing the file. This makes it 
   easy for external processes to determine when a file is completely 
   written. For details, see the destination "file" and "xml" components
   documentation.

   [Severity] 
   Moderate
   
   [Affected Releases] 
   Iguana 3.2.155
 
   [Tracking Numbers] 
   #4979

back to top

Changes

#4874: Purge logs fields have changed

1) [Description]
   The "Automatically Purge Success Logs Older Than" and "Automatically 
   Purge Error Logs Older Than" fields have changed. The "Hours" and 
   "Minutes" fields are no longer available and have been removed. If 
   you have set the Hours and Minutes fields in any version prior to 
   3.2.155, Iguana will automatically apply the ceiling in all cases. 
   
   For example:
    * If you have set the options to 1 hour and 1 minute, Iguana rounds 
      up to 1 day.
    * If you have set the options to 1 day, 1 hour and 1 minute, Iguana 
      rounds up to 2 days.

   Note that this new behavior applies to all destination and source 
   components in Iguana.

   [Severity] 
   Moderate

   [Affected Releases] 
   Iguana 3.2.155

   [Tracking Numbers]
   #4874 

back to top

#5323: Channel Configuration pages redesigned

2) [Description] 
   The "Channel Configuration" pages have been completely redesigned. The 
   new layout features a more modern and streamlined look-and-feel, making 
   it easier to configure your channels.

   [Severity] 
   Moderate

   [Affected Releases] 
   Iguana 3.2.155

   [Tracking Numbers]
   #5323 

back to top

Bug Fixes

#4340: Asterisks in file names now handled properly

1) [Problem] 
   There was a bug in which Iguana would read and process all *. files 
   (where  is the name of the file extension used), regardless of the 
   validity of the extension. When upgrading to 3.2.155, you must modify 
   any source file components so that either * or  is used instead of 
   *, otherwise an error will occur when the channel is started.

   [Severity of Problem] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.2.155

   [Tracking Number] 
   #4340 

back to top

#4949: XML components not displayed in upgrade installations

2) [Problem] 
   There was a bug in Iguana that prevented the "XML" components (introduced 
   in version 3.2.154) from being displayed for upgrade installations. This 
   bug has now been fixed.

   [Severity of Problem] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.2.155

   [Tracking Number] 
   #4949

back to top

#5097: Inconsistent case in display of "logkey" column

3) [Problem] 
   There was a bug in Iguana where the "logkey" column name would be inconsistently 
   used. In some cases the logkey column would be displayed as uppercase, lowercase 
   or a mixture of both. This has now been fixed so that the logkey column now uses
   all lowercase letters.

   [Severity of Problem] 
   Moderate

   [Affected Releases]
   Iguana Pre-3.2.155

   [Tracking Number] 
   #5097

back to top

Version 3.2 Build 154: November 30, 2006

Additions

#2893: Status information and event counter summary added

1) [Feature Description] 
   A new feature was added, allowing you to access Iguana status 
   information and a summary of event counters. In addition the ability 
   to start and stop channels is available for automation. This feature 
   is implemented as a web request to the Iguana service and can be 
   accessed either locally or remotely through any network. 
  
   [Severity] 
   High
   
   [Affected Releases] 
   3.2.154
 
   [Tracking Numbers] 
   #2893, #3006

back to top

#2509: To XML and From XML components added

2) [Feature Description] 
   "To XML" destination and "From XML" source components were added to 
   Iguana, allowing you to transform messages to/from XML files. For 
   more information, see the "Channel Source Components" and "Channel
   Destination Components" sections of the manual. 

   [Severity] 
   High
   
   [Affected Releases] 
   3.2.154
 
   [Tracking Number] 
   #2276

back to top

#3357: Sybase ASE 15 now supported

3) [Feature Description] 
   Iguana now fully supports Sybase ASE 15.

   [Severity] 
   High

   [Affected Releases] 
   3.2.154
    
   [Tracking Number] 
   #3148

back to top

#2786: Reboot no longer required if install PATH has changed

4) [Feature Description] 
   A reboot is no longer required if the install PATH has changed. In 
   versions 3.2.153 and below, installing Iguana in a different directory 
   than the previous install would result in the service not starting unless 
   the machine was rebooted. 

   [Severity] 
   Moderate
 
   [Affected Releases] 
   3.2.154
    
   [Tracking Numbers] 
   #2509, #2786

back to top

Changes

#3089: Chameleon and Iguana compiled help manuals have been merged

1) [Description]
   The Chameleon and Iguana compiled help manuals have been merged into
   one manual. The new manual is placed into a separate "doc" directory 
   (default directory is C:\Program Files\iNTERFACEWARE\doc).
   
   [Severity] 
   Moderate

   [Affected Releases] 
   3.2.154

   [Tracking Number]
   #3089 

back to top

#3114: Iguana --install no longer works in Unix environment

2) [Description] 
   Starting and Stopping services has a different executable when manually
   executed. This means that "iguana --install" no longer works. For more
   information, see the "Iguana Unix Deployment" section in the manual.

   [Severity] 
   Moderate

   [Affected Releases] 
   3.2.154

   [Tracking Number]
   #3114

back to top

Bug Fixes

#3331: Configuration file lost when error occurs during save

1) [Problem] 
   When saving the configuration file and an error occurs, the config file 
   is lost.

   [Symptom] 
   If Iguana crashes and is restarted, no channels appear.

   [Severity of Problem] 
   High

   [Status]
   Fixed

   [Tracking Number] 
   #3331

back to top

#3391: File handles from one channel may be used by another

2) [Problem] 
   Handle inheritance is causing problems between channels, possibly 
   allowing file handles from one channel to be used by another.
   
   [Symptom] 
   When a large configuration of channels use the "File" components 
   and "Client Executable" components, incorrect messages would be
   read in.
   
   [Status] 
   Fixed 

   [Severity of Problem] 
   High

   [Tracking Numbers] 
   #3357, #3391

back to top

#3001: Sybase ASE 12-15 database issues

3) [Problem] 
   Issues with Sybase ASE 12-15 databases, specifically with the execution 
   of select statements.

   [Symptom] 
   Sybase ASE users encounter errors with output similar to the following:

   "[Microsoft][ODBC Driver Manager] Driver does not support this function"

            or

   "Failed  precondition:!NewColumnName.is_null()"

   [Severity of Problem] 
   Moderate

   [Status] 
   Fixed

   [Tracking Number] 
   #3001

back to top

#3064: Duplicate table group names yield duplicate create table statements

4) [Problem] 
   Exporting tables yields duplicate create table statements.

   [Symptom] 
   Using a vmd file in either "From Database" and "To Database" components 
   that contains duplicate table group names would result in duplicate create 
   statements during an export of the tables.
   
   [Severity of Problem] 
   Moderate

   [Status]
   Fixed

   [Tracking Number] 
   #3064 

back to top

#3469: Updating status column after From Database error may file on MySQL and ASE

5) [Problem]
   When there is an error processing data from database, an attempt is 
   made to update the status column with the error message. However, 
   this can fail. Known cases:
      1. MySQL - error message is too long to fit into the status column. 
      2. ASE - doesn't work when updating.  

   [Symptom] 
   The above error does not stop the channel, filling up the error log.

   [Status] 
   Fixed. The error message is now truncated in the status column.
   
   [Severity of Problem] 
   Moderate

   [Tracking Number]
   #3469

back to top

#3592: Iguana uses custom build of Chameleon in Windows

6) [Problem] 
   Iguana used a custom build of Chameleon in Windows. 

   [Symptom]
   The version number of Chameleon from an Iguana install was not available 
   as a separate download from iNTERFACEWARE's website. 

   [Status] 
   Fixed - Iguana now uses a precise version of Chameleon in Windows.

   [Severity of Problem] 
   Moderate 
    
   [Tracking Number]
   #3592

back to top

#2998: SQL statements for log tables are inefficient

7) [Problem] 
   The SQL statements for the log tables are inefficient.

   [Symptom] 
   When browsing the logs with a large number of entries, it is very slow.

   [Status] 
   Fixed 

   [Severity of Problem] 
   Moderate

   [Tracking Number] 
   #2998 

back to top

#3235: Client Executable outbound component does not poll correctly

8) [Problem] 
   The "Client Executable" outbound component does not poll correctly. 

   [Symptom] 
   When an outbound "Client Executable" generates a successful message, 
   the event for the next message does not arrive immediately, but 
   rather after the polling event. 
   
   [Status] 
   Fixed 

   [Severity of Problem] 
   Moderate

   [Tracking Number] 
   #3235

back to top

Version 3.2 Build 153: May 4, 2006

Changes

#2398: Multiple copies of Iguana are now allowed on Unix

1) New Feature : Allow multiple iguanas on the same system, unix only.
   Status : In Beta 
   Tracking Number: #2398

back to top

#2356: PostgreSQL does not work with 64-bit integers

2) Fix : PostgreSQL support did not work with large int (64 bit)
         integers.
   Symptom: Using columns in the database with large integers would
            result in a database error.
   Status: Fixed
   Tracking Number: #2356

back to top

#2622: Login screen now links to password reset help page

3) Documentation: Forgot your password link. On the login screen, a
                  link now exists that links to the help page on how
                  to reset the password.
   Status: Completed
   Tracking Number: #2622

back to top

#2518: Logs can now be exported from a search result

4) New Feature: Logs can be exported from a search result. Users can
                now export logs using the search functionality. After
                entering a search request, an 'Export' link is
                available which allows users to export searched data
                to a file.  
   Status: Completed
   Tracking Number: #2518

back to top

#1791: LLP Client can disconnect between send retries

5) New Feature: LLP Client can disconnect between send retries. As an
                option in the configuration, the LLP Client will drop
                the connection and reconnect between send retries.
   Symptom: Some receiving systems will reach an error condition at
            which point any send retries will fail to produce a
            result, but if the connection is dropped and
            re-established before resending the message, the
            processing continues.
   Status: Completed
   Tracking Number: #1791

back to top

#1969: Routing Page added

6) New Feature: Routing Page. A new page is available from the top
                menu, which shows the current position of data in
                'From Message Filter' and 'To Message Filter'
                components. Please see the documentation.
   Status: Completed
   Tracking Number: #1969 

back to top

#2367: "logmessage" used instead of "message" when working with Sybase

7) Fix: Sybase support will now use 'logmessage' as a column name
        in log tables instead of 'message', which is a reserved key
        word for some versions of Sybase. This only affects newly
        created channels, and is only in effect for Sybase ODBC users.
   Symptoms: Using Sybase ASA Version 7 and below, would result in
             database errors concering the usage of keyword 'message'.
   Status: Fixed
   Tracking Number: #2367

back to top

#2367: Timestamp column now supported in Sybase ASA 7

8) Fix: Sybase support for timestamp type in Sybase ASA 7.
    Symptoms: Using Sybase ASA 7 and below, would result in
             database errors when a timestamp column was used.
   Status: Fixed
   Tracking Number: #2367

back to top

#1345: Database connections can be retried when starting channels

9) New Feature: Database connections can be retried when starting
                channels.  An email can be sent if all attempts to
                connect have failed.
   Symptom: Starting Iguana as a service would result in automatically
            started channels possibly failing to start because the
            database has yet to start.
   Status: Completed
   Tracking Number: #1345

back to top

#2278: Order Messages By Column in Database Outbound did not work with Oracle

10)Fix: Order Messages By Column feature in Database Outbound did not
        work with Oracle.
   Symptom: Enabling the Order Messages By Column feature would case a
            ORA-00911 error.
   Status: Fixed
   Tracking Number: #2278

back to top

#2332: Access datetime types could not be used as keys

11)Fix: Access datetime types could not be used as keys
   Symptom: Using a table with the datetime column configured as a key
            column.
   Status: Fixed
   Tracking Number: #2332

back to top

#2334: Iguana does not report that key field values are NULL for inbound database channels

12)Fix: Iguana does not report that key field values are NULL for
        inbound database channels. An error is now thrown if a key
        field is null, since key fields cannot be null.
   Symptom: For inbound channels (To Database), if the key field's
            value is NULL, nothing is inserted into the database, but
            the transaction is logged as a success.
   Status: Fixed
   Tracking Number: #2334

back to top

Version 3.2 Build 152: March 6, 2006

Changes

#1294: Error logs can be automatically purged

1) New Feature : Error Logs can be automatically purged (Except for
	         error logs on Client Executable Components).
   Tracking Number : #1294

back to top

Version 3.2 Build 151: February 8, 2006

Version 3.2 Build 150: February 1, 2006

Changes

#1945: Message status in Message Filter components could not be updated

1) Problem: Message Status in Message Filter components could not be
	    updated
   Symptom: A message that causes an error would result in that
	    message continously being resent, instead of logging an error and
	    continuing with the next message.
   Status: Fixed. Errors that are used to update the STATUS table for
	   the Message Filter are truncated to 255 chars to ensure
	   that the update of that table will succeed.
   Tracking Number: #1945

back to top

Version 3.2 Build 149: January 27, 2006

Changes

#1668: Passthru mapping selection screen not selecting the right configuration

1) Problem: Passthru mapping selection screen for Message Filter
            Components were not selecting the right configuration
   Symptom: Trying to use a different configuration for Passthru
	    Mapping in the Message Filter configuration, other than
	    the last one saved in the VMD file, would result in that
	    configuration not being selected.
   Status : Fixed. The correct configuration will not be selected, and
	    the interface reflects the ability to choose non Passthru
	    Mapping (Graphical Mapping) as well.
   Tracking Number: #1668

back to top

Version 3.2 Build 148: January 23, 2006

Changes

#969: Iguana performs an invalid check for concurrent channels

1) Problem: Iguana performs an invalid check for concurrent channels. 
            This causes Iguana to count every connection established
            by the LLP Listener against the number of channels allowed
            by the license.
   Symptoms: Opening multiple connections for a channel will cause 
             valid connections to be refused because they exceed the 
             maximum number allowed by the license.
   Status: Fixed. Iguana now only counts the number of channels, not
           the number of connections.
   Tracking Number: #969

back to top

#935: Resubmissions for a single message removed

2) Problem: Resubmissions for a single message were removed, 
            since export was available
   Symptom: Trying to resubmit a single message from a view of a
            single log was not possible.
   Status:   This has been re-enabled.
   Tracking Number: #935  

back to top

#987: Outgoing messages from a database could not be ordered

3) Problem: Outgoing messages from a Database could not be ordered.
   Symptom: Writing new messages into a database, and using the 'From
             Database' component would result in messages being sent
             in a underterministic order.
   Status: Fixed. Outgoing messages can be ordered by a specific
           column, and in ascending or descending order. See the
	   manual, under section Iguana->Source Components->From
           Database.
   Tracking Number: #987, #1069 and #1669

back to top

#1034: MySQL 5.0 support missing on Unix

4) Problem: MySQL 5.0 support missing on Unix
   Symptom: MySQL 5.0 would not appear as a database option for unix
             releases.
   Status : Fixed. The MySQL 5.0 should appear in this version of
            Iguana for unix.
   Tracking Number: #1034

back to top

#963: Missing messageId for client executable producer events

5) Problem:  Missing messageId for client executable producer events
   Symptom:  MessageID provided to onMessageRequest event does not
             match messageId in onMessageRequestCompleted event.
   Status :  Fixed. Correct message id is now returned.
   Tracking Number : #963

back to top

#1120: Iguana did not properly update Chameleon license

6) Problem: Iguana did not properly update Chameleon license
   Symptom: If an existing Chameleon license existed on a machine, but
            was expired, Iguana channels using VMD files would fail
            even though the Iguana license was valid.
   Status: Fixed. Iguana license will override the chameleon license,
           if the Chameleon license is not valid. The only time a
           Chameleon license is untouched, is when it is still valid,
           and its expiration is greater than iguana's.
   Tracking Number: #1120

back to top

#1044: Iguana sends both success and error email messages for all log types

7) Problem: When configured, Iguana sends both success and error 
            emails for all log types. This behaviour only affects 
            client-executable components.
   Symptoms: Success and error messages are sent to you for each 
             message processed in Iguana. 
   Status: Fixed. Iguana now only sends a notification email when it
           encounters an error.
   Tracking Number: #1044

back to top

#1130: Message filter and routing functionality added

8) New Feature: Message filter and routing functionality was added. 
                This allows you to filter HL7 messages and route them 
                to a set of different targets.
   Tracking Number: #1130

back to top

#1474: Iguana does not adjust status table names that contain spaces

9) Problem: Iguana correctly inserts underscores into the names of 
            channels if spaces are present, but does not adjust the 
            status table names. This causes a syntax error. This 
            only affects the Message Filter destination component.
   Symptoms: You receive a syntax error and SQL command failed 
             statement when you try to export the tables in Iguana.
   Status: Fixed
   Tracking Number: #1474

back to top

#1249: Setting admin password to null or empty string invalidates login

10) Problem: Setting admin password to null or empty string would
	     invalidate login.  
    Workaround: Edit the ChannelConfiguration.xml and reset the admin
		password. See the troubleshooting section in the manual.
    Status: Fixed. User cannot change admin password to a null string.
    Tracking Number: #1249

back to top

Version 3.2 Build 147: October 24, 2005

Changes

#269: Drop-down menu to jump to different log page only works in IE

1) Problem: The drop-down menu used to jump to a different log page 
            only functions properly in Internet Explorer.
   Symptoms: You cannot use this drop-down menu in any other browser.
   Status: Fixed. The drop-down menu has been replaced with a text box 
           to output to the current page number. This fix has been 
           confirmed to work in most browsers (e.g. IE, Firefox, etc.).
   Tracking Number: #269

back to top

#355: FTP source and destination components removed

2) Update: All of the FTP source and destination components have been 
           removed.
   Tracking Number: #355

back to top

Version 3.2 Build 146: September 30, 2005

Changes

#437: Support added for MySQL 5.0

1) Update: Added support for MySQL 5.0.
   Tracking Number: #437 

back to top

#556: Export functionality added for logs

2) New Feature: Export functionality for logs was added. This allows you
                to export/merge source and destination logs (both errors
                and successes) into one file. This replaces resubmissions.
   Tracking Number: #556

back to top

#278: OCI errors could be misreported

3) Problem: OCI errors could be misreported
   
   Symptoms: Irrelevant Errors such as "object not found" would be
             returned as SQL errors, and did not explain the actual
             error.

   Status: Fixed, the error was due to OCI being unable to provide
	   contextual info during an error that occurred, causing that
	   additional error to mask the original error.
   Tracking: #278

back to top

#125: ODBC could return undescriptive error messages with special data types

4) Problem: ODBC could return undescriptive error messages with
            special data types.
   Symptom: Receiving a ODBC error of the form similiar to 
	    "ODBC data type: -7 not supported. "
   Status: Fixed. ODBC errors related to data types will print the
	   column information as well as the original SQL statement.
   Tracking Number: #125

back to top

Version 3.2 Build 145: August 30, 2005

1) Fix : If Ack validation fails, the channel now tries resending the
         message the amount of times given by Number of Send
         Retries. After that, the channel is stopped.

back to top

Version 3.2 Build 144: August 24, 2005

1) Fix : Fixed issue where the IGC_csharp.dll was not strongly named,
         and hence could not be added to the .NET GAC. THIS REQUIRES
         USERS OF IGC C# TO RECOMPILE THEIR APPLICATIONS.

back to top

Version 3.2 Build 142/143: August 23, 2005

1) Fix : If an exception occurred in the ack verification vmd, the
         process would encounter an unhandled exception. Now if an
         exception occurs within the vmd, the channel is stopped, and
         an error is noted.

2) Fix : Issue where if a shutdown timeout occurred in the executable
	 inbound/outbound components, the process would not be killed.

3) Fix : Fixed issue where if a RPC timeout occurred in the
         inbound/outbound executable components, channel would not be
         stopped.

4) Fix : Timers not being stopped when outbound/inbound executable
         channels were being stopped.

5) Feature : If the acknowledgment vmd file in the LLP listener
	     component returns an empty string, no ACK is sent back to
	     the sender.

6) Fix : Fixed issue with LLP client, where on a close, the shutdown
         sequence would lose the last received ack.

7) Feature: Resubmissions now are part of their own subsystem. This
	    allows resubmissions to be multiple, and non blocking. A
	    Resubmissions pages is now added to the interface.
	    Resubmissions are previewed before going to a confirmation
	    stage. A progress amount is also available.

8) Fix: Issues with polling components (From Database, From File)
        reaching a state where polling stops. This was due to
        threading issues that were discovered. The implementation has
        been simplified to rectify this problem.

back to top

Version 3.2 Build 141: August 3, 2005

1) Fix : LLP client and LLP listener now stops immediately when stop
         is called on a channel. This fixes issues with remote LLP
         implementations that do not implement a graceful TCP/IP
         close. This also affects situations where badly formed
         connections do not issue a proper close request, and the LLP
         client does not properly reconnect.

back to top

Version 3.2 Build 140: July 27, 2005

1) Fix : Issue where small messages within a larger data packet would
	 be ignored.

2) Fix : Issues with buffer overruns with inbound/outbound executable.

back to top

Version 3.2 Build 139: June 29, 2005

1) Fix : If Iguana terminated unexpectedly, client executables would
         usually be left around in the background (a process leak).

2) Feature : Changed connection limit on registration to now use the
	     count of concurrently running channels.

back to top

Version 3.2 Build 138: June 28, 2005

1) Fix : Disabled handle inheritance across processes of sockets, to
         prevent orphan client executable processes if Iguana stopped
         unexpectedly.

2) Fix : Executable components used to give a timer exception when
         doing a timed out shutdown, that is now fixed.

3) Feature : Service error log now has a time stamp per entry.

4) Fix : Added extended error information for when a bind fails,
         fixes issues with error information missing when an
         insert/update failed because of a data type mismatch.

5) Fix: Changed escaping of keywords in Sybase from double quotation marks
        to square brackets.

back to top

Version 3.2 Build 137: May 9, 2005

1) Feature: Added a new shortcut to localhost:8081, allowing Iguana to
            be accessed from the Start menu and the desktop.

2) Feature: The Iguana installation now allows you to select the
            optional Components for Chameleon.

3) Fix: Fixed syntax problems with table exports for Sybase ASA
        databases.

4) Fix: Resolved a problem where the .NET stub-code generation
        components were not completely installed.

5) Fix: Fixed the issue where the LLP Client did not stop properly
        because the connection was not being closed by the operating
        system.  This problem left the channel running although it
        appeared to be stopped in the dashboard.

6) Fix: Resolved issue where ACKs were being sent instead of NACKs when
        there was a failure logging a success into the database.

back to top

Version 3.2 Build 135: April 7, 2005

1) Feature: Added two new components: LLP Active Listener and LLP
            Passive Client.

2) Feature: Added ODBC Sybase database support.

3) Feature: Added an SMTP error log file to log errors that occur when
            sending emails.

4) Fix: Resolved the issue where the From Database component would wait
        for the amount of time given by the Poll Time even if there were
        outgoing messages available in the database. Now, the component
        sends all available messages before waiting.

5) Fix: Resolved issue with the LLP listener where the Errors log would
        get flooded with errors if the channel got disconnected before
        sending an ACK.

6) Fix: All database logging operations are now transactional.

7) Fix: The FTP components will stop the channel if the FTP connection
        is lost.

8) Fix: Improved verification checks for the channel and component
        configurations.

9) Fix: The FTP component configurations can change the FTP port.

10) Fix: VMD files are reloaded when starting a channel and exporting
         tables.

11) Fix: Issue with deleting the last page of logs would show an empty
         page of results. It has been resolved to switch to the first
         page.

12) Fix: Searching the logs will accept escaped quotes.

13) Documentation: Added documentation for the File and FTP components.

14) Documentation: Added Help button in the interface, which links to
                   the web documentation.

back to top

Version 3.2 Build 132: March 1, 2005

1) Feature: Added native support for all versions of MySQL 3.23 and
            greater.

2) Fix: Improved error handling for the to/from file component so that
        if the specified directory does not exist (or has incorrect
        permissions) - a notification is provided in the error logs.

3) Fix: Issue with the to/from FTP component - errors would sometimes
        cause the FTP channel to hang.  Resolved.

back to top

Version 3.2 Build 131: February 22, 2005

1) Feature: To/From File component added to enable streaming of HL7
            to and from locally stored batch files. Documentation to
            follow.
            
2) Feature: To/From FTP component added to enable streaming of HL7
            to and from batch files that are located remotely on
            an FTP server. Documentation to follow.
            
3) Feature: MySQL 4.1 native support added (in addition to existing
            support for previous versions of MySQL).
            
4) Feature: Added PostgreSQL support through ODBC.

5) Feature: Ability to resubmit multiple messages at a time from the
            error logs.
            
6) Fix: Can no longer remove a channel that is currently running.

7) Fix: Issue with automatic log purging functionality has been
        resolved.

back to top

Version 3.2 Build 100: November 8, 2004

1) Fix: Last release of Iguana had an error in the database/python
        component.  The issue has been resolved.

back to top

Version 3.2 Build 94: November 4, 2004

* Note: Default port for the web interface has changed from 8080 to 8081
*       in this build.  This can be changed.  See the manual for details.

1) Feature: Completely revamped User Interface to make it cleaner and
            more scalable.

2) Feature: Added the ability to search the interface logs.

3) Feature: Advanced Negative ACK support added.
                  
4) Feature: Added the ability to automatically reconnect an LLP 
            client to a server that closed the connection.
                  
5) Feature: Ability to retrieve a trial license automatically via the
            iNTERFACEWARE members section on the web site.
            
6) Feature: User permissions now restrict who can edit channel details,
            only those with admin privileges.

7) Feature: Added new component types, Executable types, so that code
            can be invoked as the source or destination of a channel.
            Currently this only supports C# code.  See documentation
            for details.

8) Documentation: Completely revamped (and complete) product
                  documentation.

9) Fix: Improved support for MS Access.

back to top

Version 3.2 Build 11: October 12, 2004

1) Fix: Fixed error when casting NULL values to string.

back to top

Version 3.2 Build 10: October 8, 2004

1) Change:  Instead of using input and out channels, we now have a more
            general notion of input and output components.  This allows
            us the ability to add different input and output types.
            
2) Fix:  Added a default value of empty string for all the outgoing 
         Table Id's so that it won't be necessary to fill each and 
         every ID.
         
3) Documentation:  Added a migration section discussing how to migrate
                   from Iguana version 3.1 to 3.2
                   
4) Fix:  Added autonack for LLP listener component. This means that if 
         any connected component does not accept a message, a nack is 
         returned instead of an ack. So, for a "To Database", if the 
         database connection goes down, a nack will be sent back.
         
5) Feature:  Added ability to specify email username/password for 
             authentication on the SMTP server being used to deliver
             e-mail notification of system errors.
             
6) Fix:  Data type issues with the ODBC Oracle interface have been 
         resolved.

back to top

Version 3.1 Build 248: September 24, 2004

1) Fix: Minor Oracle ODBC error resolved.

back to top

Version 3.1 Build 246: September 3, 2004

1) Fix: Some users encountered issues while starting/stopping their 
        outgoing interface channels that had an impact on the
        performance of the dashboard user interface.  This issue has
        been resolved.

back to top

Version 3.1 Build 208: August 17, 2004

1) Fix: Compatibility issue with SQLserver isolated and resolved.

back to top

Version 3.1 Build 198: August 13, 2004

1) Fix: Fixed an iframe issue in IE where some customers reported page
        loading problems of the dashboard.

back to top

Version 3.1 Build 192: August 11, 2004

1) Fix: Oracle/OCI resubmission issue has been fixed.
2) Fix: Long waiting periods to show logs have been fixed for large log
   tables in oracle OCI, and the service apparently stopping when
   the dashboard is refreshed, or logs being viewed. 

back to top

Version 3.1 Build 173: August 5, 2004

1) Fix: Truncation of error messages to a maximum of 4000 characters
        is no longer necessary since our OCI/Oracle implementation 
        now supports binding.  

2) Feature: Improved memory management.

back to top

Version 3.1 Build 150: July 29, 2004

1) Change: A new license scheme has been decided upon and implemented
           for this release so all previous product registrations 
           will be invalidated.  Contact support@interfaceware.com for
           new license information.

2) Feature: Advanced administration of web interface users has been
            implemented to allow creation of user groups with permissions
            etc. 

3) Feature: Improved log error handling.  Errors occurring while logging
            errors to the database are handled more gracefully.

back to top

Version 3.1 Build 126: July 22, 2004

1) Fix: An error in the e-mail subsystem that would, depending on the
        platform, result in a "pure virtual function call" exception
        has been identified and resolved.

back to top

Version 3.1 Build 110: July 16, 2004

1) Feature: Added user logins for security and access control.

2) Feature: Added licensing and registration system.  Iguana now requires
       a valid registration key to run.

3) Feature: Added Iguana User's Manual.
   
4) Fix: Fixed inability to handle Oracle Numbers larger than 32-bits in OCI layer.  
   Iguana now casts database fields to their Chameleon table data types 
   to handle these issues.

back to top

Version 3.1 Build 85: July 8, 2004

1) Feature: If one or more Key fields are NULL when parsed from a message, 
            such a row is not inserted into the database. This is to avoid
            invalid inserts being made to the database if the data is to be 
            ignored.

back to top

Version 3.1 Build 76: June 29, 2004

1) Fix: Fixed the OCI/Oracle interface problem that was introduced 
        with the last release of Iguana. Exceptions on database connections
        are now handled correctly.

back to top

Version 3.1 Build 70: June 25, 2004

1) Feature: Improved log handling.  When logs can not be stored to the 
            database, they are reliably written to disk.
        
2) Fix: Fixed bug where the dashboard would not display correctly when
        the database connection was lost.

3) Feature: Improved ACKnowledgement handling for outgoing channels. 
            ACKs can now be verified against a VMD file.  Also, messages
            will be automatically resent after a certain timeout period
            if an ACK has not been received.

back to top

Version 3.1 Build 55: June 17, 2004

* NOTE: Requires version 312 build 491 or higher of Chameleon to
*       be installed on the same machine.                                              

1) Feature: Added native support for Oracle databases.  This means that
            you can now choose to access your Oracle database through
            an ODBC interface or through the native OCI layer.

2) Fix: The database log tables that Iguana creates now have abbreviated
        names since some databases impose a maximum length on table 
        names.

back to top

Version 3.1 Build 44: June 11, 2004

* NOTE: Requires version 312 build 491 or higher of Chameleon to
*       be installed on the same machine.                                              

1) Feature: Added support for WVARCHAR data type over ODBC.

2) Fix: Improved reliability of new logging subsystem.

3) Fix: E-mails were being sent out on all log entries.  This included
        success log entries.  This issue has been resolved.  E-mail will
        only be sent out on errors.

back to top

Version 3.1 Build 27 (alpha): June 2, 2004

* NOTE: Requires version 312 build 491 or higher of Chameleon to
*       be installed on the same machine.                                              

1) Feature: If error or message logging to the database fails, then 
            the logging of data is done to a file on disk.

2) Feature: Added e-mail functionality.  So, not only will errors be
            logged, but e-mail notification of these errors can also
            be sent out.

3) Fix: Fixed preview of exporting database tables before the export 
        is carried out.  Also previews export of log tables.

4) Fix: Configuration page was not showing the configuration for the
        outbound channels.

back to top

Version 3.1 Build 14: May 28, 2004

* NOTE: Requires version 312 build 491 or higher of Chameleon to
*       be installed on the same machine.                                              

1) Feature: Improved memory management.

back to top

Version 3.1 Build 6: May 26, 2004

* NOTE: Requires version 312 build 477 or higher of Chameleon to
*       be installed on the same machine.                                              

1) Feature: DBdeliver logs are now entered into the database.  The
            tables created have the prefix "log_" and will contain
            the channel name that they pertain to.
            
2) Feature: The database associated with a specific channel can 
            be queried/accessed from Python code within your VMD file.
            For details on how this works, consult the Python portion
            of the manual.  Start by reading about the Environment 
            Python object and the new Database Python object.

3) Feature: Turned off word wrap on all text area outputs in 
            the User Interface.

4) Feature: Automatic refresh of channel information on the main
            page.  Allows for near real-time viewing of the
            messages parsed / errors without having to explicitly
            refresh the entire page.
            
5) Feature: If an error occurs while parsing a message, the 
            user now has the
            ability to view the error and message, modify the
            message and then resubmit the message to the 
            dbDeliver server.

6) Feature: Added the ability to export database tables for
            a channel from within the User Interface (as opposed
            to from the command line).

7) Feature: Added User Interface support for outgoing ("client") 
            channels which will generate messages from the database.
            
8) Feature: Extended logging functionality added - successfully
            parsed messages will be logged as well as problem
            messages.

9) Feature: Can delete items from the error log displayed in the
            user interface.

10) Fix: Issue with running DBdeliver as a service has been
         resolved.

11) Feature: Support for keys on multiple columns in a table 
             instead of just one.

back to top

Version 3.1 Build 2: April 16, 2004

1) Feature: DBdeliver now uses database transactions.

2) Feature: Support for Oracle via ODBC tested and integrated.

3) Fix: Quote characters are now correctly escaped for SQL Server.