As an administrator, you need a detailed overview of all the processes involved in using RFC to transfer data.
Consider the example of qRFC with an inbound queue and outbound queue. We recommend that you always use qRFC with inbound and outbound queues. qRFC with inbound and outbound queues involves a 3-phase processing and transfer model. All three phases are completely independent of each other. Separation of these phases ensures that asynchronous processing is as secure as possible.
1. In the first step, the application data is written to the database in the outbound queue. When the first step is completed, the data is saved in the database.
2. In the second step, the QOUT Scheduler transfers this data from the database of the client system, to the inbound queue in the database of the target system.
3. In the third step, the target system QIN Scheduler activates processing of the queue in the target system.
The following figure illustrates the 3-phase communication concept:
As an SAP system administrator, you have a variety of tools at your disposal for efficient monitoring and control of the system and qRFC/tRFC. If you establish that certain applications lead to longer processing times, you can use the different tools to check this. The tools also enable you to restart “crashed” LUWs or delete them from the queue to reactivate a blocked queue. You can adapt qRFC to suit any requirements. The Programming section provides APIs (Application Programming Interfaces) that enable a programmer to adapt qRFC to specific requirements.
You can use the following transactions for monitoring the queues:
· SMQ1 – qRFC Monitor for the outbound queue You can use this to monitor the status of the LUWs in the outbound queue.
· SMQ2 – qRFC Monitor for the inbound queue. You can use this to monitor the status of the LUWs in the inbound queue.
· SMQS – You can use the Outbound Queue Scheduler to register, deregister, and exclude destinations.
· SMQR – You can use the Inbound Queue Scheduler to register and deregister queues.