IBM SG24-6526-00 사용자 설명서

Geac System21 commerce.connect: Implementation on the iSeries Server

For vendor.connect, Figure 2-2 shows the relationship between the controlling servlet and the 
vendor.connect subsystems.

Figure 2-2   vendor.connect dependencies

call.connect components are designed to be extensible, reusable, and replaceable. This 
means that the business functionality can be extended without needing to cut and paste 
entire programs. This helps to reduce maintenance overhead and allows existing code to be 
reused.

The term 

 refers to the sending of structured information between two or more 

subsystems. Typically the message is sent asynchronously. That is that the sender can 
continue to run without waiting for a reply from the receiver. Also, the sender and receiver 
typically run as separate processes and possibly on physically separate machines.

Both call.connect and vendor.connect use asynchronous messaging to meet specific 
requirements:

call.connect uses messaging to meet two requirements:

򐂰

To send information back to the client user interface (UI) such as “the order has been put 
on hold due to credit problems”, or “a given item is out of stock”

򐂰

To allow for time-consuming steps to be completed asynchronously, for example, order 
completion when the order is actually committed into System21

contract

shipment

purchaseorder

Generic

Servlet

supplier

fulfillment