Message Queues monitoring and administration
Proaxia Connector relies on the standard queuing mechanism based on qRFC. This means that Connector does not provide any specials tools for queues management – standard ones are recommended SMQ1 and SMQ2. By default, Connector uses only outbound queue for handling both outgoing and incoming messages. Connector creates dedicated queues for each company. In the Connector configuration, you will find references to ‘low priority’ queues. As it is not possible to set priorities for queues SAP system therefor Connector implements its own quasi-prioritisation mechanism. There is no ‘express queue’ in standards system.
The purpose of a given queue can be easily recognized by name:
/PACG/ECM_STD_OUT – standard outgoing queue
/PACG/ECM_LOW_OUT – low priority outgoing queue
/PACG/ECM_EXP_OUT – express outgoing queue
/PACG/ECM_RESEND – resend queue
/PACG/ECM_FULLSYNC – fullsync queue
/PACG/EM_CNF_OUT – outgoing confirmations queue
/PACG/ECM_STD_IN – standard incoming queue
Since the queues are created specifically for each FSM company, the queues names are suffixed with companies ID for better identification
Summary of queue customizing and monitoring tools
Transaction | Description | Important settings |
---|---|---|
The Communication section delivers a variety of options impacting how FSM is using system queues. |
| |
SQM1 / SQM2 | Monitor inbound/outbound queues |
|
/PACG/ECM_QSTATUS - Email notification report for Connector Monitoring | Receive email notification when there are queues with the specified status or remaining in this status for longer than expected |
|
Restart queues with a BG job |
|
Monitoring
The transaction to monitor the Queue is SMQ1. The outgoing IDOCs are sent to the Cloud through the Queue. The incoming IDOCs are processed using the Queue as well. By using the queue, we make sure, that the Documents are delivered and processed in the right order. However, the consequence of the queue is, that if the processing of the given document was not successful (e.g. because of the short dump, the connection failure between SAP and the Message Broker) the queue is stopped. As far as the incoming IDOCs are concerned an attempt to process the IDOC is performed and if the certain object could not be created in SAP (e.g. because of incorrect data) the IDOC gets the status 51 (the IDOC becomes red) and the processing is continued. In other words, only the critical errors (like short dumps or network errors) stop the Queue.
Normally the Queue should be empty. If it is not empty but the processing takes place it points no malfunction as well (especially the full synchronization is very time-consuming operation – you can monitor the progress of handling the full synchronization by analyzing the content of the Queue):
Once the queue is blocked, its status will be red:
This status (RETRY) will be set if the connection between SAP and the Message Broker is lost. In that case the Queue is blocked. You could use the button below (after double-clicking the Queue) to push the Queue:
However normally it should not be needed, if you configure the scheduler for RFC Destination = none during the installation. Choose the following menu in SMQ1:
You will be presented with the Status of the Scheduler (consider RFC Destination = None):
If the Queue is blocked with the error RETRY, the queue will be pushed automatically by the Scheduler. Once the connection between SAP and Message Broker is reestablished, the messages will be sent to the Message Broker and finally to the Cloud. It can be also the case, that the Queue is blocked with the message SYSFAIL. This can occur if there is e.g. a short dump. In that case the SAP Scheduler will not push the Queue (it indicates the serious problem which is not a candidate for the resending). In that case the Queue has to be pushed manually (after solving the problem).
The Message Queue should be monitored by the Administrator.
Related content
If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.