Re: RE: XPI....
Hi Gigi,
1) The outbound activities are done by the XBP's (eXtended Business Process). Take for instance CustomerMasterManageNotify for example. The canonical defines the message. The adapter exposes the MBF's (Master Business Functions) or tables and the XBP defines the specific MBF call order, mappings, and scripted operations necessary to actually create or interpret the canonical.
The adapter creates the XML file.
As far as I know XML is the only format.
2) Yes the XREF tables that need to be loaded in the ATC cross-reference tables are stored in a work table called atc_xref_load and they can be installed on Oracle, SQL, or DB2.
Here is the process that goes on. On OneWorld you make an entry. The entry is sent in native OneWorld format to the OneWorld Adapter. The OW adapter sends the entry in OW native format to the XPIe Broker. The XPIe Broker sends the entry to the ATC Agent in OW native format. The ATC agents does a lookup on the Cross Reference tables and converts the entry to canonical format. The ATC agent then sends the entry in the new format (Ariba Native Format) back to the XPIe Broker. The XPIe Broker sends the entry to the Ariba Adapter in Ariba native format. The Ariba adapter then sends the entry to the Ariba application.
Hope this helps.
Robby
XESP17 on NT4/SQL7, XEU3SP18 on W2K/SQL2K, XEU3SP16.1/A73 & JAS on AS400/W2K/SQL7