How to route and store exceptions?
Since the CCF is based on openAdaptor, it uses openAdaptor’s mechanisms to handle exceptions. Within the wiring configuration, one single exception handler, a chain of exception handlers or even a message hospital can be set up. Information how to setup these exception handlers can be found here. The example integration scenarios that come with the CCF typically use a form of the message hospital paradigm. All exceptions are stored with their time stamp, originating component, user name, error description and artifact data within a file or data base table. This permanent storage is called “hospital” in the openAdaptor jargon. Artifacts within the hospital can be analyzed to find out why the could not be shipped. Feel free to add further exception handlers to these scenarios just by changing the wiring configuration.
