IBM WebSphere(R) Transformation Extender Trading Manager Version 7.8 Release Notes (rev. 1) June 2006 (C) Copyright IBM Corporation 2006. All Rights Reserved. ===================================================================== CONTENTS ===================================================================== 1. About this release - Documentation notes 2. Installation instructions - Installation prerequisites - Installation instructions - Installation related issues 3. Uninstallaton instructions 4. Upgrading from an earlier version - Upgrading from Commerce Manager Version 6.1 - Upgrading from Commerce Manager Version 7.0 - Upgrading from Commerce Manager Version 7.5 - Upgrading from Commerce Manager Version 7.6 - Upgrading from Commerce Manager Version 7.7 5. Known issues 6. Contacting customer support 7. Notices and trademarks ===================================================================== 1. ABOUT THIS RELEASE ===================================================================== The file provides release notes for the IBM WebSphere Transformation Extender (WTX) Trading Manager version 7.8. This version of the product includes: - Enhanced validation and acknowledgement reporting for EDIFACT data files - Extended validation for BIN segment (claim attachment) for HIPAA version 4050X151, transaction 275 - HIPAA 824 acknowledgement reporting using Industry code version 4010 in addition to standard version 4050 - Rebranding of the product - Renaming of the product from Commerce Manager to Trading Manager - Introduction of InfoCenters to the Trading Manager documentation suite (See Documentation notes.) Documentation notes ------------------- Documentation for IBM WTX Trading Manager is available in an InfoCenter as well as in Portable Document Format (PDF). To access the documentation you must first install IBM WTX version 8.1.0 and the IBM WTX Trading Manager. NOTE Throughout these release notes, "install_dir\" is used to indicate the path where the product is installed. The default path for Windows is: C:\Program Files\IBM\IBM WebSphere Transformation Extender 8.1 Accessing the InfoCenter ------------------------ To access the InfoCenter: 1. From the Start menu select: Start > IBM WebSphere Transformation Extender 8.1 > Start the InfoCenter 2. When the InfoCenter opens, select the desired Trading Manager InfoCenter from the from the navigation pane on the left side of the InfoCenter window. The following InfoCenter topics are available for Trading Manager: - Trading Manager - Partner Manager - Trading Manager XML Autoload Utility - Trading Manager Performance Tuning and Debugging - Trading Manager Tutorial 3. After you have finished using the InfoCenter return to the Start menu and select: Start > IBM WebSphere Transformation Extender 8.1 > Dismiss the InfoCenter Accessing the PDFs ------------------ To access the PDFs, begin at the Windows Start menu and select: Start > IBM WebSphere Transformation Extender 8.1 > Trading Manager > Trading Manager Online Library ===================================================================== 2. INSTALLATION INSTRUCTIONS ===================================================================== To install IBM WTX products from the Electronic Software Distribution (ESD) site: 1. Download the file from the ESD site. 2. If you are installing on a different machine, transfer the file (in binary mode) to the target machine. 3. On Windows, run the corresponding .EXE file. OR On UNIX, untar the image and run DSTXINST. 4. Follow the instructions presented in the installation program. Installation prerequisites -------------------------- IBM WebSphere Transformation Extender version 8.1 must be installed before installing Trading Manager. Installation instructions ------------------------- Click "Install Products", and then "IBM Trading Manager" buttons to begin installation. See the Upgrading from Commerce Manager 6.1, Upgrading from Commerce Manager 7.0, Upgrading from Commerce Manager 7.5, Upgrading from Commerce Manager 7.6 or Upgrading from Commerce Manager 7.7 sections for information on upgrading from previous product versions. For information on installing and configuring this version of Trading Manager, see the Trading Manager documentation (1016.pdf). After the product is installed, this document may be accessed from your Windows Start menu: Start > Programs > IBM WebSphere Transformation Extender n.n > Trading Manager > Trading Manager Online Library Select the Trading Manager documentation from the list. To install Trading Manager Server components on Sun Solaris, HP-UX, or IBM RS/6000 AIX platforms: 1. Copy the UNIX setup file, CMSInstall.ksh, from the Trading Manager installation folder C:\install_dir\tmgr\platform_support to the target machine (where c: indicates the installation drive). 2. Execute CMSInstall.ksh on the target machine. NOTE: For information about the Launcher for UNIX, refer to the Launcher documentation. 3. Copy the Unix Shared Library for X12 Compliance Checking, cmsvu.so or cmsvu.sl from the Trading Manager installation folder C:\install_dir\tmgr_vn.n\platform_support\os&version to the target machine shared library location (where os&version indicates aix, hp, sun25, sun26, sun27). 4. Copy the Unix Shared Library for Trading Manager, cmsvc.so or cmsvc.sl from the Trading Manager installation folder C:\install_dir\tmgr_vn.n\platform_support\os&version to the target machine shared library location (where os&version indicates aix, hp, sun25, sun26, sun27). Note: If the setup script in the Integration Broker install directory is not run by the .profile of the user starting the Integration Broker, then the cmsvu.sl/cmsvu.so files must be copied to the tmgr_vn.n/mmgr/ directory path, otherwise it can be copied to the shared library location in the libs subdirectory in the Integration Broker install directory. Ensure permissions are set properly as read/write/execution permission on this shared library. Installation related issues ---------------------------- There are no installation issues at this time. ===================================================================== 3. UNINSTALLATION INSTRUCTIONS ===================================================================== - To uninstall Trading Manager product components from Windows platforms, from the Start menu, select Settings > Control Panel > Add/Remove Programs. Highlight the product component to be uninstalled and click Add/Remove. - To uninstall Trading Manager products from UNIX platforms, your current directory must not be within the IBM WebSphere Transformation Extender installation directory tree. The uninstall script does not delete the main installation directory itself. This installation directory must be manually removed. For example, if the product was installed into directory /Program Files/IBM, you could do the following: cd /Program Files rm -rf ./IBM Either individual components or the entire IBM WebSphere Transformation Extender installation can be removed. Below the directory in which the IBM WebSphere Transformation Extender products are installed is a subdirectory named /dstx_install that contains the uninstall scripts. To remove an IBM WebSphere Transformation Extender product or a component, execute the corresponding uninstall script (from a directory outside the /install_dir/directory) by providing the full path, similar to the following command: install_dir/dstx_install/item_to_be_removed.uninstall where install_dir is the directory in which IBM WebSphere Transformation Extender was installed and item_to_be_removed is the component or product to be uninstalled. ===================================================================== 4. UPGRADING FROM AN EARLIER VERSION ===================================================================== Upgrading from Commerce Manager version 6.1 ------------------------------------------- Trading Manager 7.8 utilizes updates to the source maps, type trees, database query file, and system definition file components. Therefore, any custom changes made to these files in a previous version will need to be applied to the new files. In Trading Manager 7.8 there is no longer a separate installation for the "Application Client", "Design Client", and the "Server". Instead, options now exist within the installation program in the "Select Trading Manager Components" screen. IMPORTANT: As with any upgrade, always back up your previous file system, programs, database(s), and data files in case you need to back out of the installation for any reason. You will need access to your 6.1 database during this conversion. Upgrading the 6.1 Commerce Manager database ------------------------------------------- These steps should be performed by, or under the supervision of, the Database Administrator. All database activity should be stopped (for example, no Partner Manager or Event Server processes running) before beginning this conversion. 1. The PC used to perform the conversion must have the "Partner Manager" and (if not using Access) the "SQL Scripts" components installed from the installation program. This will install the conversion programs and scripts needed to create a new 7.8 database. 2. Ensure your Trading Manager database is a version 6.1 database by issuing the following SELECT statement in the SQL tool provided with your RDBMS: SELECT CurrentBEVersion FROM BackEndVersion if the version reported is not 6.1.1, the database is not a version 6.1 database and you should not proceed with this conversion. Contact IBM Technical Support for assistance. 3. Backup the current database using whatever means are available for your RDBMS. 4. If you are using a database other than Access, create a new Trading Manager database by running the "inst" and "load" scripts (i.e. orainst78.sql and oraload78.sql). Do not run these scripts in your 6.1 database. Instead, create a new database/instance for V7.8. If you are using Access, Trading Manager 7.8 ships with a new mdb name: tmgr78.mdb. 5. Create an ODBC Data source to this new database. 6. Run the Trading Manager program PMUpdate61to78.exe. This is installed in the same location as Partner Manager (typically c:\install_dir\tmgr_v7.8\pmgr). Follow the instructions displayed on the main screen. 7. Repeat step 2. The database version should now be at 7.8.3. Upgrading the 6.1 Commerce Manager server ----------------------------------------- 1. Run the setup program, selecting the "Server" option in the "Select Trading Manager Components" screen. 2. Remove the "Message_Manager.msl" file from the "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation. Upgrading the 6.1 Commerce Manager Message Manager -------------------------------------------------- 1. Run the setup program, selecting the "Partner Manager" and "Message Manager" options in the "Select Trading Manager Components" screen. 2. Remove the "Message_Manager.msl" file from the previous "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation. Upgrading the 6.1 Commerce Manager Partner Manager -------------------------------------------------- NOTE: In 6.1, the "Application Client" was just the Partner Manager component and was meant for users who did not maintain maps or databases. If you were using just this "Application Client" in 6.1, follow these instructions. 1. No special action required; run the installation program and select only the "Partner Manager" component from the "Select Trading Manager Components" screen. 2. Update your ODBC DSN to point to the new 7.8 database. Upgrading from Commerce Manager version 7.0 ------------------------------------------- In Trading Manager 7.8 there is no longer a separate installation for the "Application Client", "Design Client", and the "Server". Instead, options now exist within the installation program in the "Select Trading Manager Components" screen. Trading Manager 7.8 utilizes updates to the source maps, type trees, database query file, and system definition file components. Therefore, any custom changes made to these files in a previous version will need to be applied to the new files. IMPORTANT: As with any upgrade, always back up your previous file system, programs, database(s), and data files in case you need to back out of the installation for any reason. You will need access to your 7.0 database during this conversion. Upgrading the 7.0 Commerce Manager database ------------------------------------------- These steps should be performed by, or under the supervision of, the Database Administrator. All database activity should be stopped (for example, no Partner Manager or Launcher processes running) before beginning this conversion. 1. The PC used to perform the conversion must have the "Partner Manager" and (if not using Access) the "SQL Scripts" components installed from the installation program. This will install the conversion programs and scripts needed to create a new 7.8 database. 2. Ensure your database is a version 7.0 database by issuing the following SELECT statement in the SQL tool provided with your RDBMS: SELECT CurrentBEVersion FROM BackEndVersion If the version reported is not 7.0.5, the database is not a version 7.0 database and you should not proceed with this conversion. Contact IBM Technical Support for assistance. 3. Backup the current database using whatever means are available for your RDBMS. 4. If you are using a database other than Access, create a new Trading Manager database by running the "inst" and "load" scripts (i.e. orainst78.sql and oraload78.sql). Do not run these scripts in your 7.0 database. Instead, create a new database/instance for V7.8. If you are using Access, Trading Manager 7.8 ships with a new mdb name: tmgr78.mdb. 5. Create an ODBC Data source to this new 7.8 database. 6. Run the Trading Manager program PMUpdate70to78.exe. This is installed in the same location as Partner Manager (typically c:\install_dir\tmgr\pmgr). Follow the instructions displayed on the main screen. 7. Repeat step 2. The database version should now be at 7.8.3. Upgrading the 7.0 Commerce Manager server ----------------------------------------- 1. Run the setup program, selecting the "Server" option in the "Select Trading Manager Components" screen. 2. Remove the "Message_Manager.msl" file from the "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation. Upgrading the 7.0 Commerce Manager Message Manager -------------------------------------------------- 1. Run the setup program, selecting the "Partner Manager" and "Message Manager" options in the "Select Trading Manager Components" screen. 2. Remove the "Message_Manager.msl" file from the previous "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation.. Upgrading the 7.0 Commerce Manager Partner Manager -------------------------------------------------- NOTE: In 7.0, the "Application Client" was just the Partner Manager component and was meant for users who did not maintain maps or databases. If you were using just this "Application Client" in 7.0, follow these instructions. 1. No special action required; run the installation program and select only the "Partner Manager" component from the "Select Trading Manager Components" screen. 2. Update your ODBC DSN to point to the new 7.8 database. Upgrading from Commerce Manager version 7.5 ------------------------------------------- Trading Manager 7.8 utilizes updates to the source maps, type trees, database query file, and system definition file components. Therefore, any custom changes made to these files in a previous version will need to be applied to the new files. IMPORTANT: As with any upgrade, always back up your previous file system, programs, database(s), and data files in case you need to back out of the installation for any reason. You will need access to your 7.5 database during this conversion. Upgrading the 7.5 Commerce Manager database ------------------------------------------- These steps should be performed by, or under the supervision of, the Database Administrator. All database activity should be stopped (for example, no Partner Manager or Launcher processes running) before beginning this conversion. 1. The PC used to perform the conversion must have the "Partner Manager" and (if not using Access) the "SQL Scripts" components installed from the installation program. This will install the conversion programs and scripts needed to create a new 7.8 database. 2. Ensure your database is a version 7.5 database by issuing the following SELECT statement in the SQL tool provided with your RDBMS: SELECT CurrentBEVersion FROM BackEndVersion if the version reported is not 7.5.1, the database is not a version 7.5 database and you should not proceed with this conversion. Contact IBM Technical Support for assistance. 3. Backup the current database using whatever means are available for your RDBMS. 4. If you are using a database other than Access, create a new database by running the "inst" and "load" scripts (i.e. orainst78.sql and oraload78.sql). Do not run these scripts in your 7.5 database. Instead, create a new database/instance for V7.8. If you are using Access, Trading Manager 7.8 ships with a new mdb name: tmgr78.mdb. 5. Create an ODBC Data source to this new 7.8 database. 6. Run the Trading Manager program PMUpdate75to78.exe. This is installed in the same location as Partner Manager (typically c:\install_dir\tmgr\pmgr). Follow the instructions displayed on the main screen. 7. Repeat step 2. The database version should now be at 7.8.3. Upgrading the 7.5 Commerce Manager Server ----------------------------------------- 1. Run the setup program, selecting the "Server" option in the "Select Trading Manager Components" screen. 2. Remove the "msg_mgr.msl" file from the "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation. Upgrading the 7.5 Commerce Manager Message Manager -------------------------------------------------- 1. Run the setup program, selecting the "Partner Manager" and "Message Manager" options in the "Select Trading Manager Components" screen. 2. Remove the "Message_Manager.msl" file from the previous "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation. Upgrading the 7.5 Commerce Manager Partner Manager -------------------------------------------------- 1. No special action required; run the installation program and select only the "Partner Manager" component from the "Select Trading Manager Components" screen. 2. Update your ODBC DSN to point to the new 7.8 database. Upgrading from Commerce Manager version 7.6 -------------------------------------------- Trading Manager 7.8 utilizes updates to the source maps, type trees, database query file, and system definition file components. Therefore, any custom changes made to these files in a previous version will need to be applied to the new files. IMPORTANT: As with any upgrade, always back up your previous file system, programs, database(s), and data files in case you need to back out of the installation for any reason. You will need access to your 7.6 database during this conversion. Upgrading the 7.6 Commerce Manager database ------------------------------------------- These steps should be performed by, or under the supervision of, the Database Administrator. All database activity should be stopped (for example, no Partner Manager or Event Server processes running) before beginning this conversion. 1. The PC used to perform the conversion must have the "Partner Manager" and (if not using Access) the "SQL Scripts" components installed from the installation program. This will install the conversion programs and scripts needed to create a new 7.8 database. 2. Ensure your database is a version 7.6 database by issuing the following SELECT statement in the SQL tool provided with your RDBMS: SELECT CurrentBEVersion FROM BackEndVersion if the version reported is not 7.6, the database is not a version 7.6 database and you should not proceed with this conversion. Contact IBM Technical Support for assistance. 3. Backup the current database using whatever means are available for your RDBMS. 4. If you are using a database other than Access, create a new database by running the "inst" and "load" scripts (i.e. orainst78.sql and oraload78.sql). Do not run these scripts in your 7.6 database. Instead, create a new database/instance for V7.6. If you are using Access, Trading Manager 7.8 ships with a new mdb name: tmgr78.mdb. 5. Create an ODBC Data source to this new 7.8 database. 6. Run the Trading Manager program PMUpdate76to78.exe. This is installed in the same location as Partner Manager (typically c:\install_dir\tmgr\pmgr). Follow the instructions displayed on the main screen. 7. Repeat step 2. The database version should now be at 7.8.3. Upgrading the 7.6 Commerce Manager server ----------------------------------------- 1. Run the setup program, selecting the "Server" option in the "Select Trading Manager Components" screen. 2. Remove the "msg_mgr.msl" file from the "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation.. Upgrading the 7.6 Commerce Manager Message Manager -------------------------------------------------- 1. Run the setup program, selecting the "Partner Manager" and "Message Manager" options in the "Select Trading Manager Components" screen. 2. Remove the "Message_Manager.msl" file from the previous "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation. Upgrading the 7.6 Commerce Manager Partner Manager -------------------------------------------------- 1. No special action required; run the installation program and select only the "Partner Manager" component from the "Select Trading Manager Components" screen. 2. Update your ODBC DSN to point to the new 7.8 database. Upgrading from Commerce Manager version 7.7 ------------------------------------------- Trading Manager 7.8 utilizes updates to the source maps, type trees, database query file, and system definition file components. Therefore, any custom changes made to these files in a previous version will need to be applied to the new files. IMPORTANT: As with any upgrade, always back up your previous file system, programs, database(s), and data files in case you need to back out of the installation for any reason. You will need access to your 7.7 database during this conversion. Upgrading the 7.7 Commerce Manager database ------------------------------------------- These steps should be performed by, or under the supervision of, the Database Administrator. All database activity should be stopped (for example, no Partner Manager or Event Server processes running) before beginning this conversion. 1. The PC used to perform the conversion must have the "Partner Manager" and (if not using Access) the "SQL Scripts" components installed from the installation program. This will install the conversion programs and scripts needed to create a new 7.8 database. 2. Ensure your database is a version 7.7.3 database by issuing the following SELECT statement in the SQL tool provided with your RDBMS: SELECT CurrentBEVersion FROM BackEndVersion if the version reported is not 7.7.3, the database is not a version 7.7 database and you should not proceed with this conversion. Contact IBM Technical Support for assistance. 3. Backup the current database using whatever means are available for your RDBMS. 4. If you are using a database other than Access, create a new database by running the "inst" and "load" scripts (i.e. orainst78.sql and oraload78.sql). Do not run these scripts in your 7.7 database. Instead, create a new database/instance for V7.7. If you are using Access, Trading Manager 7.8 ships with a new mdb name: tmgr78.mdb. 5. Create an ODBC Data source to this new 7.8 database. 6. Run the Trading Manager program PMUpdate76to78.exe. This is installed in the same location as Partner Manager (typically c:\install_dir\tmgr\pmgr). Follow the instructions displayed on the main screen. 7. Repeat step 2. The database version should now be at 7.8.3. Upgrading the 7.7 Commerce Manager server ----------------------------------------- 1. Run the setup program, selecting the "Server" option in the "Select Trading Manager Components" screen. 2. Remove the "msg_mgr.msl" file from the "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation.. Upgrading the 7.7 Commerce Manager Message Manager -------------------------------------------------- 1. Run the setup program, selecting the "Partner Manager" and "Message Manager" options in the "Select Trading Manager Components" screen. 2. Remove the "Message_Manager.msl" file from the previous "systems" subdirectory. 3. Re-deploy the Message Manager system as described in the Trading Manager documentation. Upgrading the 7.7 Commerce Manager Partner Manager -------------------------------------------------- 1. No special action required; run the installation program and select only the "Partner Manager" component from the "Select Trading Manager Components" screen. 2. Update your ODBC DSN to point to the new 7.8 database. ===================================================================== 5. KNOWN ISSUES ===================================================================== There are no known issues at this time. ===================================================================== 6. CONTACTING CUSTOMER SUPPORT ===================================================================== Contact Customer Support at 1-800-IBM-SERV or from the product page of the IBM Web site: www.ibm.com/software/integration/wtx ===================================================================== 7. NOTICES AND TRADEMARKS ===================================================================== This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 577 Airport Blvd., Suite 800 Burlingame, CA 94010 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. If you are viewing this information softcopy, the photographs and color illustrations may not appear. Programming interface information --------------------------------- Programming interface information, if provided, is intended to help you create application software using this program. General-use programming interfaces allow you to write application software that obtain the services of this program's tools. However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification and tuning information is provided to help you debug your application software. Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change. Trademarks and service marks ---------------------------- The following terms are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries, or both: i5/OS IBM the IBM logo AIX AIX 5L CICS DB2 DB2 Universal Database Domino HelpNow IMS Informix iSeries Lotus Lotus Notes MQIntegrator MQSeries MVS Notes OS/400 Passport Advantage pSeries Redbooks SupportPac WebSphere z/OS Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. This product includes software developed by the Eclipse Project (http://www.eclipse.org/). IBM WebSphere Transformation Extender Trading Manager version 7.8