Flag

Definition

SAPB1Locking=

This flag controls SAP locking:

N: More than one SAPB1 step can run simultaneously over a whole project's runtime scope.

Y (default): Only one SAPB1 step can run at a time.

If this flag does not exist, SAP will be locked.

When SAP is locked, and two flows are trying to run at the same time in an SAPB1 step, the second flow will wait until the first flow finishes.

SAPB1RemoveEmptyNodes=

This flag is used in conjunction with SAPB1, and is located in the [MAGIC_IBOLT] section of the ifs.ini file.

Set one of the following values to determine whether to remove or to retain empty nodes that may occur when configuring SAPB1 with an XML interface:

N (default): Empty nodes are retained in the XML configuration.

Y: Empty nodes are removed from the XML configuration.

Since version: V3.2 SP2

RfcAllowStartProgram=

This flag is used in conjunction with SAP R/3.

Some Business Application Programming Interfaces (BAPIs) use the RFC callback function to run a program on a client machine.

This flag lets you determine which programs are allowed to run. There are three possible options:

• The default option is that the RfcAllowStartProgram flag is not available. This prevents the local execution of programs on the client machine. You cannot use the RFC callback function without first calling this function.

• You can add the RfcAllowStartProgram flag to the [MAGIC_IBOLT] section of the ifs.ini file and set its value to NULL (not case sensitive). This allows the RFC callback function to call any program on the client machine.

• You can add the RfcAllowStartProgram flag to the [MAGIC_IBOLT] section of the ifs.ini file and set its value as a semicolon-delimited list of programs. Only the listed programs will be called by the RFC callback function.

Since version: V3.2 SP2

DebugTraceLevel=

This flag adds extended trace options to the SAP R/3 connector. It is located in the [MAGIC_IBOLT] section of the Magic.ini file. Each option returns the JCO version and runtime information, and you can select additional trace options as follows:

0: No trace.

1: Important public API calls.

2: Additional public API calls (for example, getClient and releaseClient).

3 (default): Internal middleware calls (JNI/JRfc layer).

4: Additional internal middleware details (for example, enter/leave API information).

5: Record memory allocation information; important caller stack trace information (for example, for removePool, setTraceLevel).

6: RFC metadata (name, type, offset, length, import/export-options); ASCII content data (first 1000 characters of structures and first 5 rows of tables).

7: Additional hex values for content data.

8: Full content data dump (no character or row limit).

9: Java to and from C marshalling field data; code page converter calls.

10: Memory leak analysis information (Record ObjectIDs and detailed freeRecord).

Since version: V3.2 SP3