Installing Oracle Apps Adapter

To install the adapter on AS/400, you must use the Installer's console mode, described in the Installing webMethods Products On Premises for your release.

Note:
If you are installing the adapter in a clustered environment, you must install it on each Integration Server in the cluster, and each installation must be identical. For more information about working with the adapter in a clustered environment, see Oracle Apps Adapter in a Clustered Environment.

1. Download Software AG Installer from the Empower Product Support Web site.

2. If you are installing the adapter on an existing Integration Server, shut down the Integration Server.

3. Start the Installer wizard.

4. Choose the webMethods release that includes the Integration Server on which to install the adapter. For example, if you want to install the adapter on Integration Server 9.12, choose the 9.12 release.

5. Specify the installation directory as follows:

If you are installing on an existing Integration Server, specify the webMethods installation directory that contains the host Integration Server.

6. In the Product Selection list, select Adapters >webMethods Oracle Applications Adapter. You can also choose to install documentation.

7. After the installation is finished, go to the host Integration Server_directory directory and open the OracleAppsInstall.log file. Read the file to ensure that the installation process completed successfully.

8. Start the host Integration Server.

9. When Installer installed the adapter, it also installed a set of sample transaction definitions you can use in your adapter services. If you want to use these sample transaction definitions, you must import them into the repository server that Integration Server is using. For information about which sample transaction definitions are available for import, see webMethods Oracle Applications Adapter Sample Transaction Definitions User’s Guide . For instructions on importing the sample transaction definitions into the repository server, see Importing Transaction Definitions.

Note:
For Integration Server version 6.5x, transaction definitions used by adapter services you have created must reside in the repository. In earlier versions of the adapter, once you generated an adapter service, you could remove its underlying transaction definition from the repository. However, if you are upgrading to Oracle Apps Adapter version 6.0 you must reestablish the contents of the repository by importing the transaction definitions for your adapter services. This is necessary for your adapter services and adapter notifications to function properly.

Note:
If you are using Integration Server version 7.1 or later, the repository is not maintained with Integration Server. Instead, the adapter stores the transaction definitions an external database that serves as a shared cache.

10. Install a JDBC driver that complies with the software requirements in the webMethods Adapters System Requirements in the Integration Server_directory \packages\WmOAAdapter\code\jars directory.

Note:
If the host Integration Server has already been configured to use a JDBC driver that is compatible with the adapter, you do not need to install a separate JDBC driver.

If the adapter does not have access to the Java classes for the JDBC driver, you will receive the following error when the adapter attempts to connect to the database:

If the JDBC driver loads successfully but cannot connect to the database for some reason, the resulting error message usually includes some driver-specific codes or messages. The most common source of such errors is an invalid user name or password for the database. Consult your driver documentation for details.

Note:
Software AG recommends that you install the latest fix to include updates from previous fixes to this adapter.