Batch Processes for Outbound Sync Requests
Note: To generate initial sync requests, submit the F1-SYNIL batch job. To transition Sync Requests out of the Pending state, run the F1-SYNRQ batch job.
For more information about the sync request process, the business objects, maintenance objects, and other components used for this process, refer to the Data Synchronization section in the Oracle Utilities Framework User Guide.
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
For Oracle Utilities Operational Device Management to access Oracle Integration Cloud services, create a Message Sender for each integration service.
1. Navigate to the Message Sender page.
You can do so from the Admin menu or from the Search menu.
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 the respective 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
Example Message Sender for Integration Services
Asset Device Sync Request Process
Contact Sync Response Process
Install Event Asset Node Sync Response Process
SP Node Sync Response Process
Outbound Message Type
To create a new outbound message type for each integration process, do the following:
1. Navigate to the Outbound Message Type page.
You can do so from the Admin menu or from the Search menu.
2. Enter an outbound message type, description, and detailed description.
3. Select the outbound message business object created for a specific service.
Example Outbound Message Types for Integration Points
Asset - Device Sync Integration Point Outbound Message
Service Point - Node Sync Integration Point Outbound Message
Contact Sync Integration Point Outbound Message
Install Event - Asset Location Sync Integration Point Outbound Message
External System
To create a new external system to support the integration:
1. Navigate to the External System page.
You can do so from the Admin menu or from the Search menu.
2. Enter a unique external system and description.
For example: Name = MDM_ICS, Description = Oracle Utilities Meter Data Management
3. Set the Our Name in Their System field to ODM.
4. Associate the outbound message types created to the external system.
5. For each outbound message type, set the following:
• Outbound Message Type - Set the outbound message type created for Oracle Utilities Operational Device Management outbound queue.
• Processing Method - Real-time
• Message Sender - Set the message sender created for the queue.
• Date/Time Format - XSD
• Namespace Option - Configured on Sender
If Oracle Utilities Operational Device Management sends messages to the integration service, use the Message Senders created for each integration.
For more information about Message Senders, refer to the
Message Sender section.
External System Details
Managing Catalog Service
The catalog service is used by Oracle Integration Cloud to communicate with the respective application. This is configured in Catalog URL in the Oracle Integration Cloud connection.
To configure the catalog service in Oracle Utilities Operational Device Management:
1. Navigate to the Web Service Catalog page.
You can do so either from the Admin menu or the Search menu.
The external system and inbound web services are added to the catalog.
2. To get the catalog URL, append “webservices/builtin/ServiceCatalog?wsdl” to the Oracle Utilities Operational Device Management URL.
For example: http(s)://<ODM_HOST>:<ODM_PORT>/<ContextRoot>/webservices/builtin/ServiceCatalog?wsdl
For more information about configuration, refer to the Oracle Utilities Operational Device Management documentation.