Itron OpenWay Payload Processing
By default, payload processing for the Itron OpenWay adapter works differently than it does for other adapters, but it can be configured to work like other adapters in which payloads are saved to a staging area in Oracle Object Storage and then processed via batch processing. For large volumes, saving to the staging area provides better performance because it allows the web service to simply drop off the payload, and the collection of saved payloads can then be processed in multiple batch processing threads.
-
Object Storage Locations: Itron OpenWay payload processing uses object storage locations (including Key Rings, Key Pairs and File Storage Configuration extendable lookup values) to capture usage and event payloads or exceptions received from the head end system.
-
Head End Systems and Extendable Lookups: Itron payload processing uses head end system and extendable lookup configuration in the same manner as other adapters.
-
SGG Payload Processing Configuration Extendable Lookup Values: These values define payload processing details for the Itron head end system (which is referenced on the payload processing batch control).
-
Payload Processing Batch Controls: A batch control used for payload process (based on a template batch control provided with the base package)
-
Master Configuration: Configuration settings for Itron OpenWay payload processing, including specifying the use of a payload staging area in Object Storage. See Itron OpenWay Master Configuration for more information about configuring the system to process Itron OpenWay payloads and exceptions.
Deferring Batch Processing
We recommend configuring a monitor process on the Pending status of the Initial Load initial measurement business objects so that the VEE and measurement creation processes can be deferred to batch processing.
Deferring processing has the following additional benefits:
-
It can ensure chronological processing for scalar reads which provides more efficient processing. Processing scalar reads out of order can result in additional work as reconciliation initial measurements will be created and processed to true up the consumption calculations.
-
It can ensure measuring components are processed in order based on their relationships. For example, if a scalar channel is configured as the check channel for an interval channel, the scalar channel will be processed first so that its data is available for sum checks and any interval gap filling required.
Configuration
Configuring deferred processing involves adding the “IMD Monitor – Physical Devices” Batch Control as the Monitor Process on the Pending status to the following business objects:
-
D1-InitialLoadIMDInterval
-
D1-InitialLoadIMDScalar
When initial measurement processing is deferred it will be necessary to schedule the “IMD Monitor – Physical Devices” Batch Control to run more frequently. It should be scheduled such that it runs with a higher thread count immediately after the Itron Scheduled Reads cycle has completed and with fewer threads throughout the rest of day to pick up any other initial measurements that might be received (such as those received via On Demand Read commands).
Default Processing — Not Recommended
By default, payload processing for the Itron OpenWay adapter works differently than it does for other adapters. Instead of using batch processing, Itron payloads are processed as they are received. Payloads and exceptions sent from the Itron OpenWay head end system are received via inbound web services that invoke business components that process the payloads and exceptions as they are received rather than posting them to object storage locations. See Itron OpenWay Inbound Web Services for more information about the inbound web services used to receive payloads and exceptions from the Itron OpenWay head end system. This approach is not recommended.