JDBC/ODBC Adapter Connectivity Map Properties Configuration

When you connect an External Application to a Collaboration, Netbeans IDE automatically assigns the appropriate adapter to the link. Each adapter is supplied with a list of adapter connections (transaction support levels) from which to choose.

Transaction support levels provided by the JDBC Adapter include:

• Connectivity Map Outbound Adapter Properties

• Connectivity Map Outbound non-Transactional Adapter Properties

• Connectivity Map Outbound XA Adapter Properties

For more information on Transaction Support Levels, refer to:

• Transaction Support Levels Between Different Versions

Connectivity Map Outbound Adapter Properties

The Outbound Adapter Properties include outbound parameters used by the external database.

Table 1–16 Outbound Adapter—JDBC Connector Settings

Name	Description	Required Value
Description	The description of the database.	A valid string.

Connectivity Map Outbound non-Transactional Adapter Properties

The Outbound non-Transactional Adapter Properties include outbound parameters used by the external database.

Table 1–17 Outbound non-Transactional Adapter—JDBC Connector Settings

Name	Description	Required Value
Description	The description of the database.	Any valid string.

Connectivity Map Outbound XA Adapter Properties

The Outbound XA Adapter Properties include outbound parameters used by the external database.

Table 1–18 Outbound XA Adapter—JDBC Connector Settings

Name	Description	Required Value
Description	The description of the database.	Any valid string.

Transaction Support Levels Between Different Versions

The types of transaction support levels used in Java CAPS 5.1.X may be different from the support levels used in Java CAPS 6.0. Projects that are imported from a Java CAPS 5.1.X version can potentially display different results, depending on whether the 5.1.X Java Collaboration Definition (JCD) included multiple (insert/update/delete) operations. This only affects non-XA transactions. If you are using an XA transaction, then you can skip this section.

Example:

In 5.1.X, five new records are to be inserted into a table. If the last record fails to insert (such as when a duplicate key exists), all previous records will have been inserted. This is the behavior of NoTransaction support.

In 6.0, five new records are to be inserted into a table. If one of the records fails to insert (such as when a duplicate key exists), the other four records will not be inserted. This is the behavior of the LocalTransaction.

In order to achieve the same result as in 5.1.X versions, you can choose the method below:

1. In the Connectivity Map, delete the link to the database external application, then reconnect the link and select NoTransaction.

2. Fill in the NoTransaction property for the database external system under the Environment.

3. Rebuild the Project.

The following charts identifies what transaction support levels changed between 5.0.5 and 6.0, and 5.1.3 and 6.0, respectively.

---

Note –

there are no changes when migrating from ICAN version 5.0.5 and Java CAPS 6.0.

---

If you want 6.0 behavior for a LocalTransaction, then set your adapter connection to be Outbound JDBC/ODBC non-Transactional Adapter (NoTransaction).