How to take action over an xlate failure

[Mark Blackford]

I am receiving XML messages from an external source through a fileset-ftp thread and translating them into  FRL messages during routing to a 2nd thread.

If a message received is malformed or doesn’t match the XSD then I need to take action and generate an exception to our external system which will notify support.  Ideally when this happens I would like a Tcl script to run so I can configure the necessary actions.

What happens now is that the system first identifies the problem when it parses the XML in the xlate, it writes the message to the error database and a line to the site log.

Ultimately I expect I could have a process that monitors the error DB (can I? I’m pretty new to Cloverleaf) and triggers a script that does what it needs and then clears the message from the error DB.  It would make life easier (and more consistent with the way we handle things elsewhere) if I could trigger a script directly when the parse failure happens.

Has anyone else encountered a similar requirement or can you suggest how I can achieve this.

Topic

[Troy Morton]

Hi Mark.  Did you solve this problem?  I was curious how you handled it.

Thanks,

Troy Morton

Interface Team – Contractor

Novant Healthcare

em: t.morton@novanthealth.org

[Robert Kersemakers]

Now I’m curious as well.  😀

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Mark Blackford]

No, never did solve it.  It doesn’t happen very often and we are handling the problem manually when it does.  🙁

[Jim Kosloskey]

Perhaps a Tcl proc using GRM may fail when attempting to parse the XML message. You could catch that failure and take whatever action you want.

email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

[Author]

Replies