SQL Update Interface Adapter JDBC Error; Ruleset not Set-up
EBI 3 Scenario:
During the mapping in a ruleset, we attempted to save the ruleset. The ruleset was simple and consisted of moves.
EBI 3 Issue:
While attempting to save the ruleset, we received an error that prevented us from moving forward. There was a 'hidden' condition applied to one of the rules.
EBI 3 Auditor Error:
Step 5: Execute Adapter: com.abc.core.edi.staging.PoAck.OutboundPoAckFromAs400ErpDbSelectUpdateDBA$Update
2015-06-07 11:48:54,446 [PERSISTENT] - Starting com.extol.processtasks.engine2.tasks.CommEngineTask
2015-06-07 11:48:54,446 [PERSISTENT] - Invoking Interface Adapter.
2015-06-07 11:48:54,446 [PERSISTENT] - Name : com.abc.core.edi.staging.PoAck.OutboundPoAckFromAs400ErpDbSelectUpdateDBA$Update
2015-06-07 11:48:54,446 [PERSISTENT] - Version : Deployed
2015-06-07 11:48:54,447 [PERSISTENT] - Interaction : Update
2015-06-07 11:48:54,449 [ERROR] - JDBC Adapter Execution failed.
2015-06-07 11:48:54,450 [ERROR] - Execution of Adapter ended in error.
2015-06-07 11:48:54,450 [PERSISTENT] - Ending Interface Adapter invocation.
2015-06-07 11:48:54,451 [PERSISTENT] - Completed Task.
EBI 3 Resolution:
After circulating thru the ruleset rules, there was a condition on one of the rules. It was odd, due to the rule not being a different color.
By: Sean Hoppe on