Solution Overview
The technical aspects involved in the integration between Oracle Utilities Digital Asset Cloud Service and Oracle Utilities Grid Edge Distributed Energy Resources Management System 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 DACS REST APIs and NMS-DERMS REST APIs.
• REST Adapter interacts with Oracle Cloud Infrastructure Object Storage.
• REST APIs to list, get, and rename files DERMS REST APIs with file attachments.
• FTP Adapter interacts with Oracle Utilities Digital Asset Cloud Service On Premise Server to list, get, and rename files in the server.
• Email notification is optional. Configure the property name email.flag in the OUTL-BRT-DACS_DRMS_ConfigProps lookup to 'true' to receive email notification when errors are encountered. By default, this is set to 'true'.
• The recipient(s) of the email notification sent out for technical errors is configured in the 'to' recipients of the OUTL-BRT- DACS_DRMS_Email_ID lookup. These are sent to the administrators of the applications.
• In the Oracle Utilities Digital Asset Cloud Service initiated processes, batch processes are used to send the outbound messages or create a file and uploaded to the content server defined for an external application to pull for processing. Oracle Utilities Grid Edge Distributed Energy Resources Management System uses REST APIs to receive the messages.
• In the Oracle Utilities Grid Edge Distributed Energy Resources Management System initiated processes, events are triggered to send the outbound messages and Oracle Utilities Digital Asset Cloud Service uses REST inbound web services (IWS) to receive the messages.
The integration patterns used in this solution are:
Synchronous
The synchronous integration process:
1. Receives request message from the source application.
2. Transforms the message from source format to the target format. Lookups are used for data translations, if applicable.
3. Invokes the target application.
4. Transforms the response message from the target format back to the source format. It sends back the response to the source application.
5. In case of any error, the global fault handler catches them and sends the transformed error message to the source application.
6. An optional email notification is sent to the respective users as configured. 
One-way Asynchronous
The one-way asynchronous integration process:
1. Receives request message from the source application.
2. Transforms message from the source to the target format. Lookups are used for data translations, if applicable.
3. Invokes target application to send the request message.
4. In case of any error, the global fault handler catches the error.
5. An optional email notification is sent to the respective users as configured.
6. 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. 