Specifying Inbound Retry Properties in the composite.xml File Changing the Default Value of jca.retry. count for Inbound Adapter Endpoints

ADAPTER Life-Cycle Management 2-37 You can change the global property for capping retries to alter the default value of jca.retry.count from an indefinite to a finite number. In this case, where you set the default value of jca.retry.count to a finite number, even if you do not explicitly configure a value for the jca.retry.count property for a particular inbound adapter endpoint, the global default takes effect. If you specify the global default along with the value in the composite.xml, the value specified in the composite.xml overrides the global value. You can modify the global property using the MBeans browser Adapter Mbean of the Oracle Enterprise Manager. Any change you do through the MBeans browser takes immediate effect for all current and future endpoints.

2.22.2.2.4 Global Property Modification using the MBeans Browser

To modify the global property using the MBeans browser Adapter Mbean of the Oracle Enterprise Manager, you must use the following procedure: 1. Navigate to http:servername:portnumberem. The Fusion Middleware Control Console displays its home page.

2. Right-click soa-infra from the SOA Folder in the navigator in the left pane.

The soa-infra page is displayed. 3. From the SOA Infrastructure menu, select Administration, and then System Mbean Browser, as shown in Figure 2–11 . The System Mbean Browser page is displayed. Figure 2–11 The soa-infra Page

4. Select oracle.as.soainfra.config, Server , AdapterConfig, and then adapter, as

shown in Figure 2–12 . 2-38 Oracle Fusion Middleware Users Guide for Technology Adapters Figure 2–12 The soa-infra Page: System MBean Browser oracle.as.soainfra.config, Server, AdapterConfig, and adapter selected.

5. Modify the GlobalInboundJcaRetryCount attribute as an example of a Global

Property

2.22.2.3 Inbound Non-Retryable Errors

Typically non-retryable errors are a result of either transformation or message parsing. Inbound adapters handle non-retryable errors thrown from EIS by rejecting the inbound messages. If the error is a non-retryable error, you need to use the rejection handler to handle the non-retryable error.

2.22.2.3.1 Examples of Non-Retryable Errors

Examples of non-retryable errors thrown from interaction with an Enterprise Information System include the following: ■ Primary key violation ■ Queue does not exist ■ Master record does not exist ■ Unable to serialize payload Non-retryable errors do not resolve themselves until after the operation is retried. For example, messages can be sent from a file to an inbound file adapter via a Mediator. The Mediator, in turn, has sequential routing to an outbound Database Adapter that inserts data to a database table. The DB adapter might encounter a unique constraint error as it is performing the insert operation. This unique constraint error is: ■ Considered by the outbound Database Adapter as a non-retrybable error ■ Propagated back to the inbound Adapter ■ Considered by the inbound adapter as a non-retryable error as well, using a rejection handler. The adapter will use a fault policy if one is defined.