Release Notes for ECXpert for Windows NT 4.0

Transcription

1 Release Notes for ECXpert for Windows NT 4.0 Version 3.5 Updated February These release notes contain important information available at the time of the version 3.5 release of ECXpert for Windows NT 4.0. New features and enhancements, installation notes, known problems, and other late-breaking issues are addressed here. Read this document before you begin using ECXpert for Windows NT 4.0. An electronic version of these release notes can be found at the iplanet documentation web site: Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals. These release notes contain the following sections: What s New in ECXpert for Windows NT 4.0, Version 3.5 Hardware and Software Requirements Installation Notes m Downloading ECXpert Version 3.5 for Windows NT 4.0 m Installing the ECXpert 3.5 for Windows NT 4.0 Build Known Problems and Limitations m Bug Fixes Contacting Technical Support For More Information 1

2 What s New in ECXpert for Windows NT 4.0, Version 3.5 What s New in ECXpert for Windows NT 4.0, Version 3.5 With this release, the features described in Table 1 have been been incorporated in to the code base. Table 1 New Features In ECXpert 3.5 for Windows NT 4.0 Feature Enhances Description OBI Support XML Parser Billing Code Mercator 5.0 Support HTTP SSL for XML Error Detection Services iplanet Web Server 4.1 support Interaction with BuyerXpert and SellerXpert Trading partnership document exchange Trading Partnership Billing data capture utility script Mercator Mapping Translation Engine Outgoing Protocols used by Trading Partners Service List Processing and Monitoring Front end to ECXpert UIs Use of Open Buying on the Internet standard to allow connections for document and data exchange between ECXpert and both BuyerXpert and SellerXpert. The new ECXpert XML Parser provides extensibility and flexibility for businesses that exchange xml document types with a trading partner. The optional use of a Billing code helps to determine how many sender, receiver, and document type transactions have occurred in a specified time period for billing accounting purposes. The Billing Data Capture Utility script provides users of BillerXpert with the means to better track billing information to accurately bill their customers. The Mercator Mapping Translation Engine has been updated to reflect the latest code release from Mercator which handles xml data mapping. The HTTP SSL for XML protocol can be used as the primary communications agent when exchanging xml documents. The new Error Detection Services can be used to provide a more meaningful feedback mechanism as documents are submitted and processed through ECXpert. You can control the severity level of errors that you wish to receive notification upon when a job fails. You can also customize the communication mechanism that ECXpert will handoff the error data with the Exit Service list call (e.g., , message post to web page, and so forth). The former version of the Netscape Enterprise Server, 3.6, has been end of lifed. ECXpert 3.5 is certified with version 4.1 of the iplanet Web Server, the new product name for this software. 2 ECXpert for Windows NT 4.0 Release Notes February

3 Hardware and Software Requirements Java API Layer Support Development of Java applications to enhance preentation to users The Java API is a JNI (Java Native Interface) wrapper which provides a developer the library to design and implement a java application to present the existing interface that ECXpert uses in a customized manner. Priority Processing Service List Processing Priority Processing provides an effective and efficient solution in large business document volume exchange environments whereby high priority documents can be processed ahead of non-mission critical documents that will also be processed but at a lower rate without jamming the ECXpert input queue. Hardware and Software Requirements Refer to the Preinstallation Tasks section of the Getting Started with iplanet ECXpert for Windows NT 4.0 for hardware and software requirements. Installation Notes The installation guidelines and instructions for Oracle (the only Oracle version certified with ECXpert 3.5 for Windows NT 4.0), iplanet Web Server, the optional iplanet Messenging Server, and ECXpert 3.5 for Windows NT are provided in the Getting Started with iplanet ECXpert, version 3.5 for Windows NT 4.0 guide. Please refer to the requirements and guidelines so that the installation phase for this release can proceed smoothly. Downloading ECXpert Version 3.5 for Windows NT 4.0 If you are a registered subscriber to SubcribNet, you can download and install the ECXpert 3.5 for Windows NT 4.0 build using the following steps: 1. Log on to the ECXpert machine as the administrative user, usually actraadm. The default password is actraadm. Release Notes for ECXpert for Windows NT 4.0 3

4 Installation Notes 2. Download the ECXpert 3.5 installation file. Display the ProductTracker by SubscribNet web page. The URL is The main Subscribnet page is displayed. Click the link for Subscribnet Users. Log in using your Subscribnet user ID and password. An index of the iplanet software registered for your user ID is displayed. Click the iplanet ECXpert link. A page is displayed that asks you to select the version and platform. Enter 3.5 for the version and Windows NT for the platform. Click the link matching or similar to the following: iplanet ECXpert V3.5 for Windows NT US/CAN. The available file names that can be downloaded will be displayed. NOTE If your firewall does not allow browser-based ftp, use the Advanced Options link to download via http. m Click the Download button to the left of the file name matching or similar to iplanet ECXpert 3.5 for Windows NT Domestic to display the open/save prompt for this file and save the file matching or similar to: NTECX35.zip to your target directory. m m m Obtain and enter your assigned decryption key to unzip the file. Select a temporary directory as the target directory for the unzipped files. Execute the unzip process to place the files in the temporary directory. When unzipped, the file names and specifications will be displayed as shown in Figure 1. 4 ECXpert for Windows NT 4.0 Release Notes February

5 Installation Notes Figure 1 Unzipped File List on Temporary Directory List Of Files: (please note, file sizes are approximate) CTL3D.DLL 20,976 CTL3D32.DLL 25,088 CTL3D32S.DLL 26,112 ecx.z 30,773,033 ISDBGN.DLL 129,536 setup.exe 47,616 SETUP.INI 47 SETUP.INS 81,824 setup.pkg 41,203 uninst.exe 283,648 _INST32I.EX_ 306,748 isdel.exe 8,192 Installing the ECXpert 3.5 for Windows NT 4.0 Build ECXpert 3.5 for Windows NT 4.0 includes a complete build of the ECXpert code base. This build is also compatible with a previously installed export version of ECXpert 3.0 for Windows NT 4.0. Therefore, you can install this build over an existing export ECXpert 3.0 for Windows NT 4.0 version. Perform the steps below to install the build. Coordinate this installation with the section Migrate/Upgrade of the iplanet ECXpert Getting Started Guide, Version 3.5 for Windows NT 4.0. NOTE Before running setup_exe, shut down all ecx processes and back up your ecx.ini file as it will be overwritten by the included ecx.ini file in the build 1. Expand the zip file using a unzip utility such as winzip or equivalent. The 12 files indicated in Figure 1 will be displayed. 2. Run the file setup.exe and select the desired directory for installation when prompted (i.e., other than $NSBASE, see note below). You can assign the same path for Base-Dir as used for ECX30 install; the current installation will overwrite the existing installation. Release Notes for ECXpert for Windows NT 4.0 5

6 Installation Notes NOTE 1. For the installation, it is mandatory that you delete the NS-apps/navigator directory to overwrite files that are read only. 2. It is recommended, though not required to use a different folder than the existing $NSBASE, or, delete the whole NS-apps directory before re-using it. 3. If ECXpert is running, export your existing database to preserve data before running the installation routine. Following installation, import the data to the ECX-database. Alternatively, you can select NO to the Delete and Create New Table prompt during installation. 3. The installation will proceed similarly to that performed using the instructions from the Starting the iplanet ECXpert Installer section of the Getting Started with iplanet ECXpert Windows NT 4.0 guide. 4. After completing the build installation, overwrite the installed ecx.ini file with your backed up version to restore your ecx.ini settings. 5. Restart ecx processes as desired. NOTE If you wish to enable support for enlarged text entry fields (greater than 64 to a maximum of 128 characters) for sender ID and receiver ID in the Partnership portion of the Support User Interface, you must run the script described in the section Enabling Support for Expanded Data Fields in the iplanet ECXpert Getting Started, Version 3.5 for Windows NT 4.0 guide. The rest of this document describes the known problems and limitations, changes to documentation, and how to obtain technical support. 6 ECXpert for Windows NT 4.0 Release Notes February

7 Known Problems and Limitations Known Problems and Limitations Interoperability with ECXpert for Solaris Via the HTTP AIAG Protocol Version 3.5 of ECXpert for Solaris supports the newer AIAG 2000 standard. Version 3.5 of ECXpert for Windows NT 4.0 supports the AIAG 1.0 version only. As a result, documents cannot be exchanged between this release of ECXpert for Windows NT 4.0 and ECXpert 3.5 for Solaris using the HTTP AIAG protocol. Any attempts to exchange documents between the two operating systems using this protocol will result in the following error statement: The requested object does not exist on this server. The link you followed is either outdated, inaccurate, or the server has been instructed not to let you have it. Changes Made to ecx.ini Not Updated Filed under bug ID , users who make one or more changes to the ecx.ini file while the Admin Server is on does not allow such changes to be updated to this ECXpert file since other processes are running. Therefore, the best practice is to turn the Admin Server off and make the changes to the ecx.ini file, save the file, and turn the Admin Server back on. Alternatively, all other servers can be turned off and the Admin Server left on to apply and save changes to ecx.ini. With only the Admin Server running, the changes will be updated in ECXpert s UI. Then the other servers can be turned on again. Submitted IDOC From ECXpert to SAP Results in sendidoc Function Failure Error Message Filed under bug ID , when an IDoc is submitted from ECXpert to SAP, the sendidoc function causes an error message to be displayed. This error occurs when the SAP server attempts to send an acknowledgment of having received the IDoc but connectivity is lost. The document is actually received so the error can be ignored. A patch will be forthcoming when this bug has been resolved. Bug Fixes Table 2 identifies fixes from the Solaris platform that are included with this release of ECXpert 3.5 for Windows NT 4.0: Release Notes for ECXpert for Windows NT 4.0 7

8 Known Problems and Limitations Table 2 Solaris Platform Bugs Incorporated in to ECXpert 3.5 for Windows NT 4.0 Source Release Bug ID Description ECXpert 3.0 SP The Split service creates extra files If an EDIFACT file submitted to ECXpert does not include a Sender Qualifier and a Receiver Qualifier, the file fails Parse with the error: "Unknown data found in submitted file." The GE01 and ST02 elements of 997 envelopes are not built properly If the disk where ECXpert is installed reaches full capacity, any filesubmissions that require more disk space than is left will result in a smaller than expected file, and will result in the following error: "Disk full: no error, 0 byte trk & bundle file generated." When an EDIFACT file which has some groups and some just plain messages in the same interchange is submitted, the warning "Only 4 out of 3 EDIFACT Functional Group(s) parse" shows up in Activity Tracking Netscape Communicator sometimes crashes when you view Directory Server 3.0 Schema Object classes The date that is being inserted into the TrkGroup for the second part of the Split service has an incorrect data type and causes either of these errors: in Oracle7, 7.3.4, "ORA-01843: not a valid month"; or in Oracle8, 8.1.5, "ORA-01861: literal does not match format string." Submitting an HREC to ECXpert for Application-to-EDI Translate fails if the dbupdaterarraysize parameter in the [parse] section of the ecx.ini file is on The.so files in the NAS extension are looking for *7d.so files instead of *4d.so files, resulting in the error "NasExt: ccxcnasextension lib files need to be release version." ECXpert does not to generate an 8-digit UNB date element (UNB-040-S004) for outgoing EDIFACT files. 8 ECXpert for Windows NT 4.0 Release Notes February

9 Known Problems and Limitations In the HP version, when files for a partnership whose data was imported using the import utility are submitted to be Parsed and Translated, a "No map name" error results. The PL/SQL error is "ORA-06502:character string buffer too small." Extra messages logged to gateway log with after a file is submitted via OFTP Output EDI Test/Production flag is setting the UNB value incorrectly When Type 248 documents are submitted, ECXpert cannot find the corresponding partnership, resulting in the error "map name not found." The Translate feature PARAMS_FROM_ECX, which passes the TrkId to a map during Translate, produces the error "Input card 1, file PARAMS_FROM_ECX not found." Tracking produces no output; if FAGen follows Translate, no FA is produced EDIFACT 8-digit UNB dates in the UNB-S element causes Parse to reject the file with an "Unknown data" error Damaged SQL statement: UPDATE Tracking SET TRKState = 4 WHERE 0 = Problems connecting to MQSeries using an alias for a local or remote queue or using a remote queue Output cards get incorrect file extension.out4 should be.out Parse allows only a 4-digit GS05 Time field, instead of the 4-8 digits specified in the ANSI standard Parse does not allow the underscore character ("_") as a valid alpha-numeric character. ECXpert 3.0 SP2 Release Notes for ECXpert for Windows NT 4.0 9

10 Known Problems and Limitations In the ecx.ini file, the parameter inorderreceived was not working. This caused EDI documents to be output in a different order than the input. The fix included changes to bundlenew/bundle.cpp to set the flag DB_OP_SORTBYOFFSET when retrieving docs bdgrealpurge was running too slowly. The fix includes running the command as follows:./bdgrealpurge -in $NSBASE/NS-apps/ECXpert/config/ecx.ini -all -nomanifest FTP server does not start automatically when autostart is set in ecx.ini. Fixed documentation as described in Changes to Documentation on page 7 of the Release Note Parse fails after the split service is completed on the NT build. Internal code fix Translate service error indicating too many partnerships with an error code of that also failed multiple dispatchers during scal-ability testing. The following files were fixed: ecxtranslate.cpp, v1.16 and legacyrolep.cpp (fork1 to fork) Scheduler entries overwrite one another on the NT build. Fixed with updated packaging of product and supplied as a patch bdgrealpurge deletes valid tracking files that have no partnership. Fixed documentation to properly identify the ways to use bdgre-alpurge command with or without options as described in Changes to Documentation on page 7 of the Release Note bdggenmanifest does not take any parameters (bdgmanifest -in option does not work). Fixed documentation as described in Changes to Documentation on page 7 of the Release Note No link between 997 tracking ID record and acknowledged docu-ment. Fix included changes to parsenew/*/ecxpupdtr.h and.cpp to parse 997 s or CONTRL s doc id to GotAck() ECX 3.0 Parser does not support EDI extended character set. Fix included code update in hrecseg.cpp. 10 ECXpert for Windows NT 4.0 Release Notes February

11 Known Problems and Limitations ECX 3.0 Parser fails on EDIFACT release delimiter nor the EDIFACT decimal character. Fix included code update in unaparser.cpp ECX 3.0 Parser fails on EDIFACT transaction with error #603. Fix included code update in ecxpubdtr.cpp Scheduler implementation with reset_running_state. Fix included changes to following code files: bdg/sched/scrc/ecxjobq.cpp v 1.30, bdg/public/ecxschedconst.h v1.11, bdg/config/bdg.ini.template v1.310, bdg/config/bdg.ini.nt-ix86.template v Allow up to 3 characters for segment terminator of X.12. Fix included changes to the following code files in dir paths noted: isaparser.cpp (in asrc/modules/bdg/parsenew/parsers) isaseg.cpp (actrasrc/modules/bdg/parsenew/edi) ECXpert If a tracking ID is reprocessed, that tracking ID will be unavailable from the UI once the job finishes Unable to import new root of an existing type through UI Documentation on Using Helper Card is inadequate.(8/21) Check it in doc,(8/23) updated doc, explain what and how to use helper card in detail If you define a comm agent in ecx.ini as "user-defined 2" but do not have a "user-defined 1" ECXpert will hang when you try to use "user-defined-2" in a partnership password and receiver fields should not be on http-ssl outbound protocol screen DB_DO_MULTIPART default is 1 - code should be deactivated Release Notes for ECXpert for Windows NT

12 Known Problems and Limitations Ambiguous steps in Getting Started Guide, ECXpert 3.0, Appendix C After "no member found" error submission, tcpip connector doesn't register subsequent files. (9/22) with the DB_TRIGGER_PROCEDURE = 0 set in the ecx.ini file shows the fix is in right direction Problem defining multiple comm agents incoming s with non-alpha characters in Message-Id simply disappear. 09/25: Fix planned by engineering is to replace '/' by '~'. Customer is ok for this fix. 10/5 fixed, verified by QA, sent to customer and waiting for customer's acceptance.(10/5) fixed some incoming SMTP messages makes SMTPReceive looping (9/19): reproduced by engineering. (10/19) sent "The potential problem with 2 SMTPReceives" (10/20) sent patch to customer, ask for customer's acceptance In both the EDIFACT D97B and D98A versions of the Mercator Type Trees ar not updated, Are there available from TSI? (10/20) Both of the element 1154 and element 7402 are updated correctly in Mercator 5.0, ECX 3.5 will ship with Mercator version Telnet to ECX ftp server port crashes ecxftp-m-server.customer considers this a security hole as any hacker could shut down the ECX ecxftp-server from the outside.(11/3) Aarti indicated that this bug will be fixed and include in ECX should allow use of Mercator audit options, AED ECX Partnership Search screens do not display GS Codes entered in partnership Segment count (UNT) for Edifact is incorrect (11/13) They all started with either UNA: or UNA>. But bdg/bundlenew/edidoc.cpp expects UNA only GUI problems - UNA setting not presented. 12 ECXpert for Windows NT 4.0 Release Notes February

13 Contacting Technical Support Table 3 shows the bug fixes from the earlier ECXpert 3.0 for Windows NT 4.0 version that are included with the release. In addition, there is a newer bug that has been fixed against an older NT issue, bug number Table 3 Bug Fixes from ECXpert 3.0 for Windows NT 4.0 iplanet Bug Tracking # Description PARAMS_FROM_ECX produces the error "inputcard 1,file 'PARAMS_FROM_ECX' not found." HTTP/SSL server not supported but still appears in admin UI and in ecx.ini Change of default_retention_period variable value not effecting in partnership (1/31) The default value of retention period is read from the ecx.ini file when a new partnership is added OBI comm components now in build (2/2) OBI component has been added to the ECXpert NT package Maps Failing due to Error NT : can not decrypt some signed + encrypted files Incoming s by way of SMTPReceive were not properly processed as ECXpert was adding a / character to the Message-ID field when writing the to a temporary storage location. Fix included a file that updated SMTPSend, SMTPReceive, and bdg.jar to replace slash character with an acceptable dash - character ECX 3.0 (dispatcher) crashes under load with a memory access violation Dispatcher terminates after processing a couple of jobs. Contacting Technical Support Should you need to contact iplanet Technical Support, you will need to know the correct version number of your current copy of iplanet ECXpert. iplanet ECXpert updates the version number in the About message box. To find the correct iplanet ECXpert version number after you install ECXpert Version 3.5: 1. Start your browser. 2. Enter the URL of the Netscape ECXpert Main Menu screen. Release Notes for ECXpert for Windows NT

14 Contacting Technical Support 3. Click the Support page tab. A login screen appears. 4. You do not need to log in. Simply click the About button, and a message box appears, displaying the correct version number. Example For example, the message box below shows version information for a domestic copy of the iplanet ECXpert Version 3.5 installed. For additional information, refer to the latest version of the iplanet ECXpert Release Note available at: To contact ECXpert Technical Support in the United States, call ECXpert Alliance at: To contact ECXpert Technical Support outside of the United States, call Technical Support International at: If you have problems with ECXpert 3.5 for Windows NT 4.0, contact iplanet customer support using one of the following mechanisms: iplanet online support web site at From this location, the CaseTracker and CaseView tools are available for logging problems. The telephone dispatch number associated with your maintenance contract So that we can best assist you in resolving problems, please have the following information available when you contact support: Description of the problem, including the situation where the problem occurs and its impact on your operation 14 ECXpert for Windows NT 4.0 Release Notes February

15 For More Information Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem Detailed steps on the methods you have used to reproduce the problem Any error logs or core dumps You may also find it useful to subscribe to the following interest groups, where ECXpert for Windows NT 4.0 topics may be discussed: You may also find it useful to subscribe to the ECXpert newsgroup as NT issues are sometimes discussed there. The link is: Once there, look for the iplanet ECXpert - General link to call up the newsgroup articles. Alternatively, you can enter the following direct link: news://secnews.netscape.com/iplanet.ecx.general For More Information Useful iplanet information can be found at the following Internet locations: iplanet release notes and other documentation iplanet product status iplanet Professional Services information iplanet developer information iplanet learning solutions iplanet product data sheets Use of ECXpert for Windows NT 4.0 is subject to the terms described in the license agreement accompanying it. [(See link_to_licensing_info.)] Copyright 2000 Sun Microsystems, Inc. Some preexisting portions Copyright 2000 Netscape Communications Corp. All rights reserved. Sun, Sun Microsystems, the Sun logo, Java, iplanet, and all Sun, Java, and iplanet based trademarks and logos are trademarks or Release Notes for ECXpert for Windows NT

16 For More Information registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Netscape and the Netscape N logo are registered trademarks of Netscape Communications Corporation in the U.S. and other countries. Other Netscape logos, product names, and service names are also trademarks of Netscape Communications Corporation, which may be registered in other countries. 16 ECXpert for Windows NT 4.0 Release Notes February