This section discusses the following:
To install OracleAppsODA, use the Installer for IBM WebSphere Business Integration Server Express and Express Plus. Follow the instructions in the WebSphere Business Integration Server Express installation guide for Windows, for OS/400, or for Linux.
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 11. Shell and batch file configuration variables for Windows
Variable | Explanation | Example |
---|---|---|
AGENTNAME | Name of the ODA |
Windows and Linux:
|
AGENT | Name of the ODA's jar file |
Windows:
|
DRIVERPATH | Path of JDBC driver library; OracleAppsODA uses the driver classes to establish a connection to a specified database |
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 |
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 OracleAppsODA with the startup script appropriate for your operating system.
To Use the Console function to start the ODA on OS/400, perform the following steps. On the Windows machine where the WebSphere Business Integration Server Express Console is installed:
You configure and run OracleAppsODA using Business Object Designer Express. Business Object Designer Express 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 OracleAppsODA.
Stopping OracleAppsODA: For OS/400, the method you use to stop the ODA depends upon how you started it.
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 6 illustrates the window in Business Object Designer Express 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 12 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".