RFC users on message server

[former_member197700]

Users do not logon to the message server.  They may only logon to one of 10 application servers. al08 shows the message server has hundreds of users, mostly of type RFC, that appear with the user id of the users on the application servers.  What are these RFCs? 

[LutzR]

Hi Clifton, be aware that HTTP-Access will be shown as RFC most times!

Regards,

Lutz

[isaias_freitas]

HTTP-Access will be shown as RFC most times

where? I never saw this, at any transaction...

[LutzR]

Hi Isaias, you made me doubt my memory so I just verified this on a 7.30 system with webgui.

User session is shown without transaction in AL08 and counted as RFC.

In SM04 the user is shown as type RFC.

Cheers,

Lutz

[isaias_freitas]

hmmm well... unless your webgui session opened a parallel task (which could be made through an RFC call) I do not see how HTTP sessions would be listed as RFC sessions.

The only other possibility I can think of, at this point, is a display issue at SM04, which would be showing the incorrect type of the session (but I do not recall seeing this issue).

I have just tested this on a 731 system (SAP_BASIS SAPKB73115 with kernel 721 patch level 402) and my webgui session was listed as "Plugin HTTP" at SM04, and AL08 counted it under "Number of Plug-In Users", as expected.

Anyway, I believe we are drifting from the original question .

cheers!

[LutzR]

Hi Isaias, I think it is quite relevant. One part of the original question was "What are these RFCs? ". And the answer might be: HTTP sessions caused by improper http load balancing. In the past I came into several projects where SAP Web Dispatchers were simply forgotten for load distribution in multi-Instance landscapes. This might also be the case here.

Regards,

Lutz

[mercedes_fernandez]

Hello,

Http sessions from the SAP Webdispatcher will appear as "Plugin HTTP" in SM04

Via STAD should be quite straight forward to identify the caller of those RFC's

kind regards,
Mercedes

[isaias_freitas]

Hello Lutz,

The point is, under no circumstances an HTTP connection should be listed as an RFC session at SM04, and I never saw this happen.

Kind regards,

Isaías

[mercedes_fernandez]

Hello Clifton,

in you scenario with the clasical implementation for the enqueue server (not ASCS instance) the Reads operations over the enqueue table from the dialog instances are done via RFC's on the Central instance.

If you are not referring to these ones, you could check via transaction STAD with RFC calls are being executed and look if RFC logon groups have been set in the client side of the RFC.
See SAP Note 593058: New RFC Load balancing procedure

kind regards,
Mercedes

[isaias_freitas]

Complementing Mercedes' reply, if the users are executing a transaction / report that starts parallel tasks, such parallel tasks would be executed through RFC calls.

The logon group that would be used in this case is defined at the transaction RZ12.

If no logon group is used by the application involved, then a built-in group called "parallel_generators" will be used.

This group includes all active instances of the system.

You can override it by creating this group at RZ12.

However, be aware that anything that uses this logon group (e.g., jobs) will be affected by this change.

Regards,

Isaías