Batch Code for Ongoing Sync Requests

Batch Code	Description
D1-SIOPE	Transitions ongoing sync request out of the PENDING state. It is a generic batch process that is used for different sync processes. It has a couple of parameters that can be used to control which sync request business objects to process.
D1-SIOER	Transitions ongoing sync request out of the ERROR state.

Note: Depending on how sync requests are sent from Oracle Utilities Operational Device Management, it is possible that interdependent sync requests might be received out of order.

If you wish to control the order of processing the ongoing sync requests within, you can either introduce your own batch controls to replace D1-SIOPE (each batch control will have the specific ongoing sync business object defaulted in the input parameter); or you can submit D1-SIOPE several times, each time specifying a different ongoing sync business object in the input parameter. Otherwise, you can let the built-in retry processing within the ongoing sync request life cycle resolve the error by running D1-SIOER.

Batch Processes for Usage Transaction Processing

Batch Code	Batch Process Description
F1-SYNRQ	Runs the sync request. The Sync Request Monitor Process is a generic batch process that is used for different sync processes. It has a couple of parameters that can be used to control which sync request business objects to process.
F1-SYNIL	Creates an initial sync request business object for a particular maintenance object. The algorithm parameters for filtering records are provided, so implementations can further restrict the creation of initial sync requests to certain records within the maintenance object.

Configuring Outbound Messages

Configure the outbound messages to send them out to the integration layer. The following should be configured during the outbound message configuration:

• Message Sender

• Outbound Message Type

• External System

Message Sender

If Oracle Utilities Meter Data Management accesses Oracle Integration Cloud processes, create a Message Sender for each integration process.

To configure a Message Sender for an integration service:

1. Navigate to Admin > M > Message Sender.

2. Enter a unique Message Sender name and its description.

3. Populate the following values:

• Message Sender - Sender name in Oracle Utilities Operational Device Management

• Description - Sender description

• Invocation Type - Real-time

• Message Class - SOAPSNDR (SOAP Sender)

• Active - Select the checkbox

• Message Encoding - UTF-8 message encoding

4. On the Context tab, set values for the following context types:

• HTTP Header - SOAPAction:"Operation Name in Oracle Integration Cloud integration process wsdl"

• HTTP Login User - User ID to access Oracle Integration Cloud’s integration process

• HTTP Password - Password to access Oracle Integration Cloud’s integration process

• HTTP Method (POST/GET) - POST

• HTTP Timeout - 60

• HTTP Transport Method - SendReceive

• HTTP URL 1 - Set the URL to be accessed.

• If the URL value is invalid, use the additional HTTP URL types to set the complete URL.

• Message Namespace URI - Namespace from the respective Oracle Integration Cloud integration process wsdl