The following XML section shows the configuration of a RequestListeners for the RFC MY_RFC. The first argument (here sap) has to match the defined SAP alias.
<Call name="addRequestListener">
<Arg>sap</Arg>
<Arg>
<New class="com.ebd.hub.datawizard.sap.DataWizardForwardRequestListener">
<Set name="functionName">MY_RFC</Set>
<Set name="xmlFile">conf/MY_RFC.xml</Set>
<!--Set name="messageServiceName">servicename</Set-->
<Set name="messageContext">System</Set>
<Set name="messageQueue">MY_RFC</Set>
<Set name="datawizardProfile">MY_RFC</Set>
<Set name="conversionType">XML</Set>
<Set name="useResponse">false</Set>
<Set name="synchronCall">true</Set>
<Set name="clearTablesForResponse">false</Set>
<Set name="allowParallelProcessing">false</Set>
</New>
</Arg>
</Call>The class com.ebd.hub.datawizard.sap.DataWizardForwardRequestListener will be provided with the SapConnectionService.
functionName | Defines the name of the RFC. |
xmlFile | The path to the interface definition. Note: See alternative configuration method. |
messageContext messageQueue | The message queue is defined in these two parameters. |
datawizardProfile | The processing profile. Has to be active and needs to have an Input Agent of type Message and the corresponding context and queue (see parameters messageContext and messageQueue). |
conversionType | Can have one of the values XML, CSV or FR (fixed-length) and must match the document type of the processing profile. |
messageServiceName | Only necessary if you do not use the default message service. Usually this line can be removed. |
useResponse | If true, parameter synchonCall must also be true, otherwise the setup is aborted with an error. The processing profile then also has to contain a Response of type Custom class with the class PassBackDataResponse. The data returned to the listener corresponds to the XML that is also used to define the RFC and corresponds to the “conversionType” XML. Note: See alternative configuration method. |
synchronCall | Synchronous call if true. See also parameter useResponse. Note: See alternative configuration method. |
clearTablesForResponse | If true, any existing values in the TABLE parameters are deleted. |
copyFromPeer | |
allowParallelProcessing | If true, then this provided RFC can be called up multiple times in parallel. |