Integration Flows
The integration supports the following processes:
Enrollment Request (Oracle Utilities Grid Edge Distributed Energy Resources Management System Initiated)
When customers enroll their smart controllable device(s) in a program through the head-end system provider or aggregator/vendor, like Ecobee or Google Nest, the enrollment requests are sent to Oracle Utilities Live Energy Connect.
This integration process sends the enrollment request that Oracle Utilities Grid Edge Distributed Energy Resources Management System received from Oracle Utilities Live Energy Connect to Oracle Utilities Digital Asset Cloud Service. The integration then sends the list of responses for each enrollment request back to Oracle Utilities Grid Edge Distributed Energy Resources Management System when the process is completed.
The following diagram shows a graphical representation of the Enrollment Request integration process. 
Processing Details
The integration process deployed on Oracle Integration Cloud is exposed as a REST API.
It performs the following activities:
1. The process is triggered when it receives a request message from Oracle Utilities Grid Edge Distributed Energy Resources Management System. The incoming request message can contain multiple enrollment requests, but the DACS REST API only process a single enrollment request.
2. The integration loops through each incoming request:
• Transforms the enrollment request payload from Oracle Utilities Grid Edge Distributed Energy Resources Management System to Oracle Utilities Digital Asset Cloud Service format.
• Invokes the Program Enrollment DACS REST endpoint to create the enrollment in Oracle Utilities Digital Asset Cloud Service. The enrollment is created in PENDING status.
• Responses per enrollment request coming from Oracle Utilities Digital Asset Cloud Service are collected and later returned back to Oracle Utilities Grid Edge Distributed Energy Resources Management System. If an error is encountered, the process continues to the next enrollment request.
• If the enrollment is successfully created, it will return the enrollment ID.
• If Oracle Utilities Digital Asset Cloud Service returns an ERROR, it will be captured and returned inside the collection.
3. After all the records are processed, it transforms the Oracle Utilities Digital Asset Cloud Service response into the Oracle Utilities Grid Edge Distributed Energy Resources Management System response payload. It will set the overall ackType field in the response with the following code:
• SUCCESS, if all enrollment responses from Oracle Utilities Digital Asset Cloud Service have the SUCCESS value in the responseCode field.
• FAILURE, or ERROR if at least one responseCode within the enrollment responses from Oracle Utilities Digital Asset Cloud Service contains one of those values.
4. For technical faults encountered in the process (such as Oracle Utilities Digital Asset Cloud Service unavailable), the integration will set the ackType to “FAILURE”.
• If it encounters a technical error while processing an enrollment request, but can continue processing the collection, the error details will be captured inside the response back to Oracle Utilities Grid Edge Distributed Energy Resources Management System; OIC does not have to send an email since Oracle Utilities Grid Edge Distributed Energy Resources Management System will have the response already.
• If it faults and cannot continue processing the collection, Oracle Integration Cloud will try to send a response back to Oracle Utilities Grid Edge Distributed Energy Resources Management System with the details and will also send an email notification with the error details via a common error handler to the users configured in the 'to' recipients of the OUTL-BRT-DACS_DRMS_Email_ID lookup.
• If Oracle Integration Cloud is trying to send a failure response, but that fails, it will send an email notification with the error details via a common error handler to the users configured in the 'to' recipients of the OUTL-BRT-DACS_DRMS_Email_ID lookup.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Digital Asset Cloud Service and Oracle Utilities Grid Edge Distributed Energy Resources Management System artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities NMS-DERMS DACS Enrollment Request |
Integration Process Identifier | OUTL-BA-DRMS_DACS_ENROLLRQ |
Integration Package Name | outl.ba.dacs.derms.01.22.3000 |
Source Connection (Oracle Utilities Adapter) | Oracle Utilities REST DRMS for DACS-DRMS |
trigger | • DERMS Service Name: NMS-DACSOutbound • openAPIUrl: https://{host}:{port}/nms-ofs/ • outbound/openapi.json • OperationId: enroll • Method: POST • URI: /enroll-to-dacs |
Target Connection (Oracle Utilities Adapter) | Oracle Utilities REST DACS for DACS-DRMS |
invoke | • Web Service Name: X1-ProgramEnrollment • Computed URL: https://{host}:{port}/{tenant}/{domain}/ccs/rest/apis/cross/digitalAssets/programEnrollments • Method: POST • URI:/enroll |
Local Integrations | Oracle Utilities DACS NMS-DERMS CommonErrorHandler |
Lookups Referenced
The following table describes the customized properties referenced in the integration. For more information about the lookup properties, refer to Configuring Lookups, Error Handling, and Email Notifications.
DVM | Property |
|---|---|
OUTL-BRT-DACS_DRMS_ConfigProps | • notification.email.flag • notification.type.email |
OUTL-BRT-DACS_DRMS_EnrollmentStatus | • DACS_status • DRMS_responseCode |
OUTL-BRT-DACS_DRMS_AssetSpec | • DRMS_MAKE_MODEL • DACS_SPECIFICATION |
OUTL-BRT-DACS_DRMS_AssetType | • DRMS_ASSET_TYPE • DACS_ASSET_TYPE |
Enrollment Sync
When customers enroll, unenroll, or replace their smart controllable device(s) in a program successfully in Oracle Utilities Digital Asset Cloud Service, the enrollment information is sent to Oracle Utilities Grid Edge Distributed Energy Resources Management System.
This integration process synchronizes the enrollment information from Oracle Utilities Digital Asset Cloud Service to Oracle Utilities Grid Edge Distributed Energy Resources Management System. The integration then sends an acknowledgment back to Oracle Utilities Digital Asset Cloud Service.
The enrollment synchronization and acknowledgment are handled by two Oracle Integration Cloud integration flows:
Enrollment Sync (Oracle Utilities Digital Asset Cloud Service Initiated)
The following diagram shows a graphical representation of the Enrollment Sync integration process initiated from Oracle Utilities Digital Asset Cloud Service:
Processing Details
The integration process deployed on Oracle Integration Cloud is exposed as a REST API. It performs the following activities:
1. The process is triggered when it receives a request from Oracle Utilities Digital Asset Cloud Service.
2. Transform the payload to Oracle Utilities Grid Edge Distributed Energy Resources Management System format.
3. Invoke the Oracle Utilities Grid Edge Distributed Energy Resources Management System enrollment service endpoint and Oracle Utilities Grid Edge Distributed Energy Resources Management System responds synchronously whether the request has been processed successfully or with an error.
4. If the REST service returns:
• Status 200 (OK),
• Invoke the internal Oracle Utilities NMS-DERMS DACS Enrollment Sync Ack Oracle Integration Cloud integration process.
• Error Status, such as 400 or 500,
• Throws a fault back to Oracle Utilities Digital Asset Cloud Service and send an email notification with the error details to the users configured in the OUTL-BRT-WACS_FPRC_Email_ID lookup.
5. Enrollment Sync integration will finish the initial request by returning the incoming “syncRequestId” into the response “externalId”.
6. For any errors encountered in this process:
• An error email notification with error details is sent via the common error handler Oracle Integration Cloud process to the users defined in 'to' recipients in the OUTL-BRT-DACS_DRMS_Email_ID lookup.
• The process will return a fault to Oracle Utilities Digital Asset Cloud Service.
• The integration flow will stop processing.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Digital Assets Cloud Service and Oracle Utilities Distributed Energy Resources Management System artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities DACS NMS-DERMS Enrollment Sync |
Integration Process Identifier | OUTL-BA-DACS_DRMS_ENROLL_SYNC |
Integration Package Name | outl.ba.dacs.derms.01.22.3000 |
Source Connection (Oracle Utilities Adapter) | Oracle Utilities REST DACS for DACS-DRMS |
trigger | Outbound Message Type: X1-NMSDASMSG (Synchronize Digital Asset (NMS) |
Target Connection (Oracle Utilities Adapter) | Oracle Utilities REST DRMS for DACS-DRMS |
invoke | • DERMS Service Name: NMS-DACSInbound • openAPIUrl: https://{host}:{port} /nms-ofs/rest/v1/openapi.json • OperationId: enroll • Method: POST • URI: /enroll |
Local Integrations | • Oracle Utilities NMS-DERMS DACS Enroll Sync Ack • Oracle Utilities DACS NMS-DERMS CommonErrorHandler |
OIC Lookup | • OUTL-BRT-DACS_DRMS_ConfigProps • OUTL-BRT-DACS_DRMS_Email_ID • OUTL-BRT-DACS_DRMS_Routing |
Enrollment Sync Acknowledgment (Oracle Utilities Grid Edge Distributed Energy Resources Management System Initiated)
The following diagram shows a graphical representation of the Enrollment Sync Acknowledgment integration process initiated from Oracle Utilities Grid Edge Distributed Energy Resources Management System:_Sync_Acknowledgment.jpg "Shows a graphical representation of the integration process.")
Processing Details
The integration process deployed on Oracle Integration Cloud is exposed as a REST API. This is called internally by the DACS-DERMS Enrollment Sync OIC integration process.
It performs the following activities:
1. The process is triggered when it receives the Oracle Utilities Grid Edge Distributed Energy Resources Management System acknowledgment from the Enrollment Sync Process.
2. Transform the payload to Oracle Utilities Digital Asset Cloud Service format.
3. Invoke Oracle Utilities Digital Asset Cloud Service Sync Request Update REST endpoint using the Oracle Utilities Adapter to send the acknowledgment. The EnrollmentSyncAck process is delayed by a configurable amount of second to ensure Oracle Utilities Digital Asset Cloud Service has processed the initial request prior to receiving this acknowledgment.
4. For any errors encountered in this process:
• An error email notification with error details is sent via the common error handler Oracle Integration Cloud process to the users defined in 'to' recipients in the OUTL-BRT-DACS_DRMS_Email_ID lookup.
• The integration flow will stop processing.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Digital Assets Cloud Service and Oracle Utilities Distributed Energy Resources Management System artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities NMS-DERMS DACS Enroll Sync Ack |
Integration Process Identifier | OUTL-BA-DRMS_DACS_SYNC_ACK |
Integration Package Name | outl.ba.dacs.derms.01.22.3000 |
Target Connection (Oracle Utilities Adapter) | Oracle Utilities REST DACS for DACS-DRMS |
invoke | • Web Service Name: F1-SyncRequest • Computed URL: https://{host}:{port}/{tenant}/{domain /ouaf/rest/apis/common/sync/syncRequest • Method: PATCH • URI: /{syncRequestId} |
Local Integrations | NMSDERMS_SleepTimer[sleepTimer] javascript function |
OIC Lookup | • OUTL-BRT-DACS_DRMS_ConfigProps • OUTL-BRT-DACS_DRMS_Email_ID |
Device Status Check
This integration process sends a device status check from Oracle Utilities Digital Asset Cloud Service to Oracle Utilities Grid Edge Distributed Energy Resources Management System as part of the enrollment orchestration process. Oracle Utilities Grid Edge Distributed Energy Resources Management System then gets the device status from Oracle Utilities Live Energy Connect. When Oracle Utilities Grid Edge Distributed Energy Resources Management System gets the response back from Oracle Utilities Live Energy Connect, it will send a response back to Oracle Utilities Live Energy Connect.
Device status check request and response are asynchronous processes:
Device Status Check (Oracle Utilities Digital Asset Cloud Service Initiated)
The following diagram shows a graphical representation of the Device Status Check integration process initiated from Oracle Utilities Digital Asset Cloud Service:
Processing Details
The integration process deployed on Oracle Integration Cloud is exposed as a REST API. It performs the following activities:
1. The process is triggered when it receives a request from Oracle Utilities Digital Asset Cloud Service.
2. The payload is transformed to the Oracle Utilities Grid Edge Distributed Energy Resources Management System format.
3. Invoke the Oracle Utilities Grid Edge Distributed Energy Resources Management System Status Check REST Service.
4. If the REST service returns:
• Status 200 (OK), end the process.
• Error Status, such as 400 or 500, an email notification with the error details is sent via common error handler to the users configured in the OUTL-BRT-WACS_FPRC_Email_ID lookup. The process returns a fault to Oracle Utilities Digital Asset Cloud Service.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Digital Assets Cloud Service and Oracle Utilities Distributed Energy Resources Management System artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities DACS NMS-DERMS Device Status |
Integration Process Identifier | OUTL-BA-DACS_DRMS_DEVICE_STATUS |
Integration Package Name | outl.ba.dacs.derms.01.22.3000 |
Source Connection (Oracle Utilities Adapter) | Oracle Utilities REST DACS for DACS-DRMS |
trigger | Outbound Message Type: X1-CTRLDVCS (Controllable Device Status Check) |
Target Connection (Oracle Utilities Adapter) | Oracle Utilities REST DRMS for DACS-DRMS |
invoke | • DERMS Service Name: NMS-DACSInbound • openAPIUrl: https://{host}:{port} /nms-ofs/rest/v1/openapi.json • OperationId: statusCheck • Method: POST • URI: /status-check |
Local Integrations | Oracle Utilities DACS NMS-DERMS CommonErrorHandler |
OIC Lookup | • OUTL-BRT-DACS_DRMS_ConfigProps • OUTL-BRT-DACS_DRMS_Routing |
Device Status Check Acknowledgment (Oracle Utilities Grid Edge Distributed Energy Resources Management System Initiated)
When Oracle Utilities Grid Edge Distributed Energy Resources Management System gets the device status from Oracle Utilities Live Energy Connect, it sends the asynchronous response back to Oracle Utilities Digital Asset Cloud Service for the corresponding device status check request.
The following diagram shows a graphical representation of the Device Status Check Response integration process initiated from Oracle Utilities Grid Edge Distributed Energy Resources Management System:
Processing Details
The integration process deployed on Oracle Integration Cloud is exposed as a REST API. It performs the following activities:
1. The process is triggered when it receives a request from Oracle Utilities Grid Edge Distributed Energy Resources Management System.
2. The payload is transformed to the Oracle Utilities Digital Asset Cloud Service format.
3. Invoke the Oracle Utilities Digital Asset Cloud Service postControllableDeviceStatus REST Service using the Utilities Adapter.
4. If the REST service returns:
• Status 200 (OK), the process returns the boStatus to the DERMS response.
• Error Status, such as 400 or 500, a FAILURE response will be sent back to Oracle Utilities Grid Edge Distributed Energy Resources Management System.
5. For any errors encountered in this process:
• An error email notification with error details is sent via the common error handler Oracle Integration Cloud process to the users defined in 'to' recipients in the OUTL-BRT-DACS_DRMS_Email_ID lookup.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Digital Assets Cloud Service and Oracle Utilities Distributed Energy Resources Management System artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities NMS-DERMS DACS Device Status Ack |
Integration Process Identifier | OUTL-BA-DACS_DRMS_DEVICE_STATUS |
Integration Package Name | outl.ba.dacs.derms.01.22.3000 |
Source Connection (Oracle Utilities Adapter) | Oracle Utilities REST DRMS for DACS-DRMS |
trigger | • DERMS Service Name: NMS-DACSOutbound • openAPIUrl: https://{host}:{port}/nms-ofs/outbound/openapi.json • OperationId: deviceStatusCheckAck • Method: POST • URI: /status-check-ack-to-dacs |
Target Connection (Oracle Utilities Adapter) | Oracle Utilities REST DACS for DACS-DRMS |
invoke | • Web Service Name: X1-CtrlDvcStatusCheckResp • Computed URL: https://{host}:{port}/{tenant}/ • {domain}/ccs/rest/apis/cross/digitalAssets/ controllableDeviceStatus • Method: POST • URI: /response |
Local Integrations | Oracle Utilities DACS NMS-DERMS CommonErrorHandler |
OIC Lookup | • OUTL-BRT-DACS_DRMS_ConfigProps |
Event Device Reservation (Oracle Utilities Grid Edge Distributed Energy Resources Management System Initiated)
When controllable devices are selected to participate in an upcoming event, Oracle Utilities Grid Edge Distributed Energy Resources Management System notifies Oracle Utilities Digital Asset Cloud Service of the devices reserved for the specific event.
This integration process sends the event information and the devices reserved for the event to Oracle Utilities Digital Asset Cloud Service. It then sends an acknowledgment back to Oracle Utilities Grid Edge Distributed Energy Resources Management System when the process is completed or encountered an error.
The following diagram shows a graphical representation of the Event Device Reservation integration process. 
Processing Details
The integration process deployed on Oracle Integration Cloud is exposed as a REST API. It performs the following activities:
1. The process is triggered when Oracle Utilities Grid Edge Distributed Energy Resources Management System invokes REST endpoint to send the event and device reservation information to Oracle Utilities Digital Asset Cloud Service. The message received is a json payload with a csv file attachment.
2. Invoke F1-HealthCheckRest Rest endpoint to check if the Oracle Utilities Digital Asset Cloud Service environment is up and accessible.
• If the REST service returns HTTP status 200, DACS is accessible and proceed to Step 3.
• Else:
• Transform Negative Acknowledgment message
• Invoke DERMS Event Reservation Acknowledgment REST endpoint
3. Use Stage File operation “ReadFileinSegments” to read the file in segments of 200 records with parallel processing option.
• Transform the event device reservation payload from Oracle Utilities Grid Edge Distributed Energy Resources Management System to Oracle Utilities Digital Asset Cloud Service format.
• Invokes the Event Participation-Create Device Reservation DACS REST endpoint to pass the Event Device Reservation information to Oracle Utilities Digital Asset Cloud Service.
• If any of the REST service invocation returns an HTTP Error status:
• Transform Negative Acknowledgment message.
• Invoke Oracle Utilities Grid Edge Distributed Energy Resources Management System Event Reservation Acknowledgment REST endpoint.
• When all the records are successfully created in Oracle Utilities Digital Asset Cloud Service:
• Transform Positive Acknowledgment message.
• Invoke Oracle Utilities Grid Edge Distributed Energy Resources Management System Event Reservation Acknowledgment REST endpoint.
4. After all the records in the file are processed:
• A process completed email notification is sent to the users defined in 'to.processnotification' recipients in OUTL-BRT-DACS_DRMS_Email_ID lookup.
• A positive acknowledgment is sent to Oracle Utilities Grid Edge Distributed Energy Resources Management System.
5. For any errors encountered in this process:
• An error email notification with error details is sent via the common error handler OIC process to the users defined in 'to' recipients in the OUTL-BRT-DACS_DRMS_Email_ID lookup.
• A negative Acknowledgment is sent to Oracle Utilities Grid Edge Distributed Energy Resources Management System.
• The integration flow will stop processing.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Digital Asset Cloud Service and Oracle Utilities Grid Edge Distributed Energy Resources Management System artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities NMS-DERMS DACS Event Dvc Reserve |
Integration Process Identifier | OUTL_BA_DRMS_DACS_EVT_DVCRESV |
Integration Package Name | outl.ba.dacs.derms.01.22.3000 |
Source Connection (Oracle Utilities Adapter) | Oracle Utilities REST Outbound for DACS-DRMS |
trigger | • Service Name: NMS-DACSOutbound • openAPIUrl: https://{host}:{port}/nms-ofs/outbound/openapi.json • Method: POST • URI: /event-reservation-to-dacs |
Target Connection (Oracle Utilities Adapter) | Oracle Utilities REST DACS for DACS-DRMS |
invoke | • DACS Web Service Name: X1-ProgramEventParticipation • Computed URL: https://{host}:{port}/{tenant}/{domain}/ccs/rest/apis/cross/service/programEventParticipation • Method: POST • URI: /reserveDevice |
Target Connection (Oracle Utilities Adapter) | Oracle Utilities REST DRMS for DACS-DRMS |
invoke | • DERMS Service Name: NMS-DACSInbound • openAPIUrl: https://{host}:{port}/nms-ofs/rest/v1/openapi.json • Method: POST • URI: /event-reservation-ack |
Local Integrations | Oracle Utilities DACS NMS-DERMS CommonErrorHandler |
OIC Lookup | • OUTL-BRT-DACS_DRMS_ConfigProps • OUTL-BRT-DACS_DRMS_Email_ID • OUTL-BRT-DACS_DRMS_EventType • OUTL-BRT-DACS_DRMS_Routing |
Pre-Event Cancel (Oracle Utilities Grid Edge Distributed Energy Resources Management System Initiated)
When an event is canceled in Oracle Utilities Grid Edge Distributed Energy Resources Management System, the event information is sent to Oracle Utilities Digital Asset Cloud Service, so Oracle Utilities Digital Asset Cloud Service can cancel all reserved devices linked to that event.
The following diagram shows a graphical representation of the Pre-Event Cancel integration process. 
Processing Details
The integration process deployed on Oracle Integration Cloud is exposed as a REST API. It performs the following activities:
1. The process is triggered when Oracle Utilities Grid Edge Distributed Energy Resources Management System invokes REST endpoint to send the event cancellation information to Oracle Utilities Digital Asset Cloud Service. The message received is a json payload.
2. Transform the payload from Oracle Utilities Grid Edge Distributed Energy Resources Management System to Oracle Utilities Digital Asset Cloud Service format.
3. Invokes the Event Participation-Pre event Cancellation DACS REST endpoint to pass the Event Cancellation information to Oracle Utilities Digital Asset Cloud Service.
4. For any errors encountered in this process:
• An error email notification with error details is sent via the common error handler Oracle Integration Cloud process to the users defined in 'to' recipients in the OUTL-BRT-DACS_DRMS_Email_ID lookup.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Digital Asset Cloud Service and Oracle Utilities Grid Edge Distributed Energy Resources Management System artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities NMS-DERMS DACS Pre-Event Cancel |
Integration Process Identifier | OUTL_BA_DRMS_DACS_PRE_EVENT_CANC |
Integration Package Name | outl.ba.dacs.derms.01.22.3000 |
Source Connection (Oracle Utilities Adapter) | Oracle Utilities REST DERMS for DACS-DRMS |
trigger | • Service Name: NMS-DACSOutbound • openAPIUrl: https://{host}:{port}/nms-ofs/outbound/openapi.json • Method: POST • URI: /event-cancellation-to-dacs |
Target Connection (Oracle Utilities Adapter) | Oracle Utilities REST DACS for DACS-DRMS |
invoke | • DACS Web Service Name: X1-ProgramEventParticipation • Computed URL: https://{host}:{port}/{tenant}/{domain}/ccs/rest/apis/cross/service/programEventParticipation • Method: POST • URI: /preEventCancellation • Connection Name: Oracle Utilities REST DACS for DACS-DRMS |
Local Integrations | Oracle Utilities DACS NMS-DERMS CommonErrorHandler |
OIC Lookup | • OUTL-BRT-DACS_DRMS_ConfigProps • OUTL-BRT-DACS_DRMS_Email_ID |
Send Device Score (Oracle Utilities Digital Asset Cloud Service Initiated)
Oracle Utilities Digital Asset Cloud Service computes and maintains the device score for each controllable device enrolled in a program. The calculation depends on factors, such as equipment specifications, monthly/annual capacity, device participation history, etc.
This integration process is used to transfer all approved General Ledger transactions from Oracle Utilities Customer Cloud Service to Oracle ERP Financial Cloud for General Ledger for journal creation.
This integration process is used to transfer the device score for each controllable device periodically from Oracle Utilities Digital Asset Cloud Service to Oracle Utilities Grid Edge Distributed Energy Resources Management System to facilitate its eligibility evaluation during event planning.
It is an asynchronous flow that is triggered by a schedule. Oracle Utilities Digital Asset Cloud Service creates a Device Score file and is picked up by the integration process and sent to Oracle Utilities Grid Edge Distributed Energy Resources Management System. This is just a file pass through and no transformation will be done by the integration.
The following diagram shows a graphical representation of the integration process. 
Processing Details
This is a scheduled integration process deployed on Oracle Integration Cloud and does the following activities:
1. The process is triggered by a schedule and has no schedule parameters.
• Define the integration schedule for this process and make sure the Smart Control Device Score Extract Job (X1-SDCSE) schedule in Oracle Utilities Digital Asset Cloud Service is always run first, so the file is available to be processed by the integration.
• A couple of the default values used in this integration are defined in the OUTL-BRT-DACS_DRMS_ConfigProps. Make sure to define the properties needed for this integration.
2. Once the flow is triggered, check the property value of dacs.filelocation.flag to determine where to get the extracted file from.
3. If the property value is Cloud:
• It invokes the Object Storage - List Objects REST API to get the list of files in a particular bucket where the Smart Control Device Score Extract files are stored. The bucket name is obtained from the property value dacs.os.dvcScore.bucketname. Only files that start with the string entered in the property value dacs.dvcScore.extract.filename.prefix are selected.
Note: The value dacs.dvcScore.extract.filename.prefix should match the beginning of the parameter filename in Oracle Utilities Digital Asset Cloud Service Batch X1-SDCSE.
• Repeat the following steps for each file to process:
a. Invoke the Object Storage: Gets Object REST API to get the actual file to process.
b. Prepare the file to send to Oracle Utilities Grid Edge Distributed Energy Resources Management System. This is sent as a file attachment when invoking the DERMS Send Score REST API.
c. Invoke DERMS Device Score REST API and send the file as an attachment.
• If DERMS returns an HTTP 200:
• Invoke REST API RenameObject to rename the file just processed in Object Storage by adding a prefix “Sent” or “Uploaded” to the filename.
• Else, invoke Common Error Handler and also rename the file by adding a prefix “Error” to the filename.
4. If the property value is On-Premise:
• It invokes FTP Adapter to list files from Oracle Utilities Digital Asset Cloud Service On-Premises location obtained from the property value dacs.ftp.input.directory and files that start with the string entered in the property value dacs.dvcScore.extract.filename.prefix are selected.
Note: The value dacs.dvcScore.extract.filename.prefix should match the beginning of the parameter filename in Oracle Utilities Digital Asset Cloud Service Batch X1-SDCSE.
• Repeat the following steps for each file to process:
a. Invokes the FTP Adapter with Download File operation to get the actual file to process.
b. Prepares the file to send to Oracle Utilities Grid Edge Distributed Energy Resources Management System. This is sent as a file attachment when invoking the DERMS Send Score REST API.
c. Invoke DERMS Device Score REST API and send the file as an attachment.
• If DERMS returns an HTTP 200:
• Invoke FTP Adapter to rename the file obtained from the server by adding a prefix “Sent” or “Uploaded” to the filename.
• Else, invoke Common Error Handler and also rename the file obtained from the server by adding a prefix “Error” to the filename.
5. After all the file are processed:
• A process completed email notification is sent to the users defined in 'to.processnotification' recipients in OUTL-BRT-DACS_DRMS_Email_ID lookup.
• A positive acknowledgment is sent to Oracle Utilities Grid Edge Distributed Energy Resources Management System.
6. For any errors encountered in this process:
• An error email notification with error details is sent via the common error handler Oracle Integration Cloud process to the users defined in 'to' recipients in the OUTL-BRT-DACS_DRMS_Email_ID lookup.
• A negative Acknowledgment is sent to Oracle Utilities Grid Edge Distributed Energy Resources Management System.
• The integration flow will stop processing.
Technical Details
The following table describes the integration processes and the respective Oracle Utilities Digital Asset Cloud Service and Oracle Utilities Grid Edge Distributed Energy Resources Management System artifacts used in this integration process.
Artifacts | Value |
|---|---|
Integration Process Name | Oracle Utilities NMS-DERMS DACS Send Device Score |
Integration Process Identifier | OUTL_BA_DRMS_DACS_EVT_DVCRESV |
Integration Package Name | outl.ba.dacs.derms.01.22.3000 |
Source Connection (Oracle Utilities Adapter) | OUTL-BA-DRMS_DACS_SEND_DVCSCORE |
REST Adapter (Trigger) | Oracle Utilities REST DACS Object Storage for DACS-DRMS |
DACS REST IWS (Oracle Utilities Adapter) | • Web Service Name: X1-ProgramEventParticipation • Computed URL: https://{host}:{port}/{tenant}/{domain}/ccs/rest/apis/cross/service/programEventParticipation • Method: POST • URI: /reserveDevice • Connection Name: Oracle Utilities REST DACS for DACS-DRMS |
DERMS REST IWS (Oracle Utilities Adapter) | • Service Name: NMS-DACSInbound • openAPIUrl: https://{host}:{port}/nms-ofs/rest/v1/openapi.json • Method: POST • URI: /event-reservation-ack • Connection Name: Oracle Utilities REST DERMS for DACS-DRMS |
Local Integrations | Oracle Utilities DACS NMS-DERMS CommonErrorHandler |
OIC Lookup | • OUTL-BRT-DACS_DRMS_ConfigProps • OUTL-BRT-DACS_DRMS_Email_ID |