After loading process in tester, for success scenario, user will call our process with following browser url: We can see in below screenshot that operation has completed without any error/exception and response has been shown on the browser: We can see in the database that data has been successfully inserted in the database table: Testing File Not Found Exception Scenario: As we have only one file in the required path, we can test File Not Found exception scenario by passing any other name in our http request like I did below: You can see that File Not Found Exception has been caught and user has received custom error message (of course in real scenarios, you won’t just send a response message after catching an exception.
So if user sends abbasi in the name parameter, below concatenation for file name will result in the file name as “abbasi.xml”.
In this step by step TIBCO tutorial, I will explain you how exceptions are handled in TIBCO BW.
Following my principle of “Simple is better”, I have chosen a simple scenario for this tutorial.
Step 3: Configure JDBC Update Activity After reading content from XML file, it will be stored into a database table in our example.
For this we need to configure JDBC Update activity as shown below: File content read using Read File activity are mapped to data which will be stored in the database table: Step 4: Configure Catch Activity to Catch File Not Found Exception: Just to give you an idea how to handle a particular type of exception, I have used Catch activity inside group which will handle “File Not Found” exception.