Error Handling
This section provides information about the different ways used to handle errors in the integration and also resubmitting the instances after rectifying the errors.
Error Handling Ways
In this integration, the errors are handled in different ways due to the limitation of Oracle Integration Cloud.
Synchronous Flow Error Handling
As part this error handler the errors are sent back to global fault handler and the respective system via Common Error Handler flow.
Technical Fault
This fault occurs when there is a data mismatch or any Xpath related error. On this error, the flow immediately goes to global fault handler and the fault is sent back to the respective system.
Remote Fault
This fault occurs when the target system is down. When this error occurs the flow immediately goes to global fault handler and the fault is sent back to the respective system.
Business Fault
This fault occurs only when the business fault occurs in the target system due to invalid data. When this error occurs, the fault is sent back to the respective system as part of immediate response.
Asynchronous Flow Error Handling
Technical Fault
This fault occurs when there is a data mismatch or any Xpath related error. When this error occurs, the flow immediately goes to global fault handler and an optional email to the respective user is sent via Common Error Handler flow.
Remote Fault
This fault occurs when the target system is down. When this error occurs, the flow immediately goes to global fault handler and an optional email is sent to the respective user.
Business Fault
This fault occurs only when the business fault occurs in the target system due to invalid data. When this error occurs the flow immediately goes to global fault handler and an optional email is sent to the respective user.
Summary of Integration Error Handling
Integration Process: 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)
 
(DACS enrollProgram returns - Status VAL-ERROR or ERROR)
• Set Error to record’s AckType response to DERMS
• Add to DERMS AckType Collection
• Process Next Record
• At the end of the collection processing, send ackType Collection and ERROR ackType to DERMS
 
None
 
Enrollments created in DACS
 
DACS handles the validation errors
Business Fault
 
(For Each Record Processing)
 
(DACS enrollProgram messageNumber = 10589)
• Error means the enrollment req exist in DACS already
• Ignore the error
• Process Next Record
 
None
 
Resend message from
 
Integration Process: 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
Continue Process
Send error in message
Data fix in DACS:
1. Resend message from DACS.
Business Fault
N/A
 
 
 
Integration Process: 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: Event Device Reservation
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DERMS is not accessible
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DACS
Business Fault
N/A
 
None
 
Integration Process: Pre-event Cancellation
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DERMS is not accessible
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DACS
Business Fault
N/A
 
None
 
Integration Process: Send 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 (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
 
 
Integration Process: Event Outcome
Type of error
Action
Notification Type
Retry
Technical Fault
 
Example: DACS storage is not accessible
• Send FAILURE ackType to DERMS
• Process Stop
Error Email
Resend message from DERMS
Business Fault
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.