You are on page 1of 2

How to setup OSS connection

Please do the following:


- Go to the http://service.sap.com/saprouter-sncadd
- Click on "Apply Now!"
- Follow the steps detailed in the documentation
- More details can be found on the following page:
http://service.sap.com/saprouter-sncdoc

You can test the connection with the following parameters:


Destination IP address at SAP side: 194.39.131.34
Hostname of this machine : sapserv2
Customer datas
IP address yours SAProuter/Proxy machine: XXX.XXX.XXX.XXX
Hostname yours SAProuter/Proxy machine : saprouter
Your Distinguished Name:
"CN=saprouter, OU=0000400722, OU=SAProuter, O=SAP, C=DE"
1 SAPRouter
Use the latest SAProuter version (36.x), which can be downloaded from
SAP Service Marketplace under the following link.
http://service.sap.com/patches

>
>
>
>
>
>

SAP WEB AS
SAP WEB AS 6.20
SAP KERNEL 6.20 32 BIT
NT I386
Database independent
SAPROUTERxxx.SAR

Note: Please also download the SAPCAR.exe file from the above
location to extract the SAPROUTER achive files:
Eg: SAPCAR -xvf SAPROUTERxxx.CAR
SAProuttab file format for SNC connection:
# SNC-connection from and to SAP
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
# SNC-connection from SAP to local R/3-System for Support
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server>
32<Instance>
# SNC-connection from SAP to local R/3-System for pcAnywhere
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> 5631
# SNC-connection from SAP to local R/3-System for SAPtelnet
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> 23
# SNC-connection from SAP to local R/3-System for Netmeeting
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <R/3-Server> 1503
# Access from your local Network to SAPNet - R/3 Frontend
P <internal address range> 194.39.131.34 3299
# All other connections will be denied
D***
2 Idle timer setting !!!
Note that the Idle timer (inactivity timer) of your WAN interface is set

to a minimum of 5 minutes.
3 Test of the IP connection by the customer
- Ping on sapserv2
- Test the IP connection for large IP packages (>=1500 bytes)
4 Customer configures Online Service System-LOGON
Customer configures the Transaction OSS1 in his/her R/3 System, Note
29784, and then carries out a test Online Service System logon with
Transaction OSS1.
If errors occur refer to Note 24177 (not AS/400)
5 Customer installs SAPGUI/SAPLOGON from R/3 CD.
Configuration of SAPLOGON, Note 89071
- saproute.ini
- sapmsg.ini
- Test Online Service System-Logon via SAPLOGON
6 Set up service connection
Customer sets up Service conncections in SAP R/3 Frontend for ALL
systems and ALL servers, Note 31515
7 Test the service connection together with the network hotline
To avoid problems in the future, test the connection to the SAP R/3
Frontend
Service System, SAPNet and on your R/3 server.
As soon as you implemented your server data in SAP R/3 Frontend,
contact your SAP Local Support by specifying the message number, so
that the test can be carried out.
If you need information material on the following topics, also contact
the above-mentioned phone number and ask for the required notes
Note 30289 : SAProuter documentation
Note 525751: Installation of the SNC SAProuter as NT Service
Note 46902 : Security aspects in remote access
Note 29784 : Logon to SAP R/3 Frontend(Transaction OSS1)
Note 24177 : Online Service System1: Message S1452: Connection to
Message Server.
Note 71973 : No network connection to the Online Service System
Note 89071 : SAPLOGON for Online Service System
Note 86251 : SAP R/3 Frontend: how to define a new installation?
8 End
Customer reports or confirms open SAP R/3 Frontend message after
all tests mentioned above have been performed successfully.