All cross reference mappings are stored in the form of tables. When you create a cross reference table in a Service Bus project in JDeveloper, you only define the metadata for the table (that is, the keys and not the values). All cross reference tables are stored in the database, by default in the XREF_DATA table. Cross reference tables can either be custom or generic (the default). Generic tables are all stored in a single database table that is created during installation (XREF_DATA); custom tables are each stored in individual database tables that you create. Service Bus uses the standard SOA Suite data source, jdbc/SOADataSource, to access the database tables. You can create your own data source with the following requirements:

• The data source must be named jdbc/xref, otherwise the runtime will use the default schema.

• The data source must be XA enabled.

For instructions on creating a custom database table, see "How to Create Custom Database Tables" in Developing SOA Applications with Oracle SOA Suite.

In the Service Bus message flow, you can reference cross reference tables from XQuery expressions and XSLT transformations using a set of XRef functions to lookup, populate, and update cross reference entries at runtime based on information in incoming messages. Use these functions to populate the values for the keys you defined when you first created the cross reference table.

You can access the XRef functions in JDeveloper from the XSLT mapper, the XQuery mapper, and the expression editors. In the Oracle Service Bus Console, the functions are available from the expression and condition editors. For information about the Service Bus XRef functions, see Cross-Reference Functions.

Fusion Middleware Control provides features to help you manage cross reference data in the runtime. For information and instructions, see "Managing Cross References" in Administering Oracle SOA Suite and Oracle Business Process Management Suite.

1. In the Application Navigator in JDeveloper, right-click the Service Bus project or folder in which you want to create the cross reference.
2. In the menu that appears, point to New and select Cross Reference(XREF).

   The Create Cross Reference(XREF) File dialog appears.

3. In the File Name field, enter a unique name for the cross reference file.

   Two cross reference tables cannot have same name in the cross reference repository. The file name is the name of the cross reference table with an extension of .xref.

4. Optionally enter a new directory location and a brief description for the cross reference.

   The location must be within the directory structure of the current application.

5. In the End System fields, enter the names for up to two end systems.

   The end systems map to the cross reference columns in a cross reference table. You can add more system names once you create the cross reference table. Each name must be unique within a table.

6. Click OK.

   The Cross Reference Editor appears with the new cross reference table displayed.

7. To add new end systems to the cross reference table, click Add above the End Systems table, double-click in the newly added row, and enter the end system name.
8. To create a custom database table for this cross referencing mapping, see How to Create Custom Database Tables in Developing SOA Applications with Oracle SOA Suite.

1. In the Project Navigator, right-click the project or folder to contain the new cross reference mapping, point to Create, and select Resource. Click Miscellaneous, click Cross Reference (XRef), and then click OK.

   The Create Cross Reference (XRef) dialog appears.

2. Do one of the following:

   • To upload an existing cross reference table, click Browse next to the File Upload field and then navigate to and select the file you created in JDeveloper.

     The Resource Name field is automatically populated with the file name minus the file extension. You can change this name.

   • To create a new cross reference table, enter a unique name for the cross reference resource.

3. Optionally, enter a brief description of the resource.
4. Click Create.

   The new cross reference table appears on the Cross Reference (XREF) Definition Editor.

5. In the Cross Reference (XREF) Definition Editor toolbar, click Save.
6. To end the session and deploy the configuration to the runtime, click Activate.

1. On the Cross Reference (XRef) Definition Editor, select Enable Optimization.
2. In the Table Name field, enter a custom name for the database table.

   This custom database table name must be prefixed with xref_, and cannot be XREF_DATA or XREF_DELETED_DATA.

3. Click Save.
4. Create the custom table in the soainfra schema of the Oracle Fusion Middleware database using the following syntax:

   CREATE TABLE TABLE_NAME (
       ROW_ID VARCHAR2(48) NOT NULL,
       SYSTEM1 VARCHAR2(100),
       SYSTEM2 VARCHAR2(100),
       SYSTEM3 VARCHAR2(100),
       LAST_MODIFIED TIMESTAMP NOT NULL
   );
   

   Where TABLE_NAME is the name you specified in step 2 for the custom table, and SYSTEM1, SYSTEM2, and SYSTEM3 are the names of the end systems being cross referenced.

1. In the Application Navigator or Project Navigator, expand the project and folders containing the resource to delete.
2. Right-click the name of the resource, and select Delete.
3. If you are using JDeveloper, a confirmation dialog displays the number of references for the transformation. Click Show Usages to view information about the references, and then click Yes to confirm that you want to delete the resource.
4. If you are using the Oracle Service Bus Console, click Activate to end the session and deploy the configuration to the runtime.