Integration Process & Exception Handling

LOCAL INTEGRATION PROCESS:

You use the local integration process to simplify your integration process. You can break down the main
integration process into smaller fragments by using local integration processes. You combine these
fragments to achieve your main integration process.

1. Choose the local integration process element you want to configure.

2. If you want to provide a name for the local integration process element, in the Name field
under the General tab, enter name.
3. If you want to specify the transaction handling of the message, choose a value
for Transaction Handling under the Processing tab.

What is Transaction handling?

You can configure transaction handling on integration process or local integration process level.

Transactional processing means that the message (as defined by the steps contained in a process)
is processed within one transaction.
 Integration Process & Exception Handling

For example, consider a process with a Data Store Write operation. If transaction handling is
activated, the Data Store entry is only committed if the whole process is executed successfully.
In an error case, the transaction is rolled back, and the Data Store entry is not written. If
transaction handling is deactivated, the Data Store entry is committed directly when the
integration flow step is executed. In an error case, the Data Store entry is nevertheless persisted
(and not removed or rolled back).

Required for You can specify that Java Database Connectivity (JDBC) transactional database
JDBC processing is applied (to ensure that the process is accomplished within one
transaction).

Required for You can specify that Java Message Service (JMS) transactional database
JMS processing is applied (to ensure that the process is accomplished within one
transaction).

You can define a Transaction Timeout (in minutes).

Not Required No specific transactional processing is configured. The integration process does
not process transactions even if (for example) data store operations are
included.
 Integration Process & Exception Handling

To configure a transactional process for a local Integration Process, select one of the following options for
the Transaction Handling property:

From Calling Transactional processing is inherited from the calling process. The value
Process defined for the calling process is used as the timeout.

Required for You can specify that Java Message Service (JMS) transactional database
JMS processing is applied.

Required for You can specify that Java Database Connectivity (JDBC) transactional
JDBC database processing is applied (to ensure that the process is accomplished
within one transaction).

What is Exception Subprocess?

You use this element to catch any exceptions thrown in the integration process and handle them.
 Integration Process & Exception Handling

1. Open your integration flow in the editor.

2. To add an exception subprocess to the integration flow, choose Process Exception

Subprocess from the palette. The subprocess can be dropped into the integration process
and should not be connected to any of the elements of the integration flow.

3. Select the exception subprocess.

a. In the property sheet specify a name.

4. Start the process with Error Start event always.

5. End the process with either End Message or Error End or Escalation event

Notes:
 The message processing log will be in an error state even if a user catches an exception
and performs additional processing on it.
 Integration Process & Exception Handling

 You can get more details on exception using ${exception.message} or $

{exception.stacktrace}.

 You cannot catch exceptions of local integration process in the main integration process.

 When an error is thrown during integration runtime and the same is caught by the
Exception Subprocess, the processing gets terminated.

How to handle Exception?

To handle exceptions, add an exception subprocess to the integration flow.

Exceptions that occur during message processing are caught and handled by the logic
implemented in the exception subprocess. The exception handling can even distinguish between
different error situations in the exception subprocess and, according to the error category, send
back a custom error message to the sender application system.

You can implement 3 variants - using different types of end events:

Exception
Subprocess Ending
with ... Use Case and Exception Handling

End event Use this variant if you want to reply with a custom error message.

In this case, the message is set to status Completed. You've the option

to define a custom status that allows you to distinguish this error
situation from successfully processed messages.

Error end event Use this variant to catch an error in an exception subprocess to add
additional information to the message processing log.

In this use case, the message status is set to Failed.

Escalation end Use this variant to catch an error in an exception subprocess to add
event additional information to the message processing log.
 Integration Process & Exception Handling

Exception
Subprocess Ending
with ... Use Case and Exception Handling

In this use case, the message status is set to Escalated that allows you
to search for messages based on the dedicated Escalated message
status.

------------------------------------------------------Happy Learning---------------------------------------------------------------