Installation and usage

This section discusses the following:

Installing OracleAppsODA

To install OracleAppsODA, use the Installer. Follow the instructions in the System Installation Guide for UNIX or for Windows. When the installation is complete, the following files are installed in the directory on your system where you have installed the product:

Note:
Except as otherwise noted, this document uses backslashes (\) as the convention for directory paths. For UNIX installations, substitute slashes (/) for backslashes. All product pathnames are relative to the directory where the adapter is installed on your system.

Before using OracleAppsODA

Before you can run OracleAppsODA, you must:

Add your database driver to the DRIVERPATH in the start script. For example, if you are using DB2, add db2java.zip.

After installing the JDBC driver and setting configuration values in the shell or batch file, you must do the following to generate business objects:

  1. Launch the ODA.
  2. Launch Business Object Designer.
  3. Follow a six-step process in Business Object Designer to configure and run the ODA.

The following sections describe these steps in detail.

Launching OracleAppsODA

You can launch the OracleAppsODA with the startup script appropriate for your operating system.

UNIX:

start_OracleAppsODA.sh

Windows:

start_OracleAppsODA.bat

You configure and run OracleAppsODA using Business Object Designer. Business Object Designer locates each ODA by the name specified in the AGENTNAME variable of each script or batch file. The default ODA name for this connector is JDBCODA.

Running multiple instances of OracleAppsODA

It is recommended that you change the name of the ODA when you run multiple instances of it. To create additional uniquely named instances of OracleAppsODA:

It is recommended that you prefix each name with the name of the host machine when you run ODA instances on different machines.If you registered the ODA with an Object Activation Daemon, you can use an ORB finder (osfind) to locate existing CORBA object names on your network.

Working with error and trace message files

Error and trace message files (the default is OracleAppsODAAgent.txt) are located in \ODA\messages\, which is under the product directory. These files use the following naming convention:

AgentNameAgent.txt

If you create multiple instances of the ODA script or batch file and provide a unique name for each represented ODA, you can have a message file for each ODA instance. Alternatively, you can have differently named ODAs use the same message file. There are two ways to specify a valid message file:

Important

Failing to correctly specify the message file's name when you configure the ODA causes it to run without messages. For more information on specifying the message file name, see Configure initialization properties.

During the configuration process, you specify:

Table 13 describes these values.

Table 13. Tracing levels
Trace Level Description
0 Logs all errors
1 Traces all entering and exiting messages for method
2 Traces the ODA's properties and their values
3 Traces the names of all business objects
4 Traces details of all spawned threads
5
  • Indicates the ODA initialization values for all of its properties
  • Traces a detailed status of each thread that OracleAppsODA spawned
  • Traces the business object definition dump

For information on where you configure these values, see Configure initialization properties.

Copyright IBM Corporation 1997, 2005. All Rights Reserved.