Siebel Order Management Infrastructure Guide > Signals >
About the Signals Mechanism
Within Siebel order management, you use the Signals mechanism to invoke configurable business logic. Signals are used to hold together all the C/OM services, and they are used to call external services. You configure signals in the run-time client.
Nearly all buttons and engines within Siebel order management invoke business logic by raising a signal. The business logic invoked comes in the form of one or more business service methods or workflows.
Signals are versioned objects. The numbering assigned to a signal version means that a new version of a signal can be developed while you are using the current version in the same production environment.
A signal action property specifies the business service or workflow to invoke when the signal is raised. Signal action parameters are the input arguments to signal action workflows or business service methods.
Components of the Signals Mechanism
Figure 4 shows how a signal created in the Administration - Order Management > Signals view is routed through a signal dispatcher to invoke a business service method or workflow.
Figure 4. Signals Components
Administer signals using the Administration - Order Management screen > Signals view. Use the Signals view for creating new signals, working with existing signals, and releasing signals into production. In the Versions list applet, click the Work Space hyperlink to access the Actions and Properties tabs, and the Parameters list applet, for the selected signal.
Signals are dispatched by the Context Service business service. The Context Service business service reads and caches signal definitions, and then when a business component raises the signal, Context Service executes the appropriate business service or workflow.
For more information on the Context Service business service, see Variable Maps and Context Service Business Service.
All applications supported by the Siebel order management infrastructure can be sources of signals. A signal can be invoked by any C/OM business component. Signals are not supported on non-C/OM business components.
Signals are invoked through the standard InvokeMethod call. If the method is not handled by logic or script on the source business component, then the signal dispatcher (Context Service business service) is invoked to handle the signal.
A signal action can be either a business service method or a workflow. By setting the Service Type field in Administration - Order Management > Signals > Actions, you define whether the action is a business service method or a workflow.