TRFC or QRFC?

[Former Member]

Hi,

I am completely confused about some technical terms, on XI.

The question is; XBT* queue belongs to TRFC requests, but it is managed under SMQR. The page "http://help.sap.com/saphelp_nw04/helpdata/en/f7/2c4b3f53275003e10000000a114084/frameset.htm" says that EO is a QRFC model. But some of them are calling EO as TRFC, in the forum. So, if EO is a TRFC request, shouldn't be monitored under SM58, but not under SMQ1? Can anybody explain, EO is a TRFC model or QRFC model?

Thank you

[stefan_grube · Accepted solution]

Don't mix technical aspects and logical aspects.

PI uses SMQ2 queues for any async message, no matter if EO or EOIO.

btw: trfc and qrfc refer to rfc calls. PI uses mainly HTTP calls.

Edited by: Stefan Grube on Aug 27, 2010 2:27 PM

[Former Member · Accepted solution]

viele danke

[henrique_pinto · Accepted solution]

Stefan,

but XI messages & BPM (workflows, to be more specific) are executed in the back as qRFCs, right?

That's even the reason they appear on SMQ1/SMQ2 on the 1st place.

If they were pure RFC (tRFC), you'd see them in SM58.

So, basically, all information that is available for qRFC performance improving also would improve XI performance as a whole.

But that's what there's to it. An XI developer doesn't really to dig into it.

BR,

Henrique.

[Former Member · Accepted solution]

That's exactly what I know actually, but I lost my way while working on high load scenarios

Best regards,

Orkun Gedik

[henrique_pinto · Accepted solution]

So that's basically it. PI doesn't use tRFCs, just qRFCs.

BR,

Henrique.