The PrequalifyProduct collaboration template is used to determine whether a service can be offered to a specified customer. This collaboration communicates with a provisioning system.
PrequalifyProduct uses the Generic PrequalInfo business object to represent a customer's prequalification to purchase a product. PrequalInfo contains customer information such as the customer's location, as well as information on the offered service.
This collaboration template uses the ProcessContext attribute of generic business objects to maintain process information between two or more collaboration objects. In order to maintain this information, the collaboration object performs the following actions, starting from when it receives a triggering business object:
This section includes information on port bindings and required steps for setting up collaboration objects based on this collaboration template. For information on standard features, ports, and configuration properties for collaboration templates, and for general information on creating collaboration objects refer to the documents listed in Required documents for creating collaboration objects.
The following diagram illustrates PrequalifyProduct's ports:
Note: To keep the collaboration object from using a port, bind that port to the Port connector. Doing so indicates that the port is unused without causing the collaboration object to provide additional functionality.
The following tables describe bindings for the ports of two separate collaboration objects based on this collaboration template. The purpose of the two instances is described in Setting up the collaboration object.
Business object | Bound to | Function | Verbs used |
---|---|---|---|
PrequalInfo (Instance A) | WebSphere MQ Workflow | Receives the triggering business object | Prequalify |
PrequalInfo (Instance B) | Provisioning system | Receives the triggering business object | ReturnResult |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ServiceLocationData (Instance A) | Provisioning system | Sends the triggering business object out of the collaboration object | Validate, Qualify |
ServiceLocationData (Instance B) | WebSphere MQ Workflow | Sends the triggering business object out of the collaboration object | ReturnResult |
Since this collaboration object is assumed to handle a long-running process, a special setup for an asynchronous call model is required. In order to set up the collaboration object for an asynchronous call model, complete the following steps:
This section illustrates the following business processes for this collaboration template:
This section illustrates PrequalifyProduct's process logic for its supported verbs indicated below:
The following diagram shows the process logic for this collaboration template's ReturnResult verb.
The following diagram shows the process logic for this collaboration template's ReturnResult verb.
This collaboration template uses the following standard business processes:
This collaboration template uses the following standard configuration properties for collaboration templates: