------------------------------------------------------------------------ Iguana Change Log & Release History ------------------------------------------------------------------------ Log available at ftp://ftp.interfaceware.com/iguana/change_log.txt ------------------------------------------------------------------------ This page provides documentation for issues and advisories which have been noted, fixed, have workarounds and/or are in the process of being fixed. ************************************************************************ Known Iguana Issues ************************************************************************ ------------------------------------------------------------------------ #4189 ------------------------------------------------------------------------ [Description] Iguana uses a custom build of Chameleon in Unix. [Symptom] A Chameleon shared library does not appear in the Unix package. [Severity] Moderate [Workaround] Install the Unix version of Chameleon. [Affected Releases] All Iguana releases ------------------------------------------------------------------------ #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 ----------------------------------------------------------------------- #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 ************************************************************************ * Version 3.3 * Build 2 * Date September 26, 2007 ************************************************************************ This page provides details about all the additions, changes and bug fixes in Iguana since its last release. ************************************************************************ Changes ************************************************************************ 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.1 [Tracking Numbers] #6814 ************************************************************************ * Version 3.3 * Build 1 * Date August 6, 2007 ************************************************************************ This page provides details about all the additions, changes and bug fixes in Iguana since its last release. ************************************************************************ Additions ************************************************************************ 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 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 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 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 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 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 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 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 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 ************************************************************************ Changes ************************************************************************ 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 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 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 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 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 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 7) [Description] Support for "DB Direct", a legacy version of Iguana, has been removed. [Severity] Low [Affected Releases] Iguana 3.3 [Tracking Numbers] #6271 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 5) [Problem] There was an issue in Iguana where leading and/or trailing whitespaces 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 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 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 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 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 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 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 ************************************************************************ * Version 3.2 * Build 155 * Date April 16, 2007 ************************************************************************ This page provides details about all the additions, changes and bug fixes in Iguana since its last release. ************************************************************************ Fixed Iguana Issues ************************************************************************ ----------------------------------------------------------------------- #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 ************************************************************************ Additions ************************************************************************ 1) [Feature Description] New functionality has been added to Iguana that allows you to read-in 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 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 ************************************************************************ Changes ************************************************************************ 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 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 ************************************************************************ * Version 3.2 * Build 154 * Date November 30, 2006 ************************************************************************ This page provides details about all the additions, changes and bug fixes in Iguana since its last release. ************************************************************************ Additions ************************************************************************ 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 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 3) [Feature Description] Iguana now fully supports Sybase ASE 15. [Severity] High [Affected Releases] 3.2.154 [Tracking Number] #3148 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 ************************************************************************ Changes ************************************************************************ 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 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 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 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 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 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 ************************************************************************ * Version 3.2 * Build 153 * Date May/04/2006 ************************************************************************ 1) New Feature : Allow multiple iguanas on the same system, unix only. Status : In Beta Tracking Number: #2398 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 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 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 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 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 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 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 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 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 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 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 * Version 3.2 * Build 152 * Date Mar/06/2006 ************************************************************************ 1) New Feature : Error Logs can be automatically purged (Except for error logs on Client Executable Components). Tracking Number : #1294 * Version 3.2 * Build 151 * Date Feb/08/2006 ************************************************************************ * Version 3.2 * Build 150 * Date Feb/01/2006 ************************************************************************ 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 * Version 3.2 * Build 149 * Date Jan/27/2006 ************************************************************************ 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 * Version 3.2 * Build 148 * Date Jan/23/2006 ************************************************************************ 1) Documentation: Getting the Iguana Service to Work with Your Network Drive and Installing Iguana Service From a Command Prompt Tracking Number: #857 2) Documentation: Added background info to Getting the Iguana E-Mail Notification to Work with Your Mail Server section to make it more clear. Tracking Number: #817 3) 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 3) 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 4) 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 5) 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 6) 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 7) 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 8) 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 9) Documentation: More FAQs were added to the troubleshooting section. Tracking Numbers: #811, #812, #880, #977, #962, #1196, #1231, #956 and #306 10) 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 11) 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 12) Documentation: "Writing the Client Executable" section was moved under "Advanced: Data Validation" section. 13) 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 * Version 3.2 * Build 147 * Date Oct/24/2005 ************************************************************************ 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 2) Update: All of the FTP source and destination components have been removed. Tracking Number: #355 * Version 3.2 * Build 146 * Date Sep/30/2005 ************************************************************************ 1) Update: Added support for MySQL 5.0. Tracking Number: #437 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 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 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 * Version 3.2 * Build 145 * Date Aug/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. * Version 3.2 * Build 144 * Date Aug/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. * Version 3.2 * Build 143/142 * Date Aug/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. * Version 3.2 * Build 141 * Date Aug/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. * Version 3.2 * Build 140 * Date 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. * Version 3.2 * Build 139 * Date 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. * Version 3.2 * Build 138 * Date 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. * Version 3.2 * Build 137 * Date 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. * Version 3.2 * Build 135 * Date April/07/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. * Version 3.2 * Build 132 * Date March/01/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. * Version 3.2 * Build 131 * Date 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. * Version 3.2 * Build 100 * Date November/8/2004 * ************************************************************************ 1) Fix: Last release of Iguana had an error in the database/python component. The issue has been resolved. * Version 3.2 * Build 94 * Date 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. * Version 3.2 * Build 11 * Date October/12/2004 ************************************************************************ 1) Fix: Fixed error when casting NULL values to string. * Version 3.2 * Build 10 * Date 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. 5) Fix: Data type issues with the ODBC Oracle interface have been resolved. * Version 3.1 * Build 248 * Date September/24/2004 ************************************************************************ 1) Fix: Minor Oracle ODBC error resolved. * Version 3.1 * Build 246 * Date 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. * Version 3.1 * Build 208 * Date August/17/2004 ************************************************************************ 1) Fix: Compatibility issue with SQLserver isolated and resolved. * Version 3.1 * Build 198 * Date August/13/2004 ************************************************************************ 1) Fix: Fixed an iframe issue in IE where some customers reported page loading problems of the dashboard. * Version 3.1 * Build 192 * Date 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. * Version 3.1 * Build 173 * Date August/05/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. * Version 3.1 * Build 150 * Date 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. * Version 3.1 * Build 126 * Date 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. * Version 3.1 * Build 110 * Date 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. * Version 3.1 * Build 85 * Date 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. * Version 3.1 * Build 76 * Date Jun/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. * Version 3.1 * Build 70 * Date Jun/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. * Version 3.1 * Build 55 * Date Jun/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. * Version 3.1 * Build 44 * Date Jun/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. * Version 3.1 * Build 27 (alpha) * Date Jun/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. * Version 3.1 * Build 14 * Date 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. * Version 3.1 * Build 6 (alpha) * Date 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. * Version 3.1 * Build 2 * Date 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.