QUEUE MONITORING

[Former Member]

Hi,

What is the need for Q MONITORING ......could u pls send me the step by step procedure for Q monitoring

Regards,

Somenath

[aashish_sinha · Accepted solution]

Hi,

Data elements from an application program are stored for transfer in a queue.

A queue is identified uniquely by a name, which is either defined by the application program or assigned automatically by the queue administration (time stamp) if you do not specify a name explicitly.

The attributes of a queue are determined when the queue is first opened via Queue Attributes.

A queue element (block) consists of a fixed header for queue administration and a variable data section.

Application data are stored transparently in the variable data section, so that any data objects can be stored in the queue.

Segmenting is supported for data structures, which exceed the maximum length of the variable data section. This data is stored, in a form that the application can recognize, divided into several logical storage blocks, and passed on complete to the application when it is called again. The application program makes available a sufficiently large reciever buffer.

Monitor queue with Tcode

SMQ1-> qRFC Monitor (Outbound Queue)

SMQ2-> qRFC Monitor (Inbound Queue)

WEOUTQUEUE - > to start the queue processing

SMQS - > to register the destination in QOUT scheduler

SMQR - > to register the queue

regards

Aashish Sinha

PS : reward points if helpful

[former_member193372]

Hi,

Queues explanation both SMQ1 and SMQ2

If entries can be seen in the transaction SMQ1, it means that the message processing

in the outbound queues is either slow or is stopped. Please Refresh your view and see

the number of entries in order to find out which option is valid. If processing is stopped,

so the number of entries and number of queues is increasing, an immediate action is

needed to get the message processing running again.

If entries can be seen in the transaction SMQ2, it means that the message processing

in the inbound queues is either slow or is stopped. Please Refresh your view and see

the number of entries in order to find out which option is valid. If processing is stopped,

so the number of entries and number of queues is increasing, an immediate action is

needed to get the message processing running again.

Thanks & Regards,

Venkat

[Former Member]

hi

you have 2 queues

OUT bound quque.- SMQ1

IN bounde queue - SMQ2

Also you can monitor the message in truntime workbench.

• Pls: Reward points if helpful.

Vishal

[Former Member]

Hello ,

Check this Blog....

Everything you need...

/people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i

With Regards,

BVS

********Please Reward with points ,if found useful

[Former Member]

Hi

Try this

SMQ2 - Inbound queue.

Entires in this if are due to http response or something that could be due to temporary issue and that issue is now over then select the queue and right click it and do "Execute LUW".

SMQ1 - Outbound queue.

SXMB_MONI - Find the message and go to the right side and see in the queue option that it will show that it has blocked the queue.

As part of monitoring you can view these messages also in adapter engine but in error.

Monitoring through various componenets:-

Runtime workbench -

http://help.sap.com/saphelp_nw04/helpdata/en/88/21bc3ff6beeb0ce10000000a114084/content.htm

Trace and logs -

http://help.sap.com/saphelp_nw04/helpdata/en/64/0b59010a65de44be4f26cb57b9580d/content.htm

Data archieving -

http://help.sap.com/saphelp_nw04/helpdata/en/f5/d347ddec72274ca2abb0d7682c800b/content.htm

Software components monitoring -

http://help.sap.com/saphelp_nw04/helpdata/en/9d/f984809f41b74ba010d15e1ed49065/content.htm

Try the TCode smqr if Monitoring says data struck in Queue.

/people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue