Commission / Decommission
The CommissionDecommission composite takes care of registering and de-registering a device with the head-end system.
Composite Properties
Property Name | Default Value | Description |
|---|
isExecutingCommissionReceived-Callout | true | Controls whether the Request Arrived callout executes. |
isExecutingCommissionCompleted-Callout | true | Controls whether the Request Completed callout executes. |
isExecutingDecommissionReceived-Callout | true | Controls whether the Request Arrived callout executes. |
isExecutingDecommissionCompleted-Callout | true | Controls whether the Request Completed callout executes. |
Composite WSDLs
Composite | Description |
|---|
CommissionDecommission Service | Entry point for the CommissionDecommission command. The operations are synchronous, so no additional WSDLs are needed. |
MR_ServerCallout | Reference describing the process callout. |
MR_ServerProxy | Reference describing the proxy used to invoke the head-end system. |
Process Flow
1. SGG/OUAF invokes MeterAddNotification/MeterRemoveNotification operation using CommissionDecommissionService.
2. Test whether MeterAddNotification or MeterRemoveNotification is invoked. In both cases, the following steps are common for both the operations.
3. Composite properties are loaded and local variables are initialized.
4. Both the Header and Body inputs are transformed to MultiSpeak format.
5. If required, execute a process callout in MR_ServerCallout.Assign updated data to head-end request.
6. Invoke MeterAddNotification/MeterRemoveNotification via the MR_ServerProxy to the head-end system.
7. If required, execute a process callout in MR_ServerCallout. Assign updated data to head-end response.
8. Transform Header and Body head-end responses to SGG/OUAF format.
9. Reply to SGG/OUAF with synchronous results.
Parent topic