Chapter 1 Configuring Java CAPS Project Components for Database Adapters

The following topics provide instructions on how to configure Java CAPS project components for database adapters:

• Configuring Java CAPS Adapter Connectivity Map Properties

• DB2 Connect Adapter Inbound Connectivity Map Properties

• DB2 Connect Adapter Outbound Connectivity Map Properties

• DB2 Adapter Inbound Connectivity Map Properties

• DB2 Adapter Outbound Connectivity Map Properties

• Informix Adapter Connectivity Map Properties Configuration

• JDBC/ODBC Adapter Connectivity Map Properties Configuration

• Oracle Adapter Inbound Connectivity Map Properties

• Oracle Adapter Outbound Connectivity Map Properties

• SQL Server Adapter Inbound Connectivity Map Properties

• SQL Server Adapter Outbound Connectivity Map Properties

• Sybase Adapter Connectivity Map Properties

• VSAM Adapter Outbound Connectivity Map Properties

Configuring Java CAPS Adapter Connectivity Map Properties

This topic describes how to set the connectivity map properties for Java CAPS Adapters.

All adapters contain a unique set of default configuration parameters. After the adapters are established and an External System is created in the Project’s Environment, the adapter parameters are modified for your specific system. Adapter configuration parameters are modified from the following locations:

• Connectivity Map: These parameters most commonly apply to a specific component adapter, and may vary from other adapters (of the same type) in the Project.

• Environment Explorer: These parameters are commonly global, applying to all adapters (of the same type) in the Project. The saved properties are shared by all adapters in the External System window.

• Collaboration or Business Process: Adapter properties may also be set from your Collaboration or Business Process, in which case the settings will override the corresponding properties in the adapter’s Connectivity Map configuration. Any properties that are not overridden retain their configured default settings.

Configuring the Adapter Connectivity Map Properties

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 template containing default configuration properties that are accessible on the Connectivity Map.

Adapters can be configured for inbound and/or outbound modes in a Connectivity Map.

To Configure the Inbound Adapter Properties

1. On the Connectivity Map, double-click the Adapter icon.

   The adapter Properties window appears, displaying the default properties for the Inbound adapter.

To Configure the Outbound Adapter Properties

1. On the Connectivity Map, double-click the Adapter icon.

   The adapter Properties window appears, displaying the default properties for the Outbound adapter.

DB2 Connect Adapter Inbound Connectivity Map Properties

The Inbound configuration parameters, accessed from the Connectivity Map, are organized into the following sections:

• DB2 Connect Type 4 Adapter - Inbound Parameter Settings

• DB2 Connect Adapter - Inbound Parameter Settings

DB2 Connect Type 4 Adapter - Inbound Parameter Settings

The Parameter Settings section of the DB2 Connect Type 4 Adapter Inbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–1 DB2 Connect Adapter Inbound Type 4

Name	Description	Required Value
Pollmilliseconds	Polling interval in milliseconds.	A valid numeric value. The default is 5000.
PreparedStatement	The Prepared Statement used for polling against the database.	The Prepared Statement must be the same Statement you created using the Database OTD Wizard. Only a SELECT Statement is allowed. Additionally, no place holders should be used. This is a SQL statement that cannot contain any input data (i.e. you cannot use "?" in the Prepared Query).

DB2 Connect Adapter - Inbound Parameter Settings

The Parameter Settings section of the DB2 Connect Adapter Inbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–2 DB2 Connect Adapter Inbound Type 4

Name	Description	Required Value
Pollmilliseconds	Polling interval in milliseconds.	A valid numeric value. The default is 5000.
PreparedStatement	The Prepared Statement used for polling against the database.	The Prepared Statement must be the same Statement you created using the Database OTD Wizard. Only a SELECT Statement is allowed. Additionally, no place holders should be used. This is a SQL statement that cannot contain any input data (i.e. you cannot use "?" in the Prepared Query).

DB2 Connect Adapter Outbound Connectivity Map Properties

The Outbound configuration parameters, accessed from the Connectivity Map, are organized into the following sections:

• DB2 Connect Type 4 Adapter - Outbound JDBC Connector Settings

• DB2 Connect XA Adapter - Outbound JDBC Connector Settings

• DB2 Connect Adapter - Outbound JDBC Connector Settings

• DB2 Connect non-Transactional Type 4 Adapter - Outbound JDBC Connector Settings

• DB2 Connect Type 4 XA Adapter - Outbound JDBC Connector Settings

• DB2 Connect non-Transactional Adapter - Outbound JDBC Connector Settings

DB2 Connect Type 4 Adapter - Outbound JDBC Connector Settings

The JDBC Connector Settings section in the DB2 Connect Type 4 Adapter Outbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–3 DB2 Connector Type 4 Adapter - Outbound JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is DB2 Connect Type 4 Connection Pool Datasource.
ClassName	Specify the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface for a Type 4 driver.	A valid class name.  The default is com.ibm.db2.jcc.DB2ConnectionPoolDataSource.

DB2 Connect XA Adapter - Outbound JDBC Connector Settings

The JDBC Connector Settings section in the DB2 Connect XA Adapter Outbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–4 DB2 Connect XA Adapter - Outbound JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is DB2 Connect XA Datasource.
ClassName	Specify the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface for a XA driver.	A valid class name.  The default is COM.ibm.db2.jdbc.DB2XADataSource.

DB2 Connect Adapter - Outbound JDBC Connector Settings

The JDBC Connector Settings section in the DB2 Connect Adapter Outbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–5 DB2 Connect Adapter - Outbound JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is DB2 Connect Connection Pool Datasource.
ClassName	Specify the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name.  The default is COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource.

DB2 Connect non-Transactional Type 4 Adapter - Outbound JDBC Connector Settings

The JDBC Connector Settings section in the DB2 Connect non-Transactional Type 4 Adapter Outbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–6 DB2 Connect non-Transactional Type 4 Adapter - Outbound JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is DB2 Connect Type 4 Connection Pool Datasource
ClassName	Specify the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface for a non-transactional Type 4 driver.	A valid class name.  The default is com.ibm.db2.jcc.DB2ConnectionPoolDataSource.

DB2 Connect Type 4 XA Adapter - Outbound JDBC Connector Settings

The JDBC Connector Settings section in the DB2 Connect Type 4 XA Adapter Outbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–7 DB2 Connect Type 4 XA Adapter - Outbound JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is DB2 Connect Type 4 XA Datasource.
ClassName	Specify the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface for a Type 4 XA driver.	A valid class name.  The default is com.ibm.db2.jcc.DB2XADataSource.

DB2 Connect non-Transactional Adapter - Outbound JDBC Connector Settings

The JDBC Connector Settings section in the Outbound DB2 Connect non-Transactional Adapter Outbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–8 DB2 Connect non-Transactional Adapter - Outbound JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is DB2 Connect non-Transactional Connection Pool Datasource.
ClassName	Specify the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface for a non-transactional driver.	A valid class name.  The default is COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource.

DB2 Adapter Inbound Connectivity Map Properties

The Inbound configuration parameters, accessed from the Connectivity Map, are organized into the following sections:

• DB2 Adapter Inbound Properties for Windows and UNIX

• DB2 Adapter Inbound Properties for z/OS and AS/400

DB2 Adapter Inbound Properties for Windows and UNIX

The Parameter Settings section of the DB2 Adapter Inbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–9 DB2 Adapter Inbound Connectivity Map Parameter Settings

Name	Description	Required Value
Pollmilliseconds	Polling interval in milliseconds.	A valid numeric value. The default is 5000.
PreparedStatement	The Prepared Statement used for polling against the database.	The Prepared Statement must be the same Statement you created using the Database OTD Wizard. Only a SELECT Statement is allowed. Additionally, no place holders should be used. This is a SQL statement that cannot contain any input data (i.e. you cannot use "?" in the Prepared Query).

DB2 Adapter Inbound Properties for z/OS and AS/400

The Parameter Settings section of the DB2 Adapter Inbound Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–10 DB2 Adapter Inbound Connectivity Map Parameter Settings

Name	Description	Required Value
Pollmilliseconds	Polling interval in milliseconds.	A valid numeric value. The default is 5000.
PreparedStatement	The Prepared Statement used for polling against the database.	The Prepared Statement must be the same Statement you created using the Database OTD Wizard. Only a SELECT Statement is allowed. Additionally, no place holders should be used. This is a SQL statement that cannot contain any input data (i.e. you cannot use "?" in the Prepared Query).

DB2 Adapter Outbound Connectivity Map Properties

The Outbound configuration parameters, accessed from the Connectivity Map, are organized into the following sections:

• DB2 Adapter Outbound Properties for Windows and UNIX

• DB2 Adapter Outbound Properties for z/OS and AS/400

DB2 Adapter Outbound Properties for Windows and UNIX

The JDBC Connector Settings section of the DB2 Adapter Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–11 Windows and UNIX Outbound Connectivity Map JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is DB2 Adapter Connection Pool Datasource.
ClassName	Displays the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name. The default is com.Sun.db2.jdbcx.db2.DB2DataSource  Note – Do not change this value.

DB2 Adapter Outbound Properties for z/OS and AS/400

The JDBC Connector Settings section of the DB2 Adapter Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–12 z/OS and AS/400 Outbound Connectivity Map JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is DB2 Datasource For AS400/zOS.
ClassName	Displays the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name. The default is com.Sun.db2.jdbcx.db2.DB2DataSource.  Note – Do not change this value.

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).

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).

Oracle Adapter Inbound Connectivity Map Properties

The Parameter Settings section of the Inbound Oracle Adapter Connectivity Map properties contains the top-level parameters displayed in the following table.

Name	Description	Required Value
Pollmilliseconds	Polling interval in milliseconds.	A valid numeric value. The default is 5000.
PreparedStatement	The Prepared Statement used for polling against the database.	The Prepared Statement must be the same Statement you created using the Database OTD Wizard. Only a SELECT Statement is allowed. Additionally, no place holders should be used. This is a SQL statement that cannot contain any input data (i.e. you cannot use "?" in the Prepared Query).

Oracle Adapter Outbound Connectivity Map Properties

The Outbound configuration parameters of the Oracle Adapter, accessed from the Connectivity Map, are organized into the following sections:

• Oracle Outbound Adapter Properties

• Oracle Outbound non-Transactional Adapter Properties

• Oracle Outbound Adapter with XA Support Properties

Oracle Outbound Adapter Properties

The JDBC Connector Settings section of the Oracle Adapter Connectivity Map properties contains the top-level parameters displayed in the following table.

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is Oracle thin driver 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 oracle.jdbc.pool.OracleConnectionPoolDataSource Note – Do not change this value.

Oracle Outbound non-Transactional Adapter Properties

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

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

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is Oracle thin driver non-Transactional 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 oracle.jdbc.pool.OracleConnectionPoolDataSource.

Oracle Outbound Adapter with XA Support Properties

The JDBC Connector Settings section of the Oracle Adapter Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–20 Outbound with XA Support JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is Oracle thin driver XA 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 oracle.jdbc.xa.client.OracleXADataSource.

SQL Server Adapter Inbound Connectivity Map Properties

The Parameter Settings section of the SQL Server Adapter Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–21 Inbound Adapter Connectivity Map Parameter Settings

Name	Description	Required Value
Pollmilliseconds	Polling interval in milliseconds.	A valid numeric value. The default is 5000.
PreparedStatement	The Prepared Statement used for polling against the database.	The Prepared Statement must be the same Statement you created using the Database OTD Wizard. Only a SELECT Statement is allowed. Additionally, no place holders should be used. This is a SQL statement that cannot contain any input data (i.e. you cannot use "?" in the Prepared Query).

SQL Server Adapter Outbound Connectivity Map Properties

The Outbound configuration parameters, accessed from the Connectivity Map, are organized into the following sections:

• Outbound SQL Server Adapter Properties

• Outbound non-Transactional SQL Server Adapter Properties

• Outbound SQL Server Adapter with XA Support Properties

Outbound SQL Server Adapter Properties

The JDBC Connector Settings section of the SQL Server Adapter Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–22 Outbound Connectivity Map JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is SQLServer Connection Pool Datasource.
ClassName	Displays the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name. The default is com.Sun.sql server.jdbcx.sqlserver.SQL ServerDataSource. Note – Do not change this value.

Outbound non-Transactional SQL Server Adapter Properties

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

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

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is Sqlserver driver non-Transactional 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.sqlserver.jdbcx.sqlserver.SQLServerDataSource.

Outbound SQL Server Adapter with XA Support Properties

The JDBC Connector Settings section of the SQL Server Adapter Connectivity Map properties contains the top-level parameters displayed in the following table.

Table 1–24 Outbound with XA Support JDBC Connector Settings

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is SQLServer XA Datasource.
ClassName	Displays the Java class in the JDBC driver that is used to implement the SQLServer XA Datasource interface.	A valid class name. The default is com.Sun.sql server.jdbcx.sqlserver.SQL ServerDataSource. Note – Do not change this value.

Sybase Adapter Connectivity Map Properties

When you connect an External Application to a Collaboration, the 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 supported by the Sybase Adapter include:

• Configuring the Outbound Sybase Adapter Properties

• Configuring the Outbound Sybase XA Adapter Properties

• Configuring the Outbound Sybase non-Transactional Adapter Properties

For more information on Transaction Support Levels, refer to:

• Transaction Support Levels Between Different Versions

Configuring the Outbound Sybase Adapter Properties

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

Table 1–25 Outbound Adapter—JDBC Connector Settings

Name	Description	Required Value
Description	Sybase Connection Pool Datasource.	A valid string.
ClassName	Displays the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name.  The default is:  com.SeeBeyond.jdbcx.sybase.sybaseDataSource. Note – Do not change this value.

Configuring the Outbound Sybase XA Adapter Properties

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

Table 1–26 Outbound Adapter—JDBC Connector Settings

Name	Description	Required Value
Description	The description of the database.	A valid string.
ClassName	Displays the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name.  The default is:  com.SeeBeyond.jdbcx.sybase.sybaseDataSource. Note – Do not change this value.

Configuring the Outbound Sybase non-Transactional Adapter Properties

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

Table 1–27 Outbound Adapter—JDBC Connector Settings

Name	Description	Required Value
Description	The description of the database.	A valid string.
ClassName	Displays the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name.  The default is:  com.SeeBeyond.jdbcx.sybase.sybaseDataSource. Note – Do not change this value.

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.

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

   2. 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 that 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 Sybase non-Transactional Adapter (NoTransaction).

   The Configuration properties window opens, displaying the default properties for the adapter.

   

VSAM Adapter Outbound Connectivity Map Properties

The VSAM configuration parameters, accessed from the Connectivity Map, are organized into the following sections:

• VSAM Adapter Outbound Connectivity Map Properties

• VSAM Adapter Outbound non-Transactional Connectivity Map Properties

VSAM Adapter Outbound Connectivity Map Properties

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

Table 1–28 Outbound Adapter — JDBC Connector Settings

Name	Description	Required Value
Description	VSAM Connection Pool Datasource.	A valid string.
ClassName	Displays the Java class in the JDBC driver that is used to implement the ConnectionPoolDataSource interface.	A valid class name. The default is:  com.cac.jdbc.ConnectionPoolDataSource Note – Do not change this value.

VSAM Adapter Outbound non-Transactional Connectivity Map Properties

You can create VSAM 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 parameters used by the external database.

Table 1–29 Outbound VSAM non-Transactional adapter Connectivity Map Properties

Name	Description	Required Value
Description	Enter a description for the database.	A valid string. The default is VSAM 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.cac.jdbc.ConnectionPoolDataSource