Selecting the Operation Type

Oracle JCA Adapter for Database 9-11 – Update a Field in the [Table_Name] Table Logical Delete – Update a Sequencing Table – Update an External Sequencing Table on a Different Database – Control Table Strategy Figure 9–9 Polling Operations ■ Execute Pure SQL Useful when dealing with arbitrarily complex statements, aggregate queries result is not row-based, and XMLType columns. See Section 9.3.2, Pure SQL - XML Type Support to follow this usage of the Adapter Configuration Wizard. Otherwise, see Section 9.2.5, Selecting and Importing Tables to continue using the Adapter Configuration Wizard.

9.2.5 Selecting and Importing Tables

Figure 9–10 shows where you select the root database table for your operation. If you are using multiple related tables, then this is the highest-level table or highest parent table in the relationship tree. Note: Schema Bound XML tables are not supported. 9-12 Oracle Fusion Middleware Users Guide for Technology Adapters Figure 9–10 The Adapter Configuration Wizard: Select Table Selecting Import Tables launches a sub-wizard, which lets you search for and select multiple tables to import from the database. Removing a table removes or undoes any relationships on related tables that remain. If any underlying tables have changed when running this wizard in edit mode, you get a warning showing you what changes have occurred. To reconcile, import the tables again. Note that if you click Import Tables and select multiple tables, then relationships between these tables are inferred based on the foreign key constraints. However if you launch Import Tables once for each table imported, then no relationships are inferred. See Section 9.2.6, Defining Primary Keys to continue using the Adapter Configuration Wizard.

9.2.6 Defining Primary Keys

If any of the tables you have imported do not have primary keys defined on the database, you are prompted to provide a primary key for each one, as shown in Figure 9–11 . You must specify a primary key for all imported tables. You can select multiple fields to specify a multipart primary key. Note: If you reimport a table, you lose any custom relationships you may have defined on that table as well as any custom WHERE clauses if the table being imported was the root table. Oracle JCA Adapter for Database 9-13 Figure 9–11 The Adapter Configuration Wizard: Define Primary Keys Page The primary key that you specify here is recorded on the offline database table and is not persisted back to the database schema; the database schema is left untouched. See Section 9.2.7, Creating Relationships to continue using the Adapter Configuration Wizard.

9.2.7 Creating Relationships

Figure 9–12 shows the relationships defined on the root database table and any other related tables. You can click Create Relationships… to create a new relationship Note: Note that Oracle Database Adapter only supports tables where there is a primary key defined. If primary key constraints have not been defined on a table explicitly, then you must provide one at design time while defining the Oracle Database Adapter by using the Adapter Configuration Wizard. If you do not provide a valid primary key, then the unique constraint is not guaranteed, and this could result in possible loss of messages at run time. That is, rows with duplicate primary key values are likely to be lost. To obtain a sample that describes how to use the row id field as primary key, access the Oracle SOA Sample Code site, and select the Adapters tab. Note: Oracle recommends that you use varchar instead of char for primary key columns, otherwise you will need to set the weblogic-ra.xml property shouldTrimStrings to false. The truncation of trailing spaces could cause the primary key to be read incorrectly, making it impossible to update read rows as processed.