SAPROUTER configuration for large volume of users - MS DirectAccess implementation connect w/o VPN
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.
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