SOA 11g - File Rejection Handler Part - 2 ( File Error handler for File Adapter)

In previous post, we discussed about in-build error handling for file and ftp adapter. In-build error handling will put the corrupted file to default rejected message folder.

In this post, we will discuss about File Rejection Handler i.e. how to use Fault Handling Framework to handle errors when we encounter corrupt file during file polling.

Following error handler we can define inside fault policies to handler error.

·         Web Service Handler

·         Custom Java Handler

·         JMS Queue

·         File

We will discuss each error handler one by one. In this post we will discuss about “File” Rejection handler.

File Rejection Handler

By default adapter put the rejected message to default folder (C:\Oracle\Middleware\user_projects\domains\base_domain\rejmsgs) so we can configure this error handler if we want to put that rejected message to other location.

We need to use Fault Handling Framework to configure the error handler so we need to have fault-binding.xml and fault-policies.xml file.

Create a new fault-binding.xml file in the same project and add below content to it.

<?xml version="1.0" encoding="UTF-8" ?>

<faultPolicyBindings version="2.0.1"

                     xmlns="http://schemas.oracle.com/bpel/faultpolicy"

                     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

   <service faultPolicy="RejectedMessage">

      <name>PollCustomerData</name>

   </service>

</faultPolicyBindings>

Please note that “PollCustomerData” is name of the adapter that poll the file.

Now create a fault-policies.xml file where we add fault and required action.

For this error handler below is the format for the action.

<Action id="ora-file">

  <fileAction>

    <location>FOLDER_LOCATION</location>

    <fileName>FILE_NAME</fileName>

<!-- FILE_NAME will support %ID%(rejected message instance id) or %TIMESTAMP% wildcards -->

  </fileAction>

</Action>

Use below content for fault-policies.xml file.

<?xml version="1.0" encoding="UTF-8" ?>

<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">

  <faultPolicy version="2.0.1" id="RejectedMessage">

    <Conditions>

      <!-- remote fault: -->

      <faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages"

                 name="rjm:PollCustomerData">

        <condition>

          <action ref="ora-file"/>

        </condition>

      </faultName>

    </Conditions>

    <Actions>

    <!--write rejected message to file-->

      <Action id="ora-file">

        <fileAction>

          <location>D:\rejectedmsgs</location>

          <fileName>rejmsg_%ID%_%TIMESTAMP%.xml</fileName>

        </fileAction>

      </Action>

    </Actions>

  </faultPolicy>

</faultPolicies>

Please not that fault policy id should be same in both fault-binding.xml and fault-policies.xml file.

Save your changes and deploy your composite.

Testing Result

Now put corrupted file to poll folder. You will see file got deleted and see two files in D:\rejectedmsgs folder.

rejmsg_40003_1399012637053 file contains file content.

rejmsg_40003_1399012637053_metadata file contains metadata information.

Download sample code from here.

Next post explains about next error handler, File Rejection Handler, Web Service Error Handler for File Adapter.

Tweet