As an alternative to the method described in section Providing the RFC (first configuration option), there is a second configuration option for the Lobster RFC, where the interface definition in the XML file and the parameter "xmlFile" in the listener configuration are omitted. Instead, the parameter "copyFromPeer" is used.

This second configuration type can also be used for RFC calls with response. Use the following additional parameters . Note: If "useResponse=true", you also have to use "synchronCall=true", because otherwise the caller would not wait for the response .

In this case (RFC sends back a response), the following parameter can be used to ensure that the TABLE parameters are deleted before the response is generated in the profile's Response. Otherwise, the table lines from the request would also be sent back in the response. This is usually not desired.

When the SapConnectionServices is started, the configuration of the interface for the relevant request listener/Lobster RFC is not read and loaded from an XML file, but from the repository of the SAP system. Therefore, there must be an active RFC in the SAP system with the same name as defined in parameter functionName. The interface of the Lobster RFC thus becomes the mirror image of the RFC of the same name in the SAP system. The RFC in the SAP system does not be fully need to be implemented. The interface is sufficient.

So this method allows to specify the interface from the SAP point of view and saves the effort of developing the interface XML file.