Pervasive has recently developed an effective utility for migrating Data Integrator v9 projects into Pervasive Data Integrator v10. The process is quick and relatively smooth; however, there is the potential for challenges to arise due to the complex nature of most DI projects. If you are thinking about transitioning from v9 to v10, please reach out to Emprise to learn how our team of Certified Pervasive Developers can help your transition to v10 be successful.
In most cases, Pervasive Data Integrator users want to react and handle errors has they occur. By default, Pervasive will exit a Process as soon as an error is encountered. Alternatively, a Process can be configured to allow errors, which will allow the Process to continue executing through completion regardless of an error occurring. What we have found is that neither option is practical with Pervasive Data Integrator.
Responsive error handling can be introduced to ensure that the business needs are met and all errors are handled appropriately as they occur. For example, if a step in a Process cannot find a file, the Process should not abort, nor should it continue execution as if the file exists. Instead, use responsive error handling to manage the missing file exception and send an email to the appropriate recipients.
With Pervasive Data Integrator, custom error handling should be used to ensure that a Process is behaving as intended and as defined by business rules. By introducing responsive error handling, you can gather and react to errors as they occur, versus digging through error logs to identify why a Process aborted.
Data Integrator Processes that contain steps which are dependent upon the success of a previous step, are ideal candidates for implementing responsive error handling.
The use of responsive error handling is beneficial to the:
- Developer – Implements the code for responsive error handling.
- End User – Defines business rules and reviews results of responsive error handling.
Responsive error handling is implemented within Pervasive Data Integrator Process Designer.
During the execution of a Process, Pervasive stores metadata about the Process and its steps and session objects. The metadata can be accessed via RIFL Script in both RIFL steps and Event Handlers. One approach is to create a RIFL Script step immediately after each step that ignores an error. This ensures that errors are caught immediately as they occur and can be handled appropriately. To implement responsive error handling, the Process must not be configured to “Break on First Error”. Additionally, all steps should be set to “Ignore Error”. Then, insert RIFL steps to handle errors appropriately.
Subscribe to the Emprise Technologies YouTube channel to access our library of video demos.
Want to learn more about how to use macro definition variables Pervasive Data Integrator? Emprise Technologies has created a 2 part video demo for developers using DI. This video is part 1 of the demo for using macro definition variables. Don’t forget to subscribe to our Emprise Technologies YouTube channel to receive more informational videos from us. We’ll post the 2nd video shortly.