This section discusses the following:
To install the XML ODA, use an IBM WebSphere Installer. For instructions on how to install this ODA with the Installer for IBM WebSphere Business Integration Adapters, see the Implementing Adapters with WebSphere MQ Integrator Broker or Implementing Adapters with WebSphere Application Server. For instructions on how to install this ODA with the InterChange Server Installer, see the System Installation Guide for UNIX or for Windows.
When the installation is complete, the following files are installed in the product directory on your system:
Before you run the XML ODA, verify that your system has the required files for the XML ODA. In particular, make sure that the ODA environment file has been installed in the bin subdirectory of your product directory.
UNIX |
---|
Make sure that the ODA environment file, CWODAEnv.sh, is installed in the following directory: ProductDir/bin. |
Windows |
---|
Make sure that the ODA environment file, CWODAEnv.bat, is installed in the following directory: ProductDir\bin. |
You must also make sure that the variables are correctly set in the startup
script or batch file, which runs the ODA. Open for editing the shell
(start_XMLODA.sh) or batch
(start_XMLODA.bat) file and confirm that the values
described in Table 80 are correct.
Table 80. Shell and batch file configuration variables
Variable | Explanation | Example |
---|---|---|
set AGENTNAME | Name of the ODA | set AGENTNAME=XMLODA |
set AGENT | Name of the ODA's jar file |
UNIX: set AGENT = ${ProductDir}/ODA/XML/XMLODA.jar WINDOWS: set AGENT =
%ProductDir%\ODA\XML\XMLODA.jar
|
set AGENTCLASS | Name of the ODA's Java class | set AGENTCLASS=com.crossworlds.oda.xml.XMLAgent |
After installing the XML ODA and setting configuration variables in the shell or batch file (see Table 80), you must do the following to generate business objects:
The following sections describe these steps in detail.
You can launch the XML ODA with the startup script appropriate for your operating system.
UNIX |
---|
start_XMLODA.sh |
Windows |
---|
start_XMLODA.bat |
You configure and run the XML ODA using Business Object Designer. Business Object Wizard, which Business Object Designer starts, 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 XMLODA.
You can run multiple instances of an XML ODA either on the local host machine or a remote host machine. Each instance runs on a unique port. You can specify this port number as part of launching the ODA from within Business Object Designer. Figure 44 illustrates the window in Business Object Designer from which you select the ODA to run.
By default, error and trace message files (the default is XMLODAAgent.txt) are located in the \ODA\messages, subdirectory 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 those instances use the same message file. Alternatively, you can specify different message files for each ODA instance by specifying file names in odk.dd.xml, which is the ODA deployment descriptor file installed with the XML ODA.
To specify different message files for different ODA instances, you can copy the master ODA deployment descriptor, installed at \ODA\odk.dd.xml, and edit the messagefile, tracefile, and tracelevel values accordingly. The master ODA deployment descriptor has the following format and default values:
<odk> <startup> <messagefile usestandard="true"></messagefile> </startup> <diagnostics> <tracefile usestandard="true"></tracefile> <tracelevel canoverride="true">1</tracelevel> </diagnostics> </odk>
Business Object Designer assumes you name each file according to the naming convention. For example, if the AGENTNAME variable specifies XMLODA1, the tool assumes that the name of the associated message file is XMLODA1Agent.txt. Therefore, when Business Object Designer provides the file name for verification as part of ODA configuration, the file name is based on the ODA name. Verify that the default message file is named correctly, and correct it as necessary.
During the configuration process, you specify:
Table 81 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 the XML ODA spawned * Traces the business object definition dump |
For information on where you configure these values, see Table 82.