How to react on exceptions caused by writer components?
If a writer component throws a non-timeout or non-session fault related error, the error typically lies in the synchronization status table, the XSLT scripts of the XSLT processors or the artifact schema within the target system. Misconfiguration in the synchronization status table (target values) will typically result in an exception for every single artifact. In this case, changing the table and rerunning (or keep running) the connector will suffice. XSLT and schema related problems may just affect some artifacts. After having solved the root cause (look at the CCF error code), the affected artifacts should be refreshed/updated in the source system so that they are automatically reread by the reader component.
