Installation and usage

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 using JDBCODA

Before you can run JDBCODA, you must:

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 Express.
  3. Follow a six-step process in Business Object Designer Express to configure and run the ODA.

The following sections describe these steps in detail.

Launching JDBCODA

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

Launching the ODA on Windows

start_JDBCODA.bat

Launching the ODA on OS/400

To start on OS/400, you use one of the following methods:

  1. From the Windows system where the WebSphere Business Integration Server Express Console is installed, select Programs>IBM WebSphere Business Integration Console for OS/400>Console for OS/400. Then specify the OS/400 system name or IP address and a user profile and password that has *JOBCTL special authority. Select the ODA from the list of ODAs and select the Start ODA button.
  2. From the OS/400 command entry run the QSH CL command and from the QSHELL environment run /QIBM/ProdData/WBIServer43/bin/submit_oda.sh script with the following parameters in order


    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.

  3. From the OS/400 Command entry, run the QSH CL command and from the QSHELL command entry, run the ODA startup script directly:


    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:

  1. From the OS/400 command entry, run the CL command: WRKACTJOB SBS(QWBISVR43). The screen will show all jobs running in the subsystem.
  2. Scroll through the list to find the jobname that matches the job description for the ODA. For the ODAName JDBCODA, it is QWBIJDBCODA.
  3. Select option 4 for this job, and press F4 to prompt for the ENDJOB command. Specify *IMMED for the OPTION parameter.
  4. Press Enter.

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.

Running multiple instances of 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.

Working with error and trace message files

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:

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 15 describes these values.

Table 15. 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 JDBCODA spawned * Traces the business object definition dump

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

Copyright IBM Corp. 2004