webMethods papiNet eStandards Module 6.0.1 September 2003 Copyright (C) 1996-2003, webMethods, Inc. All Rights Reserved. _______________________________________________________________ This file provides important information for using the webMethods papiNet eStandards Module 6.0.1. For information about webMethods Integration Server or webMethods Trading Networks, see the Readme and Release Notes documents in the directory in which you installed the software. Contents: 1.0 Getting Started 2.0 Documentation 3.0 Known Problems and Limitations 4.0 Usage Notes 5.0 Globalization 6.0 Deprecated Components 7.0 Fixes and Enhancements in webMethods papiNet eStandards Module 6.0.1 8.0 Copyright Information 8.1 webMethods 9.0 Contacting Us 1.0 Getting Started The webMethods papiNet eStandards Module Installation and User's Guide Version 6.0.1 contains detailed instructions for installing and configuring webMethods papiNet eStandards Module. 2.0 Documentation Documentation for webMethods papiNet eStandards Module is located in the \pub\doc directory of the WmPapinet package where you installed the server. The following manuals are provided as PDF files: - webMethods papiNet eStandards Module Installation and User's Guide Version 6.0.1 To view the documentation supplied with this version of webMethods papiNet eStandards Module you must have Adobe Acrobat Reader 4.0 or later. You can download and install Acrobat Reader 4.0 from: http://www.adobe.com/support/downloads/main.html 3.0 Known Problems and Limitations - The papiNet Interoperability Guidelines for version 2.1 discuss ebXML extensions to support backward compatibility and mapping to the papiNet 1.x envelope. This is not supported by webMethods papiNet eStandards Module 6.0.1 since neither webMethods papiNet eStandards Module nor webMethods ebXML Module support ebXML extensions. 4.0 Usage Notes - webMethods Integration Server 6.0.1, webMethods Trading Networks 6.0.1, and webMethods ebXML Module 6.0.1 must be installed before you can install and run webMethods papiNet eStandards Module. For information about webMethods Integration Server, webMethods Trading Networks, or webMethods ebXML Module, see the readme files in the directory in which you installed the software. 5.0 Globalization The webMethods papiNet eStandards Module 6.0.1 has not been tested for conformance with the international standards of webMethods. The default language for the papiNet schema is U.S. English. Testing was performed with US-ASCII data. Documents using non-English text and non-ASCII data were not tested for this release. The webMethods ebXML Module Version 6.0.1 has not been tested for conformance with the internationalization standards of webMethods. This internal certification is planned for a future release. Using this version of the ebXML Module with non-standard character encodings (discussed below) and operation in locales other than U.S. English should be reliable because the standard ebXML headers do not require significant amounts of non-ASCII data. However, care should taken when deploying this product in non-English locales. - The components on which the ebXML module is dependent (webMethods for Trading Networks, webMethods Integration Server, and webMethods Developer) have been certified and tested for international support. Users should refer to the Globalization section of those products' readme.txt files for information about the limitations of those products before using the ebXML module in an international environment. - The default character encoding for ebXML envelopes, as defined by the emXML and XML 1.0 standards, is Unicode UTF-8. Although the underlying webMethods Integration Platform components that process the envelope support XML character encoding declarations correctly, this has not been tested in conjunction with the emXML Module. Attempts to process ebXML envelopes that use other character encodings may not work correctly. As a result, emXML envelopes in character encodings other than UTF-8 are not supported. - Each ebXML payload is handled as separate multi-part MIME content and is not processed directly by the ebXML Module. Instead it is passed as a byte stream to or from your service or application along with the MIME headers associated with it. Support for character encodings rests, therefore, entirely with your process model, application or Integration Server service. The MIME Content-Type will determine how each payload block should be processed. When working with textual data, setting the character encoding (charset) is an important way to ensure that the content is properly processed by the receiver. Please refer to the Integration Server and Developer user's guides and readme files for more information about working with character encodings in the webMethods Integration Platform. 6.0 Deprecated Components None 7.0 Fixes and Enhancements in webMethods papiNet eStandards Module 6.0.1 This is a new release; therefore, this section is not applicable. 8.0 Copyright Information 8.1 webMethods webMethods Administrator, webMethods Broker, webMethods Developer, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor, webMethods Trading Networks, webMethods Workflow, and the webMethods logo are trademarks of webMethods, Inc. "webMethods" is a registered trademark of webMethods, Inc. All other marks are the property of their respective owners. Copyright (c) 2003 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form. 9.0 Contacting Us Authorized technical support contacts can reach webMethods Technical Services for support via: Advantage: http://advantage.webMethods.com E-mail: support@webMethods.com US Phone: 1-888-222-8215 Europe/EMEA Phone: +800-963-84-637 or +31-207783640 Asia/Pacific Phone: +612-8913-1198 or +656-389-3222 Self-service support is also available in the Advantage Knowledge Base and in Advantage Customer Forums at http://advantage.webMethods.com.