This section discusses the following:
To install PortalODA, use the WebSphere Business Integration Adapter (WBIA) Installer. Follow the instructions in the System Installation Guide for UNIX or for Windows. 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 PortalODA, you must copy the required Portal Infranet application's.jar files to the %ProductDir%/connectors/Portal/dependencies directory. The following files must be copied to this directory:
pcm.jar pcmext.jar
The above files are present in the %INFRANET%\jars folder.
After installing the PortalODA, you must do the following to generate or convert business objects:
The following sections describe these steps in detail.
You can start PortalODA using one of the following scripts:
UNIX:
start_PortalODA.sh
Windows:
start_PortalODA.bat
You configure and run PortalODA using Business Object Designer. Business Object Designer 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 PortalODA.
You can run multiple instances of the ODA, either on the local host or a remote host in the network. Each instance has to run on a unique port if multiple instances are being run on the same machine.
Figure 16 illustrates the window in Business Object Designer from which you select the ODA to run.
The error and trace message file (PortalODAAgent.txt) is located in \ODA\messages\, which is under the product directory. This file uses the following naming convention:
AgentNameAgent.txt
If you change an ODA's name in the AGENTNAME variable of a script or batch file, use this convention to change the name of its associated error and trace message file.
If you create multiple instances of the script or batch file and provide a unique name for each represented ODA, create a copy of the error and trace message file for each of these. Name each file according to this convention. For example, if the AGENTNAME variable specifies PortalODA1, name the associated message file: PortalODA1Agent.txt.
During the configuration process, you specify:
Table 7 describes the tracing level 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 PortalODA spawned * Traces the business object definition dump |
For information on where you configure these values, see "Configure initialization properties".