2.2.2 vendor.connect
vendor.connect uses messaging in conjunction with process.connect. The main requirement is to synchronize and respond to changes in System21 data such as purchase order updates. Figure
Flow of Information to vendor.connect after System21 Update
Trigger Program
process.connect
Trigger
Queue
Trigger Handler
|
|
|
|
| inter.connect |
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| System21 Export |
|
|
|
|
|
|
| Event |
|
|
|
|
|
|
| Export |
| |
|
|
|
|
|
|
|
|
| |||
| Queue |
|
|
| Connector |
|
|
|
| Queue |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Flow starts here
Rules
System21 Application
Application
Update
Export
Queue
Triggers
fired
Upload
Triggers
System21 database
@ctive Modular
Events
Mapping
XSLT Properties
Map Event Image
to XML BOD
inter.connect
Channel
Manager
BOD/Java
Method
Mappings
Message | Update | |
Reader | ||
|
WebSphere Application
Server
| Purchase Order |
| DB update |
| vendor.connect |
|
| via SQL |
| database | |
| EJB |
|
| ||
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
Key
System21
commerce.connect 
vendor.connect
Figure 2-4 vendor.connect messaging usage
MQSeries is used as the underlying message transport facility by process.connect.
Figure 2-5 shows the relationship between the .connect applications, the commerce.connect platform, System21, and the IBM middleware-WebSphere and MQSeries application server.
14Geac System21 commerce.connect: Implementation on the iSeries Server
