Before installing, configuring, and using the adapter, you must understand its environmental requirements:
The adapter framework that an adapter uses must be compatible with the version of the integration broker (or brokers) with which the adapter is communicating. The 2.4 version of the adapter for Oracle applications is supported on the following adapter framework and integration brokers:
See the Release Notes for any exceptions.
Note: For instructions on installing the integration broker and its prerequisites, see the following documentation.
For WebSphere InterChange Server (ICS), see the System Installation Guide for UNIX or for Windows.
For message brokers (WebSphere MQ Integrator Broker, WebSphere MQ Integrator, and WebSphere Business Integration Message Broker), see Implementing Adapters with WebSphere Message Brokers, and the installation documentation for the message broker. Some of this can be found at the following Web site: http://www.ibm.com/software/integration/mqfamily/library/manualsa/. For WebSphere Application Server, see Implementing Adapters with WebSphere Application Server and the documentation at: http://www.ibm.com/software/webservers/appserv/library.html
The adapter is supported on the following platforms:
The adapter for Oracle applications supports the following versions of Oracle Applications:
The adapter has the following software prerequisites and dependencies:
Before running the connector, if the connector runs on a different machine from the integration broker, install the Adapter Development Kit that is compatible with the integration broker version.
For example, if you are using the JDBC Type 2 driver for an Oracle database, you must install the OracleOCI libraries.
The connector processes data in an Oracle application using a driver for Oracle that follows the JDBC specification. For the connector to process data in the database, with which it talks directly, it must have access to a user account and password that is valid for the application. The user account must have the privileges to retrieve, insert, update, and delete data from the application's database. If you do not already have such an account, you must create one.
The Java runtime environment within the Java Virtual Machine (JVM) represents data in the Unicode character code set. Unicode contains encodings for characters in most known character sets (both single-byte and multibyte). Because the connector is written in Java, it understands Unicode.
The connector has been internationalized so that it can support double-byte character sets, and deliver message text in the specified language. When the connector transfers data from a location that uses one character code to a location that uses a different code set, it performs character conversion to preserves the meaning of the data.
The Java runtime environment within the Java Virtual Machine (JVM) represents data in the Unicode character code set. Unicode contains encoding for characters in most known character code sets (both single-byte and multibyte). Most components in the WebSphere business integration system are written in Java. Therefore, when data is transferred between most integration components, there is no need for character conversion.
To log error and informational messages in the appropriate language and for the appropriate country or territory, configure the Locale standard configuration property for your environment. For more information on configuration properties, see Appendix A, Standard configuration properties for connectors.