Prerequisites

Before using this tutorial you must install and be familiar with the IBM WebSphere Business Integration product.

About the tutorial

The tutorial consists of a request processing and an event notification scenario. The scenarios feature companies A, B and C. Trading relationships exist between companies A and C, and A and B. The companies have standardized communication using AS/2 protocol. All companies use the iSoft Commerce Suite server to implement AS/2. Company A has deployed the WebSphere adapter for iSoft, which facilitates communication with the iSoft Commerce Suite server and, consequently, its trading partners.

In the scenario, Company A publishes a catalog to Companies B and C. Companies B and C place orders using the information in the catalog. More specifically, an object representing the catalog, Sample_ISoft_Catalog is passed to the iSoft adapter, translated to an XML message, and placed in a queue. The iSoft Commerce Suite server deployed by Company A gets the message from the queue and transports it to Company B's iSoft Commerce Suite server, which persists the message in the file system. (In a real world scenario, an application on Company B's network would pick up and process the file at this time.) When Companies B or C place an order, their respective iSoft Commerce Suite servers pass an order to Company A's iSoft Commerce Suite server. Company A's iSoft Commerce Suite server places the order in queue, the iSoft adapter de-queues the order, translates it to a business object and passes it to an integration broker. In this tutorial all iSoft Commerce Suite servers run on the same machine and use the same queue manager. However, by updating the information in the iSoft Commerce Suite server config files (icssvr.cfg_a and icssvr.cfg_b), you could modify the scenarios to use agents running on separate machines and relying on different queue managers.

Before you begin

Before proceeding with this tutorial, make sure that:

Copyright IBM Corp. 1997, 2004