JCo RFC Live Invocation Step

Complete the following fields:

Destination System Name: Defines a unique name that identifies the SAP system on which the RFC executes. This is often the same as the Repository Name.
Destination System Connection Properties: Specifies the Destination System Connection properties file that contains connection properties with which to connect to the system that has the repository. This must be a .properties file in the Data directory of your project and contains properties that are typically found in a .jcoDestination file. For more information about supported properties, see the JavaDocs for com.sap.conn.jco.ext.DestinationDataProvider in the doc folder of your installation directory.This can be the same file as the Repository Connection Properties.
Format step response as XML: If you select this check box, the step response (the response from the live system) is serialized as XML and can be manipulated as text. This is deserialized at the respond step. Choosing this option slows the virtual service considerably.
If Environment Error: Specifies the action to take or the step to go to if the test fails because of an environment error.

Default: Abort the test.

VSE Lookup Step: For a live invocation step to support failover execution mode, it must know the step that is used to look up VSE responses so that it can redirect the VS model to the correct step when necessary. This field contains a list of steps in the VS model. Select the standard VSE Response Lookup step. That allows the live invocation step to move to the VSE response lookup step when necessary.