-------------------------------------------- Release notes for Cyclone Interchange and Activator Series 5.3.2 -------------------------------------------- Copyright (c) 2004-2005 Cyclone Commerce, Inc. All rights reserved. This information supplements the user documentation. ------------------------------ Table of contents - What's new for 5.3.2 1. Tracker allows ebXML conversation ID search 2. Meta-data can be added to outbound messages 3. Trading engine supports DB2 database 4. Support added for Oracle AQ 5. ebXML CPA API web service can add, remove CPAs 6. System-generated file names shortened 7. CSOS searches by PO number added 8. Retrieval of CRLs via HTTP through an HTTP proxy 9. Default paths displayed for file system integration 10. Delivery exchange events provide more information 11. Detail added to syntax error replies 12. Warning events aid in resolving exchange issues 13. SFTP client requests key type it has configured ------------------------------ - Known issues 1. Test result missing for improper MQSeries configuration 2. Ignore polling interval for HTTP delivery exchange 3. Secure e-mail protocol does not authenticate sender 4. Tracker fails to update receipt of resubmitted message 5. Database and document backup deletions are not logged 6. Message details show incorrect routing ID for partner 7. Receipt is not rejected when resend limit is reached 8. Multiple users can cause delete-change conflict 9. Multiple community imports adds multiple integration 10. Conditions for parsing payload for addresses 11. Possible port conflict with global HTTP server 12. Node fail-over may not work 13. Positive acknowledgment sent to non-partner 14. Outbound documents stuck "in process" 15. E-mail addresses for AS1, secure e-mail must be unique 16. Message action condition can be deleted, not changed 17. Avoid AS2 and ebXML in same partner profile 18. Starting a second node might generate false error 19. Invalid file name in XPath wizard displays blank page 20. Refreshing message tracker during purge generates error 21. Large traffic volume may generate harmless exception 22. First-time log on with CSOS signing only causes error 23. Oracle user name must exclude other database schemas ------------------------------ - 5.3.2 resolved issues 1. Time-out value ensures thread availability 2. Error importing CPA when partner already exists 3. Stylesheet improved for viewing of CSOS documents 4. Parsing changed for Tradacoms documents 5. User role permission caused improper UI display 6. Response to web service API call in error 7. Oracle 10g users advised to use 10g driver 8. JMS listener continued to reconnect when disabled 9. User password changes reported in events log 10. CYC_NETWORK_NAME binding not respected 11. Profile import does not warn about certificate 12. MessageId not copied from MMD to WebService call 13. Web Trader wizard let users skip certificate upload 14. EDIFACT document type not parsed properly ------------------------------ - What's new for 5.3 1. Primary keys added to all database tables 2. AS3 interoperability certification 3. RosettaNet 1.1 and 2.0 supported 4. HL7 supported for ebXML 5. Cyclone WebTrader option available 6. SFTP transport supported 7. Staged HTTP transport available for receiving messages 8. User interface supports Mozilla Firefox 9. Activator now uses Apache Derby database 10. System throttle enhanced 11. Message Tracker performance enhanced for detail views 12. CRL checking functionality expanded 13. Threads tuned for Derby database 14. Windows service keeps running after user logs off ------------------------------ - 5.3.1.0.12 resolved issues 1. Threads blocked while waiting for coreId token 2. Trading engine did not recognize LDAP for ARL ------------------------------ - 5.3.1.0.11 resolved issue 1. Unavailable TaskScheduler threads caused deadlock ------------------------------ - 5.3.1.0.9 resolved issue 1. Message resends sometimes caused an exception ------------------------------ - 5.3.1.0.8 resolved issue 1. Random NullPointerException due to deadlock ------------------------------ - 5.3.1.0.7 resolved issues 1. CSOS, WebTrader Java version discrepancy resolved 2. Message purge impacted performance 3. Client authentication error generated by mistake ------------------------------ - 5.3.1.0.6 resolved issues 1. Untimely receipt for ebXML message marked as "delivered" 2. New utility assures correct names for Windows service 3. Installer forces Derby database settings in upgrade ------------------------------ - 5.3.1.0.5 resolved issues 1. Corruption of Derby database during upgrade 2. Unicode format slowed performance for SQL Server ------------------------------ - 5.3.1.0.2 resolved issues 1. CollaborationRole not resolved for inbound ebXML 2. ebXML payloads did not always obey duplicate elimination 3. Produce version 4 message IDs for interoperability 4. Activator could not process CSOS documents 5. ebXML self-register message erroneously displayed 6. Database configuration tool displays correct port 7. EDIFACT with long version number could not be parsed 8. Alerts related to old exchange points deleted 9. Registration wizard checks for duplicate name, ID 10. Home page message links to new partner's summary page 11. Sponsor community prompted to act on new partner 12. ebXML message could not resubmit to JMS integration 13. Machine names in Windows service file changed 14. 2 node license only allowed 1 node 15. HTTPS information in CPA template not saved 16. EbxmlProtocolReceiver meta-data are being set 17. Leading, trailing spaces in fields not allowed 18. Restart not needed to change client authentication 19. Web trader partner self registration triggers event 20. Could not import certificate with certain data 21. Server warns when duplicate routing ID attempted ------------------------------ - 5.3.0.0.1 resolved issues 1. Activator upgrade failed 2. Changes reduce possible time synchronization conflicts 3. UNIX startServer script checks for existing process 4. Secure file HTTP or HTTPS in profile did not import 5. Base 64 encoding available for RosettaNet 6. Deleting AS2 embedded HTTP exchange caused exception 7. Tracker sometimes displayed wrong status for messages 8. Trading engine had trouble with NFS fail over 9. "More tasks" link on home page did not work 10. Windows service sometimes failed 11. FTP did not notify when message repeatedly pick up 12. Message events can be forwarded selectively to Director 13. Message no longer stuck in waiting for receipt state 14. Resubmitted messages showed incorrectly on home page 15. Primary keys added to all database tables 16. MQSeries characters set field expanded to 4 digits 17. Wrong CPA could be used in ebXML trading 18. Messages that cannot be resubmitted are rejected 19. Events log files roll over 20. Pick party wizard in Tracker fixed ------------------------------ - What's new for 5.2 1. Integration based on criteria 2. File system directories names supply meta-data values 3. Software Development Kit available 4. JMS message retrieval eliminates polling latency 5. Support for JMS TextMessage 6. Message Tracker enhanced 7. Trading engine events can be sent as e-mail alerts 8. Re-routing of messages made easier 9. AS2 URL for receipts can be superseded 10. New backup directory structure 11. Default message delete settings changed 12. Bundled SMTP address can be edited 13. Self-registration or provisioning API 14. Activator RAM requirement lowered 15. Easier setup of additional computers in a cluster 16. Installer uses preferred temporary directories ------------------------------ - 5.2.0.0.20 resolved issue 1. Activator forced to run in single VM mode ------------------------------ - 5.2.0.0.18 resolved issue 1. Modify Packaging to generate V4 style MessageIds ------------------------------ - 5.2.0.0.17 resolved issue 1. Database resources not released in web services API ------------------------------ - 5.2.0.0.16 resolved issue 1. Command-line tool unlocks documents stuck in-process ------------------------------ - 5.2.0.0.15 resolved issues 1. Could not send via HTTPS on AIX 2. Receipts erroneously identified duplicate messages 3. Some documents became locked in-process ------------------------------ - 5.2.0.0.14 resolved issues 1. Rejected events were not forwarded to Director 2. Nodes did not restart after database was restarted 3. Some users could not log on to user interface 4. HTTP user name, password not in ebXML header ------------------------------ - 5.2.0.0.12 resolved issues 1. Message rejection resolved 2. Multiple SOAP declarations in same header ------------------------------ - 5.2.0.0.11 resolved issues 1. Role permissions adjusted for message searches 2. E-mail alert configuration caused null pointer exception 3. P12 certificate files could not import on AIX 4. FTP client sending adjusted to accommodate firewall 5. JMS memory leak fixed 6. Settings not saved for fixed from, to address 7. Incorrect XML MIME type used for inbound exchange ------------------------------ - 5.2.0.0.7 resolved issue 1. Database table affected after upgrade ------------------------------ - 5.2.0.0.6 resolved issues 1. Nodes may not restart after server restarted itself 2. Nodes sometimes started twice ------------------------------ - 5.2.0.0.5 resolved issues 1. Profile export-import deleted community profile 2. Deleting, adding partner could disrupt resend tries 3. Server would stop if database connection lost ------------------------------ - 5.2.0.0.4 resolved issues 1. Using MQSeries required downloading a JAR file 2. Repeated "save" actions could spawn duplicate rule trees ------------------------------ - 5.2.0.0.3 resolved issues 1. Second node failed to poll for messages 2. StringIndexOutOfBoundsExceptions ------------------------------ - 5.2.0.0.2 resolved issue 1. Document Generator would not start on UNIX ------------------------------ - 5.2.0.0.1 resolved issues 1. Receipts appear to resubmit 2. Importing profile affected preferred transport 3. Routing inbound messages by document type was limited 4. Large data volume slowed message tracker 5. Community profiles sometimes did not export properly 6. "Delete all" button did not purge all messages 7. Mismatch between MMD, CPA not clearly identified 8. Only first ebXML payload rejected 9. Windows service repaired 10. Database tables lacked primary keys, indexes 11. Implementing upgrade logic resolves UI issue 12. Database port entry corrected during upgrade 13. Trading engine could not handle multiple SMTP responses 14. Receipt of duplicate ebXML messages was possible 15. Oracle database did not update during upgrade 16. Optimistic lock exception resolved ------------------------------ - What's new for 5.3.2 ------------------------------ ---------------------------------------------- 1. Tracker allows ebXML conversation ID search Message tracker now allows you to search for ebXML documents by conversation IDs. 20256 ---------------------------------------------- 2. Meta-data can be added to outbound messages A new feature of collaboration settings for AS1, AS2, AS3 and secure file message protocols is the ability to include any meta-data elements you want in the MIME headers of the messages a community sends. This can serve several purposes. It lets you send payload-related information to a partner. It also lets a community or partner use such data to trigger message handling actions. The meta-data that can be added are in addition to the meta-data already in MIME headers. 20708 --------------------------------------- 3. Trading engine supports DB2 database With this release, DB2 is supported as a database for the trading engine. 20740, 20741 ------------------------------ 4. Support added for Oracle AQ The trading engine now supports Oracle Advanced Queuing facility (Oracle AQ) for JMS transports. 20790 ------------------------------------------------- 5. ebXML CPA API web service can add, remove CPAs The new ebXML CPA API web service allows you to add and remove CPAs through an application program interface instead of manually through the graphical user interface. This is useful if CPAs are generated by some management application and then pushed into the trading engine for activation. The web service is described in CPAAPI.wsdl in [install directory]\[build number]\conf. There are two operations: importCPA and removeCPA. See [install directory]\[build number]\samples\Webservices\CPAAPIService for more information. 20912 ---------------------------------------- 6. System-generated file names shortened The unique file names the trading engine generated for back-end integration and delivery to partners could become too long for processing by certain applications. For this reason, the naming process has been changed to shorten the names considerably. The message core id (something that looks like "1116376836621_553_COMPUTER-T41") is no longer used in final file system or FTP file names. Instead, the hex string representation of the hash value of a GUID (looks just like a core ID) concatenated with the hex string representation of a monotonically increasing counter is used. The same monotonically increasing counter is used to "sequence" preserved FTP file names. The message core ID is still used for FTP temporary file names to support checkpoint-restart. 20542 ----------------------------------- 7. CSOS searches by PO number added You can now search in message tracker for a specific CSOS document by PO number. When you click the CSOS -> View past orders menu item, you get a custom tracker query that adds the CSOS PO number column. Now you can enter a PO number as a search condition 20615 --------------------------------------------------- 8. Retrieval of CRLs via HTTP through an HTTP proxy This release supports the retrieval of CRLs via HTTP through an HTTP proxy. The configuration of CRL retrieval through an HTTP proxy is contained in crossworks.properties at [install directory]\[build number]\conf. The new properties are: crls.http.proxyHost crls.http.proxyPort crls.http.proxyUser crls.http.proxyPassword Note that changes to crossworks.properties no longer require a server restart to take effect. 20909 ------------------------------------------------------ 9. Default paths displayed for file system integration When adding a file system integration pickup or delivery exchange, the trading engine now uses a default path as determined from the commonPath setting in the filereg.xml file, which is the conf directory. For users who at installation accept the default location of the common directory, the common directory is displayed as the default location for file system integration exchanges. 20987 ----------------------------------------------------- 10. Delivery exchange events provide more information As an aid in troubleshooting, additional information about delivery exchange points is provided in the Messaging.Transport.SendFailure and Messaging.Transport.ReceiveFailure events. Also, the format of the Messaging.Transport.SendFailure and Messaging.Transport.ReceiveFailure events has changed. These events used to contain information of the form: ExchangePointId(xxxx) Now they contain information of the form: ExchangePoint(Id(xxxx), URL(yyyy)) This exact format pertains to the way these events are represented in *_events.log files. The XML representation of these events has also changed accordingly, with the ExchangePointId element replaced by an ExchangePoint element containing Id and URL child elements. 11113 ---------------------------------------- 11. Detail added to syntax error replies For syntax error replies (reply code 500), the embedded SMTP server only returned a canned error string, "Syntax error, command unrecognized." To aid in troubleshooting, the trading engine now appends a detail message to the reply string, as well as writing a warning to the trading engine (te) log. This has been done to allow for more efficient troubleshooting of issues (such as invalid commands) both from the client and the server side. 20516 --------------------------------------------------- 12. Warning events aid in resolving exchange issues Warning events are now produced to the trading engine log to help in troubleshooting some common issues regarding delivery exchanges. When a POST request with an invalid path is received, the following two warning lines can be logged: WARN (Exchange.getExchangePointFromRequest:511) - Bad incoming HTTP request; path="frammus". Suggestions: 1. Make sure you have defined the paths correctly for your inbound HTTP delivery exchanges. 2. Make sure your partner is specifying the correct url, e.g. http://myserver:4080/exchange/mypath WARN (Exchange.doPost:88) - Refusing HTTP POST request with 404 (not found) response to client When an invalid request method is received (for example, GET) the following warning is logged: WARN (Exchange.disallowedMethodResponse:210) - Disallowed HTTP request "GET" received; returning intentionally vague 500 (internal server error) response to client 21036 --------------------------------------------------- 13. SFTP client requests key type it has configured When connecting to a SFTP server, the trading engine's SFTP client specified that either RSA or DSA keys were supported. It was up to the server as to which key was returned. The client configuration could only support one key. So if the server returned the wrong key type, the trading engine client could not authenticate the server. The client has been changed to specifically request the key type of the currently configured key. 20518 ------------------------------ - Known issues ------------------------------ ---------------------------------------------------------- 1. Test result missing for improper MQSeries configuration If you improperly set up MQSeries as an integration or trading transport, the user interface does not display a connection test result message that could help troubleshoot a configuration issue. If you properly configure the transport, a successful test result displays. 9019 ----------------------------------------------------- 2. Ignore polling interval for HTTP delivery exchange When you set up an HTTP or HTTPS delivery exchange, a polling interval field appears on the Advanced tab of the delivery exchange's maintenance page in the user interface. This field is not applicable to HTTP or HTTPS and you can ignore it. 9069 ------------------------------------------------------ 3. Secure e-mail protocol does not authenticate sender When using the secure e-mail message protocol, the system does not check whether the certificate used to sign an inbound message belongs to the message sender. 9238 --------------------------------------------------------- 4. Tracker fails to update receipt of resubmitted message When a message is resubmitted after receiving a negative response receipt, message tracker fails to update the receipt to received, although the status changes to delivered. 9326 -------------------------------------------------------- 5. Database and document backup deletions are not logged The system does not write events to logs related to the times when message database records and backed-up documents are deleted. 9357 -------------------------------------------------------- 6. Message details show incorrect routing ID for partner If a message is sent to a partner who has multiple routing IDs in the partner's profile, the message details view in message tracker only show the first ID as displayed on the partner's routing ID page in the user interface. This does not affect correct parsing of sender and receiver IDs in messages. 9368 ------------------------------------------------------- 7. Receipt is not rejected when resend limit is reached If an outbound message fails because the resend limit is reached and a receipt for a delivered message is later received, the system erroneously accepts the receipt rather than reject it. 9393 -------------------------------------------------- 8. Multiple users can cause delete-change conflict When one user deletes a community or partner while another user is trying to modify the same community or partner, the second user will notice errors. This can be avoided by setting a policy for deleting communities and partners. 9419 ------------------------------------------------------- 9. Multiple community imports adds multiple integration If a community is imported multiple times, multiple integration delivery exchanges for retrieving messages are added, each with the same directory to poll. If you import a community more than once, check the integration delivery to make sure the configuration is correct and there are no conflicts. 9389 ------------------------------------------------ 10. Conditions for parsing payload for addresses Only configure to use payload parsing for "to" and "from" addresses when address information is in the EDI or XML payload and is for parties known to the trading engine. If this is not the case, choose the setting to use the "from" and "to" address provided by the message protocol. 9426 -------------------------------------------------- 11. Possible port conflict with global HTTP server The global embedded HTTP server connects on port 4080 by default. If you set up another HTTP server, both cannot use 4080. You must change the port for one or the other. 9460 ------------------------------- 12. Node fail-over may not work When running the trading engine in a cluster and a processing node stops, the work might not be picked up by another node in the cluster. This has been observed to occur infrequently. 9550, 9551 ----------------------------------------------- 13. Positive acknowledgment sent to non-partner When a message is received from a partner who is not a member of the community, the trading engine rejects the message but returns a positive acknowledgment to the sender. The partner does not know the message was rejected. 9629 ----------------------------------------- 14. Outbound documents stuck "in process" Documents sometimes become stuck in an "in process" state when sent via an HTTP embedded server delivery exchange. 9479 ---------------------------------------------------------- 15. E-mail addresses for AS1, secure e-mail must be unique If you use both the AS1 and secure e-mail message protocols in a profile, the e-mail address must be unique for each delivery exchange. 9832 -------------------------------------------------------- 16. Message action condition can be deleted, not changed After a condition has been set up for a message action, the condition can be deleted or other conditions can be added. An existing condition cannot be changed. To change a condition, delete the existing condition and add it back with the desired change. 10007 ----------------------------------------------- 17. Avoid AS2 and ebXML in same partner profile Avoid setting up a partner profile to send messages by both the AS2 and ebXML message protocols. The two protocols do not work in the same profile unless AS2 is the default. 10008 ----------------------------------------------------- 18. Starting a second node might generate false error When you add and start a second node for the trading engine when a node with embedded SMTP and HTTP servers already is running on the same machine, error messages are written to the trading engine log file. Although this might have the appearance of a serious error, trading processes are not affected and you can ignore the messages. 10686 --------------------------------------------------------- 19. Invalid file name in XPath wizard displays blank page Pointing the XPath wizard to an invalid file name results in the display of a blank page in the user interface. 10149 ----------------------------------------------------------- 20. Refreshing message tracker during purge generates error If you choose the option for deleting all trading engine messages and refresh the message tracker page while the purge is in progress, the system generates a null pointer exception. This is a temporary condition that does not affect the purge. 10226 -------------------------------------------------------- 21. Large traffic volume may generate harmless exception When processing a large volume of messages, the system may generate an occasional null pointer exception. This does not seem to affect trading. 10321 --------------------------------------------------------- 22. First-time log on with CSOS signing only causes error If using a license that allows CSOS signing only, the first time you log on results in an exception. Refreshing the browser corrects this, as does restarting the server. 10804 -------------------------------------------------------- 23. Oracle user name must exclude other database schemas If you use Oracle and are installing for the first time or upgrading from 5.1, you must do the following before installing. Make sure the database user name has permission to access only the schema for this application. The user name supplied to the application at install time cannot have permissions to access other database schemas. If this is not done, database exceptions may occur. 11009 ------------------------------ - 5.3.2 resolved issues ------------------------------ --------------------------------------------- 1. Time-out value ensures thread availability Sometimes a thread obtained a token and held onto it for a long time. This caused all subsequent requests for the same token to block indefinitely. This had the effect of essentially removing a TaskScheduler thread from the pool. The situation continued until all TaskScheduler threads were exhausted. This issue has been resolved by enhancing the TokenManagers getToken method to take a timeout value. By specifying a timeout value, the TaskScheduler threads are returned to the pool if the requested token is unavailable. 20900 -------------------------------------------------- 2. Error importing CPA when partner already exists When importing an ebXML CPA when the partner in the CPA already had a profile, the trading engine did not properly overwrite the old information in the profile with the new information in the CPA. This issue has been resolved. The trading engine also will generate a warning if the routing ID in CPA being imported is the same, but the ebXML type is not, or if a routing ID duplicates another partner's. 20650 ---------------------------------------------------- 3. Stylesheet improved for viewing of CSOS documents The stylesheet used for displaying CSOS documents in the user interface has been improved to provide a better view of the payload. 20684 ------------------------------------------ 4. Parsing changed for Tradacoms documents Parsing of Tradacoms documents has been modified to behave the same way as version 4.x of the trading engine. If the code field is included in the file, the code field is used for the routing ID. If the code field is not included, the name field is used instead. 20901 -------------------------------------------------- 5. User role permission caused improper UI display Use of the "manage tasks" user role permission sometimes caused the user interface to display improperly. This issue has been resolved. 20940 -------------------------------------------- 6. Response to web service API call in error When the trading engine received a web services API call, the response returned to the user was a consistent error. This occurred when sending synchronous messages. The status returned to the client was: Failed with internal error: The PersistenceManager has been closed. This issue has been resolved so the persistence manager is not used after the code goes to a wait state. 20627 --------------------------------------------- 7. Oracle 10g users advised to use 10g driver To avoid database errors, users of Oracle 10g need to use the 10g JDBC driver. Users of 9i should not use the 10g driver, but the 9i driver. 20754 ---------------------------------------------------- 8. JMS listener continued to reconnect when disabled A disabled JMS listener integration pickup exchange continued trying to reconnect and published events to the alerts system. After time, this slowed the performance of the user interface. This has been resolved so the exchange does not try to reconnect when disabled. 20832 ----------------------------------------------- 9. User password changes reported in events log Password changed and user updated events are now reported to the events log when a user changes a password. 20449 ------------------------------------------ 10. CYC_NETWORK_NAME binding not respected The system management option in the user interface for binding the application's servers to only the IP address associated with CYC_NETWORK_NAME was not respected for uploading documents to Transaction Director. This issue has been resolved. 20580 -------------------------------------------------- 11. Profile import does not warn about certificate When adding a community profile by importing an XML file, the trading engine produced a warning message if the file did not contain a certificate and public-private key pair. Such warnings are no longer generated. 20590 ---------------------------------------------------- 12. MessageId not copied from MMD to WebService call The MessageId was not copied from the MMD into the WebService call. The result was that messages submitted using the sample WebServices client had no control of the MessageId utilized in packaged ebXML messages. This issue has been resolved. 20591 ------------------------------------------------------- 13. Web Trader wizard let users skip certificate upload If someone using the Web Trader self-registration wizard canceled the upload certificate part of the process, the wizard noted that the registration had been successfully completed. But the sponsor's system noted the registration was incomplete due to the missing certificate. The wizard has been changed to cancel the whole registration when the user cancels any part of the process. 20786 --------------------------------------------- 14. EDIFACT document type not parsed properly The trading engine was not properly parsing EDIFACT documents. The trading engine's EDIFACT parser has been changed to get the document type from the Message type component of the MESSAGE IDENTIFIER element of the first UNH segment. It was determined that getting the document type from the APPLICATION REFERENCE element of the UNB segment was wrong, as this element is meant to contain the name (or some other identification) of an application to be used to process the message; this is not the same as the document type. 20991 ------------------------------ - What's new for 5.3 ------------------------------ -------------------------------------------- 1. Primary keys added to all database tables Changes have been made to make sure all database tables have primary keys. 10471 ------------------------------------- 2. AS3 interoperability certification This version of the trading engine has been certified for EDIINT AS3 interoperability. ----------------------------------- 3. RosettaNet 1.1 and 2.0 supported Support has been added for RosettaNet Implementation Framework (RNIF) 1.1 and 2.0. -------------------------- 4. HL7 supported for ebXML Health Level 7 version 2 and 3 payloads are supported for ebXML trading. 10645 ------------------------------------- 5. Cyclone WebTrader option available Cyclone WebTrader is available as a licensed option. WebTrader is an easy way for anyone with a computer, a web browser and an Internet connection to engage in B2B commerce with other web traders or partners with sophisticated e-commerce systems. 10590 --------------------------- 6. SFTP transport supported Secure FTP (SFTP) is supported as a trading and integration transport. 11147 --------------------------------------------------------- 7. Staged HTTP transport available for receiving messages Communities can use the new staged HTTP web servlet transport to securely receive messages from partners without changing firewall configurations. ------------------------------------------ 8. User interface supports Mozilla Firefox The user interface supports using Mozilla Firefox 1.0 or later in addition to Internet Explorer 6 or later. 10909 ------------------------------------------- 9. Activator now uses Apache Derby database To enhance performance, data integrity and reliability, Activator and single-node Interchange now use the Apache Derby open source database as the default embedded database. 20295 ---------------------------- 10. System throttle enhanced An enhancement has been made to the system throttle. The throttle detects when the trading engine is overloaded and suspends consumption of new work. With the enhancement, the throttle monitors memory heap utilization. When the utilization reaches a high percentage, new messages are not accepted until the utilization drops. Previously, the throttle worked by counting messages in various processing states. In addition, the TaskScheduler's queue size is checked to determine whether the trading engine is stressed. To maintain performance, new work is suspended when the queue grows too large. 20812 --------------------------------------------------------- 11. Message Tracker performance enhanced for detail views Message Tracker performance has been enhanced to provide a faster response when clicking the details link on the search results page to view details of a document. 20795 --------------------------------------- 12. CRL checking functionality expanded Two enhancements have been made to the trading engine's ability to use certificate revocation lists to verify certificates. A certificate now can be checked against multiple CRLs from the same issuer. Also, the trading engine can download and check a certificate against the CRL named in the certificate being checked. 20698, 20697 ------------------------------------ 13. Threads tuned for Derby database In an effort to limit memory usage when running in a single VM, the TaskScheduler has been tuned to use 50 threads instead of 150 when the database is Derby. 20852 ----------------------------------------------------- 14. Windows service keeps running after user logs off The behavior of the Windows service has been changed. The service keeps running after the user whose account is running the service logs off. 21013 ------------------------------ - 5.3.1.0.12 resolved issues ------------------------------ ------------------------------------------------- 1. Threads blocked while waiting for coreId token In some cases, many or most TaskScheduler threads were blocked, waiting to for a message coreId token. The code was processing an inbound ebXML acknowledgement and attempting to set the originally produced message from the produced state to the delivered state. This issue has been resolved. 20984 ------------------------------------------------ 2. Trading engine did not recognize LDAP for ARL When a certificate's distribution point specified a LDAP location for an authority revocation list, the trading engine erroneously presumed it was a certificate revocation list. An ARL is like a CRL, only an ARL includes invalid intermediate CA certificates. This issue has been resolved so the trading engine can distinguish between a LDAP location for a CRL versus an ARL. This issue mostly affected users of CSOS functionality. 21012 ------------------------------ - 5.3.1.0.11 resolved issue ------------------------------ ---------------------------------------------------- 1. Unavailable TaskScheduler threads caused deadlock When running in single VM mode, the trading engine could deadlock when all the TaskScheduler threads were exhausted. This happened when a TaskScheduler thread sent a ClusterBus message and requested a response because there was not a TaskScheduler thread to execute the message and return the response. This caused the sender to wait forever. This issue has been resolved. 20937 ------------------------------ - 5.3.1.0.9 resolved issue ------------------------------ ------------------------------------------------ 1. Message resends sometimes caused an exception When a message resend was initiated, the trading engine sometimes generated an OptimisticVerificationException. This issue has been resolved. 20848 ------------------------------ - 5.3.1.0.8 resolved issue ------------------------------ ---------------------------------------------- 1. Random NullPointerException due to deadlock The events LogFileRouter randomly got a NullPointerException when trying to query a message from the database. This was being caused by some type of deadlock reading the message from the database. A retry has been implemented, so that a retry will occur a maximum of three times to get the message. For each retry a WARN event is generated, stating the coreID of the retry. 20849 ------------------------------ - 5.3.1.0.7 resolved issues ------------------------------ ---------------------------------------------------- 1. CSOS, WebTrader Java version discrepancy resolved This issue affected users of the document signing functionality for CSOS or WebTrader. FIPS validation for the Entrust Authority Security Toolkit is supported for Java version 7.0, but not 7.1. Consequently, version 7.0 is used. 20718 ------------------------------------- 2. Message purge impacted performance When SQL Server was the external database, a message purge operation took too long and used too much system resources. This issue has been resolved. 20828 --------------------------------------------------- 3. Client authentication error generated by mistake When using an HTTPS delivery exchange with client authentication turned off, the trading engine generated an error for each HTTPS connection that did not provide an SSL certificate. This condition was not an error because an SSL authentication certificate was not requested and trading was not affected. The error event no longer is generated. 20232 ------------------------------ - 5.3.1.0.6 resolved issues ------------------------------ ----------------------------------------------------------- 1. Untimely receipt for ebXML message marked as "delivered" If the trading engine designated an outbound ebXML message as "failed" for lack of receiving a receipt, but a receipt was received after the message was marked as failed, the receipt became stuck in process until the server was restarted. This has been resolved by marking such an untimely receipt as "delivered," but without associating it to the failed message. 20655 -------------------------------------------------------- 2. New utility assures correct names for Windows service On Windows, the installer sometimes wrote incorrect network information in the CycloneService.ini file, which is used to run the server as a Windows service. This occurred when the "short" network name could not be derived by removing the domain suffix from the fully qualified name. This has been resolved with a new utility named netConfig, which automatically manages the contents of the CycloneService.ini file, as well as the _environment.cmd script that is used when the trading engine is run from a command prompt. For earlier versions, the work-around is to manually set the correct values in CycloneService.ini for your network. 20677 ------------------------------------------------------ 3. Installer forces Derby database settings in upgrade When upgrading from an Activator that uses the embedded Sybase database to a version 5.3.1 Activator that uses the embedded Derby database, the Sybase connection settings were carried forward. This has been resolved so the installer forces the correct Derby connection values in the datastoreconfig.xml file. 20678 ------------------------------ - 5.3.1.0.5 resolved issues ------------------------------ ---------------------------------------------- 1. Corruption of Derby database during upgrade Upgrading from an Activator with a Sybase database to an Activator with a Derby database resulted in corruption of the Derby database. This issue has been resolved. 20554 --------------------------------------------------- 2. Unicode format slowed performance for SQL Server When SQL Server was used as the database, overall system performance was slowed as a result of string values being sent by the JDBC driver to SQL Server in Unicode format. This has been resolved by turning off sending of string parameters as Unicode for SQL Server in the datastoreconfig.xml file. 20571 ------------------------------ - 5.3.1.0.2 resolved issues ------------------------------ --------------------------------------------------- 1. CollaborationRole not resolved for inbound ebXML The trading engine could not resolve the correct CollaborationRole for inbound ebXML messages when using CPAs with multiple CollaborationRoles with the same name. This issue has been resolved. 11215 ----------------------------------------------------------- 2. ebXML payloads did not always obey duplicate elimination When an ebXML MMD with two payloads was traded, and duplicate elimination was set to true, one payload was ignored (as it should be) but the second payload overwrote the original. This has been resolved so all duplicate payloads are ignored when duplicate elimination is true. 11512 ----------------------------------------------------- 3. Produce version 4 message IDs for interoperability This version of the trading engine can be configured to generate message IDs like those produced by version 4 of the trading engine. The following explains how to accomplish this, making this version interoperable with version 4. We recommend against doing this unless necessary. A version 4 message ID has the following format: <#senderid#controlid#uniqueid#@hostname> Where: senderid is the sender primary ID controlid is the tracking information control ID uniqueid is the tracking information unique ID hostname is the hostname of the sender system To enable version 4 message IDs, configure an inline processing action in the sending community's message handler. Use the following class name: com.cyclonecommerce.custom.inlineprocessing. SetCi4StyleMessageId Do not specify any parameters. Define the operator and value to limit invocation of the action to the minimal set of messages. For example, if version 4 message IDs are required by a single trading partner, set up the operator and value to invoke the action for that single partner. Do not have the action invoked for all messages. 20122 --------------------------------------------- 4. Activator could not process CSOS documents Activator could not process CSOS documents. This issue has been resolved. 20258 ---------------------------------------------------- 5. ebXML self-register message erroneously displayed After importing a partner's ebXML CPA a message saying an ebXML partner had self-registered erroneously displayed on the home page of the user interface. This issue has been resolved. 20231 ---------------------------------------------------- 6. Database configuration tool displays correct port When using the database configuration tool (dbConfig in the bin directory) and a port number other than the default was saved, the tool's user interface would not display the port. This has been resolved so the tool displays the saved port number. 20119 ------------------------------------------------------- 7. EDIFACT with long version number could not be parsed The trading engine could not parse an EDIFACT file with a long version number. This issue has been resolved. 20109 ------------------------------------------------ 8. Alerts related to old exchange points deleted Alerts related to exchange points would display erroneously in the user interface after the exchange points had been deleted. This has been resolved so that alerts related to deleted exchange points also are deleted. 11260 ---------------------------------------------------- 9. Registration wizard checks for duplicate name, ID The partner self-registration wizard has been enhanced to display warning messages if a user tries to select a duplicate partner name or user ID. 20339 --------------------------------------------------------- 10. Home page message links to new partner's summary page After a partner registered using the registration wizard, a message appeared on the sponsor's home page, but did not link to the proper page for the sponsor to associate the partner with a community. This has been resolved to link the message to the new partner's summary page. 20375 ---------------------------------------------------- 11. Sponsor community prompted to act on new partner The partner self-registration wizard has been enhanced so prompts display on the new partner's summary page. These advise the sponsor community to approve the partner's registration or trust a certificate for SSL authentication or both. Approving a partner's registration makes the partner a member of the sponsor's community. 20371 ------------------------------------------------------- 12. ebXML message could not resubmit to JMS integration An inbound ebXML message that failed to send to integration via a JMS queue could not be resubmitted to integration. This issue has been resolved. 20432 ------------------------------------------------- 13. Machine names in Windows service file changed Values for machine names in the file that controls the Windows service, CycloneService.ini in the bin directory, have been corrected to match those in the startServer file. 20437 -------------------------------------- 14. 2 node license only allowed 1 node When a user license allowed only one processing node each for the trading engine and Transaction Director, only a single node could be added for one or the other application. This has been resolved so one node can added for each application. 20477 ----------------------------------------------- 15. HTTPS information in CPA template not saved When an ebXML partner used the self-registration wizard, the HTTPS transport information in the CPA template was not saved when the community sponsor imported the CPA to add the new partner profile. This issue has been resolved. 20363 ------------------------------------------------- 16. EbxmlProtocolReceiver meta-data are being set The ebXML meta-data DuplicateElimination, AckRequested and AckSignatureRequested are being set in EbxmlProtocolReceiver. 10481 -------------------------------------------------- 17. Leading, trailing spaces in fields not allowed The user interface has been modified so that leading and trailing spaces in fields are not saved. This corrects an issue in which saved leading or trailing spaces interfered with making changes to fields. 20474 ------------------------------------------------------ 18. Restart not needed to change client authentication When the trading engine was running and a user turned client authentication on or off for an embedded HTTPS server, the change did not take effect until the next time the trading engine was restarted. This has been resolved so restarting is not necessary. 20185 ------------------------------------------------------- 19. Web trader partner self registration triggers event An event is generated when a web trader partner self registers and awaits a sponsor's approval. The event is: Administration.Configuration.Party.PartnerSelfRegistered. 20336 -------------------------------------------------- 20. Could not import certificate with certain data The trading engine could not import a certificate file that contained the following certificate data: Authority Key Identifier and Subject Key Identifier. This issue has been resolved. 20170 ---------------------------------------------------- 21. Server warns when duplicate routing ID attempted If a user tried to add a duplicate routing ID, the trading engine would not allow this, but did not inform the user. Now the server generates a warning message to inform the user a duplicate was attempted. 20308 ------------------------------ - 5.3.0.0.1 resolved issues ------------------------------ --------------------------- 1. Activator upgrade failed When upgrading from an earlier to a later version of Activator, the Sybase database did not update properly and the upgrade failed. This issue has been resolved. 10936 --------------------------------------------------------- 2. Changes reduce possible time synchronization conflicts Changes have been made to reduce the small possibility of time synchronization conflicts occurring when starting multiple nodes at the same time on multiple computers in a cluster. 10761 ------------------------------------------------------ 3. UNIX startServer script checks for existing process The startServer script for UNIX was overwriting an existing PID file without first checking whether the existing process was running. The script has been modified to test whether the server already is running before trying to start it again. If the server is running, the startServer script generates an appropriate message and exits. 11180, 11182 ------------------------------------------------------ 4. Secure file HTTP or HTTPS in profile did not import When the trading engine imported a partner profile containing a secure file message protocol HTTP or HTTPS transport, the transport configuration was not imported. This issue has been resolved. 11102 -------------------------------------------- 5. Base 64 encoding available for RosettaNet The collaboration settings page in the user interface now have base 64 encoding options for RosettaNet 1.1 and 2.0 outbound messages. 10924 ------------------------------------------------------- 6. Deleting AS2 embedded HTTP exchange caused exception Deleting an AS2 delivery exchange that used a community- level HTTP embedded server caused a null pointer exception. This issue has been resolved. 10698 -------------------------------------------------------- 7. Tracker sometimes displayed wrong status for messages Tracker sometimes erroneously displayed messages as "in process" or "waiting for receipt." This issue has been resolved. 10546 ------------------------------------------------ 8. Trading engine had trouble with NFS fail over The trading engine had trouble handling a fail over of one Network File System on one server to a NFS on a different server while trading was in progress. This issue has been resolved. The trading engine can handle fail over on hard- and soft-mounted NFS, but hard-mounted NFS is recommended. See http://rogue/cgi-bin/wikiES?NfsBestPractices for tips on using NFS. 10552 ---------------------------------------------- 9. "More tasks" link on home page did not work The "more tasks" link on the user interface home page did not link to a page that displayed more pending tasks. This issue has been resolved. 10731 ------------------------------------ 10. Windows service sometimes failed The Windows service running the trading engine sometimes stopped. This issue has been resolved. 10774 ------------------------------------------------------ 11. FTP did not notify when message repeatedly pick up When the FTP account the trading engine used to pick up a message did not have permissions to delete a file, the server repeatedly picked up the same message, but did not generate an alert that this was happening. The server now will generate an alert in such cases. 11314 ----------------------------------------------------------- 12. Message events can be forwarded selectively to Director When the trading engine integrates with Transaction Director, you can select the specific events to forward to Transaction Director. This is controlled in the Transaction Director user interface on the page titled "Configure integration between trading engine and transaction lifecycle management." 11294 -------------------------------------------------------- 13. Message no longer stuck in waiting for receipt state If the reliable messaging setting for resend attempts was 0, a message became stuck in the "waiting for receipt" state. This has been changed so if resend attempts is 0, the message rejects if an acknowledgment is not received before the resend interval elapses. 11527 -------------------------------------------------------- 14. Resubmitted messages showed incorrectly on home page Resubmitted messages sometimes displayed erroneously as "in process" on the user interface home page, but displayed correctly in Tracker. This issue has been resolved. 10537 --------------------------------------------- 15. Primary keys added to all database tables Modifications have been performed to make sure all database tables have primary keys and indexes. 10470, 10194, 10195, 10198 ------------------------------------------------------ 16. MQSeries characters set field expanded to 4 digits The characters set field for the MQSeries transport in the user interface has been expanded from 3 to 4 characters to allow entry of 4-digit characters set numbers. 10934 -------------------------------------------- 17. Wrong CPA could be used in ebXML trading For ebXML trading, if a community had more than one CPA for one community-partner pair, the wrong CPA could be used. This issue has been resolved. 10984 ---------------------------------------------------- 18. Messages that cannot be resubmitted are rejected If a document is queued for resubmitting, but does not qualify for resubmission (for example, there is no backup file), the resubmit will be rejected with a reason explaining the rejection. 10998 ------------------------------ 19. Events log files roll over Events log files were not rolling over to new files as intended upon reaching maximum size. This issue has been resolved. 11114 -------------------------------------- 20. Pick party wizard in Tracker fixed The pick party wizard in Message Tracker was not working properly. This issue has been resolved. 20160 ------------------------------ - What's new for 5.2 ------------------------------ -------------------------------- 1. Integration based on criteria The trading engine can pickup or deliver messages from back-end integration via exchanges that segregate messages according to user-defined criteria. For example, messages can be picked up from file system directories based on document type (EDI, XML or binary). Inbound messages can be routed to different integration file system directories based on MIME content type. Criteria-based integration is supported for all transports in addition to file system. -------------------------------------------------------- 2. File system directories names supply meta-data values A back-end file system directory hierarchy can supply values for meta-data such as sender and receiver IDs for outbound messages. This is especially useful for binary messages. For example, the integration directory path Community1\Partner A can be mapped to the meta-data elements sender ID and receiver ID, respectively. ------------------------------------- 3. Software Development Kit available The optional Software Development Kit for exploiting extensibility though APIs debuts with this release. Supported APIs are in-line processing, pluggable transports and startup services. More APIs are planned in future releases. The SDK package includes user documentation, Javadocs, sample code, support hours and training. The SDK is available with certain products for an additional cost. Your account representative can tell you more. --------------------------------------------------- 4. JMS message retrieval eliminates polling latency The trading engine now can retrieve messages from a JMS server as messages are ready without waiting for a polling interval. This eliminates latency in messages handled via JMS. A polling option is still available. ------------------------------ 5. Support for JMS TextMessage The TextMessage type is supported in addition to BytesMessage for sending and receiving via JMS. --------------------------- 6. Message Tracker enhanced The following enhancements have been made to Message Tracker: a. Queries involving many records that used to take 60 or more seconds now take 1-2 seconds on certain hardware. b. Real-time message status is displayed. As query results are paged, message status is updated. However, messages that entered the system after the query was executed are not displayed unless the user clicks Find again. c. Multiple messages can be resubmitted at once. d. Receipts and messages with parent-child relationships can be filtered out of search results. e. The following meta-data are displayable: a payload's delivery exchange; ebXML meta-data such as Role, Service, Action, Conversation Id, CPA Id; Integration ID for events. f. Parent-child relationships display consistently. When an MMD with multiple payloads is picked up from integration, a separate line displays for each payload plus the MMD and correct links. This view is consistent for the ebXML and e- mail protocols. g. More Save buttons were added for convenience. h. User-defined queries are flagged with asterisks to distinguish them from built-in queries in the toolbar menu. ----------------------------------------------------- 7. Trading engine events can be sent as e-mail alerts Trading engine events can be sent as alerts to e-mail recipients. A pre-defined set of events that includes transport, configuration and fatal errors can be sent via e-mail. The type and number of events for e-mail alerts is configurable. ------------------------------------- 8. Re-routing of messages made easier Re-routing of messages has been made easier. In addition, Message Tracker clearly marks re-routed messages and messages where the routing ID in the payload is different than in the packaging. To re-route messages, a community must enable re-routing and configure the trading pickup exchange to parse for the receiver's ID in the payload. Re-routing binary payloads still requires Cyclone endpoints in order to pass the appropriate meta-data. ----------------------------------------- 9. AS2 URL for receipts can be superseded You can override the AS2 URL for receipts and use the partner's transport instead. This is useful when the URL in the AS2 header "Receipt-Delivery-Option" in the original message is not valid. ---------------------------------- 10. New backup directory structure Message backup files are now kept in subdirectories by month, day and hour. This prevents a directory from containing too many files and slowing down the file system at high traffic or high retention times. ------------------------------------------- 11. Default message delete settings changed A default message retention time of 45 days has been instituted. Older messages are deleted. You can change this to suit your needs. Previously, the default was not to delete messages, which could inadvertently fill up or affect database performance. -------------------------------------- 12. Bundled SMTP address can be edited The email address is dynamically generated upon adding a bundled SMTP exchange, but it can be edited later on the transport's maintenance page. ----------------------------------------- 13. Self-registration or provisioning API An API to enable Cyclone Professional Services to offer endpoint self-registration or provisioning has been added. Contact Cyclone Professional Services for details on this offering. ------------------------------------- 14. Activator RAM requirement lowered Activator has been tuned to run on computers with 256 MB RAM. This is down from 512. ----------------------------------------------------- 15. Easier setup of additional computers in a cluster When the startServer script is run on a computer for the first time, the configuration script for that machine is run automatically. -------------------------------------------------- 16. Installer uses preferred temporary directories After installation, the temp directory variables point to the temp directory for the platform: Linux: /tmp/cyclone Solaris: /var/tmp/cyclone Windows: C:\Documents and Settings\\Local Settings\Temp\cyclone. ------------------------------ - 5.2.0.0.20 resolved issue ------------------------------ -------------------------------------------- 1. Activator forced to run in single VM mode If an Activator trading engine was started on the same computer that was already running an Interchange trading engine, this used up all CPU resources and resulted in one of the trading engines shutting down. This has been resolved by forcing Activator to run in a single virtual machine mode, as it should. 11490 ------------------------------ - 5.2.0.0.18 resolved issue ------------------------------ --------------------------------------------------- 1. Modify Packaging to generate V4 style MessageIds Changes have been made to allow the trading engine to generate secure file MessageIDs like those generated by version 4 of the trading engine. This can be enabled by setting ASxUseCI4StyleMessageId=true in [install directory]/[build number]/conf/tuning.properties. 11464 ------------------------------ - 5.2.0.0.17 resolved issue ------------------------------ ------------------------------------------------------ 1. Database resources not released in web services API Database resources were not being freed when connections were made through the web services API. The connections were consumed until the JDBC connection pool was exhausted and the system restarted. This issue has been resolved. 11437 ------------------------------ - 5.2.0.0.16 resolved issue ------------------------------ ------------------------------------------------------- 1. Command-line tool unlocks documents stuck in-process A command-line tool has been developed to unlock documents that become stuck in an in-process state. The tool changes the status of such documents to failed. The tool is named rejectInprocessMessages and is in the application's tools directory. This tool should be used only on advice of technical support and only after nodes have been stopped. 11409 ------------------------------ - 5.2.0.0.15 resolved issues ------------------------------ ---------------------------------- 1. Could not send via HTTPS on AIX When installed on a computer with an AIX operating system, the trading engine could not send messages via HTTPS. This issue has been resolved. 11287 ----------------------------------------------------- 2. Receipts erroneously identified duplicate messages Receipts received for successfully sent ebXML messages erroneously identified the sent messages as duplicates. This issue has been resolved. 11371 ------------------------------------------ 3. Some documents became locked in-process Documents sometimes became locked in an in-process state. The trading engine has been modified to resolve this occasional issue. 11382 ------------------------------ - 5.2.0.0.14 resolved issues ------------------------------ ------------------------------------------------- 1. Rejected events were not forwarded to Director The trading engine did not forward rejected document events to Transaction Director. This issue has been resolved. This applied only in cases where a single user license supported both the trading engine and Transaction Director. 11227 ----------------------------------------------------- 2. Nodes did not restart after database was restarted Processing nodes failed to restart after an external database was restarted. This issue has been resolved. 11258 ------------------------------------------------ 3. Some users could not log on to user interface Trading engine users who used the Sybase database sometimes could not log on to the user interface after previously logging on successfully with the same user name and password. This issue has been resolved. 11270 ----------------------------------------------- 4. HTTP user name, password not in ebXML header The trading engine did not include the user name and password for the HTTP server in the header of outbound ebXML messages. This issue has been resolved. 11291 ------------------------------ - 5.2.0.0.12 resolved issues ------------------------------ ----------------------------- 1. Message rejection resolved The trading engine continuously rejected messages upon starting the server. This issue, which was occurring in isolated instances, has been resolved. 11216 -------------------------------------------- 2. Multiple SOAP declarations in same header The trading engine was packaging and sending ebXML messages with more than one header entry for xmlns:soap, when only one was needed. This issue has been resolved. 11218 ------------------------------ - 5.2.0.0.11 resolved issues ------------------------------ ------------------------------------------------- 1. Role permissions adjusted for message searches Users assigned to roles with limited permissions could not use the pick party wizard to search for records of traded messages. This has been resolved by enabling roles with either of the following permissions to use the wizard: "search for messages processed by the trading engine" or "view trading configuration." 10466 ----------------------------------------------------------- 2. E-mail alert configuration caused null pointer exception When e-mail alerts were activated, null pointer exceptions were written to the log file. This issue has been resolved. 10983 ------------------------------------------------ 3. P12 certificate files could not import on AIX When running on an AIX operating system, the trading engine could not import p12 certificate files. This issue has been resolved. 11041 ------------------------------------------------------ 4. FTP client sending adjusted to accommodate firewall Some firewalls dropped FTP client connections from the trading engine after the USER command was sent but then erroneously concluded the client had not also sent CRLF (carriage return following by line feed). This is because the client was sending the CRLF in a separate write operation. The behavior has been adjusted so the client sends the USER command and CRLF in a single write operation. 11043 ------------------------ 5. JMS memory leak fixed A memory leak related to use of the JMS transport that caused trading to fail has been resolved. This resolution affects users who employ WebLogic as the JMS provider. Such users should use WebLogic 8.1 SP3 or later. 11057 ------------------------------------------------ 6. Settings not saved for fixed from, to address On the "from address" and "to address" tabs of integration pickup exchanges, user settings for "always use the following address" did not save. This issue has been resolved. 11090 ---------------------------------------------------- 7. Incorrect XML MIME type used for inbound exchange When the default method was used to add file system integration exchanges, the content MIME type was incorrect for the XML inbound exchange, resulting in XML documents being routed to the designated default exchange. This has been resolved by using the correct MIME type of "application/XML". 11091 ------------------------------ - 5.2.0.0.7 resolved issue ------------------------------ ---------------------------------------- 1. Database table affected after upgrade Upgrading the trading engine from version 5.1 could result in data loss in the ExchangePointSecurity database table, causing operational issues in the user interface. This issue has been resolved. 10667 ------------------------------ - 5.2.0.0.6 resolved issues ------------------------------ ------------------------------------------------------ 1. Nodes may not restart after server restarted itself When the server stopped due to loss of database connectivity and then restarted itself to restore connectivity, nodes sometimes did not also restart. This issue has been resolved. 10710 -------------------------------- 2. Nodes sometimes started twice Frequently, when a multi-host cluster was attempting to restart following a database failure, nodes were being restarted twice, once by the executive node and once by the respective control nodes. This issue has been resolved so that each node only starts once. 10735 ------------------------------ - 5.2.0.0.5 resolved issues ------------------------------ -------------------------------------------------- 1. Profile export-import deleted community profile A community profile exported as a party profile and then imported on the same server as a partner failed to import, which was correct behavior, but resulted in the original community profile being deleted. This issue has been resolved. 10611 ------------------------------------------------------ 2. Deleting, adding partner could disrupt resend tries The process for resending messages to partners could be disrupted in the following case: A community sent a message to a partner, and a user deleted the partner profile before the trading engine received a receipt for the message, but immediately added back an identical partner profile. This has been resolved so the resending process continues although the partner profile is deleted and added back. 10640 ------------------------------------------------ 3. Server would stop if database connection lost If database connectivity was lost, the trading engine server shut down. This has been resolved so that if connectivity is lost, the server restarts itself and tries to re-establish the connection. The server will restart repeatedly until connectivity is restored. Any data in process is rolled back and no data is lost. 10681 ------------------------------ - 5.2.0.0.4 resolved issues ------------------------------ ------------------------------------------------- 1. Using MQSeries required downloading a JAR file Using MQSeries as a transport used to require downloading a JAR file from IBM and copying it to the system's corelib directory. The file, com.ibm.mq.jar, now is included in the corelib directory upon installation and no longer must be downloaded. 9180, 10609 ----------------------------------------------------------- 2. Repeated "save" actions could spawn duplicate rule trees When changes to exchange points were saved, it was possible for multiple updated CollaborationRules or ActionRules trees to appear in the database. This could happen when the "Save" or "Finish" button was clicked repeatedly when making exchange point changes. The result was a fatal error the next time a duplicate tree was reloaded or the next time the server was started. This issue has been resolved. 10604 ------------------------------ - 5.2.0.0.3 resolved issues ------------------------------ ------------------------------------------ 1. Second node failed to poll for messages In instances where a second JVM node was started on a second host, the later node, though running, did not poll for messages. This issue has been resolved. 10563 ----------------------------------- 2. StringIndexOutOfBoundsExceptions In some cases, StringIndexOutOfBoundsExceptions were generated in the control node log every 5 minutes, 5 seconds. This issue has been resolved. 10570 ------------------------------ - 5.2.0.0.2 resolved issue ------------------------------ --------------------------------------------- 1. Document Generator would not start on UNIX On UNIX the Document Generator utility would not start when the full path to the script in the bin directory was specified instead of changing to the bin directory before running the command. This issue has been resolved. 10548 ------------------------------ - 5.2.0.0.1 resolved issues ------------------------------ ------------------------------ 1. Receipts appear to resubmit Although the user interface appeared to allow receipts to be resubmitted in the message tracker, receipts cannot be resubmitted and the system ignores such requests. This has been resolved so there is no longer an appearance in the UI of resubmitting receipts. 9446 ------------------------------------------------- 2. Importing profile affected preferred transport When importing a partner profile that was exported from an earlier version and that contained multiple transports for sending messages, the preferred transport might not become the default for sending. This issue has been resolved. 9685 -------------------------------------------------------- 3. Routing inbound messages by document type was limited The trading engine could route inbound messages by document type (EDI, XML, binary) to file system integration only with a post-processing script. A new feature allows messages to be routed to integration with user-defined criteria set at exchange points. This lets you set integration delivery by document type. 9729 ------------------------------------------- 4. Large data volume slowed message tracker Message tracker performed slowly when large amounts of data are in the system (200,000 or more records). This has been resolved with a package of performance enhancements. 9730 ------------------------------------------------------- 5. Community profiles sometimes did not export properly Community profiles sometimes did not export properly as a partner profile. When this occurred, a partner could not import the profile file. This issue has been resolved. 9802, 9803 ------------------------------------------------- 6. "Delete all" button did not purge all messages The button for "delete all messages" in message tracker did not delete all final state messages. Instead, the trading engine only deleted messages that fit the age criterion on the "Schedule for deleting trading engine messages" page. This issue has been resolved. Final state messages include those that have been delivered or rejected, but not those that are in process. 10224 --------------------------------------------------- 7. Mismatch between MMD, CPA not clearly identified If a mismatch occurred between the role values in an ebXML message meta-data document and a CPA, the trading engine generated an error message that did not clearly identify the issue. This issue has been resolved. 10102 ------------------------------------ 8. Only first ebXML payload rejected If an outbound ebXML message with multiple payloads failed, only the first payload was rejected and the other payloads became stuck in process. Message tracker reported the rejected payload as failed and the others as in process. This issue has been resolved. 10011 --------------------------- 9. Windows service repaired The Windows service to run the trading engine as a background process was not working. This issue has been resolved. 10170 ------------------------------------------------ 10. Database tables lacked primary keys, indexes A number of database tables were missing primary keys and indexes. This issue has been resolved. 10196, 10197, 10462 ------------------------------------------------ 11. Implementing upgrade logic resolves UI issue Users upgrading from a version earlier than build 774 could not use the user interface. This was resolved by implementing logic to update the existing database during an upgrade. 10506 ------------------------------------------------ 12. Database port entry corrected during upgrade During a upgrade when a user chose in the installer to use the existing database in the new version, all database connection information was recorded correctly in the new datastoreconfig.xml file, except the default port. This issue has been resolved. 10507 ----------------------------------------------------------- 13. Trading engine could not handle multiple SMTP responses The trading engine's SMTP client could not correctly handle multiple SMTP responses. This issue has been resolved. 10508 ---------------------------------------------------- 14. Receipt of duplicate ebXML messages was possible In ebXML trading, DuplicateElimination was not working in some cases for all message protocols. Two duplicate messages that arrived at the same time or nearly the same time could both pass duplicate elimination checks. This issue has been resolved. 10518 ------------------------------------------------- 15. Oracle database did not update during upgrade Oracle databases did not update properly when upgrading to a newer version of the trading engine. This issue has been resolved. 10521 -------------------------------------- 16. Optimistic lock exception resolved An optimistic lock exception occurred while deleting one or more rows from the ActiveExchangePoints database table. Optimistic locking no longer is done on the ActiveExchangePoints and ExchangePointUsers tables. These tables do not need optimistic locking, as rows in them are only written and deleted, but never updated. 10525 ----------------- End release notes -----------------