Solution Overview
The technical aspects involved in the integration between Oracle Utilities Digital Asset Cloud Service and Oracle Field Service are:
The integration layer consists of integration processes deployed on Oracle Integration Cloud.
The integration processes interact with other applications using the following adapters:
Oracle Utilities Adapter interacts with the Oracle Utilities Digital Asset Cloud Service APIs.
Oracle Field Service Cloud Adapter interacts with the Oracle Field Service APIs.
REST Adapter interacts with other Oracle Field Service REST APIs not in the Oracle Field Service Adapter.
In the Oracle Utilities Digital Asset Cloud Service initiated processes, outbound messages are sent.
Oracle Utilities Digital Asset Cloud Service uses Inbound Web Services to receive messages.
In the Oracle Field Service initiated processes, events are triggered to send the outbound messages.
Oracle Field Service uses REST APIs to receive the messages.
The integration patterns used in this solution are:
Synchronous
The synchronous integration process:
1. Receives request message from Oracle Utilities Digital Asset Cloud Service.
2. Transforms the message from Oracle Utilities Digital Asset Cloud Service format to the target format. Lookups are used for data translations.
3. Invokes Oracle Field Service.
4. Transforms the message (after invoking Oracle Field Service) from the Oracle Field Service format back to the source format. It sends back an acknowledgment/synchronous response.
5. In case of any error, the global fault handler catches them and sends the transformed error message to Oracle Utilities Digital Asset Cloud Service.
6. An optional email notification is sent to the respective users as configured.
Synchronous integration process diagram
One-way Asynchronous
The one-way asynchronous integration process:
1. Receives request message from Oracle Field Service.
2. Transforms message from the source to the Oracle Utilities Digital Asset Cloud Service format. Lookups are used for data translations.
3. Invokes target application to send the request message.
4. In case of any error, the global fault handler catches them.
5. The error instance can be re-submitted from Oracle Integration Cloud. Refer to the Error Handling section in Configuring Lookups, Error Handling, and Email Notifications for more details. One-way asynchronous integration process diagram