------------------------------------------------------------------------ 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. ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 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 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 Windows 2000. They also do not work on versions of Windows XP that do not have recent service packs installed. This has been fixed in Iguana 4.1.10. [Affected Releases] Iguana 4.1.8, Iguana 4.1.9 [Tracking Numbers] #13866 ************************************************************************ * Version 4.1 * Build 10 * Date March 1, 2010 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 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 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 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 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 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 ************************************************************************ * Version 4.1 * Build 9 * Date February 10, 2010 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 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 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 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 ************************************************************************ * Version 4.1 * Build 8 * Date January 19, 2010 ************************************************************************ ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 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 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 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 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 ************************************************************************ * Version 4.1 * Build 7 * Date January 6, 2010 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 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 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 ************************************************************************ * Version 4.1 * Build 6 * Date December 10, 2009 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 5) [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.5. [Affected Releases] Iguana 4.1 [Tracking Numbers] #13333 ************************************************************************ * Version 4.1 * Build 5 * Date December 3, 2009 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 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 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 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 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 ************************************************************************ * Version 4.1 * Build 4 * Date November 26, 2009 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 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 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 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 ************************************************************************ * Version 4.1 * Build 3 * Date November 16, 2009 ************************************************************************ *********************************************************************** Known Issues *********************************************************************** ----------------------------------------------------------------------- #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 ----------------------------------------------------------------------- #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 ----------------------------------------------------------------------- #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 ----------------------------------------------------------------------- #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 ************************************************************************ * Version 4.1 * Build 2 * Date November 3, 2009 ************************************************************************ *********************************************************************** Known Issues *********************************************************************** ----------------------------------------------------------------------- #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 ----------------------------------------------------------------------- #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 ----------------------------------------------------------------------- #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 ------------------------------------------------------------------------ #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 ************************************************************************ * Version 4.0 * Build 12 * Date September 10, 2009 ************************************************************************ ************************************************************************ * Version 4.0 * Build 11 * Date August 21, 2009 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 ************************************************************************ Bug Fixes ************************************************************************ 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 ************************************************************************ * Version 4.0 * Build 10 * Date August 7, 2009 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 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 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 *********************************************************************** Known Issues *********************************************************************** ----------------------------------------------------------------------- #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ************************************************************************ * Version 4.0 * Build 9 * Date July 2, 2009 ************************************************************************ ************************************************************************ Additions ************************************************************************ 1) [Feature Description] The SocketHandle and IsValidSocketHandle properties have been added to the connection interface classes. [Affected Releases] Iguana 4.0 [Tracking Numbers] #11957 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 ************************************************************************ * Version 4.0 * Build 8 * Date June 17, 2009 ************************************************************************ ************************************************************************ Bug Fixes ************************************************************************ 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 ************************************************************************ Known Iguana Issues ************************************************************************ ------------------------------------------------------------------------ #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 ************************************************************************ * Version 4.0 * Build 7 * Date May 4, 2009 ************************************************************************ ************************************************************************ * Version 4.0 * Build 6 * Date April 20, 2009 ************************************************************************ ************************************************************************ Additions ************************************************************************ 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 ************************************************************************ * Version 4.0 * Build 5 * Date March 31, 2009 ************************************************************************ ************************************************************************ Bug Fixes ************************************************************************ 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 ************************************************************************ * Version 4.0 * Build 4 * Date March 23, 2009 ************************************************************************ ************************************************************************ Bug Fixes ************************************************************************ 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 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 ************************************************************************ * Version 4.0 * Build 3 * Date March 15, 2009 ************************************************************************ ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 ************************************************************************ Known Iguana Issues ************************************************************************ ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ************************************************************************ * Version 4.0 * Build 2 * Date March 10, 2009 ************************************************************************ ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ************************************************************************ Fixed Known Issues ************************************************************************ ------------------------------------------------------------------------ #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 ************************************************************************ * Version 4.0 * Build 1 * Date March 3, 2009 ************************************************************************ This page provides details about all the additions, changes and bug fixes in Iguana since its last official release. ************************************************************************ Additions ************************************************************************ 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 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 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 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 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 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 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 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 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 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 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 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 ************************************************************************ Changes ************************************************************************ 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 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 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 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 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 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 [Tracking Numbers] 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 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 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 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 ************************************************************************ Bug Fixes ************************************************************************ 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 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 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 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 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 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 ************************************************************************ Known Iguana Issues ************************************************************************ ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ------------------------------------------------------------------------ #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 ************************************************************************ * Version 3.3 * Build 2 * Date September 27, 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.2 [Tracking Numbers] #6814 ************************************************************************ * Version 3.3 * Build 1 * Date August 17, 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.