The ServiceOrderManagement collaboration template enables telecommunications (telco) companies to automate the data piping and data synchronization functionality commonly required between order entry, order management, billing, and provisioning applications.
Customer care applications generally require customer account information as well as order information to appropriately bill customers for services.
Provisioning applications can require more detailed information on the order to activate a service. This detailed information can include service-specific information such as design and circuit layout records. Once service is activated, the order information and status need to be sent to the billing application.
ServiceOrderManagement uses the generic ServiceOrder business object to synchronize service order data between the various customer care and provisioning applications.
This section includes information on port bindings and required steps for setting up collaboration objects based on ServiceOrderManagement. 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.
Figure 1 illustrates ServiceOrderManagement's ports, as they are displayed in System Manager.
Figure 1. ServiceOrderManagement collaboration'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.
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ServiceOrder | The destination application's connector | Sends a reference-valued business object to retrieve the full-valued business object. |
Retrieve |
Business object | Bound to | Function | Verbs used |
---|---|---|---|
ServiceOrder | Source application's connector or calling collaboration | 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 |
---|---|---|---|
ServiceOrder | The destination application's connector |
Sends the triggering business object out of the collaboration |
Create Update Delete |
ServiceOrderManagement is designed to be used as a stand-alone collaboration. To set up ServiceOrderManagement as a stand-alone collaboration object, follow these steps:
This section illustrates the process logic for this collaboration template:
Figure 2 illustrates ServiceOrderManagement's process logic.
Figure 2. ServiceOrderManagement collaboration's process logic
This collaboration template uses the following standard collaboration business processes:
For information on these processes, see Required Documents for Creating Collaboration Objects.
InterChange Server can roll back a transaction when any step in a transactional collaboration fails. For example, when ServiceOrderManagement 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 should roll back the processing of every collaboration in the group.
When a ServiceOrderManagement 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 modifying the collaboration template. To understand transaction processing in the WebSphere business integration system, see the Technical Introduction to IBM WebSphere InterChange Server. For information on adding transaction processing to the collaboration template, see Required Documents for Creating Collaboration Objects.
To extend the collaboration object to handle transaction processing, complete the following steps:
Note: ServiceOrderManagement does not have unique configuration properties. All of its properties are standard.
This collaboration template uses the following standard configuration properties for collaboration templates:
For information on these configuration properties, see Required Documents for Creating Collaboration Objects.
To view an explanation of the messages of this collaboration template, launch the Log Viewer and open the collaboration template's message file. To launch the Log Viewer and open the collaboration template's message file: