Invoking qRFCs

qRFC is an enhancement on tRFC. qRFC enables tRFC invocations to be handled sequentially in the target SAP system. External systems in the TIBCO environment can invoke tRFCs as qRFCs in SAP systems.

Any tRFC can be invoked as a qRFC in the inbound adapter. No design-time configuration is required. All parameters necessary to invoke a tRFC as a qRFC can be provided at run time as part of the RFCCLOSURE class discussed in the previous section.

To perform a qRFC invocation in the SAP system:
  1. Click the activity which you want to specify with this feature.
  2. Expand the _caret_userclosure_caret_ element and set the bQueue property to 1.
  3. Specify the qName property with the name of the qRFC queue, in which the qRFC call is to be inserted.
Note: The boolean property, bTransactional, determines whether or not the call must be invoked as a tRFC in SAP. The boolean variable, bQueue, determines whether or not the call must be invoked as a qRFC in SAP. They must not be set to 1 at the same time, or an error is generated.

For inbound adapter services, when using the qRFC protocol, the count property is not supported. Since the qCount property is assigned by the SAP system when the message is received by adapter, you need to ensure that the messages are sent to the adapter in the required order and that the number of threads per adapter service is not greater than one.

Outbound qRFC calls can be invoked in the adapter from the SAP system. The adapter extracts the queue parameters for each qRFC invocation from the SAP system and appends them in the request's RFCCLOSURE class that is passed on to the TIBCO environment.

To perform a qRFC invocation in the TIBCO environment:
  1. Click the activity which you want to specify with this feature.
  2. Expand the _caret_userclosure_caret_ element and set the bQueue property to 1.
Note:

For outbound qRFC calls, the properties, qName and counter, associated to the

message are not available in the RFCCLOSURE class.