Configuring Inbound Adapters to Handle Retryable Errors

2-36 Oracle Fusion Middleware Users Guide for Technology Adapters You can configure inbound adapters to handle inbound retryable errors. The following properties, which you can specify in the composite.xml file, are supported for retryable exceptions for inbound interactions: By default, there is unlimited retry for inbound errors; however, adapter retry is either at the level of the composite local application or at the global level. Once you have configured properties in the composite, at the service level, the configuration of the properties has meaning. For example, once you configure the number of retries before rejection, the value of the interval property takes its default value. Properties you can specify in the composite.xml file include: ■ jca.retry.count Specifies the maximum number of retries before rejection. Again, specifying this value is a pre-requisite to specifying the other property values. ■ jca.retry.interval Specifies the time interval between retries measured in seconds. ■ jca.retry.backoff Specifies the retry interval growth factor positive integer. ■ jca.retry.maxInterval Specifies the maximum value of retry interval, that is, a cap if backoff 1

2.22.2.2.2 Specifying Inbound Retry Properties in the composite.xml File

You can modify the composite application’s xml descriptor to specify properties that apply to retries. The preceding list of properties are specified in the composite.xml file in JDeveloper, as shown in the following example: service name=Inbound interface.wsdl interface=http:xmlns...wsdl.interfaceInbound_PortType binding.jca config=Inbound_db.jca property name=jca.retry.count5property property name=jca.retry.interval1property property name=jca.retry.backoff2property property name=jca.retry.maxInterval6property binding.jca service For retryable exceptions, you must set the value of jca.retry.count to the number of times that you want the retry to be carried out. For example, if you set the value of jca.retry.count to 10, the retry occurs 10 times. However, if you have not set any value for jca.retry.count, the retry is carried out indefinitely, which is the default for retryable errors.

2.22.2.2.3 Changing the Default Value of jca.retry. count for Inbound Adapter Endpoints

Note: Infinite retries by inbound adapters for errors results in the creation of multiple composite instances, because for every retry a separate composite instance is created. 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 .