SAS IT Resource Management Adapter 3.21 for SAP

SAS IT Resource Management Adapter 3.21 for SAP
SAS IT Resource
Management Adapter 3.21
for SAP
®
User’s Guide
The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2011. SAS IT
Resource Management Adapter 3.21 for SAP: User’s Guide. Cary, NC: SAS Institute Inc.
®
SAS IT Resource Management Adapter 3.21 for SAP: User’s Guide
®
Copyright © 2011, SAS Institute Inc., Cary, NC, USA
All rights reserved. Produced in the United States of America.
For a hard-copy book: No part of this publication may be reproduced, stored in a retrieval system, or
transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without
the prior written permission of the publisher, SAS Institute Inc.
For a Web download or e-book: Your use of this publication shall be governed by the terms
established by the vendor at the time you acquire this publication.
The scanning, uploading, and distribution of this book via the Internet or any other means without the
permission of the publisher is illegal and punishable by law. Please purchase only authorized electronic
editions and do not participate in or encourage electronic piracy of copyrighted materials. Your support
of others’ rights is appreciated.
U.S. Government Restricted Rights Notice: Use, duplication, or disclosure of this software and related
documentation by the U.S. government is subject to the Agreement with SAS Institute and the
restrictions set forth in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987).
SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513.
1st electronic book, October 2011
®
SAS Publishing provides a complete selection of books and electronic products to help customers use
SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs,
and hard-copy books, visit the SAS Publishing Web site at support.sas.com/publishing or call 1-800727-3228.
®
SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks
of SAS Institute Inc. in the USA and other countries. ® indicates USA registration.
Other brand and product names are registered trademarks or trademarks of their respective companies.
1
C H A P T E R
1
Introduction to the SAS IT Resource
Management Adapter for SAP
Overview............................................................................................................................................................. 1 Data Flow Architecture ..................................................................................................................................... 3 Benefits ............................................................................................................................................................... 3 Configuration and Administration .................................................................................................................. 4 SAP Server Performance Data Extraction ....................................................................................................... 4 Components........................................................................................................................................................ 4 Business Warehouse Server Performance Data Extraction ............................................................................ 5 Tables ................................................................................................................................................................. 6 Accessibility ....................................................................................................................................................... 7 What’s New ........................................................................................................................................................ 8 Overview
SAP stores performance data as statistics files on stand-alone SAP servers. The SAS
IT Resource Management Adapter for SAP provides code to read these statistics files
and transform them into a ready-to-use format. The files are then exported to SAS IT
Resource Management. Figure 1.1 illustrates this process.
Note: References to the SAS IT Resource Management client in this document pertain
to the use of SAS Data Integration Studio with ITRM plug-ins. These plug-ins are not
specifically required for the SAS IT Resource Management Adapter for SAP tasks and
jobs. In other words, you can use either the SAS Data Integration Studio client or the
SAS IT Resource Management client to perform the tasks and work with the jobs that
are referenced in this document.
A typical SAP installation uses more than one SAP server and several SAP instances.
The SAS IT Resource Management Adapter for SAP provides the capability to choose
and customize SAP instances and to monitor their performance.
In addition, a business warehouse server can be part of an SAP installation. Its
performance can be analyzed using the underlying SAP server performance data.
2
Data Flow Architecture
Chapter 1
Figure 1.1 Solution Architecture
The SAS IT Resource Management Adapter for SAP provides ready-to-use ETL jobs in
SAS IT Resource Management. The ETL jobs read performance data from source SAP
systems and transform the data into standard raw data tables that are given as input to
the SAS IT Resource Management solution. These jobs are built on the SAS Data
Surveyor and can communicate with any SAP R/3 system.
The SAS IT Resource Management Adapter for SAS uses the SAS Data Surveyor for
SAP to extract SAP performance data. The process involves transparent table extracts,
Business Application Programming Interface (BAPI) calls, and calls to remote-enabled
Advanced Business Application Programming (ABAP) functions that SAS provides.
Based on whether your business needs to extract performance data from a single
server or multiple servers, you can customize the ETL jobs. The architecture of SAS IT
Resource Management components provides the environment for the ETL jobs.
Therefore, you can use SAS IT Resource Management to view and edit your ETL jobs as
needed.
Introduction to the SAS IT Resource Management Adapter for SAP
3
Data Flow Architecture
The SAS IT Resource Management Adapter for SAP begins a data flow that moves
data from source SAP systems to the Rawdata library. The performance data is stored in
the Rawdata library as SAS data sets. The SAS IT Resource Management solution uses
these raw data sets as input and provides solutions for your business needs.
Source data from various SAP systems flows through a series of extraction,
transformation, and loading processes to be converted into a usable format for SAS IT
Resource Management. Figure 1.2 details the basic concept behind this data flow. The
SAS IT Resource Management Adapter for SAP plays its role in the first step of the
model.
To extract data, define extraction jobs that create SAS data sets in the Rawdata
library. The Rawdata library is the input library for the SAS IT Resource Management
staging jobs, as displayed in the following figure.
Figure 1.2 Data Flow from SAP Servers to SAS IT Resource Management
Multiple steps are required before you can run the SAS IT Resource Management
Adapter for SAP to extract performance data from SAP. Separate transformations are
used to extract standard SAP statistics and business warehouse server performance
tables.
Benefits
The SAS IT Resource Management Adapter for SAP enables the SAS IT Resource
Management solution to turn SAP data into business intelligence. By automating and
streamlining certain parts of the data conversion from SAP to SAS, the adapter
decreases the time taken to convert source data into business intelligence. Primarily, it
reduces the time taken to perform SAP ETL by 80% or more. Therefore, you have more
time to concentrate on generating business solutions from SAP data.
4
Components
Chapter 1
The SAS IT Resource Management Adapter for SAP also includes SAP knowledge
that streamlines the data conversion process. So, you do not need to depend on SAP
resources to help you understand how SAP works. The SAS IT Resource Management
Adapter for SAP also saves you time and valuable SAP resources so that they can be
used for other projects.
Configuration and Administration
The SAS IT Resource Management Adapter for SAP is installed using the SAS
Deployment Wizard and a set of manual configuration steps described in Chapter 4 of
this document.
After you configure the SAS IT Resource Management Adapter for SAP, you can use
SAS IT Resource Management to manage and customize the adapter.
SAP Server Performance Data Extraction
To understand the workflow, suppose there is an SAP server called Server1. A system
administrator defines Server1 and its library metadata in SAS Management Console.
You need to give the server details in the preprocglobal.sas program in the initialization
job 0010 Step 1 Select Single SAP Server in SAS IT Resource Management that
monitors the server. Thereafter, the system administrator deploys the jobs to extract
performance data for Server1 on a regular hourly basis.
Next, SAS code calls an SAP ABAP function directly or calls an ABAP function
provided by SAS to extract performance data from Server1. The SAS code assembles the
performance data into logical SAS tables in the Rawdata library.
The table populates SAS IT Resource Management IT data marts. Reports containing
the extracted performance data from Server1 are generated for SAS IT Resource
Management.
Components
The SAS IT Resource Management Adapter for SAP consists of the following
components:
SAP servers
collect performance data the standard way. Additional Advanced Business
Application Programming (ABAP) functions are installed on the SAP servers to
support the SAS Data Surveyor for SAP and to allow indirect calls of standard
SAP ABAP functions.
SAS Management Console client
defines the SAP servers that are accessed by the SAS IT Resource Management
Adapter for SAP.
SAS IT Resource Management client
provides technology that the SAS IT Resource Management Adapter for SAP uses
to generate and submit code to the SAS Application Server.
Introduction to the SAS IT Resource Management Adapter for SAP
5
SAS Metadata Server
SAS IT Resource Management and SAS Management Console do not store data
locally. They communicate with the SAS Metadata Server, which stores and
retrieves metadata from the jobs and tables in SAS IT Resource Management and
SAS Data Integration Studio.
SAS ITRM Application Server
executes the code generated by SAS IT Resource Management. The following
software must be installed on the SAS Application Server:
 Base SAS software
 SAS IT Resource Management server-side software
 SAS Solutions Adapter software (includes the server component of the SAS
Data Surveyor for SAP: SAS/ACCESS Interface to R/3 software)
 Web server to deploy reports for common access
SAS IT Resource Management transformation (new)
In this release of SAS IT Resource Management Adapter, a new transformation
named Libref Collector transformation is defined in the initialization job 0010
Step 1 Select Single SAP Server.
SAS code files
installed on the SAS Application Server. These open source files are automatically
copied to a location where they can be modified if necessary.
SAS macros
include simple macros that are provided as open source code as well as complex
macros that are provided without source code so that SAS can maintain them
easily.
SAS libraries
provide storage for administration and data tables.
Business Warehouse Server Performance Data Extraction
The business warehouse server runs on a standard SAP threaded kernel. Therefore,
business warehouse server performance can be monitored using the same methodology
for standard R/3 instances.
However, each ABAP function must be installed on each business warehouse server
in order to collect business warehouse server performance data. This means that
performance data for business warehouse servers cannot be extracted through a hub.
However, a business warehouse server can function as a hub for R/3 system statistics
data.
Additional business warehouse server performance data can be collected by extracting
data at the InfoCube level. This is explained in more detail in the “Extract Business
Warehouse InfoCube Performance Data” section.
.
6
Tables
Chapter 1
Tables
The following table lists the tables that contain performance data extracted from the
SAP systems.
Long SAP Table Name
SAS Data
Table
Performance
Database
(PDB) Tables
Description and Notes
V2_NORMAL_RECORDS
NRM
Normal transaction
history.
V2_BTC_STEP_RECORDS
BTC
SAPR3S
SAPHST
SAPSMT
SAPSYS
SAPTRN
SAPTSK
SAPBTCH
V2_NORMAL_RECORDS,
V2_BTC_STEP_RECORDS
NRM
BTC
SAPWKLD
V2_TABLE_RECORDS
TAB
SAPTAB
V2_RFC_CLIENT_RECORDS
RC0
SAPRC0
V2_RFC_SERVER_RECORDS
RS0
SAPRS0
V2_RFC_CLIENT_DEST_RECORDS
RCD
SAPRCD
V2_RFC_SERVER_DEST_RECORDS
RSD
SAPRSD
V2_SPOOL_PRINT_RECORDS
SPP
SAPSPP
Batch transaction
history.
SAPWKLD is built on a
combination of NRM
and
BTC.
Table access history.
Not collected in SAP
by default because
collecting table access
statistics places a
heavy load on the SAP
system.
RFC client access
history.
RFC server access
history.
RFC client destination
access history.
RFC server destination
access history.
Printing history.
V2_SPOOL_ACTIVITY_RECORDS
SPA
SAPSPA
Spool activity history.
V2_RFC_TIME_INT_RECORDS
TII
SAPTII
DB_PROCEDURE_RECORDS
DBP
Time interval history
(typically not collected
by default).
Database procedure
history.
Introduction to the SAS IT Resource Management Adapter for SAP
7
Long SAP Table Name
SAS Data
Table
Performance
Database
(PDB) Tables
Description and Notes
NORM_SUBRECORD_INDEX
CIX
Not
applicable
RSDDSTAT
RSDDS
SAPRSS
RSDDSTATWHM
WHM
SAPWHM
ADM_MESSAGE_RECORDS
ADM
CLIENT_INFO_RECORDS
CIF
HTTP_RECORDS
HTP
HTTP_CLIENT_DEST_RECORDS
HTPCD
Contains indexes to
associate records in
sub-tables with
normal transactions.
For example, a normal
transaction accessing
tables would have one
record in NRM and
one record in TAB for
each table access.
This index table is
used to establish this
link.
SAP business
warehouse InfoCube
query performance
statistics.
SAP business
warehouse server
maintenance statistics.
ADM message
additional
information.
Client (also known as
passport) additional
information.
HTTP additional
information.
HTTP client
destination additional
information.
Accessibility
The SAS IT Resource Management Adapter for SAP does not have a stand-alone
graphical user interface (GUI). It is configured and managed using features of SAS IT
Resource Management and SAS Management Console.
SAS IT Resource Management and SAS Management Console include accessibility
and compatibility features that improve their usability for users with disabilities. These
features are related to accessibility standards for electronic information technology that
were adopted by the U.S. Government under Section 508 of the U.S. Rehabilitation Act
of 1973, as amended.
8
What’s New
Chapter 1
For more information about specific accessibility features of SAS IT Resource
Management and SAS Management Console, see their respective documentation
available at http://support.sas.com.
SAS is committed to improving the accessibility and usability of our products. If you
have questions or concerns about the accessibility of SAS products, send an e-mail to
accessibility@sas.com.
What’s New
The SAS IT Resource Management Adapter for SAP supports the SAS IT Resource
Management Adapter 3.21 for SAP and the following platforms:

WIN (Windows 32 bit on x86)

WX6 (Windows 64 bit on x86)

S64 (Solaris on SPARC)

R64 (AIX on PowerPC)

H61 (HP/UX on Itanium)

z/OS
You can find the list of host platforms supported by the SAS IT Resource Management
solution in the System Requirements document available at http://support.sas.com/itrm.
The current version of SAS IT Resource Management Adapter for SAP supports the
following SAP versions:
 SAP - ECC 4.7 ( SAP Kernel 610, 620)
 SAP - ECC 5.0
 SAP - ECC 6.0 (ERP 6.0) (SAP Kernel 700, 701)
 SAP - BW 3.1
 SAP - BI 7.0
9
C H A P T E R
2
SAP Customization Tasks
Introduction ....................................................................................................................................................... 9 Install SAP Transports ..................................................................................................................................... 9 Set Up Hub Servers to Extract Performance Data for Indirect Extraction .................................................. 11 Connect to SAP Destination Servers for Indirect Extraction ........................................................................ 11 Extract Business Warehouse Server Performance Data ................................................................................ 12 Set Up SAP Authorization .............................................................................................................................. 16 Test ABAP Functionality ................................................................................................................................ 16 Introduction
The SAS IT Resource Management Adapter for SAP requires customization to work
in your unique installation environment. The system administrator must perform the
following tasks:
1
Install SAP transports.
2
Set up hub servers to extract performance data for indirect extraction.
3
Connect to SAP destination servers for indirect extraction.
4
Extract business warehouse server performance data.
5
Set up SAP authorization.
6
Test ABAP functionality.
Furthermore, the SAS IT Resource Management Adapter for SAP uses the SAS Data
Surveyor for SAP. The server component of the SAS Data Surveyor for SAP is the
SAS/ACCESS Interface to R/3 software. SAS/ACCESS Interface to R/3 software requires
additional setup. For more information, see the installation instructions for
SAS/ACCESS Interface to R/3.
The following sections provide approximate instructions on how to complete these
tasks. For specific information about how to complete these tasks in your environment,
see your SAP documentation.
Install SAP Transports
There are two ways to gather performance data from an SAP server:

Direct extraction: This requires installing standard SAP transports on each SAP
server.
10 Install SAP Transports

Chapter 2
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.
Table: 2.1 Specific Transports Required for the SAS IT Resource Management Adapter for SAP
Transport
Objects
To Be Applied to
SAPKI31001INSAS
Package /SAS/ADITM
SAPKI31002INSAS
Package /SAS/ADITM
SAPKI31003INSAS
Package /SAS/ADITM
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.
SAP Customization Tasks
11
Set Up Hub Servers to Extract Performance Data for Indirect Extraction
Some SAP servers need to function as adapter gateway servers (or hubs). SAS calls
this ABAP function to extract performance data for the hub and for other SAP servers.
Multiple extractions can be channeled through a single hub, which means that only one
or two servers might need to function as hubs.
Note: Each unique SAP release requires a hub, because underlying data structures
can change between releases. Remote function calls between SAP instances that have
different underlying data structures can result in corrupt data.
Connect to SAP Destination Servers for Indirect Extraction
Servers connect to a hub using an SAP destination. On the hub, an ABAP function
extracts data from other servers using an SAP destination defined on the hub itself.
An SAP destination must be defined for each server on each hub, so that the server’s
performance data can be extracted by the hub. To define an SAP destination, complete
the following steps:
1
Issue transaction SM59 from SAP, and then provide the following:
 For the RFC destination, specify system-id_hostname (for example,
SI9_ENDAPP09).
 For connection type, enter 3.
 For description, enter Connection to SI9 on appserver.pc.domain.com.
2
In the Technical Settings section, verify the following settings and
information:
 Do not allow load distribution.
 A host name or IP address of the SAP server is specified.
3
In the Logon and Security sections, provide a user ID and password for nontrusted systems to run code on the target SAP system.
4
In the Special Options section, complete the following steps:
 Set the Unicode flag based on the setting of the target SAP server.
 Review all other settings and make sure that they meet the local site’s
standards.
For more information about destinations, see Appendix 2.
12 Extract Business Warehouse InfoCube Performance Data
Chapter 2
Extract Business Warehouse InfoCube Performance Data
Additional business warehouse server performance data can be collected by
extracting data at the InfoCube level. For example, an InfoCube query has a single
record that identifies the resources that were used by the query. The information in this
record can be collected in an underlying table that stores performance data for the entire
SAP system. This InfoCube performance data can help identify problem queries.
The SAS IT Resource Management Adapter for SAP provides the tools to extract the
business warehouse InfoCube performance table’s data by using SAS Data Surveyor for
SAP technology. That means business warehouse InfoCube performance data is
extracted by using standard ABAP functions. No additional ABAP functions are
required. The extraction involves exploiting the SAP threaded kernel. There is no need
for business warehouse server-specific technology.
Business warehouse servers must be activated in order to collect performance data.
To activate a business warehouse server, complete the following steps:
1
Issue transaction RSA1 to access the business warehouse server workbench.
2
From the workbench, select Tools  BW Statistics for Info Cubes.
The BW Statistics: Entry Mode window appears with a listing of all active info
cubes.
Figure 2.1 BW Statistics: Entry Mode Window
SAP Customization Tasks
13
3
Click the Select all icon to select all information cubes (Info Cube). Or, select the
OLAP and WHM check boxes to select individual information cubes.
4
Click Save.
5
In BI 7.0 from the workbench, select Tools  BW Setting for BI
Statistics.
14 Extract Business Warehouse InfoCube Performance Data
Chapter 2
The following window appears.
Figure 2.2 Maintenance of Statistic Properties Window
6
Click the Select all icon to select all information providers (InfoProvider). As an
alternative, you can select individual information providers.
SAP Customization Tasks
15
Figure 2.3 Maintenance of Statistic Properties Window
7
Select the Change Default option at the bottom of the preceding screen.
8
Click the Close button
.
The pop-up window closes.
9
Click the Save button
, and then click
to continue.
Note: When this transaction takes place in new versions like B17.0, you determine
the objects for which you want to write run-time statistics in the BI system. You can
choose queries, information providers, Web templates, workbooks, and data transfer
processes (DTPs) from the WarehouseManagement area. For information providers,
Web templates, workbooks, and DTPs, you can choose only On or Off. For queries, you
can also choose the level of detail for the statistics.
A newly created object always has the default setting D. If the default value D is not
altered, the system writes the statistics according to the setting that you made for the
default value of the run-time object. You can change the default value in the menu
under Extras  Change Default Value. The default always refers to the objects on
the current tabbed page.
16 Test ABAP Functionality
Chapter 2
Set Up SAP Authorization
The system administrator must create user IDs before performance data can be
extracted. To create all necessary user IDs, complete the following steps:
1
Create a user ID for extracting performance data.
2
Create a user ID for the SAS administrator, if one does not already exist. This
user ID must have permission to issue transactions SE37, SE38, SM37, and SM59.
User IDs must be given the necessary permissions. For more information, see the
installation instructions for SAS/ACCESS Interface to R/3 software.
The SAS administrator can configure the SAS IT Resource Management Adapter for
SAP to allow only authorized SAP users to log on.
In addition, some sites might need to restrict permission so that only performance
data can be extracted. To restrict permission, see Appendix 3.
Test ABAP Functionality
To ensure that ABAP functions are correctly installed, run a test job using the ABAP
workbench function.
When all ABAP functions are installed and the SAS environment is customized, you
can execute the test job. The job should not take more than a few minutes to execute,
because the ABAP Workbench function extracts only a few test records.
SAP Customization Tasks
17
17
C H A P T E R
3
Preparing to Import the SAS IT
Resource Management Adapter for SAP
Introduction ..................................................................................................................................................... 17 Installation Prerequisites ................................................................................................................................ 17 System Requirements ...................................................................................................................................... 18 Installation Sequence ...................................................................................................................................... 18 Defining the Environment............................................................................................................................... 18 Overview ................................................................................................................................................... 18 Define Users ............................................................................................................................................. 18 Define an SAP Server and an SAP Library ........................................................................................... 25 SAS RFC Server (Only for SAS/ACCESS Interface to R/3 for z/OS) ................................................ 32 Test the SAP Connection ......................................................................................................................... 34 Create Directories for Administrative and Raw Data ........................................................................... 37 Introduction
As part of the installation and configuration of the SAS IT Resource Management Adapter
for SAP, the system administrator must complete the following steps:
1 Verify that the environment meets the system requirements. 2 Follow the correct installation sequence.
3 Prepare the environment.
4 Import sample metadata.
All of these steps are necessary before you can use the SAS IT Resource Management
Adapter for SAP.
Installation Prerequisites
As part of the installation of SAS IT Resource Management Adapter for SAP, it is
mandatory to install the following dependent SAS software.

SAS 9.3

SAS Data Surveyor for SAP 4.4 (includes SAS/ACCESS to R/3)
Refer to the installation instructions for the specific SAS product for more information.
18 Defining the Environment
Chapter 3
System Requirements
The SAS IT Resource Management Adapter for SAP requires that the following be
installed:

SAP, Release 4.7 or later

SAS Foundation

SAS IT Resource Management

SAS/ACCESS Interface to R/3 software

SAS Data Integration Studio

SAS Data Surveyor for SAP
Complete these installations before you start using the SAS IT Resource Management
Adapter for SAP.
Installation Sequence
Here is the recommended sequence for installing the components and software:
1
Install SAS Foundation, SAS IT Resource Management, and SAS/ACCESS Interface to
R/3 software on the SAP server.
2
Install SAS Data Integration Studio on the client server.
3
Install SAS Data Surveyor for SAP on the client server.
4
Install SAS IT Resource Management Adapter for SAP.
5
Import the SAS IT Resource Management Adapter for SAP sample metadata.
Defining the Environment
Overview
Before the SAS IT Resource Management Adapter for SAP is installed, complete the
following steps to prepare the environment:

Define users in SAS Management Console.

Define an SAP library and an SAP server in SAS Management Console.

Test the SAP connection to SAS Data Integration Studio.

Create a directory for administrative data.
Define Users
To define a user for the SAS IT Resource Management Adapter for SAP, complete the
following steps:
Preparing to Import the SAS IT Resource Management Adapter for SAP
19
1
Open SAS Management Console. 2
Select Foundation in the Repository field to connect to the SAS Metadata Server
at the Foundation level. You must have administrator access to complete this task.
Figure 3.1 SAS Management Console
20 Defining the Environment
3
Chapter 3
Right-click User Manager in the navigation tree, and then select New  Group.
Figure 3.2 SAS Management Console: User Manager
Preparing to Import the SAS IT Resource Management Adapter for SAP
4
In the New Group Properties dialog box, enter SAPUsers in the Name field.
Figure 3.3 New Group Properties
21
22 Defining the Environment
Chapter 3
5
Select the Members tab. Select SAS Demo User in the Available Members box.
6
Click the single arrow button
Members box.
to move the selected member to the Current
Figure 3.4 SAP USERS Properties: Members Tab
Preparing to Import the SAS IT Resource Management Adapter for SAP
23
7
Select the Groups and Roles tab. Select Metadata Server: Operation in the
Available Groups and Roles box.
8
Click the single arrow button
box.
to move the selected member to the Member of
Figure 3.5 SAP USERS Properties: Groups and Roles Tab
24 Defining the Environment
9
Chapter 3
Select the Accounts tab. Click New.
Figure 3.6 SAP Users Properties: Accounts Tab
10 In the Edit Login Properties dialog box, complete the following steps:
a
Enter the user ID and password for the SAP server.
b
Select SAPAuth from the Authentication Domain menu.
If this option is not already available on the menu, click New, enter SAPAuth as
the name of the new authentication domain, and enter a short description. Click
OK to save the new authentication domain.
c
Click OK to save the new login properties.
d
Click OK to save the new group properties.
Figure 3.7 Edit Login Properties
Preparing to Import the SAS IT Resource Management Adapter for SAP
25
Define an SAP Server and an SAP Library
When you have only one SAP Server defined, defining an SAP library for the server is not
required. Library is automatically assigned to the server, once you import the package files
into the SAS IT Resource Management. However, it is mandatory to define SAP libraries,
when there are multiple servers and you need to extract data from specific servers. For
example, when you need to extract data from a specific server, you are required to enter the
SAP library of that server in the preprocglobal.sas program.
To define an SAP server for the SAS IT Resource Management Adapter for SAP, complete
the following steps:
1
Open SAS Management Console.
2
In the Repository field, select Foundation, or select a repository that is solely
dependent on the Foundation repository.
This connects to the metadata server at the foundation level.
3 Right-click Server Manager and select New Server.
The New Server Wizard appears.
4 Select SAP Server from the Enterprise Applications Servers folder.
5 Click Next to name the new SAP library.
Figure 3.8 New Server Wizard
26 Defining the Environment
Chapter 3
6
Enter a name and description for the server. Click Next.
7
Enter the version numbers for your SAP software.
These values are optional.
8
Click Next.
Figure 3.9 Enterprise Applications Servers – SAP Server
9
Select SAPAuth from the Authentication Domain menu. Select the connection type
that corresponds to a normal SAP GUI connection for your system.
Preparing to Import the SAS IT Resource Management Adapter for SAP
27
Figure 3.10 New Server Wizard: Connection Properties
10 Click Options for your selection. The Application Server Options dialog box appears.
11 Specify the RFC server host and system number. Click OK.
Figure 3.11 Application Server Options
12 Click Advanced Options in the New Server Wizard dialog box.
If you have defined batch servers or processes, specify some of the advanced options
that are available.
13 Select Batch Mode and click OK.
Figure 3.12 Advanced Options
28 Defining the Environment
Chapter 3
14 For a z/OS environment, specify the RFC Server host name (where your RFC server is
available) and RFC server port in the field Other option(s) to be appended.
Figure 3.13 Advanced Options
15 Click Next, in the New Server Wizard.
16 Review the information and click Finish.
This takes you to the main screen of the SAS Management Console, where you can
view in the Servers list, the server that you have just defined.
Figure 3.14 New Server Wizard: Summary of Specifications
To define an SAPlibrary for the SAS IT Resource Management Adapter for SAP,
complete the following steps:
17 Expand Data Library Manager in the navigation tree.
Preparing to Import the SAS IT Resource Management Adapter for SAP
29
18 Right-click Libraries and select New Library.
The New Library Wizard appears.
19 Select SAP Library from the Enterprise Applications Libraries folder. Click
Next.
Figure 3.15 New Library Wizard
20 Enter a name and description for the library. Click Next.
Figure 3.16 New Library Wizard
30 Defining the Environment
Chapter 3
21 Select the required SAS SASITRM server.
Figure 3.17 New Library Wizard: Server Selection
The value SAPEng appears in the Libref field. This is the default value that the
imported metadata uses. You can give any other name and description that uniquely
identifies the SAP server that you have created.
22 Click Next.
Figure 3.18 New Libref Wizard: Libref Name
Preparing to Import the SAS IT Resource Management Adapter for SAP
31
23 In the Database Server field, select a database server that contains parameters
connecting to the SAP server.
24 If an appropriate database server is not already available in the menu, complete steps
1–16 to create one. Click Next.
Figure 3.19 New Library Wizard: Database Server
32 Defining the Environment
Chapter 3
25 Click Finish.
Figure 3.20 Library Properties
SAS RFC Server (Only for SAS/ACCESS Interface to R/3 for z/OS)
A SAS RFC server was needed in the previous releases of SAS IT Resource Management
Adapter for SAP, to enable communication between the SAS/ACCESS Interface to R/3 and
the SAP system. In this release of SAS IT Resource Management Adapter for SAP,
SAS/ACCESS Interface to R/3 communicates directly with the SAP system, so that a SAS
RFC server is not required. However, a SAS RFC server is needed for the LIBNAME engine
on z/OS. SAS/ACCESS Interface to R/3 for z/OS includes RFC servers for z/OS, AIX, and
Windows. The SAS RFC server is no longer supported for the SAS/ACCESS Interface to R/3
for Windows and UNIX. There is no Unicode RFC server on z/OS. You need to use the
Unicode RFC server on one of the other supported platforms. Currently, the Unicode server
for Windows and AIX is delivered with SAS/ACCESS to R/3 on z/OS.
You need to use the Unicode RFC server on AIX or Windows to connect the Unicode SAP
system from z/OS environment. For this, you need to set up AIX RFC Unicode server on AIX
box, and then provide the host name and port of the AIX RFC server when you create the
SAP server on z/OS.
For more information about running the RFC server on z/OS, see the chapter entitled
“Installing SAS/ACCESS Interface to R/3 Software on z/OS” in the Post-Installation
Instructions for SAS/ACCESS® 4.4 Interface to R/3 available at
http://support.sas.com/.
Preparing to Import the SAS IT Resource Management Adapter for SAP
33
34 Defining the Environment
Chapter 3
Test the SAP Connection
1
Open SAS Management Console. 2
Open the Connection Profile for the user. Figure 3.21 SAS Management Console Designer Box
3
Select Tools  Extract From R3.
The SAP R/3 Metadata Extract dialog box appears.
Figure 3.22 SAP R/3 Metadata Extract
Preparing to Import the SAS IT Resource Management Adapter for SAP
35
4
In the Configured SAP Server field, select the SAP server that you defined in SAS
Management Console. 5
Click Test SAP Server Connection. If the connection is successful, then the following message appears: Figure 3.23 Connection Successful Message
Note: If the connection is not successful, the SAS log indicates a problem. For
example, RFC server errors might indicate that the RFC server is not running, or an
invalid user ID might indicate that the password is incorrect. For more information
about troubleshooting connection problems, see the SAS/ACCESS Interface to R/3
installation documentation that is included in your installation package.
6 Click Yes.
The View SAS Log dialog box displays the LIBNAME statement that is generated using
the specified parameters.
36 Defining the Environment
7
Chapter 3
Click OK to exit the SAS log.
Figure 3.24 SAS Log Example
8
In the SAP R/3 Metadata Extract dialog box, click Cancel.
Note: Before you test the SAP connection, create the SAP library that is associated
with the SAP server. You should test this connection after you have imported the
package files for the first time. This ensures that the SAP library is automatically
available for testing the connection. If you want to test the SAP connection for other
SAP servers, then you need to create SAP libraries for the corresponding SAP servers.
Preparing to Import the SAS IT Resource Management Adapter for SAP
37
Create Directories for Administrative and Raw Data
1
Create the ITManagementAdapterSAP folder on the SAS ITRM Application Server
at the following location:
X:\SAS\<ConfigDir>\Lev1\SASITRM\Data
2
Create two directories, one for the administrative data and another for the raw data
at the following location:
X:\SAS\<ConfigDir>\Lev1\SASITRM\Data\ITManagementAdapterSAP
After you create the two directories, the paths should be:


X:\SAS\<ConfigDir>\Lev1\SASITRM\Data\ITManagementAdapterSAP\Admin
X:\SAS\<ConfigDir>\Lev1\SASITRM\Data\ITManagementAdapterSAP\
Rawdata
Note: The above path is for windows. While working in a z/OS environment, you
need to create the ITManagementAdapterSAP, Admin, and Rawdata folders in the
following location.
<ConfigDir>/Lev1/SASITRM/Data/
38 Defining the Environment
Chapter 3
37
C H A P T E R
4
Installation and Customization of
SAS IT Resource Management
Adapter for SAP
Installing the SAS IT Resource Management Adapter for SAP Jobs and Metadata .................................. 37 Customizing the SAS Environment................................................................................................................ 37 Customization for Internationalization (I18N) ............................................................................................. 39 Deploying SAS IT Resource Management Adapter for SAP Jobs and Tables Metadata............................ 41 Customizing SAS Data Integration Studio Jobs and Programs .................................................................. 48 Customize the get_sap_lib_info.sas Program................................................................................................. 49 Customize the preprocglobal.sas Program ..................................................................................................... 49 Installing the SAS IT Resource Management Adapter for SAP Jobs and
Metadata
Installation of ETL job packages and related metadata for the SAS IT Resource
Management Adapter for SAP is performed using the SAS Deployment Wizard that is
part of your software order.
Customizing the SAS Environment
Since the configuration of SAS IT Resource Management Adapter for SAP is not
handled by SAS Deployment Wizard, you need to perform certain steps manually. To
customize the SAS IT Resource Management Adapter for SAP to suit your SAS
environment:
1
Create the following folder structure on the machine where SAS IT Resource
Management Adapter for SAP is installed.
38 Customizing the SAS Environment
Chapter 4
The default path to create the ITManagementAdapterSAP folder structure
under the Windows environment is
C:\SAS\<ConfigDir>\Lev1\SASITRM\Data.
Display 4.1 SAS Environment Folder Structure
Note: If you do not give full permission to the folder and proceed with the
deployment, then an error occurs while importing the adapter jobs. Therefore,
granting full permissions to the Install folder is mandatory.
Note: The default path mentioned above is for Windows
environments. While working in a z/OS environment, you need to create the
ITManagementAdapterSAP, Admin, and Rawdata folders in the following
location.
<ConfigDir>/Lev1/SASITRM/Data/
Installation and Customization of SAS IT Resource Management Adapter for SAP
2
39
Modify the sasv9.cfg file to configure the adapter installation path and data path.
Display 4.1 Select the SASV9.CFG File
3
Add the following code to the config file:
-SET adptitminstall "C:\Program
Files\SASHome\SASITResourceManagementAdapterforSAPData\3.21\Cus
tomSASCode"
-SET adptitmdata
"C:\SAS\Config\Lev1\SASITRM\Data\ITManagementAdapterSAP"
Note: The above paths are default paths in a Windows environment. Apply the
above changes appropriately as per your host and Install location at your site.
Note: In a z/OS environment, create the following variables in the config file.
SET='ADPTITMINSTALL1 /SASHOME’
SET='ADPTITMINSTALL2 /SASITResourceManagementAdapterforSAPData'
SET='ADPTITMINSTALL3 /3.21/CustomSASCode'
These variables are required in order to find the program location while running
the jobs in the SAS Data Integration Studio.
For more information about the location where you need to create these variables,
see the manual entitled Configuration Guide for SAS® 9.3 Foundation for
z/OS. The guide has a section about customizing default options and system
configuration files in the location &prefix.CONFIG.
4
Grant full permissions to the Install folder named CustomSASCode, as the
deployment writes custom SAS code into this folder.
Customization for Internationalization (I18N)
This configuration step is optional. SAS IT Resource Management does not extract
any text tables from SAP. Therefore, you can use the default language encoding even if
40 Customization for Internationalization (I18N)
Chapter 4
your customer requires your SAP system to be a Unicode system. To configure the
Adapter in an Internationalization Environment:
1
Configure SAS Unicode Server, if your SAP system is a Unicode system.
SAP data is on Unicode pages. You therefore need to use appropriate transcoding
while extracting the SAP data using the SAS Data Surveyor for SAP. Configure
SAS environment to point to the SAS Unicode Server.
2
Modify the SASV9.CFG file to access the SAS Unicode server. The default path
for SASV9.CFG is C:\Program Files\SASHome\SASFoundation\9.3.
Display 4.2 SASV9.CFG
3
Change the following code snippet in the SASV9.CFG file to replace “en” by “u8”
-CONFIG
"C:\ProgramFiles\SASHome\SASFoundation\9.3\nls\u8\SASV9.CFG"
In a UNIX environment, replace “en” by “u8,” in the sas file, under the
/SASFoundation/9.3 folder. Here is the code that appears in the UNI X
environment after you replace “en” with “u8.”
# Environmental variable to define config file lookthrough
if [ "$SASCFGPATH" ] ; then
SASCFGPATH="!SASROOT/sasv9.cfg, !SASROOT/nls/u8/sasv9.cfg,
!SASROOT/sasv9_local.cfg, $SASCFGPATH"
else
SASCFGPATH="!SASROOT/sasv9.cfg, !SASROOT/nls/u8/sasv9.cfg,
!SASROOT/sasv9_local.cfg"
4 Restart the SAS Services after the code changes are complete. Change the
SASV9.CFG file to point to the appropriate encoding, based on your encoding
requirement.
Installation and Customization of SAS IT Resource Management Adapter for SAP
41
Note: The preceding example is for a Windows environment. Apply the above changes
appropriately, as per the host at your site. For further details about SAS Unicode server,
see the SAS support site.
Note: Steps 1–4 are not applicable for z/OS, as there is no Unicode server in a z/OS
environment.
Deploying SAS IT Resource Management Adapter for SAP Jobs and Tables
Metadata
After the installation of SAS IT Resource Management Adapter for SAP, deploying
jobs and tables metadata for the adapter is a manual process.
In a Windows environment, when you install the adapter, the files in the following
screen are available in the path C:\Program Files\SASHome\
SASITResourceManagementAdapterforSAPData\3.21\CustomSASCode
While working in a Windows or UNIX environment, delete the following files; they are
specific to MVS:
 preprocglobal_mvs.sas
 get_sap_lib_info_mvs.sas
In a z/OS environment, delete the following files; they are specific to Windows or
UNIX environment:
 preprocglobal.sas
 get_sap_lib_info.sas
After you delete the preceding files in a z/OS environment, you need to rename the
remaining files by deleting _mvs.
To deploy metadata objects (in this case, jobs and tables) for the SAS IT Resource
Management Adapter for SAP, use the standard metadata import and export features of
the SAS Data Integration Studio.
The components for the SAS IT Resource Management Adapter for SAP are stored as
package files. A package file is available in the Install location. The standard Install
location in a Windows environment for storing the package file is C:\Program
Files\SASHome\SASITResourceManagementforAdapterSAPData\3.21\SASPacka
ges
Note: The above install location is platform-dependent, and it can be changed as
needed. For example, the path would be in z/OS
<SASHOME>/SASITResourceManagementAdapterforSAPData/3.21/
SASPackages
42 Deploying SAS IT Resource Management Adapter for SAP Jobs and Tables Metadata
Chapter 4
As the SAS packages are installed in the z/OS, you need to transport them manually
via File Transfer Protocol (FTP) to the PC where the client is running. Ensure that the
SASPackages are transported in binary mode. This enables the import function of the
SAS Data Integration Studio to read the SAS package files.
To deploy tables and jobs, complete the following steps:
5
Open SAS Data Integration Studio with Connection Profile for the
user.
6
In the metadata profile, select the project that you defined when you added the
SAP server and SAP library.
The SAS IT Resource Management Adapter for SAP is imported to the project that
you select in this step.
7
Right-click Products in the SAS Folders Tree, and then click Import.
Display 4.3 SAS Data Integration Studio: Products
In the Import from SAS Package dialog box, click Browse, and then open the
SASPackages folder.
You can find the SASPackages folder within the Install folder that you created at
the time of installation.
8
Select the package SASITMAdapterforSAP_DIS_ProductFolders.spk.
9
Under Import Options, select All Objects, and then click Next.
Retain the default options and continue.
Display 4.4 Export SAS Package Wizard
Installation and Customization of SAS IT Resource Management Adapter for SAP
The objects to be imported appear.
Display 4.5 Select Objects to Import
10 Click Next to continue.
The following screen appears.
Display 4.6 Summary, Import from SAS Package Window
11 Review the summary, and then click Next.
A progress indicator appears.
43
44 Deploying SAS IT Resource Management Adapter for SAP Jobs and Tables Metadata
Chapter 4
Display 4.7 Important Objects Window
12 The Import from SAS Package dialog box displays a completion message. If
the import process fails, click View Log, check for messages, and take
appropriate action.
Display 4.8 Import Complete Message
Note: Use the following sequence while performing the preceding steps to deploy
application folders, data sources, and jobs.
 SASITMAdapterforSAP_DIS_ProductFolders.spk
 SASITMAdapterforSAP_DIS_AppFolders.spk
 SASITMAdapterforSAP_DIS_Tables.spk
 SASITMAdapterforSAP_DIS_Jobs.spk
Installation and Customization of SAS IT Resource Management Adapter for SAP
45
Note: To import the second package SASITMAdapterforSAP_DIS_AppFolders.spk,
right-click System in the SAS Folders Tree, and then click Import. For other
packages, right-click Products in the SAS Folders tree and then click Import.
While importing to the package file SASITMAdapterforSAP_DIS_Tables.spk, perform
the following steps:
13 In the Import from SAS Package dialog box, select the package
SASITMAdapterforSAP_DIS_Tables.spk.
14 Under Import Options, select All Objects, and then click Next.
Retain the default options and continue.
Display 4.9 SAS Application Servers Window
15 Verify that the SAS Application Servers is set correctly as SASITRM. Select
Next.
46 Deploying SAS IT Resource Management Adapter for SAP Jobs and Tables Metadata
Display 4.10 Other Servers Window
16 Select an SAP server.
Chapter 4
Installation and Customization of SAS IT Resource Management Adapter for SAP
47
Display 4.11 Directory Paths, Import from SAS Package Window
17 Verify that all directories and paths appear correctly.
18 Click Import to import the selected objects.
19 Click View Log to review the SAS log.
Note: The SAS log might contain the warning the person ETL Developer 1
was not found. Ignore the warning.
A new folder named SAS IT Management Adapter for SAP is added to the
Products folder.
48 Customizing SAS Data Integration Studio Jobs and Programs
Chapter 4
Display 4.12 Products Folder
Once the import process is complete, the environment for data extraction and
transformation from SAP is set.
You can customize your environment further in the SAS Data Integration Studio
environment, as needed.
Note: In a z/OS environment, while importing tables package file
SASITMAdapterforSAP_DIS_Tables.spk, delete the default target directory paths.
Then, manually select the paths of the Admin and Rawdata folders. While importing
jobs package file SASITMAdapterforSAP_DIS_Jobs.spk, manually enter the
preprocglobal.sas file from the adapter installation location.
Customizing SAS Data Integration Studio Jobs and Programs
To customize the SAS IT Resource Management Adapter for SAP to fit into your
unique SAP environment, you need to review and change a few jobs in the SAS Data
Integration Studio. You also need to review and change several SAS programs within
these jobs.
Although many of the jobs and programs do not require changes, you need to review
each one to ensure the results that you get the results that you want. The following
sections provide information about each job and program that requires your review and
changes. It describes each job in the SAS Data Integration Studio and explains whether
the job or program requires changes to work successfully.
Installation and Customization of SAS IT Resource Management Adapter for SAP
49
Customize the get_sap_lib_info.sas Program
The custom SAS code get_sap_lib_info.sas needs to be customized so as to point to the
appropriate metadata server. The default location of the custom code is in Windows:
C:\Program Files\SASHome\SASITResourceManagementAdapterforAPData\
3.21\CustomSASCode
The default location of the custom code in z/OS is
<SASHOME>/SASITResourceManagementAdapterforSAPData/3.21/CustomSASCode
Display 4.13 get_sap_lib_info.sas File
In the above program, modify the highlighted section to point to the appropriate
Metadata Server.
Note: The metauser in the above code should not have any unrestricted authorizations.
Therefore, SAS demo user or any other external user created in Software Management
Console is preferred. If the user does not provide the correct information in this program, the 0010
Step 1 Select SAP Servers job that uses this program will not create any records in the output table.
Make sure that all the information is correct in the program before you run the job.
Customize the preprocglobal.sas Program
SAS IT Resource Management Adapter for SAP jobs use global macro variables that
are initialized in the preprocglobal.sas program. This program serves as the
preprocessing step in the first initialization job. The custom SAS code preprocglobal.sas
needs to be customized so as to point to the appropriate libref of the SAP server.
The preprocglobal.sas program is in the Install directory. The file is located at the
place where you specified the Install directory on the SAS Deployment Wizard during
Installation. The default location of the custom code is in Windows:
C:\Program Files\SASHome\SASITResourceManagementAdapterforSAPData\
3.21\CustomSASCode
Make appropriate changes in the following section of the program to suit your
environment.
50 Customize the preprocglobal.sas Program
Chapter 4
* Select
wanted sap librefs that you want extract statistical data from.
List must be entered as quoted company codes
separated by commas;
% let wanted_sap_libref = 'SIO';
Use the preceding section of the program to assign values to the macro variable %let
wanted_sap_libref in order to restrict the initialization job from specific SAP
systems. Enter libref values of the SAP systems, from which you want to extract the
data.
options mstored mrecall;
filename macro '!ADPTITMINSTALL';
* This macro filename setting is more portable, but
* can only work from the right context ;
options sasautos = (macro sasautos );
* Select wanted sap librefs that you want extract statistical data from.
List must be entered as quoted company codes
separated by commas ;
%let wanted_sap_libref = 'SIO';
/*
* End of preprocglobal.sas
*/
While running the preprocglobal.sas program in an UNIX environment, a small
change has to be done in the program. As UNIX is case sensitive, you need to replace
filename macro '!ADPTITMINSTALL'; with filename macro
'!adptitminstall';
In z/OS, the preprocglobal.sas program should resemble the program in the following
figure.
options mstored mrecall;
filename macro “%sysget
(ADPTITMINSTALL1)%sysget(ADPTITMINSTALL2)%sysget(ADPTITMINSTALL3)”;
* This macro filename setting is more portable, but
* can only work from the right context ;
options sasautos = (macro sasautos );
* Select wanted sap librefs that you want extract statistical data from.
List must be entered as quoted company codes
separated by commas ;
%let wanted_sap_libref = 'SIO';
/*
* End of preprocglobal.sas
*/
Note: The variables that you find in the filename statement of the above program are
those that you defined in the config file of the z/OS environment.
51
C H A P T E R
5
SAS Data Integration Studio Jobs
Overview........................................................................................................................................................... 51 Using SAS Data Integration Studio or SAS IT Resource Management .............................................. 51 Job Naming Conventions ........................................................................................................................ 51 Initialization Jobs ........................................................................................................................................... 52 Overview ................................................................................................................................................... 52 0010 Step 1 Select SAP Servers .............................................................................................................. 53 0020 Step 2 Suggest Destinations for Selected SAP Servers: Extracts Destinations .......................... 54 0030 Step 3 Create Final List of Servers and Destinations .................................................................. 55 0040 Step 4 Create Mapping for SAP Program Types........................................................................... 55 Extraction Jobs ................................................................................................................................................ 55 Extraction of Default R/3 Statistics ....................................................................................................... 55 0110_1A Extract Default Performance Data from SAP Server ..................................................... 55 0110_1B Extract All Performance Data from SAP Server ............................................................ 57 Extraction of Business Warehouse (BW) Statistic Tables ..................................................................... 57 Transformations .............................................................................................................................................. 59 Libref Collector ........................................................................................................................................ 59 Extract SAP Business Warehouse (BW) Performance Statistics ........................................................... 60 Suggest SAP Library and Destination Parameters ............................................................................... 60 Extract SAP IT Performance Statistics .................................................................................................. 61 Jobs in z/OS .................................................................................................................................................... 62 Overview
Using SAS Data Integration Studio or SAS IT Resource Management
This chapter describes the SAS IT Resource Management jobs that are provided with
the SAS IT Resource Management Adapter for SAP. The SAS IT Resource Management
jobs require customization so that they reference the SAP servers.
Note: References to the SAS IT Resource Management client in this document pertain
to the use of SAS Data Integration Studio with ITRM plug-ins. These plug-ins are not
specifically required for the SAS IT Resource Management Adapter for SAP tasks and
jobs. In other words, you can use either the SAS Data Integration Studio client or the
SAS IT Resource Management client to perform the tasks and work with the jobs that
are referenced in this document.
Job Naming Conventions
The jobs use the following naming conventions:
 Ordering Jobs: A job has a numeric prefix that indicates its order of execution. A
job with a lower number is executed before a job with a higher number. The
display order of the job is the same as its execution order. Numbering between
jobs is not contiguous so that additional jobs can be added between two existing
jobs.
52 Initialization Jobs
Chapter 5


Internal Jobs: An internal job is submitted from within another job (using a LOOP
construct). It has a two-part prefix, separated by an underscore. The first part of
the prefix refers to the calling job, and the second part refers to the individual
internal job. For example, the prefix 0020_10 refers to an internal job that is
called by the job with the prefix 0020. Internal jobs are grouped in subfolders.
Internal jobs cannot be executed independently because the parameters set up by
the calling job are not available.
Alternative Jobs: When there is more than one job that achieves the same results,
an additional alphabetic character is added to the prefix. For example, 0010A and
0010B are alternative jobs; that is, only one of these two jobs is required.
The following figure displays all of the SAS Data Integration Studio jobs provided
with the SAS IT Resource Management Adapter for SAP:
Display 5.1 SAS IT Resource Management Adapter for SAP Jobs
Initialization Jobs
Overview
The initialization jobs are listed in the following sections. The job descriptions and
figures provide a high-level overview of the SAS IT Resource Management interface
and how to work with the jobs. 0010 Step 1 Select SAP Servers is the only initialization
job to select the required SAP libraries to extract the performance data from the SAP
systems. The rest of the other initialization jobs are required to run in both the indirect
as well as the direct extraction method.
SAS Data Integration Studio Jobs
53
0010 Step 1 Select SAP Servers
This job lists the servers that are monitored. The job appends the attributes of the
source SAP servers to the Admin SAP Server Libraries table. The job uses the Libref
Collector transformation, which extracts the details of all the SAP libraries registered
in the SAS Metadata Server. You need to apply a filter if you want to restrict some
libraries, otherwise, you can leave the job as it is shipped. (In the previous release, this
was a customization job where you needed to drag and drop the relevant libraries for
data extraction.)
Display 5.2 0010 Step 1 Select SAP Servers
Table 5.1: Parameters Used in the 0010 Step 1 Select SAP Servers
Parameter
Name
Macro Variable
Name
Description
Libref
libref
SAS libref to SAP server
Options
options
All options for the SAS LIBNAME statement to
connect to an SAP server
_n_
_n_
Observation number in loop input table
The output of the Libref Collector transformation is the following data set, which
contains the LIBNAME and the options used in separate columns.
54 Initialization Jobs
Chapter 5
To customize this job, provide the libref values of the relevant SAP servers to the
macro variable in Preprocglobal.sas program, which is used in this job.
0020 Step 2 Suggest Destinations for Selected SAP Servers: Extracts
Destinations
This job takes the output table Admin.SAP Server Libraries of the previous job as
input. The job then reads destinations from the selected SAP servers and creates an
output table named Admin LibDests_Suggestion Librefs and Dests Suggestion, with
destinations for indirect extraction. By default, performance data is extracted directly
from a single SAP system. If you need indirect extraction via RFC-connected SAP
systems, then additional data has to be supplied for the extraction. Indirect extraction is
not supported for the statistic tables specific to the SAP Business Warehouse.
This job has an internal job named 0020_10 Step 2 Internal Job-Extract and Add
Dests. This job collects the attributes of all the libraries and saves the attributes in a
table. This internal job takes the tables RFCDES and SAPWLSERV as input. These
SAP tables are assigned by the import process to an SAP server through the SAP
sample library mapping. The job reads these tables from the SAP server that is used in
job 0010A Step 1 Select single SAP Server. The tables RFCDES and SAPWLSERV serve
rather as templates than real tables.
Display 5.3 0020 Step 2 Suggested Destinations for Selected SAP Servers
The internal job is called in a loop over input table Admin.SAP Server Libraries. The
loop provides the values for the parameters of the job. It has three input tables and one
output table.
SAS Data Integration Studio Jobs
55
0030 Step 3 Create Final List of Servers and Destinations
This job lists the SAP systems connected via RFC to the selected SAP hub server.
There are two tasks that you need to perform:
 Modify the code in the User Exit to Clean Suggested List transformation that adds
or removes unwanted remote systems.
 Remove unwanted destinations from the output table. This can be done by
customizing the job 0030 Step 3 Create Final List of Servers and Destinations.
This job uses the table min. LibDests_Suggestion as input. SAS table Admin.SAP
Server libraries + Destinations is the output table. This table is basically the
Admin.SAP Server Libraries table extended by destinations.
Run the saved job and verify that the output table contains the right records. The
value 'NONE' in column RFC Destination (RFCDEST) implies direct extraction from the
SAP server with SAP System ID specified in column SAPSYS. Other values denote the
SAP servers connected to the hub server via RFC.
0040 Step 4 Create Mapping for SAP Program Types
The SAS IT resource Management solution does not require an output table from this
job. Therefore, this job is optional for both direct and indirect extraction methods.
This job extracts objects from SAP servers and maps them to SAP programs, provided
you extract performance data via the hub server. The job uses the table
Admin.SAP_Server_dests as input and generates the table
RAWDATA.PROGRAM_MAP as output.
Note: If you want to run this job and the SAP system is Unicode, then you need to set a
Unicode encoding option, which is mentioned in the "Customization for
Internationalization (I18N)" section in Chapter 4.
Extraction Jobs
Extraction of Default R/3 Statistics
This process involves either one of the two jobs that are described in detail in the
following sections. Whenever you run the job, it extracts data corresponding to the
current date. For example, if you run the job today, it retrieves today’s R/3 statistics.
0110_1A Extract Default Performance Data from SAP Server
This job is an alternative job for job 0110_1B Extract All Performance Data from SAP
Server. This job uses the input table Admin.SAP_Server_dests, which is created in
previous job (0030 Step 3) and extracts default SAP performance data from the
monitored SAP servers. This extraction job generates the following output tables:
 RAWDATA.RC0
 RAWDATA.BTC
 RAWDATA.RS0
 RAWDATA.RCD
56 Extraction Jobs
Chapter 5





RAWDATA.NRM
RAWDATA.SPP
RAWDATA.RSD
RAWDATA.SPA
RAWDATA.TII
Before you start running this job, run the initialization jobs based on the type of
extraction that you use. To execute this job under direct extraction:
1
Define each of the source SAP systems as an SAP library with associated SAP
server. To do this, you need to customize the initialization job 0010 Step Select
SAP Servers. Enter required SAP libraries in preprocglobal.sas program.
2
Run the initialization jobs 0020 and 0030. This creates the final input table for the
extraction job. In direct extraction, the final admin table looks like the following
table.
Figure 5.1 Sample Data Administration SAP_Server_destinations
3
After you run the jobs 0020 and 0030, verify that the output table Admin SAP
Server Libraries + Destinations contains the right records. The value 'NONE' in
column RFC Destination (RFCDEST) implies direct extraction from the SAP
server with SAP System ID specified in column SAPSYS.
Note: If you want to extract data from multiple servers, then you need to enter all
the required SAP systems in the preprocglobal.sas program.
To execute this job under indirect extraction:
1
Specify an SAP system to be the hub. From this hub, you can establish
destinations to other SAP systems.
2
Enter the libref of the hub SAP server in the preprocglobal.sas program.
Note: The job 0020 Step 2 Suggest Destinations for Selected SAP Servers takes the
output table Admin.SAP Server Libraries of the previous step as input. It reads
destinations from the selected SAP servers and generates an output table with
possible destinations for indirect extraction. By default, the output table is named
as Admin LibDests_Suggestion Librefs and Dests Suggestion.
Display 5.4 Sample Data Admin LibDests_Suggestion Librefs and Dests Suggestion
SAS Data Integration Studio Jobs
3
57
Edit the job 0030 Step 3, and then run it. This creates the final list of servers and
destinations.
Display 5.5 Sample Data Administration SAP_Server_destinations
4
Run the saved job and verify that the output table Admin SAP Server Libraries +
Destinations contains the right records. The value 'NONE' in column RFC
Destination (RFCDEST) stands for direct extraction from the SAP server with
SAP System ID specified in column SAPSYS. Other values stand for other SAP
servers RFC-connected to the hub server.
0110_1B Extract All Performance Data from SAP Server
This job is an alternative job for job 0110_1A Extract Default Performance Data from
SAP Server. The job extracts all SAP performance data from all SAP servers to populate
the raw data tables. The job uses the input table Admin.SAP_Server_dests. This input
table is created in a previous job (0030 Step 3) and generates the following output
tables:
 RAWDATA.RC0
 RAWDATA.BTC
 RAWDATA.RS0
 RAWDATA.RCD
 RAWDATA.NRM
 RAWDATA.SPP
 RAWDATA.RSD
 RAWDATA.SPA
 RAWDATA.TII
 RAWDATA.DBP
 RAWDATA.ADM
 RAWDATA.TAB
 RAWDATA.CIF
 RAWDATA.HTPCL
 RAWDATA.HTPCD
 RAWDATA.HTP
Note: Some of the raw data tables are created based on the version of SAP that you
are using.
Extraction of Business Warehouse (BW) Statistic Tables
The job 0120 Extract SAP BW Stats in the SAS Data Integration Studio is specifically
meant for the extraction of SAP BW performance statistics from selected BW systems.
58 Extraction Jobs
Chapter 5
This job uses the transformation Extract SAP BW Performance Statistics to get
statistics form SAP. The statistics are specified as output tables of the transformation
Extract SAP BW Performance Statistics. The transformation takes as input the
Admin.SAP Server Libraries table created in the previous step and the BW Delta
Control table. The selected statistic tables are extracted from each selected SAP system.
The job extracts records from BW statistic tables by taking the starting time as the
first day of the first month of the current year. The end time is the time when you run
the job. That is, it extracts data from the starting time to till date. For instance, the
extraction condition for the year 2010 would be:
STARTTIME > 20100101(yymmdd)
Note: You cannot set STARTTIME dynamically.
To extract SAP BW performance statistics from selected BW systems:
1
Define each SAP system that is accessed for extraction of performance data as an
SAP library with its associated SAP server.
2
The initialization job 0010 Step Select SAP Servers needs to be customized for this
purpose. Enter required bwsap libraries in the preprocglobal.sas program.
3
Run the extraction job 0120 Extract SAP BW Stats in the Data Integration Studio
to extract SAP BW Performance Statistics from selected BW systems.
This extraction job uses the following input tables:


Admin. SAP_Server_libraries
Rawadmin BW_DELTACTL
The job creates the following output tables:


RAWDATA.WHM
RAWDATA.RSS
The following tables are optional. If you want to extract data from these tables, you
have to customize the job accordingly.
 RAWDATA.RSS
 RAWDATA.WHM
 RAWDATA.AGR
 RAWDATA.BCA
 RAWDATA.CND
 RAWDATA.DELXTR
 RAWDATA.LOG
 RAWDATA.DEL
Note: BW Delta Control table is defined as input table, but it also gets updated by the
transformation.
Note: You might have set up a Unicode (u8) encoding option, which is mentioned in
"Customization for Internalization (I18N)" in Chapter 4. If so, then before you run the
0120 Extract SAP BW Stats job, you need to add the following option to the System
Options tab in the properties section of the BW job: 0120 Extract SAP BW Stats.
To add this option, right-click Properties on the Job tab and then go to the Option
tab. In the System Options field, enter the following statement:
Varlenchk=NOWARN;
SAS Data Integration Studio Jobs
59
If this option is not specified, a warning about truncating field lengths might appear in the
job log files. Since the system error options (syserr) are set to 4 because of these warnings,
the job will be unable to process the creation of the output tables in the raw data folder.
Transformations
Libref Collector
The Libref Collector transformation is the new transformation that is developed
in this release of SAS IT Resource Management Adapter. The transformation collects
SAP library values in a data set.
In the previous release, there was a Java component named Libref Collector in 9.1.3,
plugged into the SAS Data Integration Studio. This plug-in was used to collect the SAP
library values. In this release, the Libref Collector transformation with SAS code
replaces the Libref Collector plug-in.
Display 5.6 Libref Collector Transformation
The Libref Collector transformation extracts the details of all the SAP libraries
registered in the SAS Metadata Server. Also, you can customize the job that contains
this transformation, as per your requirements.
60 Transformations
Chapter 5
Extract SAP Business Warehouse (BW) Performance Statistics
The transformation extracts performance statistics tables from the SAP BW, using a
delta control mechanism. Extraction time stamps are logged in a delta control table by
SAP host instance and extracted SAP BW table. Successive extractions retrieve only
records with a time stamp larger than the previous extract minus one hour, and append
the extracted records to the output tables. The rationale for one-hour overlap is to
ensure that even the long running jobs are caught. This might result in duplicate
records. However, any duplicate records are removed by the loading steps into the SAS
IT Resource Management IT data marts.
The transformation has two input tables:
 the BW Delta Control table
 the list of SAP systems to extract data from
Note: The BW Delta Control table is defined as input table, but it is also updated by
the transformation. The table fills details about BW tables and extraction conditions so
that the next extraction of data from a particular table starts from that time onwards
from SAP.
The transformation has 1–11 output tables. All output tables are located in the same
library. The transformation has the following options to extract data from SAP BW
systems.
Table 5.2 Parameters Used in the Transformation
Parameter
Name
Macro
Variable
Valid Values and Description
MODE
_MODE
INIT: Initialize the BW Delta Control Table and overwrite
output tables.
APPEND: Append new records to output tables according
to time stamps from Delta Control Table.
OVERWRITE: Replace output tables with new records
according to time stamps from Delta Control Table.
Default is APPEND.
The transformation calls the SAS SCL program sashelp.r3itadp.read_bw_stats.scl.
this program loops through the input table. The transformation also performs the
following functions:
 Lists the SAP systems for data extraction.
 Assigns an SAP LIBNAME to each SAP system.
 Calls the macro %readBwStats to extract the statistic tables.
Suggest SAP Library and Destination Parameters
The Suggest SAP Library and Destination Parameters transformation has
to be used in a DATA step. The transformation also has to be used in input and output
statements. The transformation has three input tables and one output table. The
following table describes the three input tables used by this transformation.
SAS Data Integration Studio Jobs
61
Table 5.3 Input Tables Used by the Suggest SAP Library and Destination Parameters Transformation
Prompt
Description
Place table RFCDES
here
Table of Destinations in the SAP system for Remote Function
Call. A sample schema of this table is distributed with the
installation. It can also be registered using Source Designer
for SAP from the table RFCDES on the SAP system.
Place table
SAPWLSERV here
Table of active SAP servers. A sample schema of this table is
distributed with the installation. It can also be registered
using Source Designer for SAP from the table SAPWLSERV
on the SAP system. This table needs to be updated with all
active SAP servers from which we are extracting data via the
hub server for indirect extraction.
Place table
ADMIN.SAP Server
Libraries here
List of SAP servers to extract performance data from. This
table should have been created with the first initialization job.
Extract SAP IT Performance Statistics
The transformation calls the SAS SCL program
sashelp.r3itadp.read_r3_stats.scl involving RFC function modules to extract
the data from SAP. The log files are read from SAP for particular RFC destination
assigned by the SAP Library, beginning date and end date. Table 5.4 gives more
information about the RFC destination, beginning date and end date.
Once extraction is complete, administration tables Las_extract_information and
EXTRACTION_RECORD are filled by date and time stamps. The
EXTRACTION_RECORD table contains the information about when the last extraction
takes place. The table also contains date stamps against the current extraction start
times and end times. Therefore, the next extraction will take the starting date from this
table itself.
Table 5.4 Extraction Condition for Function Module
Condition
DEST
BDAT AND EDAT
Description
Optional. Specifies the name of an SAP destination (that was
setup using SM59) for indirect extraction.
If DEST is set and its value is NONE, then it stands for direct
extraction from the SAP server.
If the value of DEST is different from NONE, then it stands for
other SAP servers RFC-connected to the hub server. This
means it stands for the indirect extraction method.
The job looks for a previous run date in the table
LAST_EXTRACT_INFO. If a previous run date is found, then
the job takes it as the begin date. If no previous run date is
found in the table, then it takes the previous night midnight as
the begin time. The end date is current date plus one.
62 Jobs in z/OS
Chapter 5
Jobs in z/OS
If you are executing on a SAS workspace server in z/OS, then add the following
options to the SAS configuration file or to the individual SAS IT Resource Management
Adapter for SAP batch jobs:
options nocardimage;
options linesize=300;
Note: These options are required. Without these options, the default values in z/OS
might truncate the inherently long string of parameters that are associated with
LIBNAME statements that access SAP.
SAS Data Integration Studio Jobs
63
65
A P P E N D I X
1
Restricting the RFC User Account for
IT Resource Management Adapter for
SAP
Overview........................................................................................................................................................... 65 Create and Edit a Profile ................................................................................................................................ 73 Associating the Profile with User Account ..................................................................................................... 87 Overview
The example detailed in this appendix was performed on SAS 6.0. In this example,
the system administrator creates a new authorization, uses it in a profile, and defines a
user account that uses the profile. (In addition, the user account is designated as a
system account, which prevents interactive logons.) Here is the sequence of events:
1
Create the authorization SASCPIC.
2
Specify the program that SASCPIC is allowed to execute. Using the SAP
authorization administration, enter the program name /SAS/SAPLADITM with
the function group /SAS/ADITM.
3
Specify that only activities 37 and 51 are allowed.
4
Save your settings. Activate SASCPIC.
5
Create a new profile named ITRM using the SASCPIC authorization. (The profile
uses other more standard authorizations as well, such as those that allow CPIC
and RFCs to run.)
6
Associate the new ITRM profile with the SAP user ID and account that performs
data extractions.
By completing these steps, the account can be used only for extracting performance
data. Functions in the /SAS/ADITM function group are the only functions that can be
used to return data. Any attempt to extract tables or metadata results in an error that
indicates a lack of permission. Create an Authorization
To create an authorization, complete the following steps:
1
In the SAP Easy Access window, under Authorizations and Profiles
(Manual Maintenance), double-click Edit Authorizations Manually.
66 Overview
Appendix 1
Display A1.1 SAP Easy Access Window
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.2 Maintain Authorizations: Object Classes Window
2
Double-click BC_A Basis: Administration.
Display A1.3 Object List Window
67
68 Overview
Appendix 1
3
In the Object column, double-click S_CPIC CPIC Calls from ABAP
Programs.
Display A1.4 Authorization List Window
4
Click Authorization  Create.
Display A1.5 Create New Authorization Dialog Box
5
In the Text field, enter a description for this authorization. Click
.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.6 Authorization List Window
6
Double-click ABAP program name with search help.
Display A1.7 Field values Dialog Box
7
To restrict permission for S_CPIC so that it can execute only the
/SAS/SAPLADITM program, complete the following steps:
69
70 Overview
Appendix 1
a. In the From column, type /SAS/SAPLADITM (where /SAS/ADITM is the
function group).
b. Note that there is no value for To.
c. Click the diskette icon to save your changes.
Here is an example of the system-generated code associated with the /SAS/ADITM
function group:
*******************************************************************
* System-defined Include-files. *
**********************************************************
****
INCLUDE LZSASXTOP. “Global Data
INCLUDE LZSASXUXX. “Function Modules
*******************************************************************
* User-defined Include-files (if necessary). *
*******************************************************************
* INCLUDE LZSASXF... “Subprograms
* INCLUDE LZSASXO... “PBO-Modules
* INCLUDE LZSASXI...
Permission is restricted so that only the function module
/SAS/SAPWL_STATREC_READ_FILE can be executed.
8
In the Authorization List window, select Activity and then click Enter Values.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.8 Authorization List Window
71
72 Overview
Appendix 1
Display A1.9 Define Values Dialog Box
9
Select the check boxes for activities 37 and 51. Click the diskette icon to save the
changes.
10 In the Maintain Authorization window, click Authorization  Activate. This
activates the newly created authorization.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
73
Display A1.10 Authorization List Window
Create and Edit a Profile
To create a profile, complete the following steps:
1
In the SAP Easy Access window, under Authorizations and Profiles
(Manual Maintenance), double-click Edit Profiles Manually or enter the
transaction code SU02.
74 Create and Edit a Profile
Appendix 1
Display A1.11 SAP Easy Access Window
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.12 Profiles: Initial Screen Window
2
Click Generate Work Area.
75
76 Create and Edit a Profile
Appendix 1
Display A1.13 Profile List Window
3
Click Profile  Create.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.14 Create New Profile Dialog Box
4
To create a new profile, complete the following steps:
a. In the Profile field, enter a profile name.
b. In the Text field, enter description.
c. Under ProfType, select Single profile.
d. Click
to save the profile.
Display A1.15 Maintain Profile Window
5
To edit the profile, click Add object.
77
78 Create and Edit a Profile
Appendix 1
Display A1.16 Maintain Profiles: Object Classes Window
6
Double-click BC_A Basis: Administration.
Display A1.17 Maintain Profiles: List of Objects Window
Restricting the RFC User Account for IT Resource Management Adapter for SAP
7
Click the check box next to S_CPIC and then select Authorizations  Copy.
Display A1.18 Maintain Profile Window
8
79
In the Authorization column, click
.
A list of associated authorizations for the object S_CPIC appears in the
Restrictions window.
80 Create and Edit a Profile
Appendix 1
Display A1.19 Restrictions Window
9
Double-click SASCPIC. The authorization SASCPIC is associated with the object
S_CPIC.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.20 Restrictions Window – Selecting SASCPIC
81
82 Create and Edit a Profile
Appendix 1
Display A1.21 Maintain Profile Window
10 Click Add object.
You see the following display.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
83
Display A1.22 Maintain Profiles: Object Classes Window
11 Double-click AAAB Cross-application Authorization Objects.
Display A1.23 Maintain Profiles: List of Objects Window
12 Click the check box next to S_RFC, and then select Authorizations  Copy.
84 Create and Edit a Profile
Appendix 1
Display A1.24 Maintain Profile Window
13 In the Authorization column, click
corresponding to S_RFC.
A list of associated authorizations for the object S_RFC appears in the Restrictions
window.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.25 Restrictions Window
14 Double-click S_RFC_ALL.
You see the following display.
85
86 Create and Edit a Profile
Appendix 1
Display A1.26 Maintain Profile Window
15 Click the diskette icon to save the profile.
Figure A1.27 Maintain Profile Window
Restricting the RFC User Account for IT Resource Management Adapter for SAP
87
16 To activate the profile, select Profile  Activate.
Display A1.28 Activate Profile: Execution Screen Window
17 To activate execution, select Profile  Activate.
Associating the Profile with User Account
To associate the profile with a user account, complete the following steps:
1
In the SAP Easy Access window under User Maintenance, double-click Users.
As an alternative, you can enter transaction Code SU01 in the command bar at
the top of the SAP Easy Access Window.
88 Associating the Profile with User Account
Appendix 1
Figure A1.29 SAP Easy Access Window
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.30 User Maintenance: Initial Screen Window
2
In the User field, enter a unique user name. Click
.
89
90 Associating the Profile with User Account
Appendix 1
Display A1.31 Maintain User: Address
3
Fill in the Last name field, and then click Logon data.
4
Fill in Alias, Initial password, and Repeat password.
5
Click Profiles.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
Display A1.32 Maintain User: Profiles
6
In Profile column, click
. Enter ITRM in the Profile name field.
91
92 Associating the Profile with User Account
Appendix 1
Display A1:33 Entering Profile Name of ITRM
7
Click the diskette icon to save your changes.
Restricting the RFC User Account for IT Resource Management Adapter for SAP
93
Display A1.34 Maintain User: Profiles
Any attempt to access data other than performance data results in the following error
message in the SAS log:
Display A1.35 SAS Log
94 Associating the Profile with User Account
Appendix 1
Any attempt to read metadata results in the following error message in the SAS log:
Display A1.36 SAS Log
99
A P P E N D I X
2
The RFC Destination for the Hub
Overview ............................................................................................................................................................................. 99 RFC Connection to Another Machine ............................................................................................................................. 102 Overview
This appendix explains how an RFC destination is used to get data either directly or indirectly.
The following figure (also in Chapter 1) shows how data from SAP servers 2 and 3 is extracted
directly into SAS.
Figure A2.1 Solution Architecture
Data from SAP Server 1 is extracted indirectly using SAP Server 2.
100 Overview
Appendix 2
Note: A hub can retrieve data from other SAP servers only if they are of the same SAP threaded
kernel release.
SAP Server 2 is used as a hub to get data from SAP Server 1 using an SAP destination.
 The advantage of direct access is that there is no load on the hub.
 The advantage of indirect access is that you do not have to install any ABAP functions or
maintain a remote machine.
 The disadvantage of using a hub is that if the hub is down, then extractions from other
machines are not made.
Note: If there are no restrictions on installing ABAP functions on each machine, then you
should use direct access.
The following example shows an SAP ECC 6.0 (release 6.10) being used as an adapter gateway
server. The RFC destination for this adapter gateway server is the predefined NONE internal
connection.
Type SM59 on the command line to display the RFC destination. The Display and maintain
RFC destinations window appears. To display the internal connection properties for NONE,
double-click NONE.
The RFC Destination for the Hub
101
The RFC Destination NONE window appears. The properties for the RFC Destination NONE
are displayed. The following figure shows the Technical Settings tab.
The following figure shows the Logon & Security tab.
102 RFC Connection to Another Machine
Appendix 2
The following figure shows the Special Options tab.
RFC Connection to Another Machine
An RFC connection can be made from the hub to another machine. As a result, performance
data can be extracted from that machine without having to install any ABAP functions.
Note: If an internal connection to this machine already exists, reference the existing connection.
A new connection is not necessary.
1
Type SM59 on the command line to display the Configuration of RFC Connections. The RFC
connections window appears.
The RFC Destination for the Hub
2
103
To display the internal connection properties for TESTCRM, double-click TESTCRM.
104 RFC Connection to Another Machine
Appendix 2
The RFC Destination TESTCRM window appears.
Note: The Connection Type = 3. Enter the System Number; the system number is the
instance number of the child machine. Enter the Target Host; the target host is the IP address
of the other machine.
The following figure shows the Logon & Security tab.
The RFC Destination for the Hub
The following figure shows the Special Options tab.
The following figure shows the MDMP & Unicode tab.
105
106 RFC Connection to Another Machine
Appendix 2
107
A P P E N D I X
3
Terms and Statistics Files Duration
Terms and Definitions ..................................................................................................................................................... 107 Introduction.............................................................................................................................................................. 107 Front-End Network Time ........................................................................................................................................ 107 DBRequestTime........................................................................................................................................................ 107 Response Time .......................................................................................................................................................... 108 Statistics Files Duration ................................................................................................................................................. 108 Host Platforms ................................................................................................................................................................. 108 Terms and Definitions
Introduction
The following terms and their definitions are extracted from SAP notes.
Front-End Network Time
SAP measures time as starting when the request from the front-end system reaches the server.
Time ends when the final data package is sent from the server. During the transaction, several
communication steps might occur between the server and the front-end system. These are called
round trips.
During a round trip, the server transfers data for the controls to the front-end system. The user
context is rolled out. The time to do these two tasks is roll-wait time. The time line for every
round trip is measured on the server in GUI time. The influence of network performance and
front-end system performance on the SAP response time can be defined with the help of GUI
time.
The difference between the first time measurement (how SAP measures time) and the second
time measurement (SAP response time) is included as front-end network time. In other words, it
is the total network time for the first and the final communication steps between the front-end
system and the server. The front-end network time is not included in the GUI time.
DBRequestTime
DBRequestTime (database request time) is the time that it takes to process logical database
requests (calls to the SAP database interface).
108
Host Platforms
Appendix 3
Response Time
Response time is the total time used on the server, including database request time.
The response time of a dialog step is the time that it takes from the request of the dialog to the
application dispatcher to when the work is actually processed. The response time consists of
single values such as:
 CPU time
 load+gen time
 queue time
 database request time
All dialog steps that are initiated directly by the front-end user are evaluated. Automatic ABAP
functions or dialog steps of the SAPSYS user are not relevant.
The response time value, which measures overall system performance, is reported to
transaction RZ20. This transaction is executed every five minutes. The length of the run time to
report the response time depends on the number of users logged on and the number of dialog
steps.
Statistics Files Duration
As of SAP Release 4.6D (for application statistics: Base SAS 6.10), the threaded kernel starts a
statistics file on the hour. This procedure offers two advantages:
 Access to the statistics file is much faster.
 Updated statistics files are available.
Before SAP Release 4.6D, the collector deleted the statistics file if it was larger than a defined
size.
In the current release, the duration for storing the statistics files can be specified (for example,
48 hours). The collector deletes statistics files that are older than the specified time if all records
from the statistics file have been processed.
The duration should always be shorter than the value for the stat/max file. A stat/max file
defines the maximum number of statistics files that are allowed. When you reach the limit, the
threaded kernel overwrites the older statistics files.
A reasonable value for a stat/max file is 72 hours. If this value is set to 0, SAP works with one
statistics file only, as it did in releases before 4.6D.
When SAP is invoked, statistics files older than seven days are automatically deleted. In
addition, for each collector that runs, files older than the specified duration are deleted.
Host Platforms
You can find the list of host platforms supported by the SAS IT Resource Management solution
in the document that is available at http://support.sas.com/itrm.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising