Informix 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 Informix Adapter include:

• Table 1–13

• Table 1–14

• Table 1–15

For more information on Transaction Support Levels, refer to:

• Transaction Support Levels Between Different Versions

Outbound Adapter Properties

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

Table 1–13 Outbound Informix Adapter Connectivity Map Properties

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is INFORMIX Connection Pool Datasource.
ClassName	Specifies the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name. The default is com.SeeBeyond.informix.jdbcx.informix.InformixDataSource.

Outbound XA Adapter Properties

The Outbound XA Adapter Properties include outbound parameters used by the external database. Informix supports XA, a data source that provides connections that can participate in a distributed transaction. XA is a two-phase commit protocol that forms part of the JDBC 2.0 Standard Extension.

Table 1–14 Outbound Informix XA Adapter Connectivity Map Properties

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is INFORMIX XA Datasource.
ClassName	Specifies the Java class in the JDBC driver that is used to implement the XADataSource interface.	A valid class name. The default is com.SeeBeyond.informix.jdbcx.informix.InformixDataSource.

Outbound non-Transactional Adapter Properties

You can create Informix databases with or without logging enabled. If logging is disabled, then Non-Transactional mode must be used. Because data logs are not retained during Non-Transactional execution of SQL calls, data recovery is not possible during accidental or unscheduled shut-down of the database server.

Disabled logging also prevents transactions—enclosed in BEGIN-Tran and END-Tran statements—from occurring. This means that Non-Transactional mode cannot be used in XA (two-phase commit) transactions.

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

Table 1–15 Outbound Informix non-Transactional Adapter Connectivity Map Properties

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is INFORMIX non-Transactional Connection Pool Datasource.
ClassName	Specifies the Java class in the JDBC driver that is used to implement the non-Transactional ConnectionPoolDataSource interface.	A valid class name. The default is com.SeeBeyond.informix.jdbcx.informix.InformixDataSource.

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.

   ---

   Note –

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

   ---

   Under the scenario noted above, if you want 6.0 behavior for a LocalTransaction, then set your adapter connection to be Outbound Informix non-Transactional Adapter (NoTransaction).