------------------------------------------- Release notes for TPI Server 4.1.2 ------------------------------------------- The following information supplements the user documentation. Contents -------- 1. Required and recommended operating system patches 2. Tuning capability 3. Changing ports for bundled e-mail 4. FTP servers that use DNS service, CP.Net 5. Supported transports for ebXML and RosettaNet 6. Zeros in local IP address 7. MDNs with multi_mdn extension are not archived 8. Temp directory created on FTP server 9. RC_MDN_OPTIONS database field no longer populated 10. Do not delete "md" files in archive directory 11. Do not use quotes in company name during installation 12. InterchangeURL and InterchangeHttpsURL not populated 13. Network down interrupts processing 14. Large XML documents require more memory 15. Company name not in CompanyID object 16. Changing CRL information requires server re-start 17. HTTPS Client uses most recent valid certificate 18. Internet Explorer 4.0.1 or later required on Windows 19. CI 3.0.5 has hard-coded ports for Bundled Email 20. Adding partner profiles via client may crash the AIX TPI server 21. 4.1.2 resolved issues 22. 4.1 resolved issues Note: If you are a 4.1 user who is upgrading to 4.1.2 by installing the 4.1.2 JAR file, see the following procedure. Installing the 4.1.2 JAR file ----------------------------- The following are the steps for installing the JAR file for implementing this release for a previously installed application. This procedure is not applicable for a new installation of the application. Step 1. Close all system applications, including the Server application, Administrator, Tracker and Document Generator. Step 2. Rename the cyclone.jar file in the application's lib directory. For example, cyclone.jar_[old version number]. You must rename the cyclone.jar file on the computer running the Server application as well as all computers running client applications. Step 3. Copy the new cyclone.jar file to the lib directory of all server and client computers. Step 4. Restart the Server application. ---------------------------------------------------- 1. Required and recommended operating system patches ---------------------------------------------------- Patches for the following operating systems are recommended or required before installing: IBM AIX 4.3.3 Hewlett-Packard HP-UX 11.0 Sun Solaris 7 and 8 IBM OS/400 4.4 1.a. IBM AIX 4.3.3 ------------------ Java 1.3.0 AIX version 4.3.3 LPP Name Java_dev2 Installation directory /usr/java_dev2 Latest update PTF 7 IY12075 (ca130-20001124) 1.b. Hewlett-Packard HP-UX 11.0 ------------------------------- PHCO_19666 PHCO_22314 PHKL_18543 PHKL_20016 PHKL_22589 PHSS_17535 PHSS_21982 PHSS_22341 PHSS_21959 PHNE_22086 PHSS_20863 1.c. Sun Solaris 7 and 8 ------------------------ Version Patch ID Note Description ---------------------------------------------------------- 7 (5.7) 106980-10 required Libthread Patch 7 (5.7) 107636-03 required X Input & Output Method Patch 7 (5.7) 108376-07 required 1,2 OpenWindows 3.6.1 Xsun Patch 7 (5.7) 107153-01 required 1 Replaces bad font in zh.GBK locale 7 (5.7) 106541-11 required Kernel update 7 (5.7) 107544-03 required To be used with Kernel update patch 7 (5.7) 109104-01 required To be used with Kernel update patch 7 (5.7) 106950-09 required Linker Patch 7 (5.7) 106327-08 required Shared library patch for C++ 7 (5.7) 106300-09 required Patch for C++ 7 (5.7) 107081-20 required Motif 1.2 and Motif 2.1 patch 8 (5.8) 108940-07 required Motif 2.1 patch – available soon from SunSolve NOTES: 1 This patch is required in Asian locales. 2 Required for running Java Compatibility Kit tests It is recommended that the Libthread patch be applied last. 1.d. IBM OS/400 4.4 ------------------- Version: V4R4 PTF level: C9229440 or higher Group PTF#: SF99067-04 or higher 5769JV1 option 3 contained in PTF 5769JV1 SF55645 -------------------- 2. Tuning capability -------------------- In addition to the document tuning capabilities available on the Company Profile Tuning tab, values in the vm.properties file in the installation directory can be adjusted to affect application performance. We recommend that you first contact technical support before changing values in this file. We also recommend that you make a copy of the file for backup purposes before making any changes. For example, you can name the copy vm.properties.original. ------------------------------------ 3. Changing ports for bundled e-mail ------------------------------------ The bundled e-mail transports do not re-start when the bundled e-mail server ports are changed on the Ports tab in Tools > Preferences in Administrator. Make sure values are present in the port fields and re-start the server application. ------------------------------------------- 4. FTP servers that use DNS service, CP.Net ------------------------------------------- If you use an FTP transport that uses a DNS service to resolve server names, we recommended adding the following statements to the start server batch file, ini file or start-up script: For JVM 1.2: Djava.net.namelookup.cache=0 For JVM 1.3: Dsun.net.inetaddr.ttl=1 These settings force Java to look up the server name again for each call to the FTP server. ------------------------------------------------ 5. Supported transports for ebXML and RosettaNet ------------------------------------------------ The XML business protocols RosettaNet and ebXML are supported on the following transports: RNIF 1.1 Bundled HTTP Bundled HTTPS RNIF 2.0 Bundled HTTP Bundled HTTPS Bundled e-mail Standard e-mail ebXML 1.0 Bundled HTTP Bundled HTTPS Bundled e-mail Standard e-mail ---------------------------- 6. Zeros in local IP address ---------------------------- In the server.log file, the local IP address appears as zeros. For example: 08:47:30.904 EVENT Started SocketListener on 0.0.0.0/0.0.0.0:4080 08:47:30.904 EVENT Stopped SocketListener on 0.0.0.0/0.0.0.0:4080 ------------------------------------------------- 7. MDNs with multi_mdn extension are not archived ------------------------------------------------- When you receive from a version 3.0.x partner an MDN that acknowledges two or more documents that you sent, the MDN has an extension of multi_mdn. Although such MDNs are processed normally, version 4.1 does not archive them. You must manually delete MDNs with extensions of mutli_MDN that are in the backup directory. --------------------------------------- 8. Temp directory created on FTP server --------------------------------------- The application creates a temp directory on the FTP server when polling the server for inbound documents. The application does this to make sure inbound documents are retrieved properly. ---------------------------------------------------- 9. RC_MDN_OPTIONS database field no longer populated ---------------------------------------------------- The RC_MDN_OPTIONS field in the INBOUNDS_RECORDS table is no longer populated. This field was being populated with MDN options that looked like: singed-receipt- protocol=option,pkcs7-signature;signed-receipt-micalg- optional,sha1. ------------------------------------------------- 10. Do not delete "md" files in archive directory ------------------------------------------------- Do not manually delete files that begin with "md" in the archive directory. Deleting such files can result in errors when reprocessing documents. These files are associated with conversations in trading using message control documents (MCDs). To delete files in the archive directory, use File > Clear All Archive Logs in Tracker. --------------------------------------------------------- 11. Do not use quotes in company name during installation --------------------------------------------------------- Do not use quotes in the company name during the software installation process. This causes a fatal exception during installation. -------------------------------------------------------- 12. InterchangeURL and InterchangeHttpsURL not populated -------------------------------------------------------- The InterchangeURL and InterchangeHttpsURL are not populated in the document that is attached to the event sent to API event listeners. These values should be populated. This forces the API user to use a document listener. Note that the values are populated in the documentReceived call. -------------------------------------- 13. Network down interrupts processing -------------------------------------- The following message signals a normal network-down issue: SSL Failurejava.io.IOException: Broken pipe. If this occurs during document processing, the trading engine server will re-send any affected documents using the application's re- send rules when the network recovers. See resolved issue 4443. ------------------------------------------- 14. Large XML documents require more memory ------------------------------------------- You might have to increase the memory on the computer that runs the server application if you trade XML files larger than 100 megabytes. Processing such a large file can cause the packaging thread to pause and not be released. This situation is caused by a lack of resources. ---------------------------------------- 15. Company name not in CompanyID object ---------------------------------------- The company name does not appear in the CompanyId object for the sender in the MDNReceived Event for MCDs that were sent using secondary IDs only. It appears as null. ----------------------------------------------------- 16. Changing CRL information requires server re-start ----------------------------------------------------- If you change the polling information for a certificate revocation list (CRL) in Administrator, re-start the Server application for the change to take effect. --------------------------------------------------- 17. HTTPS Client uses most recent valid certificate --------------------------------------------------- When sending documents, the company's most recent valid certificate is sent to the partner's HTTPS server for authentication. If authentication fails, try deleting all the valid certificates from the company. If there are no valid certificates, then the company's active certificate will be used. -------------------------------------------------------- 18. Internet Explorer 4.0.1 or later required on Windows -------------------------------------------------------- Microsoft Internet Explorer 4.0.1 or later must be installed on a Windows computer before installing the application. The application installation process uses IE scripts to create program shortcuts. --------------------------------------------------- 19. CI 3.0.5 has hard-coded ports for Bundled Email --------------------------------------------------- If you are trading with a partner that is using 3.0.5, you will need to configure CI 4.1 as follows to trade bundled emial. Admin / Preferences / Ports - Bundled email server port = 25 Bundled email SSL server port = 465 ----------------------------------------------------------------------- 20. Adding partner profiles via client may crash the AIX TPI server ----------------------------------------------------------------------- When running TPI on AIX, it is possible to stop the server by adding new partner profiles while in client server mode. The server process goes away and the log file shows that the system is writing a core dump file. This is a JVM issue only on AIX. The work around is to add the command "export JAVA_COMPILER=NONE" to the TPI Server start script. ------------------------- 21. 4.1.2 resolved issues ------------------------- Issue 4910 ---------- crysec throws an error when parsing a x509 certificate which contains a UTF8String within a X500Name within the subject or issuer. This issue has been resolved. Issue 3376 ---------- When a user selects a rejected document in Tracker to reprocess it, the document is supposed to be moved from the rejected directory to the backup directory after the document is successfully sent to the partner. However, reprocessed documents were remaining in the rejected directory. This has been resolved by moving successfully reprocessed documents from the rejected directory to the backup directory. Issue 4443 ---------- System messages have been enhanced to notify users when the application encounters SSL connection failures that disrupt document trading. This has been done to clarify that such interruptions are network related and external to the application. Issue 4555 ---------- While the Server application was running, deleting a company certificate, which has the effect of retiring it from use, did not disable document trading as is supposed to occur. This has been resolved. Issue 4599 ---------- Changes to the name or IP address of the computer that runs the Server application (General tab in Tools > Preferences) were not being persisted properly to the database. This issue has been resolved. Issue 4622 ---------- When a newly created user of Administrator, who had been given limited permissions to change profiles for a specific group or groups of partners, logged on to Administrator and selected the partner profiles view, the application crashed. This issue has been resolved. Issue 4629 ---------- The system was only processing the first IEA of multi-part EDI-X12 documents. Everything after the first IEA was ignored. This issue has been resolved. Issue 4644 ---------- When the system sent a document via SMTP that exceeded the maximum size of attachments allowed by the receiving SMTP server, the system kept trying to resend the document even though the attachment was too large for the SMTP server to handle. This has been resolved by making the system stop trying to resend. The system now can recognize any 500- level result code returned from an SMTP server (code 554 excepted). When an SMTP server returns a result code in this range, the system rejects the outbound document and does not try to resend it. Issue 4663 ---------- The system was rejecting messages received via HTTP and HTTPS that had a minimal set of MIME headers. This occurred even though the system is supposed to accept MIME messages with only Content-Type and Content-Length specified, assuming the partner settings are valid. This issue has been resolved. Issue 4675 ---------- Document integration with IBM MQSeries was not functioning properly. This issue has been resolved. Issue 4681 ---------- The "To:" field was not being included in the MIME header for messages sent via the standard e-mail transport. This issue has been resolved. Issues 4683, 4742 ----------------- An error occurred when initially trying to save a partner profile that used the wildcard asterisk character (*) as a secondary ID. This issue has been resolved. Issue 4707 ---------- The system could not send clear-text documents (that is, unencrypted, no signatures, no acknowledgments) via the file system transport. This issue has been resolved. Issue 4712 ---------- The API event client was not reporting file extensions properly for processed documents. This issue has been resolved. File extensions are displayed or are null if there are none. Issue 4726 ---------- The MIME element "Host:" has been restored for compliance with the HTTP specification. Issue 4734 ---------- The update partners function was not working properly in sending refreshed profiles to partners after some types of transports were added to company profiles (for example, bundled HTTP or HTTPS, SMTP, POP). This issue has been resolved. Issue 4746 ---------- Tracker sometimes experienced an out-of-memory exception when exporting a configuration data file (Tracker.dat) containing a large number of records. This issue has been resolved. Issue 4748 ---------- The Original-Recipient and Final-Recipient elements were being populated erroneously with SenderID and ReceiverID values in MDNs for EDIINT transactions (that is, AS1 and AS2). They should have been populated with values from the original messages. This issue has been resolved. In the case of AS2, they are populated with the value of AS2-To in the original message. In the case of AS1, they are populated, respectively, with the values of To and Final- Recipient (or To if Final-Recipient is not available). Issue 4751 ---------- At times when the system experienced a high volume of trading activity, the agent controlling the sending of MDNs, which acknowledge the receipt of documents, would pause for a company. This also caused the system to pause from sending any documents or MDNs for that company to any partner. This issue has been resolved. Issue 4801 ---------- The system's bundled SMTP server responded only to commands in all upper case from SMTP clients. For example, the system could handle "MAIL FROM" but not "Mail From." This has been resolved so that the case of all such commands is ignored in compliance with the governing specification (RFC 2821). Issue 4802 ---------- The system rejected EDI documents that included the vertical pipe character | when used as a delimiter to mark the boundaries of various fields throughout the document. This issue has been resolved. ----------------------- 22. 4.1 resolved issues ----------------------- Issue 1 ------- The receiving system was rejecting two documents with the same control ID that were re-routed through a hub and sent by different partners. The receiving system rejected the documents as duplicates. This has been resolved by ensuring the true sender is checked so documents with the same control ID that pass through a hub are not rejected by the intended receiver's system. Issue 2 ------- All alphanumeric characters and the following other characters are allowed in profile IDs: "!\"#$%&\'()*+,- ./:;<=>?@[\\]^_`{|}~". Issue 3 ------- When using DB2 as the external database, deleting and adding partners while documents were being traded caused the server to lock. This issue has been resolved. Issue 4 ------- The DB2 definitions for column length were found to vary in the Inbound_Records and X_Inbound_Records tables. This issue has been resolved. Issue 5 ------- For manually created partner profiles, default ports have been added to the port and SSL port fields on the Partner Profile Outbound Transport Bundled E-mail Transport Options window. The default ports are 25 and 465, respectively. Issue 6 ------- Alerts are properly generated and sent via e-mail in the event of a document send failure. This corrected a situation in which some alerts were not sent when two documents failed to send at the same time. Issue 7 ------- Application behavior has been changed to prohibit a user from manually creating a partner profile that has an ID or secondary ID that is identical to an existing company profile. Issue 8 ------- In the Audit information viewer in Tracker, new schedules appeared as updated instead of added schedules. This issue has been resolved. Issue 9 ------- The import utility erroneously allowed the import of an Administrator.dat file into the Administrator application after user attributes had been changed in an otherwise new installation of the application. This behavior has been corrected so that an Administrator.dat file can be imported only into a completely new instance of the application. Issue 10 -------- The number of characters allowed in e-mail address fields has been increased from 50 to 255. ----------------- End release notes -----------------