Skip to Content
avatar image
Former Member

SAPROUTER configuration for large volume of users - MS DirectAccess implementation connect w/o VPN

Background:

To use MS DirectAccess in an SAP load balanced environment, this REQUIRES saprouter to manage / allow for the load balancing in this vpn-less scenario.

Instead of creating a new / separate connection on EP for both ECC & BI to support MS Direct Access, we’ve decided to change existing definitions, therefore ALL users will now be load balancing thru SAPROUTER.

We’ve been running SAP since 1998 and have NEVER been dependent on SAPROUTER as tier 1.  With this MS DirectAccess solution we will be driving (600+) users thru SAPROUTER.  Have read much of the SAPROUTER documentation on options / parameters etc. but wanted to ask those of you who’ve been thru this and proven configuration.

Question(s):

How many SAPROUTER(s) are you running?

What is your SAPROUTER startup string with options etc.?

Where (what server) did you chose to install SAPROUTER?

If separate server, what is the # cpu / memory / disk for the saprouter server?

Did you notice overall performance impact to your SAP environment due to all I/O routing thru SAPROUTER?

Thank you in advance

Doreen

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Jan 07, 2015 at 11:05 AM

    Hi Doreen,

    I can answer a couple of these questions:

    1. SAPROUTER for hundreds of users

    2. CPU is minimal, so co-exists with other services.  Just think of it as a very fast software router/ Virtual Network Appliance.  And there is very little disk space required, except for the log files.

    3. You can install it on a PC, but I'd recommend putting it on one of your servers.

    Hope this helps,

    Graham

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 19, 2016 at 01:55 PM

    Hi Doreen!

    We are also implementing MS Direct Access, with two SAP routers in order to balance and distribute the load to connect to SAP logon groups, instead direct connections to servers. Also will be used a unique sap gui shortcut for all connected clients.

    So, after you're experience what's the best way to balance the load across sap routers, Is NLB the way to go? RRDNS? or other are available?

    Best Regards

    Nuno Campos

    Add comment
    10|10000 characters needed characters exceeded