Search results

This paper describes the factors involved in measuring WebSphere Data Interchange Version 3 Release 2 performance when using Data Transform (DT) maps. Some executions with variations in message size number of messages are show. The tests are run on both Intel and IBM AIX hardware.

This document describes how to integrate the (IBM) Crossworlds Interchange Server v4.0.1 product and WebSphere Data Interchange v3.2 translation engine. It shows how to exchange Electronic Data Interchange (EDI) transactions with your trading partners.

The SAP IDOC Formatter Utility is a field developed program that converts SAP IDOCs into a WDI Import / Export format. The attached document shows how to extract IDOCs from SAP, execute a conversion, and import the converted output into WebSphere Data Interchange.

This document explains the steps needed to install the SAP IDOCs Utility for creating a WebSphere Data Interchange import file. The file created is a WDI Data Format representation of the SAP IDOC.

This document explains how to exploit WebSphere MQSeries and the MQSeries Link for SAP R/3 to avoid the need for files.

This document describes the replication of a customer scenario in an AIX environment and the performance attained using WebSphere Data Interchange. The results are specific to the environment established for this test, but the results are indicative of WDI performance with DT maps.

This document describes the SAP Status Reporting capability of WebSphere Data Interchange Version 3 Release 2. It describes the commands and keywords supported and the means of processing SAP Status records.

This document describes the procedures (with screen captures to illustrate) required to use the Message Repository Manager (MRM) featured within WebSphere MQ Integrator (WMQI) v2.1 to transfer Electronic Data Interchange (EDI) messages from WebSphere Data Interchange (WDI) to interface with the customer's existing systems.

This guide is intended for users who desire to integrate WebSphere Data Interchange translation engine and the Cyclone Interchange B2B gateway product. It is assumed users have some understanding of the WebSphere Data Interchange and CycloneInterchange products. If you are new to WebSphere Data Interchange, it is highly recommended that you first review the WebSphere Data Interchange User's Guide. The CycloneInterchange Administration Guide is also a useful resource. This document assumes some experience wo

This IBM Redpaper describes the implementation of AS/2 client products, iSoft's P2PAgent and Trading Partner Interchange, in an environment with multiple trading partners. First, we discuss the implementation of TPI between two trading partners and then that configuration is extended with another partner that is using iSoft's P2PAgent. The next step in the implementation of TPI is the interaction with back-office applications. We describe how to work with the EDI translation product WebSphere Data Interchange. This Redpaper explains both the inbound and outbound flow for a purchase order and a purchase order acknowledgement. Finally, we look at the use of the Interchange Server as the integration platform and how the ICS interacts with WebSphere Data Interchange and TPI. The last chapter of this Redpaper discusses the interoperability of AS/2 providers. The first part of that chapter discusses how trading partners using different AS/2 providers can interact with each other. A network of three partners is considered, where two partners are using TPI and another partner is using iSoft's P2PAgent. The second part of this last chapter discusses interoperability of AS/2 providers within a given enterprise. We first implement an integration solution for UCCnet that interacts with the TPI. In two steps, we demonstrate that this integration solution can also work with a different AS/2 provider. For more up-to-date information about WebSphere B2B, please refer to the following books: B2B solutions using WebSphere Partn