This section discusses the following:
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:
Before you can run OracleAppsODA, you must:
Table 17. Shell and batch file configuration variables
Variable | Explanation | Example |
---|---|---|
AGENTNAME | Name of the ODA |
UNIX: AGENTNAME=OracleAppsODA Windows: set AGENTNAME=OracleAppsODA
|
AGENT | Name of the ODA's jar file |
UNIX: AGENT=$CROSSWORLDS/ODA/OracleApps/ OracleAppsODA.jar Windows: set AGENT=%CROSSWORLDS%\ODA\OracleApps\
OracleAppsODA.jar
|
DRIVERPATH | Path of JDBC driver library; OracleAppsODA uses the driver classes to establish a connection to a specified database |
UNIX: DRIVERPATH=$CROSSWORLDS/lib/ xwutil.jar:$CROSSWORLDS/lib/ xwbase.jar:$CROSSWORLDS/lib/ xwsqlserver.jar:$CROSSWORLDS/lib/ spy/lib/spy.jar Windows: set DRIVERPATH=%CROSSWORLDS%\lib\
xwutil.jar;%CROSSWORLDS%\lib\
xwbase.jar;%CROSSWORLDS%\lib\
xwsqlserver.jar;%CROSSWORLDS%\lib\ spy\lib\spy.jar
|
DRIVVERLIB | Path of the native libraries used by the JDBC driver |
UNIX: DRIVERLIB=$CROSSWORLDS/bin/db2jdbc.dll Windows:
DRIVERLIB=%CROSSWORLDS%\bin\db2jdbc.dll
|
After installing the JDBC driver and setting configuration values in the shell or batch file, you must do the following to generate business objects:
The following sections describe these steps in detail.
You can launch the JDBCODA with the startup script appropriate for your operating system.
UNIX:
start_JDBCODA.sh
Windows:
start_JDBCODA.bat
You configure and run JDBCODA 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.
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.
Figure 8 illustrates the window in Business Object Designer from which you select the ODA to run.
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 18 describes these values.
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 |
|
For information on where you configure these values, see "Configure initialization properties".