The following section describes the installation and usage of SAPODA.
To install SAPODA, use Installer for IBM WebSphere Business Integration Adapters. Follow the instructions in the Implementation Guide for WebSphere InterChange Server, Implementing Adapters with WebSphere Brokers, Implementing Adapter with WebSphere Interchange Server, Adapter for WebSphere MQ Integrator Broker, System Installation Guide for Windows or for Unix. When the installation is complete, the following files are installed in the product directory on your system:
This section contains the following sections:
Before you can run SAPODA, you must:
Make sure that you download the SAPJCo for the operating system that your connector is running on. The SAPJCo is available for download from SAP's website at http://service.sap.com/connectors. You must have a SAPNet account to access the SAPJCo (if you do not already have one, contact your local SAP BASIS administrator).
UNIX |
---|
From the zipped file, extract the executable jar file .jarextension and the runtime libraries (.o for AIX, and .so for Solaris). |
Windows |
---|
From the zip file, extract the executable jar file, (.jar extension) and the runtime libraries (.dll extension). |
If you have already followed instructions for installing the IBM WebSphere Business Integration Adapter for mySAP.com on the same machine on which you install SAPODA, copy these files from the \connectors\SAP directory to the \ODA\SAP directory. If you install SAPODA on a different machine from the connector, after you unzip the SAPJCo files, copy these four files to the \ODA\SAP directory. For Windows, the librfc32.dll requires one or more C runtime dlls. The C runtime dlls depend on the version of the SAP release being used. Through SAP release 45B, the C runtime dll required is msvcrt.dll version 5.00.7022 or newer. Starting with SAP release 46A, the C runtime dlls required are msvcrt.dll version 6.00.8267.0 or newer and msvcp60.dll version 6.00.8168.0 or newer. The dll or dlls should be copied into the C:\WINNT\system32 directory. This dll or these dlls may already be present and if not, can be found on the "Presentation CD" that contains the Windows SAPGUI setup in the folder <cddrive>:\GUI\Windows\Win32\system. See SAP OSS note number 0182805 for more information.
You can use SAPODA to generate business object definitions for the ABAP Extension Module and the ALE Module based upon an IDoc (Intermediate Document):
After installing SAPODA, you must do the following to generate business objects:
The following sections describe these steps in detail.
You can launch SAPODA by running the appropriate file:
UNIX |
---|
start_SAPODA.sh |
Windows |
---|
start_SAPODA.bat |
You configure and run SAPODA using Business Object Designer. Business Object Designer locates an ODA using the Agent's host and the port. The Agent's name is specified in the AGENTNAME variable of each script or batch file. The default ODA name for this connector is SAPODA. For more on ODAs and business object definitions and how to configure, start and use ODAs, see the IBM WebSphere Business Object Development Guide.
Error and trace message files (the default is SAPODAAgent.txt) are located in \ODA\messages\, which is under the product directory. These files are language and country or territory specific and use the following naming convention:
AgentNameAgent_ll_TT.txt
Where _ll is the language, and _TT is the country or territory.
For instance, a Chinese mainland file name would be:
SAPODAAgent_zh_CN.txt.
The same file name for Taiwan would be:
SAPODAAgent_zh_TW.txt.
The Business Object Designer uses this information when selecting a message file. The default search order is to first look for the locale-specific file that matches the locale in which the Business Object Designer is running. If that is not found, the Business Object Designer defaults to the English-US (en_US) version, and finally, the Business Object Designer looks for the file name without any locale or language information.
Although not required, 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 51 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 |
|
For information on where you configure these values, see Configure initialization properties.