This note provides a central overview of the required technical preparation steps that must be taken prior to an SAP Remote Service session.
You need to carry out the following technical preparation steps in order to ensure the successful execution of an SAP Remote Service session.
1. Network connection
SAP Remote Services are executed via a remote connection by an expert. Therefore, we need a working network connection to your SAP installation.
Note the following:
a) Make sure that all hosts to be analysed can be reached via X.25, ISDN, or Frame Relay. The IP address of your host must be registered at SAP. For more information on this subject, refer to SAP Note 28976. Correct routing entries must exist for your hosts.
For detailed information on this subject and on network connections, refer to the following SAP notes:
SAP Note 35010 Service connections: Composite note
(overview)
SAP Note 30289 SAProuter documentation
b) If you have restricted the ports for allowed connections for your SAProuter, make sure that port 32xx (xx = instance number) is available and released for our service. For information on the route permission table maintenance, refer to SAP Note 30289 (Section 4.4).
c) Make sure that your network provider has also entered all the required routing entries. If difficulties occur with the network connection, open a customer message under the corresponding component:
XX-SER-NET-HTL Establishing connection to the customer
XX-SER-NET Network and connection problems to the
SAPNet R/3 frontend
If difficulties occur, contact your network provider. For detailed information on how to set up and open the remote connection refer to SAP Note 31515.
2. RFC destination
In order to ensure a successful data transfer between your customer system and SAP, a functioning RFC destination to the SAPNet - R/3 frontend is required.
You can maintain the RFC destination "SAPOSS" via Transaction OSS1 (path: "Transaction OSS1 -> Parameters -> Technical settings") by saving the technical settings and thus updating the SAPOSS connection.
For detailed information on this subject, refer to the guide for Transaction OSS1 in SAP Note 33135.
3. Collectors
In order to obtain useful statistical analysis data on your SAP System, you need to run the Performance Collector and the OS Collector regularly. On servers without an R/3 instance, you need to run the collector program RFC-SAPOSCOL regularly.
Note that the collector programs must run correctly for at least two weeks prior to the session to carry out a complete analysis. Otherwise SAP will not be able to give you any recommendations on how to improve the system runtimes of your SAP installation.
Note the following points:
a) Performance Collector
The Performance Collector regularly collects data on the system workload and on the system performance. To do this, you need to run the collector once an hour.
In order to check whether the collector program runs regularly, call Transaction ST03 and choose "Environment -> Data Collector -> Display Protocol". The latest entry in this list should not be older than a few hours. Make sure that the SAP performance data is accumulated correctly. Call Transaction ST03, choose "Workload -> Reorganization -> Parameters -> Performance database", and press the "Modify parameters" button as well as the "Add min. configuration for TCC Services" button.
If the "Add min. configuration for TCC Services" button should not be available in your system, set the following minimum values for the parameters:
'Standard Statistics: 2 Days, 2 Weeks, 2 Months'
'Time comparison data': 20 Days, 20 Weeks, 14 Months'
As of Basis Release 6.10, use Transaction ST03N which replaces Transaction ST03. In ST03N, switch from the "Administrator" to the "Expert" mode by using the button at the top left. In the tree, you will find the item "Control" under "Collector & Perf. Database -> Workload collector". You can set the standard values via the pushbutton "SAP Standard/current values". Save the settings by choosing "Save values".
In addition, you find the item "Statistics to be generated" under "Collector & Perf. Database" -> "Workload collector". Here you can activate/deactivate individual statistics. If individual statistics had not been deactivated for specific reasons (e.g. performance), set the standard values here via the pushbutton "SAP Standard/current values". Save the settings by choosing "Save values".
For more information on how to schedule the Performance Collector, refer to the following SAP Notes:
SAP Note 12103 Contents of the TCOLL table
SAP Note 16083 Standard jobs, reorganization jobs
From Basis Release 7.00 use transaction STO3N.
Ensure you are in "Expert" mode.
Reorganization
In the tree on the left side of the screen, you will find the item "Control" under "Collector & Performance DB -> Performance Database -> Workload Collector Database" -> Reorganization".
The retention time for daily aggregates must be at least 7 days.
SAP recommends 14 days.
The retention time for weekly aggregates must be at least 5 weeks.
SAP recommends 9 weeks.
The retention time for monthly aggregates must be at least 2 months.
SAP recommends 12 months.
For the Entry "WA" SAP recommends a retention time of 31 days, 20 weeks and 14 months.
Instance Collector
In the tree, you will find the item "Control" under "Collector and Performance Database -> Workoad Collector -> Instance Collector".
Activate all entries in the table.
TOTAL Collector
In the tree, you will find the item "Control" under "Collector and Performance Database -> Workload Load Collector-> TOTAL Collector". For all entries in this table activate at least the weekly aggregates.
You can find more information about the Performance Collectors in the following SAP Notes
SAP Note 966309 Content of table TCOLL in SAP_BASIS 700
SAP Note 966631 Content of table TCOLL in SAP_BASIS 710
In case of problems with the performance collector a message can be opened in component BC-CCM-MON-TUN
a) OS Collector for server with R/3 instance
The periodically running background job of the operating system collector (OS Collector) regularly collects performance data on your operating system. To do this, you need to run the collector daily. Use Transaction ST06 to check whether the OS Collector SAPOSCOL runs without any problems.
If the values displayed there are zero, the collector program either does not run or it runs with errors. In order to (re)start the OS Collector, call Transaction ST06 and choose "OS collector -> Start". Refer to SAP Note 19227 for information on how to install the latest release of the SAPOSCOL for your operating system.
b) OS Collector for servers without R/3 instance
For all servers without an R/3 instance like standalone database servers, standalone LiveCache servers, all servers with an Optimizer or selected frontend servers, you need to install a remote operating system monitor RFC-SAPOSCOL according to SAP Notes 20624 and 19227.
The monitor is a separate program that is independent from the R/3 instances and runs as a background job. It delivers data on the CPU and on the main memory workload and only collects data for the Transactions ST06/OS06. You only need one RFC-SAPOSCOL per host, even if several R/3 instances or even several SAP Systems run on one host. If Transaction ST06/OS06 does not display any data or incorrect data, refer to SAP Note 189072 for detailed information.
If the RFC-SAPOSCOL or the OS Collector do not run, refer to SAP Note 10616 for detailed information.
Important: SAP Note 20624 is not applicable for the Microsoft Cluster Solution (MSCS). Instead, install the NT Monitor on the database system as described in Note 114287.
Important: SAP Note 20624 is not applicable for Database servers with the operating system OS/390 or z/OS.
In this case refer to the SAP Note 103135.
In case of problems with the OS COllector a message can be opened in component BC-CCM-MON-OS.
SAP Note 202934 contains additional information on the installation of Transactions RZ20 and RZ21 which allow a long-term monitoring by the configuration of collector runs. This functionality is required for standalone LiveCache servers as well as for standalone CTM/SNP servers for GoingLive and EarlyWatch services.
4. Hardware and software configuration
We will need technical data on your SAP installation, like hardware, operating system, and database system in order to be able to give you any recommendations on how to improve your system performance. Make sure that all software and hardware data have a current status in the SAPNet - R/3 Frontend (former OSS). We particularly need the current system data on your release and on your servers to be able to carry out the session.
For detailed information on how to maintain your system data, refer to the following SAP notes:
SAP Note 31515 Service connections
SAP Note 172481 System data maintenance (collective note)
5. Profile parameters
In order to activate the recording of the required performance data, you need to set the R/3 instance profile parameters as follows:
stat/level = 1
rsdb/staton = 1
For an Oracle database system, you need to set the following parameterin configuration file "init.ora":
timed_statistics = true
For an Informix database system, you need to set the following parameter in configuration file "/informix//etc/onconfig..":
WSTATS = 1
Valid releases
This note is release-independent.