Release notes for WebSphere Transformation Extender Trading Manager V8.2.1.6

Release Notes

Abstract

IBM WebSphere® Transformation Extender Trading Manager
Version 8.2.1.6 release notes

Content

This fix pack enables Trading Manager on WebSphere Transformation Extender version 8.4.
This fix pack fixes the Authorized Program Analysis Reports (APARS) noted in Section 6 of these release notes.

Documentation notes

Documentation for this product is provided in Portable Document Format (PDF) and in an IBM Eclipse help system called an information center. Instructions for accessing both the PDF documentation and the information center are provided below. For more information about WebSphere Transformation Extender product documentation, see the IBM WebSphere Transformation Extender Documentation Release Notes.

PDF

Information center

information center

Translated documentation

============================================================
2. INSTALLATION AND CONFIGURATION INFORMATION
============================================================

Installation prerequisites for Trading Manager

Before you install this version of Trading Manager, make certain that one of the following versions of the WebSphere Transformation Extender base product is installed.

If you are installing Trading Manager from the ESD site, install the pack using the executable (*.exe) file associated with your WebSphere Transformation base product as indicated in the table below:

WebSphere Transformation Extender base product required	Executable file
8.2.0.6 and later	tmgr8216_82.exe
8.3.0.4 and later	tmgr8216_83.exe
8.4.0.2 and later	tmgr8216_84.exe

Install the desired WebSphere Transformation Extender pack:

To install the WebSphere Transformation Extender Pack for X12 - Install version 2.8.0.x of this pack.

To install the WebSphere Transformation Extender Pack for EDIFACT - Install version 2.8.0.x of this pack.

To install the WebSphere Transformation Extender Pack for HIPAA - Install version 4.4.0 of this pack.

For additional installation prerequisites related to the WebSphere Transformation Extender base product, refer to the WebSphere Transformation Extender release notes.

Installing Partner Manager on Windows 7 and Windows 2008

When installing Partner Manager on 64-bit Windows 7 and Windows 2008 systems, a 32-bit version of ODBC is required.

On 64-bit Windows systems, the 32-bit ODBC Administrator is run using C:\Windows\SysWOW64\odbcad32.exe and the 64-bit ODBC Administrator is run using C:\system32\odbcad32.exe.

On 32-bit Windows systems the 32-bit ODBC Administrator is run using C:\system32\odbcad32.exe.

Deploying on z/OS operating system

If you are deploying this Fix Pack to a Trading Manager system running WebSphere Transformation Extender V8.2 or V8.3 on the z/OS operating system, and using DB2, contact IBM Support as additional maintenance might be required. Reference PM 61425 when you call.

Installing the pack

Follow these steps to install the pack on Windows systems:

Obtain the product media, or image, from the Support Downloads page.
Run the setup.exe command. If you are installing the pack from the ESD site, run the part_number.exe command.
Follow the instructions in the installation program.

Uninstalling the pack

Follow these steps to uninstall the pack from Windows systems:

Click Control Panel > Add/Remove Programs.
Select the pack that you want to remove.
Click Change/Remove and follow the prompts.

NOTE: The Repair or Remove options are no longer available in the installation program. You must uninstall the packs using the procedure detailed above.

============================================================
3. UPGRADE AND MIGRATION INFORMATION
============================================================

Note: prior to release 7.8, this product was known as DataStage TX Commerce Manager. For users converting to this release from versions prior to 7.8, the steps mentioning the Trading Manager Server refers to the Commerce Manager server in those earlier versions.

For HIPAA users

If you are converting from versions prior to 8.2.1.4, be aware of the following:

HIPAA no longer supports Non-Addenda transactions for the 4010 version. These Non-Addenda versions can be recognized as not ending in "A1", and beginning with "4010X" (for example: 4010X092). If you have existing trade links with those versions, you must update these trade links in Partner Manager to use the new versions. The Partner Manager windows seem to allow Type 2, and above, validation for these versions, however, since this is not supported, the Trading Manager maps generate a rejected file that indicates tha the version is not valid. In these cases, you must edit the trade links and disable those options.
Similar behavior occurs when you convert from a database that contains trade links for versions 5010X220, 5010X221, 5010X222, 5010X223A1, 5010X224A1 and 5010X279. Only Type 1 validation is allowed for these versions. The Partner Manager windows seem to allow Type 2, and above, validation for these versions, however, since this is not supported, the Trading Manager maps generate a rejected file that indicates that the version is not valid. In those cases, you must edit the trade links and disable those options.
If desired, before converting, you can run a query to see what trade links need to be modified. See HIPAA Non-Addenda Queries. You should consider deleting all 4010 Non-Addenda trade links that you might have. These can be found using the Trade Link Maintenance window in Partner Manager. Use the Search By Document feature, and sort by version.

Microsoft Access

Conversion to Trading Manager version 8.2 and above is not directly supported on Microsoft Access. If you have an Access database (mdb) that must be converted, you must first copy it to a supported database (DB2, Oracle, SQL Server, or Sybase) using the "Database Copy Utility" in that release. Then perform the conversion process as outlined below. Then you can use the "Database Copy Utility" supplied in the current release to copy it back to Access.

Backup before upgrading

Before performing an upgrade it is important that you 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 current database during this conversion.

Handling custom changes

Trading Manager 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.

Making database upgrades

The database 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.

Components requiring upgrade

There are three major components requiring upgrade steps:

the Server (where the maps are run)
the Message Manager portion, and
the Database

The Server contains the directory structure of Trading Manager; the Message Manager contains the maps, trees, and system definitions. If your Server is on a different Windows machine than the development machine, follow the "Upgrading the Trading Manager Server" instructions, running the setup while logged-on to that machine.

Upgrading the Trading Manager Server

Run the setup program, selecting the "Server" option in the "Select Trading Manager Components" screen. This will install the Server portion onto your windows machine. If your server is on UNIX, follow those instructions above using tmsinstall.ksh.
Remove the "Message_Manager.msl" and (if present) "msg_mgr.msl" files from the "systems" subdirectory.

Upgrading the Trading Manager Message Manager (Development Machine)

Run the setup program, selecting the "Partner Manager", "SQL Scripts" and "Message Manager" options in the "Select Trading Manager Components" screen. If deployment and development is on the same machine, also select "Server".
If present, remove the "Message_Manager.msl" and/or "msg_mgr.msl" files from the previous "systems" subdirectory. These might not be present if you use a separate server.
Re-deploy the Message Manager system as described in the Trading Manager documentation.

Previous users of the XML Autoload

Note: If you have used the XML Autoload in the past: In version 8.2, a "Test" post office to X12 Outbound Links was introduced. The existing post office field, PutMailPO, is now the "Production" post office. If you make no changes to your XML script generation, the post office you have used in the past for X12 Outbound Links will be the "Production" post office.

If you do not want to take advantage of the new "Test" versus "Production" post offices, you must set the two post offices to the same value. For more information, see the tag X12OBAppLink in the Trading Manager XML Autoload documentation.

Installing and upgrading Trading Manager databases

This section describes how to install or upgrade your Trading Manager databases. The steps differ based on whether or not you are installing the product for the first time or you are upgrading. Upgrade scripts differ based on you current version.
Select the proper script to follow below.

Trading Manager SQL scripts

The scripts mentioned below are in the <install dir> in the directory "sql" or "sql/Migration". SQL scripts names are prefaced with either "db2", "ora", "sql", or "sybase" denoting IBM DB2, Oracle, Microsoft SQL Server, or Sybase databases respectively. These prefixes are represented with an asterisk in the names listed
below.

Note: For Sybase users only - certain scripts do not have a "sybase" version. If there is no "sybase" version for the script mentioned, use the "sql" script. Also note all Sybase "load" scripts come in two separate scripts, which was required due size limitations of early Sybase tools.

Note that only "Sybase ASE" is supported.

Run each script individually, and examine the results for errors, and most importantly, commit the script if you do not have "autocommit" on. Do not proceed with the next script if an error is returned; contact IBM support or your DBA for assistance.

Backup your database before conversion. For all releases starting with TM 7.8, the database is upgraded in place, not in a separate database. Once upgraded, there is no script to reverse those changes.

Important: the start of each script contains additional information/changes needed that vary by database vendor. Read those comments before executing the scripts.

It is recommended to use you SQL tool's "Stop On Error" option if it has one.

Installation instructions

Follow these steps if you are installing IBM WebSphere Transformation Extender Trading Manager for the first time. If you have an existing version and you want to convert it, refer to the Upgrade instructions below instead. Trading Manager version 8.2.1.6 is a full installation but it requires multiple steps to bring the database up to the current version if you are using a database other than Microsoft Access.

Refer to "Trading Manager SQL Scripts", above, before proceeding.

To install a new database for Trading Manager 8.2.1.6, run the following scripts in this order. Do not run these scripts to convert an existing database:

*inst78.sql
*load78.sql
*update78to82.sql
*update82to821.sql
*update821to8211.sql
*update8211to8213.sql
*update8212or8213to8214.sql
*update8214to8215.sql
*update8215to8216.sql

All but the last script, *update8215to8216.sql, is in the sql/Migration directory.

Upgrade instructions

All upgrade instructions depend on the value of the "TM database version". To obtain this version, issue the following SQL statement and make note of the value returned. Use that value to find the proper instruction set to follow, below.

SELECT CurrentBEVersion FROM BackEndVersion

Refer to "Trading Manager SQL Scripts", above, before proceeding.

Run each script individually, examine the results for any errors, and most importantly, commit the script if you do not have "autocommit" on. Do not proceed with the next script if an error is returned; contact IBM support or your DBA for assistance.

Scripts must be run in the order presented here.

Converting from 8.2.1.5 (CurrentBEVersion = 8.2.1.5)

Run the following script:

*update8215to8216.sql

Converting from 8.2.1.4 (CurrentBEVersion = 8.3.2)

Run the following script:

*update8214to8215.sql

*update8215to8216.sql

Converting from 8.2.1.2 or 8.2.1.3 (CurrentBEVersion = 8.3.1)

Run the following scripts:

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

Note the database schema did not change between 8.2.1.2 and 8.2.1.3, so one script handles both vesions upgrade to 8.2.1.4.

Converting from 8.2.1.1 (CurrentBEVersion = 8.3)

Run the following scripts:

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

Converting from 8.2.1 (CurrentBEVersion = 8.2.1.3)

Run the following scripts:

*update821to8211.sql

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

Converting from 8.2 (CurrentBEVersion = 8.2.4)

Run the following scripts:

*update82to821.sql

*update821to8211.sql

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

Converting from 7.8 (CurrentBEVersion = 7.8.3)

Run the following scripts:

*update78to82.sql

*update82to821.sql

*update821to8211.sql

*update8211to8213.sql

*update8212or8213to8214.sql

*update8214to8215.sql

*update8215to8216.sql

Converting from releases prior to 7.8 (CurrentBEVersion 7.8.3)

Converting database prior to release 7.8 requires two main steps: convert your database to 7.8, and then following the "Converting from 7.8" steps above. To convert to 7.8, there are "PMUpdate" programs in the pmgr directory that are used. The steps are:

Create a new 7.8 database. Run the "*inst78.sql" and "*load78.sql" scripts to create this database in a new instance.
Convert your existing database by running the proper "PMUpdate" program found in the pmgr directory. The program will confirm you are using the correct version, so you cannot run the wrong one. Pick one of the following programs, set the "source" database to you current version, and the "destination" database to the 7.8 database created in step 1.

PMUpdate61to78.exe

PMUpdate70to78.exe

PMUpdate75to78.exe

PMUpdate76to78.exe

PMUpdate77to78.exe
3. Following the steps for "Converting from 7.8", above.

HIPAA Non-Addenda Queries

As mentioned above, any 4010 HIPAA Non-Addenda trade links you may have with a validation level of Type 2 or greater will be automatically set to "Type 1 only" when upgrading from a version prior to 8.2.

To see which trade links will be impacted by this change, you may run the following queries on the Trading Manager 7.8 database, which is the source database for the update SQL scripts. Note you may not have any such trade links; if so these queries will return zero rows.

As a conversion to Trading Manager 8.2 requires the source database to be at the 7.8 release, first convert your database to 7.8 before issuing the queries. Note the queries vary by database vendor; choose the correct query for your database.

Note: For Microsoft Access only -- Running these queries on an Access database requires the Microsoft Office Access application. Create a new "Query" using the SQL syntax below. If you do not have the Microsoft Office Access application, you may send your Access database (.mdb) to support for analysis.

Note: These queries can take some time to process if you have many trade links in your database.

Access, SQL Server, Sybase

SELECT DISTINCT X12InboundGroups.GS_VersionRelease,
X12IBTrans.TransactionID,
X12InboundGroups.GS_FunctionalID, X12TP_0.PartnerName,
X12AppPartners_0.ApplicationName, X12TP_1.PartnerName,
X12AppPartners_1.ApplicationName
FROM X12IBTrans,X12InboundGroups,
X12AppPartners X12AppPartners_0,
X12TradingPartners X12TP_0, X12IBTradeLink,
X12AppPartners X12AppPartners_1,
X12TradingPartners X12TP_1, X12Version
WHERE X12InboundGroups.X12IBTradeLinkNo =
X12IBTradeLink.X12IBTradeLinkNo AND
X12AppPartners_0.PartnerNo = X12TP_0.PartnerNo AND
X12IBTradeLink.FromExtAPNo =
X12AppPartners_0.ApplicationNo AND
X12IBTradeLink.ToIntAPNo =
X12AppPartners_1.ApplicationNo AND
X12AppPartners_1.PartnerNo = X12TP_1.PartnerNo AND
X12IBTrans.X12InboundGroupNo =
X12InboundGroups.X12InboundGroupNo AND
X12InboundGroups.TradeUnknownInd = 'T' AND
X12Version.VersionSubSet = 'H'
AND X12Version.GS_VersionRelease =
X12InboundGroups.GS_VersionRelease AND
RIGHT(X12InboundGroups.GS_VersionRelease,2) <> 'A1' AND
LEFT(X12InboundGroups.GS_VersionRelease,4) = '4010' AND
RIGHT(X12InboundGroups.ValType,6) <> '000000'
UNION SELECT DISTINCT X12InboundGroups.GS_VersionRelease,
X12IBTrans.TransactionID, X12InboundGroups.GS_FunctionalID,
' UNKNOWN', 'UNKNOWN', X12TradingPartners.PartnerName,
X12AppPartners.ApplicationName
FROM X12InboundGroups, X12Unknown_Link, X12IBTrans,
X12TradingPartners, X12Version,
X12AppPartners WHERE X12InboundGroups.X12Unknown_LinkNo =
X12Unknown_Link.X12Unknown_LinkNo
AND X12Unknown_Link.ToIntAPNo = X12AppPartners.ApplicationNo
AND X12AppPartners.PartnerNo = X12TradingPartners.PartnerNo
AND X12IBTrans.X12InboundGroupNo =
X12InboundGroups.X12InboundGroupNo AND
X12InboundGroups.TradeUnknownInd = 'U' AND
X12Version.VersionSubSet = 'H'
AND X12Version.GS_VersionRelease =
X12InboundGroups.GS_VersionRelease AND
RIGHT(X12InboundGroups.GS_VersionRelease,2) <> 'A1' AND
LEFT(X12InboundGroups.GS_VersionRelease,4) = '4010' AND
RIGHT(X12InboundGroups.ValType,6) <> '000000'

Oracle and DB2

SELECT DISTINCT X12InboundGroups.GS_VersionRelease,
X12IBTrans.TransactionID,
X12InboundGroups.GS_FunctionalID, X12TP_0.PartnerName,
X12AppPartners_0.ApplicationName, X12TP_1.PartnerName,
X12AppPartners_1.ApplicationName
FROM X12IBTrans,X12InboundGroups, X12AppPartners
X12AppPartners_0,
X12TradingPartners X12TP_0, X12IBTradeLink,
X12AppPartners X12AppPartners_1,
X12TradingPartners X12TP_1, X12Version
WHERE X12InboundGroups.X12IBTradeLinkNo =
X12IBTradeLink.X12IBTradeLinkNo AND
X12AppPartners_0.PartnerNo = X12TP_0.PartnerNo AND
X12IBTradeLink.FromExtAPNo =
X12AppPartners_0.ApplicationNo AND
X12IBTradeLink.ToIntAPNo = X12AppPartners_1.ApplicationNo AND
X12AppPartners_1.PartnerNo = X12TP_1.PartnerNo AND
X12IBTrans.X12InboundGroupNo =
X12InboundGroups.X12InboundGroupNo AND
X12InboundGroups.TradeUnknownInd = 'T' AND
X12Version.VersionSubSet = 'H'
AND X12Version.GS_VersionRelease =
X12InboundGroups.GS_VersionRelease
AND
SUBSTR(X12InboundGroups.GS_VersionRelease,
LENGTH(X12InboundGroups.GS_VersionRelease) - 1) <> 'A1' AND
SUBSTR(X12InboundGroups.GS_VersionRelease, 1, 4) = '4010' AND
SUBSTR(X12InboundGroups.ValType,2,6) <> '000000'
UNION SELECT DISTINCT X12InboundGroups.GS_VersionRelease,
X12IBTrans.TransactionID, X12InboundGroups.GS_FunctionalID,
' UNKNOWN', 'UNKNOWN', X12TradingPartners.PartnerName,
X12AppPartners.ApplicationName
FROM X12InboundGroups, X12Unknown_Link, X12IBTrans,
X12TradingPartners, X12Version,
X12AppPartners WHERE X12InboundGroups.X12Unknown_LinkNo =
X12Unknown_Link.X12Unknown_LinkNo
AND X12Unknown_Link.ToIntAPNo =
X12AppPartners.ApplicationNo AND
X12AppPartners.PartnerNo =
X12TradingPartners.PartnerNo AND
X12IBTrans.X12InboundGroupNo =
X12InboundGroups.X12InboundGroupNo AND
X12InboundGroups.TradeUnknownInd = 'U' AND
X12Version.VersionSubSet = 'H'
AND X12Version.GS_VersionRelease =
X12InboundGroups.GS_VersionRelease AND
SUBSTR(X12InboundGroups.GS_VersionRelease,
LENGTH(X12InboundGroups.GS_VersionRelease) - 1) <> 'A1' AND
SUBSTR(X12InboundGroups.GS_VersionRelease, 1, 4) = '4010' AND
SUBSTR(X12InboundGroups.ValType,2,6) <> '000000'

============================================================
4. KNOWN LIMITATIONS, PROBLEMS, AND WORKAROUNDS
============================================================

Versions not supported

The following versions are not supported in HIPAA and as such should not allow any acknowledgement above type 1. All existing tradelinks with the following versions are converted to only allow type 1 validation:

4010Xnnn

5010X220

5010X221

5010X222

5010X223A1

5010X224A1

5010X279

Creation of claim acknowledgement not supported

Trading Manager does not support the creation of claim acknowledgement, 5010X214 277CA. Use the Pack for HIPAA to obtain those.

Modifications required for Trading Manager to interct with EDI and HIPAA EDI

The following modifications are required in order for this version of Trading Manager to interact with the Pack for HIPAA EDI V4.4.0 and the Pack for EDI V2.8.0.x:

In the EDI pack for X12 V2.8.0.x, open the ansi5010.mtt type tree. Add version 006030 to the restriction list in the element VersionReleaseIndustryCd.
In the Pack for HIPAA EDI V4.4.0, open the hipaa_x12_type_1.mtt and make the following changes:

Add version 006030 to the restriction list for the element VersionReleaseIndustryCd under the V4010, V4050 and V5010 categories.
Add value 603 with a description of Transportation Equipment Registration to the restriction list for element TSIDCd under the V4010, V4050 and V5010 categories.

============================================================

5. NEW AND CHANGED BEHAVIOR
============================================================

Enhanced EDI support

This version of Trading Manager supports EDI V2.8.0, in order to support X12 6030 and EDIFACT 10a and 10b versions.

Enhanced HIPAA support

This version of Trading Manager supports only the Pack for HIPAA EDI V4.4.0.

============================================================
6. RESOLVED AUTHORIZED PROGRAM ANALYSIS REPORTS (APARS)
============================================================

For a list of APARS that are resolved in this version of the product, see the WebSphere Transformation Extender Trading Manager 8.2.1.6. Fix List.

============================================================
7. CONTACTING CUSTOMER SUPPORT
============================================================

Contact Customer Support at 1-800-IBM-SERV, or go to the support portal.

============================================================
8. 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, a nd 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
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce
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.
Linux is a registered trademark of Linus Torvalds 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.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office
UNIX is a registered trademark of The Open Group in the United States and other countries.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Oracle and all Oracle-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Other product and service names might be trademarks of IBM or other companies.

This product includes software developed by the Eclipse Project
(http://www.eclipse.org/).

[{"Product":{"code":"SSR2U3","label":"WebSphere Transformation Extender Trading Manager"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Trading Manager","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF025","label":"Platform Independent"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.2.1.6","Edition":"International;US","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Tips

Release notes for WebSphere Transformation Extender Trading Manager V8.2.1.6

Release Notes

Abstract

Content

Was this topic helpful?

Document Information

UID

Share your feedback

Need support?