XBTO and XBTS Queues

[Former Member]

I have a simple question. Why are the XBTO* and XBTS* queues shown in the SMQ2 (Inbound Queue Monitor) when these are actuallly Outbound and should have been shown under SMQ1 (Outbound Queue Monitor) ?

Thanks,

Badari

[former_member334189]

Dear Badari,

in context of PI it is important to make clear whether you are talking about qRfc queues or PI queues.

Let me start with some words on pipeline processing: The pipeline for asynchronous message processing in the Integration Server mainly consists of 2 parts. When a message is received by the Integration Server the inbound handler does some initial checks, creates an XI message object, serializes the same and schedules the message for asynchronous pipeline processing. During part 1of pipeline processing the receiver determination, interface determination and message split take place. Then the message object is serialized and again it is scheduled for asynchronous processing. During part 2 of pipeline processing the mapping and outbound binding is executed before invoking the adapter for sending the message to the receiver.

Part 1 of pipeline processing is named the "inbound" while the second part is called "outbound". Consequently PI refers to queues of part 1 as to "PI inbound queues" and all queues used by part 2 of pipeline processing are called "PI outbound queues".

And here is comes the crucial point: Both PI inbound queues and PI outbound queues are technically implemented as qRfc inbound queues.

Due to this reason you will find PI queues in SMQ2 only.

Best regards,

Harald Keimer

[stephen_xue]

what about the sender queue and receiver queue in the application system? are both of them dealt as inbound qrfc queue as well? coz i found these two types of queues are both taken as inbound queue. even the sender queue, like XBTS, is taken as inbound queue. why?

[Former Member]

Hi guys,

It is kind of late to answer the question.

T-code SMQ2 is to monitor inbound queues. When using inbound queue, there are two possible scenario.

1, The queue is registered in t-code SMQR, and then the received inbound RFC will be put in this queue and system will process the RFC from this queue.

2, If the queue is not registered, the queue will be created when the system receives a inbound qRFC. And then, in most cases, the application has responsibility to process this queue.

Ideally, if everything is going well, there should be nothing in the queue for both outbound and inbound queues.

For qRFC, the outbound queue really means the queue is used for calling RFCs and inbound queue is used for receiving RFCs.

Cheers

[Former Member]

I don't think the Queue names are confusing like the direction of the interface definitions in the IR. XBTI and XBTO on IS and XBTR and XBTS on IE of sender/receiver application systems represent the Inbound and Outbound correctly.

I wonder why then, both XBTI/XBTO on PI and XBTR/XBTS on application systems are shown under SMQ2 (qRFC Inbound Monitor). Any ideas?

Thanks,

Badari

[Former Member]

Hey

The naming convention for SMQ2 and SMQ1 are the other way round,same as Outbound message interface means sender and not receiver

SMQ2 will track messages leaving PI and going to receiver system so in reality they are tracking messages after message mapping and pipeline steps etc.thus XBTO* is shown under SMQ2

similarly SMQ1 tracks messages coming into PI

so the flow is :

sender adapter engine->smq1->pipeline steps->smq2->receiver adapter engine

You can check the below blog for more information on queue

http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1238996250DB11763581612892844947End...

Thanks

Aamir

Edited by: Aamir Suhail on Sep 23, 2009 1:35 PM

[VijayKonam]

This has always been a confusion. Just as Amir said, they are name just like the interfaces.

VJ

[Former Member]

This message was moderated.