Exception Handling – TIBCO BW

Guru Lakshmeekar

Objectives

– Handle exceptions in a uniform manner across projects

– Improve the reliability

– Avoid the duplicate request processing

– Reduce the damage by real-time alerts

– Standardizing the request and response structure

– End to End traceability of the request processing thru the logs

– Create the dashboards thru the structured logs

Generic Standards

• Logging :

– Use Write To Log General Activity to write the exceptions in the log file

– Write the request and response for all the integrations as a standard practice

• Alert :

– If these application errors are detected on an early stage, it lessens the effort of reworking. Time, cost and resources can also be saved upon the detection. Use Send Mail activity to send email notification in the case of any technical error to the production support team and service manager.

• Performance:

– Use Checkpoint to save the logical state

Standard Structure

• Request Structure

– There should be a standard way to identify the Caller (Ex: APP ID) and the functionality (method) across the web methods.

– There should be a Unique ID to identify each call uniquely (may be timestamp). This will be helpful in end to end traceability

• Response Structure:

– Every Integration should have both Success and Error structure

– There should be a Unique ID to identify each call uniquely (may be timestamp). This will be helpful in end to end traceability

– There should be a Status attribute which represents Success / Failure

– Error Structure should have standard attributes like Error Code, Error Description, Error System across the integrations

– We can have the common error XSD which contains the above attributes. This XSD should be included in all the response XSDs

Handle Exceptions

• Error Handling:

– Every process should have a Catch General Activity and select Catch Allcheck box to catch any exception. .

– Any exception (functional / technical) in integration should be converted in to the proper error structure, to make sure that the calling application get the proper response structure always

– Group the activities and catch the similar exceptions in same catch block

– Use GENERATE ERROR activity in case of the error and throw the error. Parent process handle the Exception

• Retry :

– In the case of only connection failures, retry option should be present to retry the connections for defined (ex: 3) times

Thank YouIntegration, Interaction, Ideation and Innovation