Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How to react on exceptions caused within reader or processor components?

April 26, 2017caused components exceptions processor react reader

0

Posted

How to react on exceptions caused within reader or processor components?

1 Answer

0

Posted

If a reader or processor component caused an exception, the synchronization status table, the reader component, the source system or the processor component has been configured in an improper way. In all cases the best idea is to fix the problem (e. g. wrong repository name in the synchronization status table(target values), wrong artifact schema in the source system, wrong property of the reader component, wrong XSLT file of the XSLTProcessor or wrong SQL statement for the ?EntityService/MappingDBUpdator) and rerun (or keep running) the connector. In most cases, fixing the problem will result in changing the affected artifacts. Therefore, just rerunning the connector (or keep it running) will typically solve the problem. An artifact replay is not suggested.