Routing a Portal user to a designated ABAP instance

[Former Member]

Hi experts,

my concern is about performance testing in a portal landscape which is connected to several ABAP systems and a Producer Portal.

Because functional and performance testing will temporarily overlap, we consider to route our Mercury test users to a designated ABAP/Producer Portal instance in order to separate the load from funtional testing.

My question:

How can I ensure that the mercury test users get linked to the second ABAP instance/Producer Portal instance?

First ideas:

- Does it help to assign the test users to a specific user group which could be evaluated during SSO?

- Use of ABAP Logon groups without changing the System Object in the Portal;

- Taking advantage of the Load Balancer configuration.

Many thanks in advance and best regards,

Martin

[Former Member · Accepted solution]

The nice thing about loadrunner and other such products is also a headache... and that is handling the headers correctly. In the HTTP header you can set the load balance and session cookies to force the session to a particular place via a web dispatcher.

You need also to be aware RFC's from the Portal to the ABAP and these should use a logon group that you can force to the instance you desire.

It is also possible if going via a web dispatcher to hard code the web dispatcher to only have a single system.

In essence there are a few ways