Overview
In this tutorial you will use TIBCO ActiveMatrix BusinessWorks and TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® running on one machine to send an ORDERS message to a trading partner.
Normally the trading partner is represented by another B2B engine running on another machine. However, this tutorial is run on a single machine (Initiator) and when the ORDERS message is sent to the trading partner, the defined transport properties store the request in a directory on the local file system.
When you run the tutorial, the following steps occur:
|
1.
|
TIBCO Business Studio reads an XML file which contains the data for the ORDERS message. |
|
2.
|
TIBCO Business Studio parses the XML and sends the XML data to TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream®. |
|
3.
|
TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® converts the XML data to EDIFACT data. |
|
4.
|
TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® validates the EDIFACT data against an ORDERS guideline. |
|
5.
|
The validated EDIFACT data is bundled into an interchange for sending to the trading partner. |
|
6.
|
The FILE transport is used to simulate sending the interchange to the trading partner. By using the FILE transport, the EDIFACT interchange is written to a file on the local file system when it is sent to the trading partner. |
The following sections describe how to set up and run the tutorial. The steps involved in setting up TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® to run the tutorial are the same steps that have been discussed in Exchanging Documents of TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® User Guide.
|
•
|
EDI Guideline Authoring |
|
•
|
TIBCO ActiveMatrix BusinessWorks Process |