The ATP (AvailableToPromise) collaboration is used to enable eBusiness and customer-care applications to access product availability information from an inventory management or supply chain application. The following are possible business scenarios for this collaboration:
ATP uses the generic ATP business object to synchronize product availability data.
This section includes information on port bindings and required steps for setting up collaboration objects based on ATP. For information on standard features, ports, and configuration properties for collaboration templates, see the Collaboration Development Guide. For general information on creating collaboration objects, see the System Implementation Guide.
Figure 1 illustrates the ATP collaboration's ports, as they are displayed in System Manager.
Figure 1. ATP collaboration's ports
Note: To prevent the collaboration object from using a port, bind that port to the Port connector. Binding the port indicates that the port is unused without causing the collaboration object to provide additional functionality.
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ATP | Destination (supplier's) application connector | Sends a reference-valued business object to retrieve the full-valued business object. | Retrieve |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ATPLine | Destination (supplier's) application connector | Sends a reference-valued business object to retrieve the full-valued business object. | Retrieve |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ATP | The source (buyer's) application connector | Receives the triggering business object. At the end of a synchronous call, this port also returns the triggering business object to the source application when the collaboration ends successfully. |
Create Retrieve Update Delete |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ATP | The destination (supplier's) application connector | Sends the triggering business object out of the collaboration. Normally this is bound to the destination application, but it can be bound to a wrapper collaboration. |
Create Update Delete |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ATPLine | The destination (supplier's) application connector | Sends the triggering business object's contained line object out of the collaboration. Normally this is bound to the destination application, but it can be bound to a wrapper collaboration. |
Create Update Delete |
This section illustrates the process logic for this collaboration template:
Figure 2 illustrates ATP's process logic.
Figure 2. ATP Collaboration's process logic
This collaboration template uses the following standard collaboration business processes:
For information on these processes, see the Collaboration Development Guide.
Figure 3 illustrates ATP's Iterate process logic.
Figure 3. ATP Collaboration's Iterate process logic
InterChange Server Express can roll back a transaction when any step in a transactional collaboration fails. For example, when ATP is a member of a collaboration-object group that participates in a transactional collaboration, its actions are one subtransactional step of a larger transaction. If any step in the collaboration-object group's business process fails, the transactional collaboration details how InterChange Server Express rolls back the processing of every collaboration in the group.
When an ATP collaboration object is used independently of other collaboration objects or the collaboration object's From port is bound to a source application rather than to another collaboration, its process comprises a single transactional step. In such a situation, it is not necessary to perform rollback.
To cause a collaboration object or a collaboration-object group to perform rollback requires modification of the collaboration template. To understand transaction processing in the IBM WebSphere Business Integration Server Express Plus system, see the System Implementation Guide. For information about adding transaction processing to the collaboration template, see the Collaboration Development Guide.
To extend the collaboration object to handle transaction processing, complete the following steps:
This section describes the standard properties and collaboration template-specific properties for this collaboration template:
This collaboration template uses the following standard configuration properties for collaboration templates:
For information on these configuration properties, see the Collaboration Development Guide.
In addition to its standard configuration properties, this collaboration template has the configuration properties described below.
Property name and explanation | Possible values | Default value |
---|---|---|
ATP_OR_ATPLINE This property allows the user to decide whether the collaboration will send the entire ATP object, possibly containing multiple line items, into the destination or whether it will send one line item at a time. If set to "ATPLine", the collaboration will iterate through the line items contained in the batch object and send each one into the destination application individually. |
ATP, ATPLine | ATP |