------------------------------------------------ Release notes for Transaction Director Series 5.4 SP2 (5.4.0.0.3) ------------------------------------------------ Copyright (c) 2004-2006 Cyclone Commerce, Inc. All rights reserved. This information supplements the user documentation. ----------------- Table of contents - What's new for 5.4 1. Detail parser and pipeline improvements 2. Faster paging in user interface 3. User security enhanced 4. Method for running UI over HTTPS enhanced ------------------------------ - Known issues 1. The same document triggers multiple alerts 2. Subtracting user management authority can affect user 3. Do not delete a document type in a report 4. On UNIX copy aXML Agent install files to the computer 5. Manually set up server parsing of large XML documents 6. System sometimes cannot generate reports 7. Do not use large sample documents with XPath wizard ------------------------------ - 5.4 resolved issues 1. Faulty fail-over message discontinued 2. Specific upgrade path resulted in DB table error 3. Default alert event filter added to events.xml 4. aXML Agent fatal runtime errors when using JMS 5. Oracle-specific "upper" index added for searches ------------------------------ - What's new for 5.4 ------------------------------ ------------------------------------------ 1. Detail parser and pipeline improvements Enhancements have improved the performance of the Transaction Director detail parser by 10 to 15 percent. In addition, the detailparser.properties file and any configured lookup files have been made “hot-swappable.” This means if these files are changed while Transaction Director is running, the changes become effective with the next file processed in about 15 seconds. ---------------------------------- 2. Faster paging in user interface When multiple pages of data are available for display (for instance, search results, rejected documents), Transaction Director loads next and previous pages faster and provides links to directly access a page while skipping other pages. ------------------------- 3. User security enhanced Controls have been added to the user interface that let administrators with a role permission of "manage users and roles" set rules for user IDs and passwords. These include rules for user ID and password character length. Administrators also can control: Elapsed days before passwords can be reused Days passwords remain valid before they must be reset Elapsed days before disabling inactive users Force new users to reset password upon initial log-in In addition, administrators can specify whether users can log on to the user interface multiple times simultaneously. 21512, 20538 -------------------------------------------- 4. Method for running UI over HTTPS enhanced The method has been enhanced for running the user interface over HTTPS. Configuration details are in the user documentation. 21738 ------------------------------ - Known issues ------------------------------ --------------------------------------------- 1. The same document triggers multiple alerts Alerts that trigger according to a schedule can result in duplicate alerts being produced for the same document, even one that entered the system some time ago. This does not occur when an alert is configured to check documents upon entering the system, rather than using a schedule. 9104 -------------------------------------------------------- 2. Subtracting user management authority can affect user If a user with a role that allows user management changes to a role without such authority, the user no longer can navigate in the user interface. An administrative user should make this type of role change for the user. 8920 -------------------------------------------- 3. Do not delete a document type in a report After configuring a report, do not delete any document types upon which the report is based. If you do so, you cannot change or delete the report. Before deleting a document type, change the report configuration so the report no longer relies on it. 9134 -------------------------------------------------------- 4. On UNIX copy aXML Agent install files to the computer If you are installing aXML Agent on a computer with a UNIX operating system and are using an installation CD, copy the files from the CD to a directory on the UNIX computer before proceeding. 9156 -------------------------------------------------------- 5. Manually set up server parsing of large XML documents Using the user interface controls, you might not be able to set up XPaths for parsing attributes of XML documents that are approximately 1 megabyte or larger in size. If this occurs, see the user documentation for configuring server parsing with the manual method. 9592 ------------------------------------------- 6. System sometimes cannot generate reports The system sometimes cannot generate reports. This can occur when the system must process a large number of records or report a large number of attributes or both. 9304 ------------------------------------------------------ 7. Do not use large sample documents with XPath wizard The XPath wizard in the user interface cannot be used when the sample XML document is large (1 megabyte or more). As a work-around, use a smaller sample document with the XPath wizard or manually configure server parsing by following the instructions in the user manual. 9592 ------------------------------ - 5.4 resolved issues ------------------------------ ---------------------------------------- 1. Faulty fail-over message discontinued A message that gave the impression that node fail-over may not be working has been removed from the log file. Fail- over – one node stops and other picks up the processing – does work and is not affected by discontinuing the message. The offending message was: "Unable to start Director HTTP upload server on port 6081, it has probably been started by another node." 21892 --------------------------------------------------- 2. Specific upgrade path resulted in DB table error When a specific path was followed for upgrading this application, two database tables were not cleaned up properly. These tables were OPERANDS and COMPAREOPERATORS. The upgrade path that resulted in this error was: from a version before 5.3.2 b1419, then to 5.3.2 b1419, then to 5.3.3 b1524. If the upgrade path did not include both 5.3.2 b1419 and 5.3.3 b1524, the upgrade task was completed properly. This issue has been resolved. 21841 ------------------------------------------------- 3. Default alert event filter added to events.xml In conf/events.xml the Administration.Alert event has been enabled by default. When an alert is generated, it can have an action to generate this event. The stand-alone filter for this event in events.xml is Alerts Event Filter, and it can be used by other custom event routers. 21631 ------------------------------------------------- 4. aXML Agent fatal runtime errors when using JMS When aXML Agent was configured to hand off documents to a JMS queue for delivery to the server, fatal runtime errors occurred. This issue has been resolved. 21454 --------------------------------------------------- 5. Oracle-specific "upper" index added for searches To speed up document searches in the user interface when Oracle is the database, an index called IX_ATTRIBUTES_UPPER has been added to the table ATTRIBUTES. 20396 ----------------- End release notes -----------------