Common
The Common composite is a repository for files and logic that is used by other composites. For instance, the Proxies and default implementations of Process Callouts are defined in the Common composite.
Composite Properties
None.
Composite WSDLs
Callout Services
Process Callouts are customization points for integrators with identical inputs and outputs based on head-end formats. The Common composite contains default implementations in which incoming data is reflected back in an identical state. Each of the following is a Mediator component and uses an “echo”-type definition.
Process Callouts are usually associated with boolean composite properties which control whether they will be executed. They are activated by default so uses can easily inject their customizations, but setting the properties to false can be a performance optimization. When set to false, the associated Process Callout will not be made and execution will continue normally.
|
Service |
Description |
|---|---|
|
OA_CalloutService |
Used when the asynchronous reply in DeviceStatusCheck arrives. |
|
MR_CalloutService |
Used during Commission/Decommission and OnDemandRead operations. |
|
CB_CalloutService |
Used by the asynchronous callback processes of OnDemandRead and Connect/Disconnect. |
|
CD_CalloutService |
Used by Connect/Disconnect. |
|
OD_CalloutService |
Used in DeviceStatusCheck. |
Proxies
Placing all the proxy web services in the Common composite creates a place to conveniently set endpoints. Each is a Mediator component which passes the data to the head-end system without modification
|
Proxy Web Service |
Description |
|---|---|
|
OD_ServerProxy |
Used to transmit a DeviceStatusCheck request to the head-end system. |
|
CD_ServerProxy |
Used to transmit a Connect/Disconnect request to the head-end system. |
|
MR_ServerProxy |
Used to transmit an OnDemandRead request to the head-end system. |
Other
AuxiliaryRoutinesService: A container defining helpful, commonly used functions:
-
FindExpTime: Many MultiSpeak functions contain an expTime element, which is used to deliver the length of time to wait for the command to complete before failing. (The included test harness does not support timeouts.) If the input to the command composite does not contain this timeout, the process will read from its properties the years, months, days, hours, minutes, and seconds to wait for a result. This web service utilizes a Java method to combine these inputs into the proper XML field used in the MultiSpeak API. The properties are also used to control the timeout wait period of asynchronous callbacks within a command's BPEL process.
-
FindTimeout: When the expTime element and units are supplied as input, it is usually still necessary to compute the timeout used in asynchronous callbacks. This method accepts the MultiSpeak fields and replies in the “P0Y0M0DT0H0M0S” format understood by BPEL.