This Is Not an Official SAP Document.

Tips for Remotely Connecting to SAP Systems Using SAProuter

SDN Community Contribution

(This is not an official SAP document.)

Disclaimer & Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Applies To:

SAProuter for all SAP solutions.

Summary

Using SAProuter to access SAP systems remotely can be challenging for customers or partners who are new to the SAP environment. This article presents some of the basics of using SAProuter to connect to remote systems.

By: Chung-Ho Fan

Company: SAP Labs, LLC

Date: 5 December 2005

Table of Contents

Applies To:...... 2

Summary...... 2

Table of Contents...... 2

SAProuter Program Instructions...... 3

SAP GUI for Windows...... 5

SAP Java connector...... 6

SAP .Net Connector...... 7

Summary...... 7

Author Bio...... 7

SAProuter Program Instructions

The SAProuter program is an Application Level Gateway that basically functions as Proxy between the workstations on your LAN and the SAProuter at SAP.

In order to run SAProuter, two files are necessary – saprouter.exe and saprouttab. The saprouter.exe file is provided by SAP and the saprouttab can be created locally using a text editor such as notepad.

The saprouttab file contains permissions to either permit or deny a connection. To permit connections from the LAN to SAP’s gateway, a simple saprouttab would only need to contain:

#For connections via sapgate9:

P * 194.117.106.130 3297

#For connections via sapgate8:

P * 204.79.199.244 3299

The saprouter.exe and saprouttab files should both be placed in the same directory (c:\saprouter)

From the command line, you can type ‘saprouter’ to see a list of available commands. To start saprouter, the command would be ‘saprouter –r’, for example:

You can display status with ‘saprouter –l’:

And you can stop saprouter with ‘saprouter –s’:

You can find more specific information regarding SAProuter on in SAP Note 30289. To setup SAProuter to run in the background as a Service, see SAP Note 41054.

SAP GUI for Windows

To access SAP systems via SAP GUI for Windows, you need to set its properties properly. Your input to the field “SAProuter String” should be like this: “/H/Target_SAProuter/H/Source_SAProuter/S/3297/H/”, depending on how many routers or specific ports through which you need to connect.

SAP Java connector

To access SAP systems via SAP Java Connector, you need to program your code similarly as below:

SAP .Net Connector

To access SAP systems via SAP .Net Connector, you need to configure your application server object in the design time similarly as below:

Summary

Based on my working experience with SAP partners, the most frequently encountered problem when dealing with SAProuter is using an invalid "router string". Below is a formula to define the correct router string and to avoid the problem:

Example: sapgate1 and sapgate9: /H/Partner_Internal_IP_address_of_SAProuter/H/sapgateX/S/3297/H/ Example: sapgate8: /H/Partner_Internal_IP_address_of_SAProuter/H/sapgateX/H/ where sapgateX is: sapgate1 = 147.204.2.232 Netextend analog dial-up sapgate8 = 204.79.199.244 For connections in the US (ISDN,

Frame Relay, ...) sapgate9 = 194.117.106.130 for VPN IPSec connections over the Internet

Author Bio

Chung-Ho Fan is an integration consultant at the SAP Integration and Certification Center, in Palo Alto, California.