This section describes how to install and launch the i2 ODA, run multiple instances of the i2 ODA, and work with error and trace message files.
Before you begin: This chapter assumes you have already installed the i2 connector, as well as the required software for using the connector (see Installing and configuring the connector). Be sure you are using the i2 application version 6.0.1 and the i2 ODA 1.2.x.
To install i2 ODA, refer to the WebSphere Business Integration Server Express Installation Guide for Windows. Follow the instructions in the installation guide. Insert the product CD. Follow the instructions. When the installation is complete, the following files are installed in the directory on your system where you have installed the product:
Notes:
Before you can run i2 ODA, you must:
Table 3. Shell and batch file configuration variables for Windows
Variable | Explanation | Example |
---|---|---|
AGENTNAME | Name of the ODA | set AGENTNAME=i2ODA |
AGENT | Name of the ODA's jar file | set AGENT= %CROSSWORLDS%\ODA\i2\i2ODA.jar |
After installing the i2 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.
Before you begin: Ensure that the i2 ODA and XML schema ODA are installed on your system.
To launch the i2 ODA, run start_i2ODA.bat
You have to add the proper path to the start files for CIS-SDK and j2ee.jar. You need to point to the exact location of connector jar as found in the i2 lib directory.
Example: The following path information needs to be added to the start_i2.bat file:
set I2_CIS_HOME_DIR=C:\i2\CIS\6.0\cis-sdk set J2EE_PATH=C:\J2EE_JAR set CONNECTORJAR=
You configure and run the i2 ODA 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 i2ODA.
Error and trace message files (the default is i2ODAAgent.txt) are located in \ODA\messages\, which is under the product directory. These files use the following naming convention:
AgentNameAgent.txt
Example: If the AGENTNAME variable specifies i2ODA1, the tool assumes that the name of the associated message file is i2ODA1Agent.txt
You can have a message file for each ODA instance or have differently named ODAs use the same message file. The name of the message file is specified in Business Object Designer Express as part of the ODA configuration.
During the configuration process, you specify:
The following table describes the tracing levels.
Trace Level | Description |
---|---|
0 |
|
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 business object properties and the values received |
5 |
|
For information on where to configure these values, see "Configure agent properties".