Documente Academic
Documente Profesional
Documente Cultură
PUBLIC
qR8$9%[MlP Z.L):c)m&{
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.
You can find the latest version at the following location:
http://service.sap.com/instguides Database Upgrades SAP MaxDB
The following table provides an overview of the most important document changes.
Version
Date
Description
1.02
2012-04-17
1.01
2010-05-04
1.0
2009-12-14
Revised Version
Minor correction
Revised Version
Change to paths in Upgrading the SAP MaxDB Client Software.
Initial Version
2/34
PUBLIC
2012-04-17
Table of Contents
Chapter 1
1.1
1.2
1.2.1
1.2.2
1.2.3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Before You Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
More Information on SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . .
Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
2.1
2.2
2.3
2.4
2.5
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SAP MaxDB Isolated Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SAP System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Upgrade Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 3
3.1
3.2
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Preparing for an Upgrade with In-Place . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Preparing for an Upgrade with Patch Installation . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 4
4.1
4.2
4.3
Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing an Upgrade for In-Place . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing an Upgrade for Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading the SAP MaxDB Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
17
18
18
Chapter 5
5.1
5.2
5.3
5.4
Post-Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Post-Upgrade Steps After an In-Place Upgrade . . . . . . . . . . . . . . .
Updating the Database Software to the Current Release . . . . . . . . . . . . . . . . .
Installing or Upgrading Database Studio for SAP MaxDB . . . . . . . . . . . . . . . . .
Secure Sockets Layer Protocol for Database Server
Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the SAP Cryptographic Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Generating the Personal Security Environment . . . . . . . . . . . . . . . . . . . . . . . .
21
21
22
22
5.4.1
5.4.2
2012-04-17
PUBLIC
5
5
5
6
6
6
24
25
26
3/34
Chapter 6
6.1
6.2
4/34
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Database Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Log Files for Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
PUBLIC
2012-04-17
Introduction
1.1
New Features
1 Introduction
This documentation explains how to upgrade the SAP MaxDB database for the SAP system:
Zwy2 From at least SAP Max DB version 7.5
Zwy2 To SAP MaxDB version 7.8
CAUTION
Make sure you have the latest version of this document. See the version number on the front
page. You can always find the latest version at:
http://service.sap.com/instguides Database Upgrades SAP MaxDB
Implementation Considerations
Zwy2 Make sure that you read the relevant SAP Notes [page 6] before beginning the upgrade. These notes
contain the most recent information about the upgrade, as well as corrections to the
documentation.
Zwy2 For more information about SAP MaxDB, see the following:
http://help.sap.com SAP NetWeaver SAP MaxDB
For the most up-to-date information about the SAP MaxDB documentation and where to find it,
see SAP Note 767598.
For more information about the most important enhancements and features for version 7.8, see SAP
Note 1364181.
NOTE
As of SAP MaxDB version 7.6, support packages and patch levels have been introduced. For more
information, see SAP Note 820824.
As of SAP MaxDB version 7.8, the installation has changed. For more information, see SAP MaxDB Isolated
Installation [page 9].
2012-04-17
PUBLIC
5/34
Introduction
1.2
Subject
1353266
820824
498036
668849
829408
CAUTION
Before you begin the upgrade, always make sure that you read the first SAP Note listed above,
1353266, because it contains up-to-date information essential to the upgrade, including corrections
not contained in this upgrade documentation.
This note also contains the valid DVD numbers for SAP MaxDB 7.8.
Address
http://service.sap.com/instguides
Database Upgrades
SAP
MaxDB
Product Availability Matrix (PAM)
SAP Notes
Support Packages and patches
http://service.sap.com/pam
http://service.sap.com/notes
http://service.sap.com/patches
MaxDB
MAXDB GUI
COMPONENTS/TOOLS
6/34
PUBLIC
2012-04-17
Introduction
1.2
Always enter the user name <sapsid>adm in lowercase for the standalone database server.
Support Packages and patches
For more information, see:
http://service.sap.com/patches
Meaning
ONLINE
ADMIN
OFFLINE
2012-04-17
PUBLIC
7/34
Planning
2.1
2 Planning
Prerequisites
You have checked the SAP Notes for the upgrade [page 6].
Process Flow
Variable Name
Properties
Shared
Global
programs path
GlobalProgPath
/sapdb/programs
Global data
path
GlobalDataPath
Installation
path
InstallationPat
2012-04-17
/sapdb/data
PUBLIC
Stored Components
9/34
Planning
2.2
Database Requirements
Path Name
Variable Name
Properties
Shared
Private data
path
PrivateDataPath
Stored Components
/sapdb/<DBSID>/db
No
As a consequence of the new installation principles, higher versions can no longer unintentionally
update existing software from a previous version.
Since more than one client can be installed on an individual computer, as of SAP MaxDB 7.8 each
application server has its own SAP MaxDB runtime (client software installation). This lets you update
any client installation without affecting any other client installation. For example, you can now update
the SAP MaxDB runtime of an individual application server without affecting a second application
server on the same computer. Likewise, you can upgrade a database together with its software to a
higher version without affecting another database on this computer and its current connections. You
also can run test systems and production systems on the same computer. The creation of system copies
in SAP systems is now much easier, since a private data path is used for the SAP MaxDB software.
CAUTION
There is still only one database instance allowed for each software installation.
As part of the upgrade planning [page 9], make sure that your database meets the following requirements
before you start the upgrade:
/h The database is ready to run.
/h The system tables have been loaded at least once for the existing instance.
10/34
PUBLIC
2012-04-17
Planning
2.3
g[? The database instance is the only instance that refers to the installation path of the software version
that you want to upgrade.
g[? The database parameters of the database instance that you want to upgrade have not changed
since the last restart.
g[? The database start version that is, before you start the upgrade is at least 7.5
CAUTION
If the database start version does not meet the above requirement, you must upgrade to this
version before starting the upgrade
For more information about how to upgrade to the correct database start version, see SAP
Note 498036.
As part of the upgrade planning [page 9], make sure that your operating system meets the following
requirements before you start the upgrade:
Operating System
Supported Version
AIX
HP-UX
Linux
2012-04-17
PUBLIC
11/34
Planning
2.4
Operating System
Supported Version
RedHat EL 5 (PPC64)
9 (Sparc, 64-bit)
10 (Sparc, 64-bit)
10 (X64, 64-bit)
SUN Solaris
For the most up-to-date SAP MaxDB-specific release information on the database and operating system
of your product, including required patch levels, check the SAP Product Availability Matrix (PAM) at:
http://service.sap.com/pam
There you can also find additional information on required operating system patch levels and patches
for C++ RTE.
g"fKyZ
eJGmO^ {e
As of SAP MaxDB version 7.6, we no longer support the operating system HP Tru64 UNIX.
g"nyZ"
iJ)m^
As part of the upgrade planning [page 9], make sure that your SAP system meets the following requirements
before you start the upgrade:
sBf SAP MaxDB Version 7.8 is initially released for SAP Basis Release 7.2, and subsequent releases.
sBf For previous SAP releases, SAP Note 1353266 shows with reference to the Product Availability
Matrix (PAM) whether an official downward-compatible release exists for SAP products or
whether a special release has been granted for the SAP upgrade start release.
For more information, see the Product Availability Matrix (PAM) at:
http://service.sap.com/pam
You can also find the information in the above SAP Notes at:
http://service.sap.com/notes
As part of the upgrade planning [page 9], you choose an upgrade strategy, which depends on your database
start version:
Your Database
Start Version
7.5 or later
12/34
In-Place Upgrade
With an In-Place upgrade, you upgrade the database instance and the database
software.
The start version of the database software must be Version 7.5 or later and the
target version must be 7.8 or later
PUBLIC
2012-04-17
Planning
2.5
Upgrade Strategy
Your Database
Start Version
7.8
2012-04-17
PUBLIC
13/34
Preparation
3.1
3 Preparation
Prerequisites
1.
2.
3.
4.
5.
Make sure that the operational state [page 6] of your database is ONLINE.
In case you need to recover the database, make sure that you have an installation kit with the start
version of the database software. This means that you must have database Version 7.5, 7.6, or 7.7
with the same or a higher build.
Check the required free space in the database. You need at least 15% free space.
Check that there are no bad indexes in the database, using the Database Studio or the Database
Manager GUI.
For more information about how to remove bad indexes, see SAP Note 566883.
Shut down the SAP system using the command stopsap or if you have Windows platforms in
your SAP system the SAP Microsoft Management Console (SAP MMC).
To use stopsap, enter the following command as user <sapsid>adm:
stopsap <system ID> <system number> <SAPDIAHOST>
NOTE
<SAPDIAHOST> refers to the instance ID of the additional application server instance.
2012-04-17
PUBLIC
15/34
Preparation
3.2
6.
7.
8.
CAUTION
If you do not have a backup, you might lose data in the event of a database failure that
requires database recovery.
After the backup, put the database in operational state ONLINE before the upgrade.
9. Exit the Database Manager CLI, GUI, or Database Studio and any other database applications that
are running.
10. If you need to upgrade your operating system do this now.
1.
2.
Make sure that the operational state [page 6] of your database is ONLINE, ADMIN, or OFFLINE without
any errors.
Stop application software such as Database Studio, Database Manager CLI or GUI and the
database that you intend to upgrade, so that you can run a full backup. In this case, you do not
need to stop the X server.
CAUTION
The upgrade tool does not check whether a database backup is available.
Therefore, always perform a database backup before the upgrade, so that you can recover
the database in the event of data loss.
16/34
PUBLIC
2012-04-17
Upgrade Process
4.1
4 Upgrade Process
Prerequisites
Depending on the size of your database catalog, the upgrade can take a long time to finish,
especially database migration.
CAUTION
1.
2.
3.
4.
2012-04-17
PUBLIC
17/34
Upgrade Process
4.2
Result
When you see the message confirming that the upgrade has completed successfully, this means that:
@? The database instance and its software are now upgraded.
@? The database instance is in the operational state ONLINE.
@? The isolated database client software (installation name CL_<SAPSID>) is now installed in the
directory /sapdb/clients/<SAPSID>. This is only valid for database servers where associated SAP
application software is installed.
@? The DBENV scripts (.dbenv_<hostname>.csh, .dbenv_<hostname>.sh, dbenv.csh,
and .dbenv.sh) are now up-to-date in the home directories of the SAP system administrator
(<sapsid>adm) and the SAP database administrator (sqd<sid>). This is only valid for database
servers where associated SAP application software is installed.
@? The upgrade is flagged as complete.
1.
2.
3.
4.
Result
When you see the message confirming that the upgrade has completed successfully, this means that:
@? The database software is now upgraded.
@? The database instance is now in the operational state ONLINE.
@? The upgrade is flagged as complete.
18/34
PUBLIC
2012-04-17
Upgrade Process
4.3
Prerequisites
1.
2.
3.
4.
5.
Make sure that you log on from the beginning, because the environment of <sapsid>adm
and sqd<dbsid> has been changed.
Restart the SAP system using the commands stopsap and startsap or if you have Windows
platforms in your SAP system the SAP Microsoft Management Console (SAP MMC).
To use the stopsap and startsap commands, enter the following commands as user
<sapsid>adm:
stopsap <system ID> <system number> <SAPDIAHOST>
startsap <system ID> <system number> <SAPDIAHOST>
NOTE
<SAPDIAHOST> refers to the instance ID of the additional application server instance.
6.
2012-04-17
PUBLIC
19/34
Post-Upgrade
5.1
5 Post-Upgrade
Prerequisites
1.
Perform a complete backup of the database data so that you can recover the new database if
necessary.
CAUTION
2.
We do not guarantee that you can recover the database using backups from different versions
of the database.
Log on again as the <sapsid>adm or sqd<dbsid> user, or both.
NOTE
3.
Make sure that you log on from the beginning, because the environment of <sapsid>adm
and sqd<dbsid> has been changed.
This step applies only to SAP installations that include AS Java (SAP J2EE Engine):
Obtain the JDBC driver as follows:
/sapdb/clients/<SAPSID>/runtime/jar
NOTE
The location of the driver has changed compared to previous versions of SAP MaxDB. This
is the old location of the JDBC driver, before SAP MaxDB version 7.8:
/sapdb/programs/runtime/jar
2012-04-17
PUBLIC
21/34
Post-Upgrade
5.2
4.
SAP Note 867976 describes how to update the location of the JDBC driver for the Java application
server.
Start the SAP system using the command startsap or if you have Windows platforms in your
SAP system the SAP Microsoft Management Console (SAP MMC).
To use startsap, enter the following command as user <sapsid>adm:
startsap <system ID> <system number> <SAPDIAHOST>
NOTE
<SAPDIAHOST> refers to the instance ID of the additional application server instance.
5.
6.
Only deinstall the old legacy SAP MaxDB client software if you are completely sure that you
do not need it.
Log in as user root and execute the following command
/sapdb/programs/bin/sdbuninst -i Legacy
1.
22/34
PUBLIC
2012-04-17
Post-Upgrade
5.3
For more information about Database Studio, see one of the following:
y http://maxdb.sap.com/doc/7_8/default.htm Tools Database Studio
y http://www.sdn.sap.com/irj/sdn/maxdb SAP MaxDB Knowledge Center The Complete SAP
MaxDB Documentation Set SAP MaxDB 7.8 Library Tools Database Studio
NOTE
Database Studio replaces Database Manager GUI and SQL Studio, which were available in previous
releases.
For up-to-date information on installing Database Studio, see SAP note 1360996.
Prerequisites
y You can install Database Studio on Linux or Windows in your network, even if your database runs
on a different operating system. You can then remotely administer the database on a different host.
The instructions below refer mainly to the Windows version.
NOTE
To run Database Studio on Linux, you need to meet the requirements for the SAP MaxDB
database server.
y Your PC must meet the following minimum requirements:
y Software requirements:
Operating System Requirements for Database Studio
Operating System
Version
Windows XP
Windows 2008
Windows 2008 R2
Windows Vista
Windows 7
y Hardware requirements:
y RAM: 512 MB ( recommended RAM: 1 GB)
y Processor speed: 1.5 GHz
y Free disk space: 200 MB
y Monitor: 1024x768 pixels, 256 colors
y You can obtain the required files from one of the following:
y The DVD for the SAP MaxDB RDBMS or SAP liveCache
y By downloading from:
service.sap.com/patches Database Patches MaxDB MAXDB GUI COMPONENTS/
TOOLS MAXDB DATABASE STUDIO 7.8
y You need Java version 5 (also known as 1.5) or higher.
To check your Java version, enter the following command:
2012-04-17
PUBLIC
23/34
Post-Upgrade
5.4
1.
Start the installation or upgrade as follows (the paths shown are for the 32-bit installation):
If you are using the SAP MaxDB RDBMS DVD:
<DVD>/DATA_UNITS/MAXDB_LINUX_I386/DBSTUDIO/SDBSETUP
2.
3.
4.
5.
If you are using the downloaded files, simply execute the downloaded SDBSETUP file.
The Installation Manager starts.
Choose Start Installation/Upgrade and then Custom.
You see a list of the components to be installed.
Deselect all components except Database Studio.
Choose Install.
The installation manager installs Database Studio.
If you are prompted to restart your computer after the installation, make sure that you first shut
down any databases that are running.
More Information
For more information about Database Studio, including troubleshooting, see SAP Note 1097311.
There is a performance cost for SSL since the data has to be encrypted, which requires time and
processing power.
To use SSL you need to:
1. Install the SAP cryptographic library [page 25] on the client host and on the server host machines
2. Generate the Personal Security Environment [page 26] (PSE) on the server (SSL Server PSE) and on the
client (SSL Client PSE).
24/34
PUBLIC
2012-04-17
Post-Upgrade
5.4
You might have already installed the SAP cryptographic library when prompted to do so by
SAPinst during the installation. If so, you do not need to perform this procedure.
The installation package sapcrypto.car consists of the following:
6 SAP Cryptographic Library: libsapcrypto.so/sl
6 License ticket: ticket
6 Configuration tool: sapgenpse.exe
You use the configuration tool to generate key pairs and PSEs.
CAUTION
The SAP Cryptographic Library is subject to German export regulations and might not be available
to some customers. In addition, the library might be subject to the local regulations of your
country. These regulations might further restrict import, use, and export or re-export of
cryptographic software.
For more information, contact your local SAP representative.
Prerequisites
Download the appropriate SAP Cryptographic Library installation package for your operating system
from http://service.sap.com/swdc.
Procedure
1.
Unpack the installation package for the SAP Cryptographic Library using sapcar.exe, which you
can find for example on your Installation Master DVD, using the following command:
car -xvf SAPCRYPTO.CAR
NOTE
2.
The remainder of the procedure (as described below) does not apply to client applications
such as SQL Studio, which do not recognize a global directory. In this case, you must copy
the SAPCRYPTO installation package to the installation directory of the application. In this
directory you need to create a directory sec, into which you copy the ticket file.
Copy the sapcrypto library to the lib subdirectory of the global program directory.
You can find the value of the global program directory by entering the following command:
sdbconfig IndepPrograms
2012-04-17
PUBLIC
25/34
Post-Upgrade
5.4
3.
4.
5.
Make sure that the directory and the files that the sec directory contains including the ticket
file and the SSL Server PSE belong to the user lcown and the group lcadm, and that the rights are
restricted to 0600.
Result
The system copies the SAP Cryptographic Library to the application server and correctly configures
the environment so that the server can find the library at runtime.
You need to know the naming convention for the distinguished name of the database server. The
syntax of the distinguished name, which you enter in the procedure below, depends on the
Certification Authority (CA) that you are using.
1.
2.
26/34
PUBLIC
2012-04-17
Post-Upgrade
5.4
3.
Create an SSL Server PSE, SDBSSLS.pse, and generate a certificate request file, certreq, in the
directory defined by SECUDIR (see previous step):
sapgenpse gen_pse -v -r <SECUDIR>\certreq -p SDBSSLS.pse <your distinguised name>
4.
5.
For each database server that uses a server-specific PSE, you must set up a unique certificate request.
If you are using a valid system-wide SSL Server PSE, you only need to set up a single certificate
request for all servers.
Send the certificate request to the CA for signing. You can either send it to the SAP CA or to another
CA.
You must make sure that the CA offers a certificate corresponding to the PKCS#7 certificate chain
format. Thawte CA at http://www.thawte.com offers a suitable certificate, either SSL Chained CA
Cert or PKCS#7 certificate chain format.
The CA validates the information contained in the certificate request, according to its own
guidelines, and sends a reply containing the public key certificate.
After you have received the reply from the CA, make sure that the contents of the certificate
request have not been destroyed during download.
For example, if you requested the certificate on a UNIX system and stored it on a Windows front
end, the formatting (that is, line indents and line breaks) is affected.
To check the contents, open the certificate request with a text editor (such as Notepad) and repair
the line indents and the line breaks.
EXAMPLE
6.
You have generated the SSL Server PSE. You can now start the XServer as usual (if it is already
running, you must stop and restart it).
2012-04-17
PUBLIC
27/34
Post-Upgrade
5.4
7.
To check whether the SSL functionality is working correctly, view the trace file niserver_<local
computer name>.trace in the <global data>\wrk directory.
1.
2.
3.
4.
5.
6.
You can check whether to trust the database server certificate. The client certificate is not affected
by this.
Start the import with this command:
x_ping -n <servermode> -i[import]
7.
To administer the PSE, use the configuration tool sapgenpse. For more information, enter the
following command:
sapgenpse -h
NOTE
For applications such as SQL Studio replace the global data or global program in the above
description with the relevant installation directory.
28/34
PUBLIC
2012-04-17
Additional Information
6.1
6 Additional Information
As of SAP MaxDB version 7.8, with the introduction of the isolated installation, the database
directory structure in SAP installations has changed. This section describes the new structure.
#q Global programs path: GlobalProgPath
This area contains all services that are only allowed to exist once per computer and are downward
compatible (for example, installation tools and the global listener, sdbgloballistener). Therefore,
only programs of the most recent installed version exist here.
You can check the path for GlobalProgPath with the following dbmcli command:
dbmcli dbm_getpath GlobalProgPath
2012-04-17
PUBLIC
29/34
Additional Information
6.2
You can display instance names and the associated InstallationPath on a computer with the
following dbmcli command:
dbmcli db_enum
You can display the InstallationPath of installed software on a computer with the following
dbmcli command:
dbmcli inst_enum
If the directory <independent_data_path> is not known at the time of failure, the log is written to the
current directory.
NOTE
If you are updating the SAP MaxDB client software, you can find the log files here instead:
/var/tmp/SDBINST.log
30/34
PUBLIC
2012-04-17
Typographic Conventions
Example
Description
<Example>
Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Arrows separating the parts of a navigation path, for example, menu options
Example
Example
Example
Example
http://www.sap.com
/example
123456
Example
Example
EXAMPLE
EXAMPLE
2012-04-17
PUBLIC
31/34
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
32/34
PUBLIC
2012-04-17
Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other
countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
(SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or
altered in any way.
Documentation in the SAP Service Marketplace
2012-04-17
PUBLIC
33/34
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com