13 Oracle Application Server Integration InterConnect

This chapter describes the issues related to Oracle Application Server Integration InterConnect (OracleAS Integration InterConnect). This chapter contains the following topics:

Section 13.1, "General Issues and Workarounds"
Section 13.2, "Documentation Errata"

13.1 General Issues and Workarounds

This section describes the following general issues:

Section 13.1.1, "Adapters Duplicate the Messages During Failover on Real Application Cluster (RAC) or Cold Failover Cluster (CFC) Environment"
Section 13.1.2, "JCA adapter Does Not Support High Availability"

13.1.1 Adapters Duplicate the Messages During Failover on Real Application Cluster (RAC) or Cold Failover Cluster (CFC) Environment

If your AQ adapter and the database adapter are configured to use the RAC database or the CFC database for high availability, then during the failover of the adapters from primary instance to the secondary instance, the message which is being processed at the time of failover will get duplicated.

Example: You send 100 messages from the AQ adapter. The Database adapter is subscribing to these messages. If the primary instance of the database fails while processing the thirtieth message, then the adapters successfully fail over to the secondary instance, but in the process, duplicate the thirtieth message. As a result, the subscribing adapter ends up subscribing to the thirtieth message twice and the total number of messages would be 101.

13.1.2 JCA adapter Does Not Support High Availability

In Oracle Application Server Integration InterConnect release 10.1.2.0.2, the JCA adapter does not support high availability functionality.

13.2 Documentation Errata

This section describes known errors and omissions in Oracle Application Server Integration InterConnect documentation.

13.2.1 Documentation Errors

This section describes the following known errors in the Oracle Application Server Integration InterConnect documentation.

Section 13.2.1.1, "Incorrect Release Number"

13.2.1.1 Incorrect Release Number

Appendix A " Upgrading Oracle Application Server Integration InterConnect" of Oracle Application Server Integration InterConnect Installation Guide contains incorrect release number. The release number 10.1.2.0.1 in the appendix should read as 10.1.2.0.0.

13.2.2 Additional Documentation

This section describes following known additions to the Oracle Application Server Integration InterConnect documentation.

Section 13.2.2.1, "Configuring the InterConnect JCA adapter for use with DB2 and Sybase Database"

13.2.2.1 Configuring the InterConnect JCA adapter for use with DB2 and Sybase Database

The section 2.3 "Configuring the JCA Adapter" of the Oracle Application Server Integration InterConnect Adapter for JCA Installation and User's Guide is missing the subsection "Configuring the InterConnect JCA adapter for use with DB2 and Sybase Database." This subsection should be read as follows:

You can connect to an external database in the following ways:

By using the DataDirect drivers (provided by Oracle)
By using the drivers provided by specific vendors

DB2 Configuration

This section explains how to configure the JCA adapter, for use with the DB2 database, by using the following drivers:

DataDirect Driver
Net Driver

DataDirect Driver If using the DataDirect driver, then perform the following steps:

In the classpath variable of the Start file, specify the path of the following files:

YMbase.jar
YMoc4j.jar
YMutil.jar
YMdb2.jar

For example:

java -server -Dadapter=dbapp -DORBdisableLocator=true -ms${INITIAL_MEMORY}m -mx${MAX_MEMORY}m -classpath :/private1/hsrirama/Ora1012/integration/interconnect/lib/YMbase.jar:/private1/hsrirama/Ora1012/lib/YMoc4j.jar:/private1/hsrirama/Ora1012/lib/YMutil.jar:/private1/hsrirama/Ora1012/lib/YMdb2.jar

Specify the driver class name in the adapter.ini file of the JCA adapter.
```
DriverClassName=com.oracle.ias.jdbc.db2.DB2Driver
```

Specify the database URL in the adapter.ini file of the JCA adapter:

ConnectionString=jdbc:oracle:db2://144.23.214.118:50001;DatabaseName=TOPLINK;PackageName=JDBCPKG; CreateDefaultPackage=TRUE;ReplacePackage=TRUE

For example:

connection1_name=eis/DB/DB2Connection
connection1_mcf_class=oracle.tip.adapter.db.DBManagedConnectionFactory
connection1_mcf_params={ConnectionString=jdbc:oracle:db2://144.23.214.118:50001;DatabaseName=TOPLINK;PackageName=JDBCPKG; CreateDefaultPackage=TRUE;ReplacePackage=TRUE, DriverClassName=com.oracle.ias.jdbc.db2.DB2Driver, UserName=testuser, Password=testpassword, platformClassName=oracle.toplink.internal.databaseaccess.DB2Platform}

Net Driver If using the Net driver, then perform the following steps:

In the service_classpath parameter of the adapter.ini file (for Windows) or the classpath variable of the Start file (for Unix), specify the path of the following files:

db2java_81.zip
db2jcc_81.jar

For example:

<Windows>
service_classpath=C:\Oracle\midtier\integration\interconnect\lib\db2java_81.zip; C:\Oracle\midtier\integration\interconnect\lib\db2jcc_81.jar

<Unix>
java -server -Dadapter=dbapp -DORBdisableLocator=true -ms${INITIAL_MEMORY}m -mx${MAX_MEMORY}m -classpath :/private1/hsrirama/Ora1012/integration/interconnect/lib/db2java_81.zip:/private1/hsrirama/Ora1012/lib/db2jcc_81.jar

Specify the driver class name in the adapter.ini file of the JCA adapter.
```
DriverClassName=COM.ibm.db2.jdbc.net.DB2Driver
```

Specify the database URL in the adapter.ini file of the JCA adapter:

ConnectionString=jdbc:db2:144.23.214.118:TOPLINK, DriverClassName=COM.ibm.db2.jdbc.net.DB2Driver, UserName=testuser, Password=testpassword, platformClassName=oracle.toplink.internal.databaseaccess.DB2Platform

For example:

connection1_name=eis/DB/DB2Connection
connection1_mcf_class=oracle.tip.adapter.db.DBManagedConnectionFactory
connection1_mcf_params={ConnectionString=jdbc:db2:144.23.214.118:TOPLINK, DriverClassName=COM.ibm.db2.jdbc.net.DB2Driver, UserName=testuser, Password=testpassword, platformClassName=oracle.toplink.internal.databaseaccess.DB2Platform}

Sybase Configuration

This section explains how to configure the JCA adapter, for use with the Sybase database, by using the following drivers:

DataDirect Driver
Jconn Driver

DataDirect Driver If using the DataDirect driver, then perform the following steps:

In the service_classpath parameter of the adapter.ini file (for Windows) or the classpath variable of the Start file (for Unix), specify the path of the following files:

YMbase.jar
YMoc4j.jar
YMutil.jar
YMsybase.jar

For example:

<Windows>
service_classpath=C:\Oracle\midtier\integration\interconnect\lib\YMbase.jar; C:\Oracle\midtier\integration\interconnect\lib\YMoc4j.jar;C:\Oracle\midtier\integration\interconnect\lib\YMutil.jar;C:\Oracle\midtier\integration\interconnect\lib\YMsybase.jar;

<Unix>
java -server -Dadapter=dbapp -DORBdisableLocator=true -ms${INITIAL_MEMORY}m -mx${MAX_MEMORY}m -classpath :/private1/hsrirama/Ora1012/integration/interconnect/lib/YMbase.jar:/private1/hsrirama/Ora1012/lib/YMoc4j.jar:/private1/hsrirama/Ora1012/lib/YMutil.jar:/private1/hsrirama/Ora1012/lib/YMsybase.jar

Specify the driver class name in the adapter.ini file of the JCA adapter.
```
DriverClassName=com.oracle.ias.jdbc.sybase.SybaseDriver
```

Specify the database URL in the adapter.ini file of the JCA adapter:

ConnectionString=jdbc:oracle:sybase://144.23.214.104:5001;DriverClassName=com.oracle.ias.jdbc.sybase.SybaseDriver, UserName=testuser, Password=testpassword, platformClassName=oracle.toplink.internal.databaseaccess.DatabasePlatform

For example:

connection1_name=eis/DB/SybaseConnection
connection1_mcf_class=oracle.tip.adapter.db.DBManagedConnectionFactory
connection1_mcf_params={ConnectionString=jdbc:oracle:sybase://144.23.214.104:5001, DriverClassName=com.oracle.ias.jdbc.sybase.SybaseDriver, UserName=testuser, Password=testpassword, platformClassName=oracle.toplink.internal.databaseaccess.DatabasePlatform}

Jconn Driver If using the Jconn driver, then perform the following steps:

In the service_classpath parameter of the adapter.ini file (for Windows) or the classpath variable of the Start file (for Unix), specify the path of the jconn2.jar file.

For example:

<Windows>
service_classpath=C:\Oracle\midtier\integration\interconnect\lib\jconn2.jar

<Unix>
java -server -Dadapter=dbapp -DORBdisableLocator=true -ms${INITIAL_MEMORY}m -mx${MAX_MEMORY}m -classpath :/private1/hsrirama/Ora1012/integration/interconnect/lib/jconn2.jar

Specify the driver class name in the adapter.ini file of the JCA adapter.
```
DriverClassName=com.sybase.jdbc2.jdbc.SybDriver
```

Specify the database URL in the adapter.ini file of the JCA adapter:

ConnectionString=jdbc:sybase:Tds:144.23.214.104:5001/TestUser;DriverClassName=com.sybase.jdbc2.jdbc.SybDriver, UserName=testuser, Password=testpassword, platformClassName=oracle.toplink.internal.databaseaccess.DatabasePlatform

For example:

connection1_name=eis/DB/DB2Connection
connection1_mcf_class=oracle.tip.adapter.db.DBManagedConnectionFactory
connection1_mcf_params={ConnectionString=jdbc:sybase:Tds:144.23.214.104:5001/TestUser, DriverClassName=com.sybase.jdbc2.jdbc.SybDriver, UserName=testuser, Password=testpassword, platformClassName=oracle.toplink.internal.databaseaccess.DatabasePlatform}

13.2.2.2 Application Name value in the oc4j-ra.xml File

The section A.3 "Configuration" of the Oracle Application Server Integration InterConnect User's Guide has incomplete information in "The name of the application" step. This step should be read as follows:

The name of the application.
```
<config-property name="applicationName" value="BPELServer"/>
```
Note:
Application name in the oc4j-ra.xml file should be similar to the application name in iStudio.