15 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 15.1, "General Issues and Workarounds"
Section 15.2, "Installation Issues and Workarounds"
Section 15.3, "Documentation Errata"

15.1 General Issues and Workarounds

This section describes the following general issues:

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

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

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

15.2 Installation Issues and Workarounds

This section describes the installation issues and workarounds for OracleAS Integration InterConnect. It contains the following topics:

Section 15.2.1, "Configuration Assistant Fails During Hub Installation for Incremental InterConnect Installation"

15.2.1 Configuration Assistant Fails During Hub Installation for Incremental InterConnect Installation

Problem

When installing a new version of OracleAS Integration InterConnect on same computer, creation of the new oaiusers.dbf file fails. This is because the oaiusers.dbf file exists even after uninstalling the earlier version of OracleAS Integration InterConnect. The deinstall_schema.sql script is configured to uninstall only the hub schema. Thus, oaiusers.dbf still remains after the uninstallation.

Solution

The deinstall_schema.sql script is modified to uninstall both the hub schema and the associated tablespaces. Dropping the tablespaces will delete the oaiusers.dbf file. So, you should run the deinstall_schema.sql script on the database manually to delete the oaiusers.dbf file before you start the deinstallation. This script is located in the following directory:

MidTierHome\integration\interconnect\repository\sqlHowever, if you skip this step and delete the earlier InterConnect version, then the workaround is to manually delete the oaiusers.dbf file, which is located in the WINNT/System32 directory.

15.3 Documentation Errata

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

15.3.1 Documentation Errors

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

Section 15.3.1.1, "Incorrect Release Number"

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

15.3.2 Additional Documentation

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

Section 15.3.2.1, "Configuring the InterConnect JCA adapter for use with DB2 and Sybase Database"
Section 15.3.2.2, "Application Name value in the oc4j-ra.xml File"

15.3.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 service_classpath parameter of the adapter.ini file, specify the path of the following files:

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

For example:

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\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=TOPLI
NK;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, specify the path of the following files:

db2java_81.zip
db2jcc_81.jar

For example:

service_classpath=C:\Oracle\midtier\integration\interconnect\lib\db2java_81.zip; C:\Oracle\midtier\integration\interconnect\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, specify the path of the following files:

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

For example:

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;

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.o
racle.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, specify the path of the jconn2.jar file.

For example:
```
service_classpath=C:\Oracle\midtier\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=c
om.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}

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