Middleware Queues & Monitoring

The job of a middleware Functional Consultant in the role of Support can broadly classified as: Monitor the System Monitoring the Inbound, Outbound and R&R Queues Enhance System Performance by managing the Queues Fix the problems of minor configuration mismatches between the CRM & the leading OLTP system, CRM & Mobile clients Synchronize the Master and Transaction and Master Data Pictorially it can be seen as below the Architecture and the monitoring points

- Monitor Points for a MW Functional Consultant This would logically lead us to Queues. The data exchange between CRM and other system - When the information arrives at the CRM Middleware Server, the data is forwarded to the Inbound / Outbound queue The asynchronous data transfer between CRM and SAP R/3, Mobile Client or external systems is based on the technology of queued remote function calls (qRFC).

Transferring data using a queue guarantees: The correct sequence of transferred data records (serialization) A faulty queue entry is not transferred. The serialization effect means subsequent entries within the same queue name or that are contained in the same logical unit of work (LUW) are also not transferred That the transfer is only carried out once Set which queue type (inbound queue or outbound queue) should be used to transfer the data records qRFC LUW Logical unit of work (LUW) in which multiple queued remote function calls (qRFC) are collected for a data transfer. The sequence of qRFCs within an LUW is determined in the source system and retained during posting to the target system. Changes to data that are made using the qRFCs in an LUW are only posted if all qRFCs in the LUW can be processed successfully.

To get to queues in Middleware SAPGUI : -

SMWMQUEUES - The mapping of the site name, specified in the Administration Console, to the queue name, used by qRFC SMQR / SMQS Queue Scheduling (Receiver / Sender) - schedule & register/deregister function, Status monitor SMWMSCHEDULER - Display the status of the qRFC standard scheduler for all clients (Note Monitoring Only) SMQ1 - Display Outbound Queues SMQ2 - Display Inbound Queues SMOHQUE - Displays information about the status and contents of the replication and realignment queues for the clients defined in your CRM Middleware System

qRFC queues are displayed in three steps: After specifying the client, queue names and queue destinations, the transaction SMQ1or SMQ2 displays a list of all queues that match the specified values.

Now it is possible to select particular queues of interest and view further details.

To get a detailed view on the selected queues, double-click after checking the corresponding queue.

The above scene shows 3x queues in SYSFAIL error and 1x in Ready state. The field details of a Queue is: Field Names Entries Status Options 1. Date 1. Time NxtDate NxtTime Descriptions Number of logical units of work (LUWs) RUNNING / READY Oldest date of queue Time of oldest queue Most recent date of queue Time of most recent date of queue

Other Status option - SYSFAIL (System or program error), CPICERR (Connection error between systems), STOP, WAITSTOP (Waiting), WAITING, NOSEND (Queue is not released, use the SMQ1 transaction for queue release) To get more information you have to double click on a queue line in the queue details screen. Here you can see the function modules or the BDoc names in case of a mobile client outbound queue that are recorded in this queue. If there are more entries, only the first 8 and last 8 entries are displayed.

To get detailed information about the content of a BDoc in the qRFC, double-click on the 'User' field

The Queue scheduler SMQR / SMQS The qRFC status display lists the information about each R/3 client in a separate line. Each line contains the scheduler status and the last data/time, when the scheduler was started.

Nestle Scenerio: Tivoli qRFC alert: Report for monitoring the data transfer between CRM and R/3, Mobile Client or external systems. The Tivoli monitors all outbound and inbound queues. If the report determines a queue block, it can either send a message to the initiator or another person, depending on the settings made. The peregrine Tivoli tickets are raised from this.

Queue Management:
SMQ2: Monitoring CRM Inbound Queues The inbound queues are normally empty or small, if the CRM server has enough resources and no errors occur.The qRFC Inbound Queue Monitor, SMQ2, is not a critical monitor on the R/3 OLTP System because there is normally no data to display. Instead, monitor the outbound queue (SMQ1) on the CRM system. SMQ1: Monitoring of CRM outbound Queues When the CRM Middleware system tries to send data to the OLTP system and the OLTP system is not up, the data stays in the outbound queue of the CRM system. Data is not deposited in the OLTP in-queue and picked up later. If the OLTP is available, the data is in the OLTP system inqueue gets processed through to the respective application or to its appropriate end location. SMOHQUEUE: Monitor R & R Queues Normally one will see 5x queues - AC_EXTRACT,EXTRACTBULK,EXTRACT,REALIGN & SUBCHECK - should be in status released or running and the status of Queue Demon at the top of the screen should be running. If this is the case then automatically all incoming entries get processed. The number displayed besides a queue represents the number of entries currently in the queue. This number should be continuously decreasing, unless new entries are entered into the queue at the same time. To view the entries in the respective queue, double-click the number. To stop or start replication queues manually, double-click the traffic light => the light changes between red and yellow or green If you interrupt queue processing, the processing of the current entry is completed and then the queue is set to status Hold.

Handling Procedure:
The queues, either Inbound or Outbound, should never be stuck up for long ! 1. Go to transaction SMQ1 / SMQ2 2. Look for blocked queues 3. By double clicking on the queue name and looking at the status text of the first entry in the queue, you will find a short error message describing the error reason. 4. If the error is CPIC error, try reprocessing the queue after some time 5. If SYSFAIL, then go to transaction SMW01 to find the cause of error, and fix the proble. 5. After the problem is fixed, reset the status of the selected entry (Shift + F5) or reprocess the queue. 6. In extreme cases, one may have to delete one or two entries of a LUW and process the queue. If the error persists, escalate! 7 If there are large numbers of entries in outbound queue, typically of the order of couple of millions, then look for sites that have large entries and inform the market to run the Contranns Programme to reduce the entries. 8. In transaction SMQR / SMQS, check if the queue is registered, has correct default values. 9. go to transaction SMOHQUEUE. Monitor the Queue Demon and Queue status. Look for errors any, take the corective action & set the above parameters to original correct values 10. It is strongly recommended to avoid deleting the queue or entries in it, because this can lead to data inconsistencies. Consult Peer group or TDL before!!!!!