Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Stardust/Knowledge Base/Integration/Camel/Exception Handling in Generic Camel Application

< Stardust‎ | Knowledge Base‎ | Integration‎ | Camel
Revision as of 01:41, 12 May 2014 by Vikash.pandey.sungard.com (Talk | contribs) (How To)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Overview

In this article we are going to discuss, how we can handle exception in Generic Camel Application and propogate it to Stardust process, also how we can gather exception data (e.g. exception message) and set it to Stardust process data for further processing during process execution.

Use Case

Lets take an example, we have a Generic Camel Application that is calling a REST service, during execution of this application there are chances that execption may occur (network issue, service unavailable, wrong user credentials etc.). Our aim is to catch thsi exception and set certain process data and use that process data in the process to define different transitions (process flow), for example, if the process data named exceptionMessages is not null (which it will only be if there is an execption in calling the REST service), we need to define process flow to an activity that will manage the exceptional cases.

Process Diagram: CATExcp1.JPG

How To

To define a Generic Camel Application Type to call a REST service the route is like:

<setHeader headerName="CamelHttpMethod"><constant>GET</constant></setHeader>
 
<setHeader headerName="CamelHttpUri">
   <constant>http://customer1.enterprise12.qa.sungardims.net/Apollo/rest/auth/token?
   loginName=ccuser&amp;operatorId=1937&amp;httpClient.authenticationPreemptive=true
</constant>
</setHeader>
<to uri="http://isoverwritten?authMethod=Digest&amp;authUsername=ccuser@customer1&amp;authPassword=ccpassword"/> 
 
<convertBodyTo type="java.lang.String"/>

And to handle the exception one needs to add the following route in the above mentioned route:

<onException>
<exception>java.lang.Exception</exception>
  <handled>
    <constant>true</constant>
  </handled>
<setHeader headerName="Message">
<simple>$simple{property.CamelExceptionCaught.message}</simple>
</setHeader>
<simple>exception=null</simple>
<setProperty propertyName="CamelExceptionCaught">
<simple>null</simple>
</setProperty>
</onException>

Once this is done, one can set the parameter to get the exception message named "Message" and store the value in Stardust process data. CATExcp2.JPG


Model can be found here File:TestModel (3).zip

Back to the top