This section discusses the following:
To install JDBCODA use the Installer for IBM WebSphere Business Integration Server Express and Express Plus and follow the instructions in the WebSphere Business Integration Server Express installation guide for Windows, OS/400, or 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 JDBCODA, you must:
Table 13. Shell and batch file configuration variables for Windows
Variable | Explanation | Example |
---|---|---|
AGENTNAME | Name of the ODA |
set AGENTNAME=JDBCODA
|
AGENT | Name of the ODA's jar file |
set AGENT= %CROSSWORLDS%\ODA\JDBC\JDBCODA.jar
|
DRIVERPATH | Path of JDBC driver library; JDBCODA uses the driver classes to establish a connection to a specified database |
set DRIVERPATH=%CROSSWORLDS%\ /
lib\xwutil.jar;%CROSSWORLDS%\lib\ /
xwbase.jar;%CROSSWORLDS%\lib\ /
xwsqlserver.jar;%CROSSWORLDS%\lib\ / spy\lib\spy.jar
|
DRIVERLIB | Path of the native libraries used by the JDBC driver |
DRIVERLIB=%CROSSWORLDS%\bin\db2jdbc.dll
|
Table 14. Shell and batch file configuration variables for Linux
Variable | Explanation | Example |
---|---|---|
AGENTNAME | Name of the ODA | set AGENTNAME=JDBCODA |
AGENT | Name of the ODA's jar file | set AGENT= ${CROSSWORLDS}/ODA/JDBC/JDBCODA.jar |
DRIVERPATH | Path of JDBC driver library; JDBCODA uses the driver classes to establish a connection to a specified database | set DRIVERPATH=${CROSSWORLDS}/ lib/xwutil.jar:${CROSSWORLDS}/lib/ xwbase.jar:${CROSSWORLDS}/lib/ xwsqlserver.jar:${CROSSWORLDS}/lib/ xworacle.jar:${CROSSWORLDS}/lib/ spy/lib/spy.jar:${CROSSWORLDS}/lib/ db2java.zip |
DRIVERLIB | Path of the native libraries used by the JDBC driver | DRIVERLIB=${CROSSWORLDS}/bin |
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.
Launching the ODA on Windows
start_JDBCODA.bat
To start on OS/400, you use one of the following methods:
pathToODAStartScript jobDescriptionName
where pathToODAStartScript is the full path to the ODA start
script, and jobDescriptionName is the name of the job description
to use in the QWBISVR43 library.
start_ODAName.sh
Stopping the ODA on OS/400
The way to stop the ODA for OS/400 depends on how it was started. If you used option 1 or 2 in "Launching the ODA on OS/400" then:
If you used option 3 in Launching the ODA on OS/400 to start the ODA, then press F3 from the QSHELL command entry where you ran the start_ODAName.sh script.
Linux:
start_JDBCODA.sh
You configure and run JDBCODA 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 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 JDBCODA:
It is recommended that you prefix each name with the name of the host machine when you run ODA instances on different machines.
Select the ODA tells you how to select the ODA to run.
Error and trace message files (the default is JDBCODAAgent.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:
During the configuration process, you specify:
Table 15 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 | * Indicates the ODA initialization values for all of its properties * Traces a detailed status of each thread that JDBCODA spawned * Traces the business object definition dump |
For information on where you configure these values, see "Configure initialization properties".