Update a Sequencing Table Update an External Sequencing Table on a Different Database

Oracle JCA Adapter for Database 9-23 Figure 9–24 The Adapter Configuration Wizard - External Sequencing Table page

9.2.10.5 Update a Sequencing File

Use this option to update a sequencing file. Figure 9–25 shows the Adapter Configuration Wizard - Update a Sequencing File page where you specify the details for performing this operation. Figure 9–25 Adapter Configuration Wizard - Update a Sequencing File Page 9-24 Oracle Fusion Middleware Users Guide for Technology Adapters

9.2.11 Specifying Polling Options

You can specify additional polling options, if any, in this page. Figure 9–26 shows the Adapter Configuration Wizard - Polling Options page. Figure 9–26 Specifying Polling Options In this page, you specify details about how to poll the database table for new rows or events. From the Polling Frequency list, select how frequently to poll for new records or events. In the Database Rows per XML Document field, specify the number of rows per XML document when sending events to Oracle BPEL PM or Mediator. This is the batch setting between the database adapter and its consumer: Oracle BPEL PM or Mediator. In the Database Rows per Transaction field, select Unlimited or enter a value to indicate the number of table rows to process during a single transaction. When polling the database for events, you can order the returned rows by the selected column by using the Order By list. The best practice is to choose No Ordering, as message ordering regardless is not guaranteed without extra configuration. In the SQL field, if the SQL syntax is incorrect, then a message is displayed in red. For more information about specifying polling options, click Help in the Polling Options page or press F1.

9.2.12 Specifying Advanced Options

You can specify advanced options, if any. Figure 9–27 shows the Adapter Configuration Wizard - Advanced Options page. In this page, you can specify advanced JDBC and DBAdapter options, configure retries, and configure native sequencing. Oracle JCA Adapter for Database 9-25 Figure 9–27 Specifying Advanced Options You must specify JDBC options in the JDBC Options section. Set low-level JDBC options on calls to the database. The operation you selected determines which options may appear here. In the Auto-Retries section, specify the value for auto-retry incase of time out. In case of a connection related fault, the Invoke activity can be automatically retried a limited number of times. You can specify the following values in the fields in this section: ■ To retry indefinitely, type unlimited in the Attempts field. ■ Interval is the delay between retries. ■ Backoff Factor: x allows you to wait for increasing periods of time between retries. 9 attempts with a starting interval of 1 and a back off of 2 will lead to retries after 1, 2, 4, 8, 16, 32, 64, 128, and 256 2 8 seconds. In the Interaction Options, specify the interaction options, as follows: ■ GetActiveUnitOfWork is an advanced setting that forces all invoke activities in the same global transaction to use the same SQL connection if going to the same database. This makes it easier to guarantee that later invoke activities can see the changes of earlier invoke activities, but you may not need to set this at all if using emulated two-phase commit, it should automatically be the same connection. Another difference is that for MERGE and INSERT, all changes are not written until the global transaction commits, so this setting also changes the timing of when WRITE operations occur. ■ Detect Omissions allows the MERGE and INSERT operations to ignore empty or missing XML elements in the input payload. For a MERGE operation, this will prevent valid but unspecified values from being overwritten with NULL. For INSERT operations, they will be omitted from the INSERT statement, allowing default values to take effect. ■ Optimize Merge should always be set to true, as it is a general enhancement to MERGE performance using an in query for the primary key existence check.