There are two ways to
gather performance data from an SAP server:
-
Direct extraction: This requires
installing standard SAP transports on each SAP server.
-
Indirect extraction: This involves
extracting data via a hub SAP server that has standard SAP transports
installed. A destination that is configured on the hub enables the
hub to connect to the server from which data is to be extracted.
Note: Indirect extraction can be
used only with SAP servers that are of the same threaded kernel release.
If there is more than one release represented in the SAP server environment,
you must use direct extraction for individual SAP servers.
The main difference
between the two ways is the effort to install the SAP transports on
each server (direct extraction) versus the effort to configure the
destination on the hub. Also, indirect extraction has additional overhead
for the hub.
The transports in table
2.1 need to be installed in the SAP servers based on the release or
kernel versions. The SAPKI31001INSAS transport is provided for SAP
releases 4.6C or later (up to, but not including, SAP release 6.10).
The SAPKI31002INSAS transport is provided for SAP release 6.10 or
later. The SAPKI31003INSAS transport is provided for SAP Release 700
or later. Each transport installs the RFC function /
SAS/SAPWL_STATREC_READ_FILE,
which is provided by SAS.
Specific Transports Required for the SAS IT Resource Management
Adapter for SAP
|
|
|
|
|
|
|
SAP systems 46C and
prior to 610
|
|
|
|
SAP systems 610 and
higher
|
|
|
|
SAP systems 700 and
higher
|
The transports are located
in the
\itmadaptsap\sasmisc directory.
The directory location is relative to the location where SAS Foundation
is installed (for example,
x:\Program Files\SASHome\SASFoundation\9.3\itmadaptsap\sasmisc).
From the local directory,
a system administrator with the necessary privileges can install the
transport files using the SAP Transport Manager.