Error Handling
This section describes the different ways errors are handled in the integration:
Summary of Integration Error Handling
Integration Process: DERMS DACS Enrollment Request
Type of Error
Action
Notification Type
Retry
Technical Fault
 
Example: DACS is not accessible
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DERMS
Business Fault
 
(For each record processing where DACS enrollProgram returns - Status VAL-ERROR or ERROR)
• Set Error to the record’s responseCode and add to DERMS Responses Collection.
• Process the next record.
• At the end of the collection processing, send ERROR ackType and the response collection to DERMS.
 
None
 
Enrollments created in DACS in Pending Status.
 
DACS handles the business errors.
Business Fault
 
(For each record processing DACS enrollProgram returns messageNumber = 10589)
• Error means the enrollment request already exists in DACS.
• Ignore the error
• Process the next record
 
None
 
Integration Process: DACS DERMS Enrollment Sync
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DERMS is not accessible
Process Stop
Error Email
Resend message from DACS
Business Fault
 
Example: Cannot create the subscription in DERMS due to null CIS_PERSON_ID.
Process Stop
Send Enrollment Sync Ack with Error
Fix the data in DACS.
 
Resend message from DACS.
 
Integration Process: DACS DERMS Device Status Check
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DERMS is not accessible
Process Stop
Error Email
Resend message from DACS
 
Integration Process: DERMS DACS Program Event Status Update
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DACS is not accessible
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DERMS
Technical Fault
 
(When HTTP 400 encountered)
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DERMS
Integration Process: DERMS DACS Event Device Reservation
Type of error
Action
Notification Type
Retry
Technical Fault
 
(DACS HealthCheck API Error)
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DERMS
Technical Fault
 
(Read File Error)
 
Example: File Empty
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
 
Process Complete Email - Error
Resend message from DERMS
Technical Fault
 
(DACS Event Participation -Reserve Device API Error)
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
 
Process Complete Email - Error
Resend message from DERMS
Business Fault
N/A
 
None
 
DACS handles the business errors
 
Integration Process: DERMS DACS Event Device Outcome
Type of error
Action
Notification Type
Retry
Technical Fault
 
(DACS HealthCheck API Error)
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DERMS
Technical Fault
 
(Read File Error)
 
Example: File Empty
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
 
Process Complete Email - Error
Resend message from DERMS
Technical Fault
 
(DACS Event Participation -Post Event Outcome API Error)
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
 
Process Complete Email - Error
Resend message from DERMS
Business Fault
N/A
 
None
 
DACS handles the business errors
 
Integration Process: DACS DERMS Customer Event Opt Out Update
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DERMS is not accessible
Process Stop
Error Email
No Retry
 
Manual Update in DERMS
Business Fault
 
(DERMS Response AckType = Error)
Process Stop
Error Email
No Retry
 
Manual Update in DERMS
 
Integration Process: DACS DERMS Program Rule Sync
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DERMS is not accessible
Process Stop
Error Email
Resend message from DACS
Business Fault
 
(DERMS Response AckType = Error
Process Stop
Error Email
Resend message from DACS
 
Integration Process: DACS DERMS Aggregator Sync
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DERMS is not accessible
Process Stop
Error Email
Resend message from DACS
Business Fault
 
(DERMS Response AckType = Error
Process Stop
Error Email
Resend message from DACS
 
Integration Process: DERMS DACS SP Network Location Transfer
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: Common OS or FTP Flow is not accessible
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
 
Process Complete Email - Error
Resend message from DERMS
Business Fault
 
(DERMS Response AckType = Error
N/A
 
None
 
DACS handles the business errors
 
Integration Process: DACS DERMS Device Score
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: Source FTP or Source Object storage is not accessible
Process Stop
Error Email
Next scheduled run will pick up the files from DACS source content server or manually run the OIC process.
Partial Processing
 
Technical Fault During Processing in Loop
 
Example:
DERMS is not accessible
Process Stop
Error Email
 
Process Complete Email (also includes list of files not transferred)
Rename the file in DACS content server by removing the “Error-‘ prefix in the filename then manually run the OIC Process.
Business errors
N/A
 
 
 
Resubmitting the Error Instances in Oracle Integration Cloud
In this integration, the flows initiated are asynchronous flows. The Resubmit option is available only for asynchronous flows.
To resubmit the error instances in Oracle Integration Cloud:
1. Login to Oracle Integration Cloud.
2. Navigate to Integrations > Monitoring > Errors.
3. Select the integration to resubmit.
4. Click the Resubmit icon.