qRFC Monitoring: Creating Queue Groups

In Customizing of the qRFC monitoring using the monitoring architecture, you can define subtrees (queue groups) that are to display messages for particular qRFC queues. A queue group can include multiple inbound or outbound queues. In this way, queue groups provide you with an overview, as the messages for different queues are reported in a single subtree by default.

This procedure is part of the process setting up monitoring of qRFC calls. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure.

The system is displaying the Change Queue Groups: Overviewscreen. The system displays the entries for the queue groups that already exist for the selected owner of Customizing settings.

1. If you want to create a new queue group, choose New Entries.
2. If you want to change an existing queue group, choose the desired queue group by double clicking it.
3. In both cases, the system displays the Change Queue Groups: Detailscreen. You can enter the following data here. There is also help for each of the entries available by choosing F1.

   Entry	Meaning
   Owner	Your owner name
   Queue Group Name	Name of the monitoring subtree in the Alert Monitor; choose a descriptive name, such as CRM* Outbound Queues or APO Outbound Queues
   MTE Class	Technical name for the queue group and therefore the name of the MTE class that is assigned to the queue group; use only letters, numbers, and underscores here (such as CRM_Outbound_Queues)
   Queue Type (I,O)	Indicator for outbound queue (O) or inbound queue (I)
   F1 Message ID	Identification of a message from table T100 for the documentation of the queue group
   F1 Message Number
   Analysis Method	Alternative analysis method; by default, the outbound queues are assigned transaction SMQ1 and the inbound queues are assigned transaction SMQ2 as an analysis method
   Auto-React. Method	Auto-reaction method that is performed in the case of an alert in this queue group; for example, the method CCMS_Email_OnAlert that automatically informs you about an alert by e-mail or pager  (see Defining Automatic Alert Notification)
   Exit FM	Name of a function module that is to perform the additional monitoring for this queue group Definition of the interface: See example function module SALK_QRFC_CALLBACK_SAMPLE Ready-to-Use Examples: SALK_CRM_QUEUE_AGE (Age of the oldest entry in days) SALK_CRM_QRFC_QUEUE_ENTRIES  (Number of entries in the queue)
   Exit Parameters	Possible static parameters in addition to the parameters transferred in the interface; dependent on the function module SALK_CRM_QUEUE_AGE: Maximum_Queue_Age displays the age of the queue in days as of which an alert is generated (by default seven days)
   Parameter Value
   Rec. Exits per Clnt	If the content of this field is X, specifies that the exit function module is to run once for each client; as a consequence, the data that the function modules return is output separately for each client Note This indicator only has meaning if the exit function module is programmed appropriately. This is, for example, the case for SALK_CRM_QRFC_QUEUE_ENTRIES.

   The entries Owner, Queue Group Name, MTE Class, and Queue Type (I,O) are required, all others are optional.

4. Save your individual entries.
   Note

   You should only use the named exit function modules if it is absolutely necessary to do so. If you use qRFC extensively, the associated tables become very large, meaning that the modules could create a large workload.

You have created one or more queue groups meaning that messages for different qRFC queues are to be displayed in different subtrees. For an example of the output of the queue groups in the Alert Monitor, see Transactional RFC and Queued RFC Monitor.