Configure initialization properties

The first time Business Object Designer communicates with SAPODA, it prompts you to enter a set of initialization properties. You can save these properties in a named profile so that you do not need to re-enter them each time you use SAPODA. For information on specifying an ODA profile, see the IBM WebSphere Business Object Development Guide.

Figure 37. Configuring agent properties

Configure the SAPODA properties described in Table 50.

Table 50. SAPODA properties

Row # Property name Property type Description
1 UserName String SAP logon user name (not required when generating a definition only from an extracted IDoc definition file)
2 Password String SAP logon password (not required when generating a definition only from an extracted IDoc definition file)
3 Client String SAP logon client number (not required when generating a definition only from an extracted IDoc definition file)
4 Language String SAP logon language (not required when generating a definition only from an extracted IDoc definition file)
5 SystemNumber String SAP system number (not required when generating a definition only from an extracted IDoc definition file)
6 ASHostName String Host name of the SAP application server (not required when generating a definition only from an extracted IDoc definition file)
7 RFCTrace Single-card, multi-value RFC tracing for the SAP system
8 DefaultBOPrefix String Text that is prepended to the name of the business object to make it unique.

You can change this later, if required, when Business Object Designer prompts you for business object specific properties.

9 MaximumHits String Maximum number of objects returned during a node search. For more information, see Expand nodes and select objects.

Default is: 100

10 TraceFileName String Name of the trace file. If the file does not exist, SAPODA creates it in the \ODA\SAP directory. If the file already exists, SAPODA appends to it.

SAPODA names the file according to the naming convention. For example, if the agent is named SAPODA, it generates a trace file named SAPODAtrace.txt.

Use this property to specify a different name for this file.

11 TraceLevel Integer Level of tracing enabled for SAPODA

For more information on tracing, see Working with error and trace message files.

12 MessageFile String Name of the error and message file.

SAPODA names the file according to the naming convention. For example, if the agent is named SAPODA, it names the message file SAPODAAgent.txt. For more information, see Working with error and trace message files.

Important: The error and message file must be located in the \ODA\messages directory.

Use this property to verify or specify an existing file.

13 File destination Directory Directory where ODA-generated files are stored.

Default is the default directory on the Windows system. It is recommended that you change the default setting to the \connectors\SAP\utilities\generatedfiles directory.

Important:
Correct the name of the message file if the default value displayed in Business Object Designer represents a non-existent file. If the name is not correct when you move forward from this dialog box, Business Object Designer displays an error message in the window from which the ODA was launched. This message does not popup in Business Object Designer. Failing to specify a valid message file causes the ODA to run without messages. For more information, see Working with error and trace message files.

Copyright IBM Corp. 1997, 2004