OSS1 Guide

Configuration

The SAProuter connection via transaction OSS1 continues to be used for the following RFC connections:
– Transfer of EarlyWatch Alert data
– Exchange of data using the SAP Notes Assistant

To install and configure this transaction, proceed exactly as follows:

Making the technical settings for OSS1
You must configure transaction OSS1 before you can use it. Choose “Parameter” fromthe menu bar (-> Techn. Settings) and choose “Change”.

After making these changes, the screen for the technical settings should be as follows:

Routerdata for the logon to SAPNet – R/3 Frontend

+-Customer SAPRouters————————————————-+
|+-SAPRouter 1——————+    +-SAPRouter 2—————–+ |
| |  Name         my_saprouter  |    |   Name                      ||
| |   IP Address   x.x.x.x       |    |  IP Address                | |
| |  InstancNo.  99            |    |  Instance No.              ||
| +——————————+    +—————————–+|
+———————————————————————+

+-SAPRouterand OSS Message ServeratSAP—————————–+
| +-SAPRouter at SAP————-+    +-OSS Message Server———-+|
| |   Name          sapservX     |    |    Name          oss001    | |
| |   IPAddress    x.x.x.x      |    |    DBName       O01        | |
| |   InstanceNo.  99          |    |    Instance No.  01        | |
| +——————————+    +—————————–+|
+———————————————————————+

NOTE:
Replace sapservX with the following values:

sapserv1 (194.117.106.129) connection via Internet VPN
sapserv2 (194.39.131.34)  connection via Internet SNC

Choose “Start Logon to SAPNet – R/3 Frontend”. If the system issues message S1 452, there are errors in the operating system configuration. In this case, see appendix A.
When you install an access authorization file “saprouttab”, you should ensure that all of your front ends and R/3 servers can establish a connection to sapserv1 or sapserv2, service sapdp99. Appendix E contains examples of saprouttabs. For more information on the SAPRouter,refer to the SAPRouter documentation (Note 30289).
Try it again until the dialog box “Please select a group” appears. If the dialog box “Please select a group” is displayed, the configuration for transaction OSS1 is correct. You can then proceed with the next section.

Error solving

Appendix A

If message S1 452 appears when you try to log on to SAPNet – R/3
Frontend with transaction OSS1, there is an incorrect setting somewhere (either in the technicalsettings for OSS1 or at operating system level).
To find out why the connection to the message server was unsuccessful, choose Tools (Case, Test ( Developer trace (transaction ST11). The trace contains an entry for dev_lg. This file contains the error log. The LOCATION line, if available, contains the host on which the error occurred. The problem description is found in the ERROR line. If you cannotfind the entry dev_lg, check whether the program “lgtst” exists (see appendixB).

Examplesof the contents of dev_lg:

************************************************************************
*
*  ERROR       partner not reached (hostabc.def.gh.i, service sapdp99)
*
*  TIME        ThuAug1009:17:57 1995
*  RELEASE    21J
*  COMPONENT   NI (network interface)
*  VERSION    15
*  RC          -10
*  MODULE      niuxi.c
*  LINE        773
*  DETAIL      NiPConnect
*  SYSTEMCALLconnect
*  ERRNO      239
*  ERRNO TEXT  Connection refused
*  COUNTER    1
*
************************************************************************
Here,the system could not reach the SAPRouter. For example, no SAProuter could be found under service 99 (port 3299) on the host with the IP address abc.def.gh.i. The SAPRouter process does not work ortheIPaddresswas not configured correctly inOSS1.

************************************************************************
*
*  ERROR      service ‘sapdp99’ unknown
*
*  TIME        ThuAug1009:22:00 1995
*  RELEASE    30A
*  COMPONENT   NI (network interface)
*  VERSION    17
*  RC          -3
*  MODULE      niuxi.c
*  LINE        404
*  DETAIL      NiPServToNo
*  SYSTEMCALL getservbyname
*  COUNTER    1
*
************************************************************************
Thismessage indicates that the service sapdp99 was not entered in /etc/services. Add the entry in /etc/services. Thismustbe availableon all R/3 servers and front ends.

************************************************************************
*
*  LOCATION    SapRouteronabc.def.gh.i
*  ERROR      route permission denied(XXXXXXXXto sapservX, sapdp99)
*
*  TIME        ThuAug1009:37:44 1995
*  RELEASE    30A
*  COMPONENT   NI (network interface)
*  VERSION    17
*  RC          -94
*  MODULE      nixxrout.c
*  LINE        1426
*  COUNTER    1
*
************************************************************************
Thefile saprouttab, which contains the valid connections, is not correct. The SAPRouter on the host abc.def.gh.i does not set up the connection to sapservX. Check the SAPRouter file saprouttab. This should containeveryR/3server and frontend (see also appendixE).

************************************************************************
*
*  LOCATION    SapRouteron abc.def.gh.i
*  ERROR      internal error
*
*  TIME        ThuAug1010:50:18 1995
*  RELEASE    21J
*  COMPONENT   NI (network interface)
*  VERSION    15
*  RC          -93
*  MODULE      niuxi.c
*  LINE        773
*  DETAIL      NiPConnect
*  SYSTEMCALLconnect
*  ERRNO      242
*  ERRNO TEXT  No route to host
*  COUNTER    1
*
************************************************************************
Thiserror message indicates that the host abc.def.gh.i cannot process the IP address of the next host configured in OSS1. If the SAPRouter error message appears and the next host is sapservX, check the address for sapservX. OSS1 is delivered with the default settings sapserv3 and IP address 147.204.2.5. Customers in the U.S.A. are normally connected to sapserv4, IP address 204.79.199.2. If required,changethe technical settings of OSS1accordingly.

************************************************************************
*
*  ERROR      internal error
*
*  TIME        ThuNov2300:11:20 1995
*  RELEASE    21J
*  COMPONENT   NI (network interface)
*  VERSION    15
*  RC          -1
*  COUNTER    1
*
************************************************************************
Thismessage shows that the instance number entered does not agree with at least one of the technical settings for the SAPRouter defined in OSS1. The default for the instance number of the SAPRouter is 99. Under no circumstances should you enter the instance number of your R/3 system for the SAPRouter. You need to specify instance number 99 for sapservX. Otherwise, itisnotpossibleto log on to SAPNet – R/3 Frontend.

************************************************************************
*
*  LOCATION    SapRouteron sapservX
*  ERROR       route permission denied(XXXXXX to oss002, sapmsO01)
*
*  TIME        MonNov2719:25:54 1995
*  RELEASE    30A
*  COMPONENT   NI (network interface)
*  VERSION    15
*  RC          -94
*  MODULE      nixxrout.c
*  LINE        1390
*  COUNTER    1
*
************************************************************************
Anincorrect server was entered as message server 001, in this example,theserveross002.The message server for O01isoss001.Change the technical settings for transaction OSS1 accordingly.

AppendixB (for Windows NT only)

Change to the directory “usrsap<SID>SYSexerun” and search for the program “lgtst.exe”. If you cannot find it, or if the length of this file isnotexactly 640216 bytes, import the program “lgtst.exe” from sapservX via ftp:

>ftp sapservX
Connected to sapservX.
220 sapservX FTP server (Version 1.7.194.2 Wed Sep  8 17:23:04 GMT 1993) ready.
Name: ftp
331Guest login ok, send identaspassword.
Password:<Your_customer_number>
ftp>cd dist/permanent/OSS1/lgtst.exe
250 CWD command successful.
ftp>binary
200 Type settoI.
ftp> get lgtst.exe
150OpeningBINARY mode data connection for lgtst.exe (640216bytes).
226Transfercomplete.
640216bytes received.
ftp> bye

Copy this file into the aforementioneddirectory.

Appendix C

The messages from transaction OSS1 (error messages and information) are given in thefollowinglist. Eachmessageis described briefly.

———————————————————————–
|No.|MessageText
———————————————————————–
|450|Maintaintechnicalsettings first.
|452|Unable to connect to SAPNet- R/3 Frontend message server.
|454|E: Unable to start SAPGUI.
|455|SAPGUI was started.
|456|Specify a server name.
|457| Specify an IP address.
|458|Specify an instance number.
|459| Specify a databasename.
|460| No authorization to log on toSAPNet- R/3 Frontend.
|461| No authorization to maintain technical settings.
|462|E: RFC destination could not be generated
———————————————————————–

Number450: Maintain technical settings first
You can only log on to SAPNet – R/3 Frontend if the technical settings
aremaintained. The technical settings determine the network path fromthecustomer R/3 system to the online service system.

Number 452:Unable to connect to SAPNet – R/3 Frontend message server.
This message appears if the connection to the SAPNet – R/3 Frontend message server was not possible (systemnameO01, server oss001). There can be different reasons for this (seeappendix A).

Number 454: E: Unable to start SAPGUI.
Transaction OSS1 could start the SAPGUI (not SAPTEMU), either because the program does not exist in the path given, or because the execute permissionis not set correctly. Check whether the SAPGUI exists; SAPTEMU aloneis not sufficient.

Number 455: SAPGUI was started.
This is not an error message. It merely informs you that an additional SAPGUI was started to establish a connectiontoSAPNet – R/3 Frontend.

Number456:Specify a server name.
The server name was omittedfromthe technical settings.

Number 457:Specify an IP address.
The IP address was omitted from thetechnicalsettings.

Number 458: Specifyan instance number.
The instance number was omitted from the technicalsettings.

Number 459: Specify a database name.
The database name for the Online Service System (001) was omitted from the technical settings.

Number460: No authorization to log on to Online Service System
You do not have authorization to call transaction OSS1. Up to Release 2.2F: The authorization S_TSKH_ADM is checked for value 1. After Release 2.2F: For transaction OSS1,thereare two special authorization profiles (see appendix D).

Number461: No authorization to maintain technical settings.
You do not have the authorization to maintain the technical settings (see appendix D).

Number462: E: RFC destination could not be generated.
In Releases 2.2*, you can ignore this message. When saving the technical settings, an attempt is made to generate the RFC destination SAPOSS. The lengthofanRFCdestinationislimitedin 2.2*, and the maximum length was exceeded by the parameters ofthe technical settings.

Appendix D

As of Release 2.2F, there are two different authorization profiles for transaction OSS1: S_OSS1_START and S_OSS1_ADMIN.

S_OSS1_START authorizes you to call transaction OSS1 and to log on to the Online Service System. In addition, S_OSS1_ADMIN contains the
authorization to maintain the technical settings for the transaction.

The technical settings of OSS1 must be made at least once. Therefore, add S_OSS1_ADMIN to your user profile, log off, and then log on again afterwards.

Appendix E

Prerequisites:
(A TCP/IP connection can be established between the SAProuter on
the customer system and the SAProuter on sapserv3 in Walldorf.
(The SAProuter process must be started on the server that is registered
with SAP:

saprouter -r -R saprouttab &

Example of the “saprouttab” file with minimum configuration:

# saprouttab – Example
#
# Allows connections from the entire customer network to sapservX
# and therefore to the Online Service System via SAProuter port 3299.
P      *      sapservX    sapdp99         *
# Allows connections from sapserv3 to the entire customer network,
# for example for EarlyWatch or First Level Support.
P   sapservX      *          *            *

OSS1 Guideultima modifica: 2010-02-23T16:12:26+01:00da pedroccda
Reposta per primo quest’articolo

Lascia un commento