sog_saperp60_sr3

107
Solution Operation Guide – Support Release 3 SAP ERP 6.0 powered by SAP NetWeaver 7.0 Using SAP ® ECC 6.0 Document Version 7.00 – March 26, 2009

Upload: ludenskz

Post on 28-Aug-2014

88 views

Category:

Documents


1 download

DESCRIPTION

SAP Solution Operations Guide for ERP 6.0 SR3

TRANSCRIPT

Page 1: SOG_SAPERP60_SR3

Solution Operation Guide – Support Release 3

SAP ERP 6.0powered by SAPNetWeaver 7.0Using SAP® ECC 6.0

Document Version 7.00 – March 26, 2009

Page 2: SOG_SAPERP60_SR3

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of theOpen Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, SAP, SAP.com, xApps, xApp, SAP NetWeaver, and otherSAP products and services mentioned herein as well as their respectivelogos are trademarks or registered trademarks of SAP AG in Germanyand in several other countries all over the world. All other product andservice names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informationalpurposes only. National product specifications may vary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following Internet address:service.sap.com/instguides

In order to make your document available under this alias, contactGBU AI.

SAP AGNeurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

Page 3: SOG_SAPERP60_SR3

Typographic ConventionsType Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, titles ofgraphics and tables

EXAMPLETEXT

Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surroundedby body text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLETEXT

Keys on the keyboard, forexample, function keys (suchas F2) or the ENTER key.

IconsIcon Meaning

Caution

Example

Note

Recommendation

Syntax

Page 4: SOG_SAPERP60_SR3

Solution Operation Guide for SAP ERP 6.0

Dezember 2009 4

Contents1 Getting Started ......................................................................... 7

1.1 Global Definitions ................................................................... 81.2 Further Information ................................................................. 8

1.2.1 General SAP Notes ..................................................................... 81.2.2 General Web Links ..................................................................... 9

1.3 History of Changes ............................................................... 131.4 The Main SAP Documentation Types.................................. 14

1.4.1 Cross-Phase Documentation .................................................. 141.4.2 Implementation ......................................................................... 151.4.3 Production Operation............................................................... 161.4.4 Upgrade ..................................................................................... 16

2 Technical System Landscape .............................................. 172.1 Landscape Description ......................................................... 192.2 Example: Communication Structure for SAP LearningSolution ............................................................................................ 302.3 Further Information ............................................................... 31

2.3.1 Technical System Landscape SAP Notes .............................. 312.3.2 Technical System Landscape Web Links ............................... 33

2.4 SAP Solution Manager .......................................................... 353 Monitoring .............................................................................. 35

3.1 Monitoring Using SAP Solution Manager ........................... 363.1.1 SAP Solution Manager Diagnostics ........................................ 363.1.2 Further Information .................................................................. 37

3.1.2.1 SAP Solution Manager SAP Notes .......................................................... 373.1.2.2 SAP Solution Manager Web Links ........................................................... 373.1.2.3 SAP Solution Manager Documents ......................................................... 38

3.2 Monitoring Using the Alert Monitor ..................................... 383.3 CCMS Monitoring Architecture ............................................ 39

3.3.1 Monitoring Architecture Tools ................................................ 393.4 Scenario Alert Monitoring .................................................... 42

3.4.1 SAP E-Commerce in SAP ERP 6.0 .......................................... 423.4.2 Example: Configuring GRMG Monitoring for the SAPLearning Solution - Content Player ..................................................... 43

3.5 Detailed Monitoring ............................................................... 453.5.1 Monitoring of SAP ABAP Components .................................. 45

3.5.1.1 Detailed Monitoring of SAP ERP Components ....................................... 463.5.2 Database Monitoring ................................................................ 483.5.3 Monitoring of SAP Java Components .................................... 50

3.5.3.1 Java Monitoring and Management .......................................................... 503.5.3.2 Detailed Monitoring for SAP ERP 6.0 Java Components ....................... 50

3.6 Further Information ............................................................... 51

Page 5: SOG_SAPERP60_SR3

Solution Operation Guide for SAP ERP 6.0

5 Dezember 2009

3.6.1 Monitoring SAP Notes.............................................................. 513.6.2 Monitoring Web Links .............................................................. 523.6.3 Monitoring Documents ............................................................ 53

4 Management of SAP Technology ......................................... 544.1 Starting and Stopping ........................................................... 54

4.1.1 Detailed Starting and Stopping ............................................... 544.1.1.1 Example: SAP Enterprise Portal .............................................................. 554.1.1.2 Starting and Stopping SAP Notes ........................................................... 564.1.1.3 Starting and Stopping Web Links ............................................................ 564.1.1.4 Starting and Stopping Documents .......................................................... 59

4.2 Backup and Recovery ........................................................... 604.2.1 Detailed Backup and Recovery ............................................... 62

4.2.1.1 Operating System, Software and Configuration Data ............... 664.2.1.2 Database ................................................................................................... 674.2.1.3 SAP ERP 6.0 ABAP Components ............................................................ 674.2.1.4 SAP ERP 6.0 Additional Components ..................................................... 69

4.2.2 Further Information .................................................................. 694.2.2.1 Backup and Recovery SAP Notes ........................................................... 694.2.2.2 Backup and Recovery Web Links ............................................................ 704.2.2.3 Backup and Recovery Documents .......................................................... 72

4.3 System Copy ......................................................................... 724.3.1 Detailed System Copy .............................................................. 74

4.3.1.1 SAP ERP 6.0 ABAP Components ............................................................ 744.3.1.2 SAP ERP 6.0 JAVA Components ............................................................. 75

4.3.2 Further Information .................................................................. 754.3.2.1 System Copy SAP Notes .......................................................................... 754.3.2.2 System Copy Web Links .......................................................................... 764.3.2.3 System Copy Documents ........................................................................ 79

4.4 Periodic tasks ........................................................................ 794.5 SAP User Management ......................................................... 82

4.5.1 Detailed SAP User Management ............................................. 82User Management – Roles and Profiles ................................................................. 83User Management Tool ........................................................................................... 834.5.1.1 SAP ERP 6.0 ABAP Components ............................................................ 894.5.1.2 SAP ERP 6.0 JAVA Components ............................................................. 894.5.1.3 SAP ERP 6.0 Additional Components ..................................................... 89

4.5.2 Further Information .................................................................. 904.5.2.1 SAP User Management SAP Notes.......................................................... 904.5.2.2 SAP User Management Web Links .......................................................... 904.5.2.3 SAP User Management Documents ........................................................ 93

4.6 High Availability .................................................................... 934.6.1 Downtimes ................................................................................ 94

4.6.1.1 Planned Downtimes ................................................................................. 944.6.1.2 Unplanned Downtimes ............................................................................. 96

4.6.2 Detailed High Availability ......................................................... 974.6.3 Further Information .................................................................. 97

4.6.3.1 High Availability SAP Notes..................................................................... 974.6.3.2 High Availability Web Links ..................................................................... 984.6.3.3 High Availability Documents ................................................................... 99

Page 6: SOG_SAPERP60_SR3

Solution Operation Guide for SAP ERP 6.0

Dezember 2009 6

4.7 Archiving ................................................................................ 994.7.1 Detailed Archiving .................................................................. 100

4.7.1.1 SAP ERP 6.0 ABAP Components .......................................................... 1014.7.2 Further Information ................................................................ 102

4.7.2.1 Archiving Web Links .............................................................................. 1024.7.2.2 Archiving Documents ............................................................................ 102

5 Software Change Management .......................................... 1035.1 Software Change Management SAP Notes ...................... 1035.2 Software Change Management Web Links ....................... 1035.3 Software Change Management Documents ..................... 105

6 Glossary ................................................................................ 105

Page 7: SOG_SAPERP60_SR3

Getting Started

7 Dezember 2009

1 Getting StartedThis guide does not replace the daily operations handbook that we recommend customerscreate for their specific production operations.

About this GuideThis guide provides a starting point to optimally maintain and run your SAP applications. Designing,implementing, and running your SAP application at peak performance, around the clock, has neverbeen more vital for your business success than now.This document provides you with an overview of technical runtime scenarios, which result fromsetting up the corresponding business scenarios. For example, in a business self-service scenario,the technical runtime scenario starts by opening the browser. The browser displays data generatedby Web Dynpro and SAP Enterprise Portal, which runs on SAP NetWeaver Java runtime, and thenretrieves the business-relevant data from an SAP back-end system.Unlike SAP ERP 6.0 systems, SAP Business Suite uses several SAP components to implementcross-system processes. Data is no longer held centrally in a single SAP system; instead, it isdistributed between several SAP components. Therefore, to ensure the operation of such technicalscenarios, you must understand the different steps and dependencies.This guide provides references to the documentation required for such tasks, so you will sometimesneed to refer to other documentation, such as the Master Guide, the Technical InfrastructureGuide, and SAP Library documentation. This document also describes specific tasks and lists thetools that you can use to implement them. The four main sections of this document are:

Technical System Landscape: This section provides an overview of the architecture ofthe components in SAP ERP 6.0

Monitoring of SAP ERP 6.0: This section describes the standard and specific monitorsfor different components and provides you with information about necessary tasks fordetailed monitoring.

Managing of SAP Technology: This section describes related topics on the SAP ERP6.0 application level, such as starting and stopping, backup and restore, and so on.

Software Change Management: This section summarizes the two areas of transportchange management and software maintenance.

Target AudienceThis documentation contains both high-level information on a application and business processlevel as well as very detailed technical information. It is therefore intended for the followingaudiences:

Decision makers SAP consultants SAP system administrators with operating system, database, and SAP system knowledge

Page 8: SOG_SAPERP60_SR3

Getting Started

Dezember 2009 8

1.1 Global DefinitionsSAP Business Suite: ApplicationsApplications of the SAP Business Suite represent a market view of groups of related businessscenarios. The delivery of an application contains SAP components, which are essential forimplementing all application-related business scenarios, processes and functions. Implementationknowledge is included with each application.

Business Scenario:From a microeconomic perspective, a business scenario is a cycle, which consists of severaldifferent interconnected logical processes in time. Typically, a business scenario includes severalcompany departments and involves other business partners. From a technical point of view, abusiness scenario needs at least one SAP application component (SAP ECC, SAP SCM, or others)for each cycle and possibly other third-party systems. A business scenario is a unit, which can beimplemented separately and reflects the customer’s prospective course of business.

Component:A component is the smallest individual unit within the application development lifecycle;components are separately produced, delivered, installed and maintained.

1.2 Further InformationThis chapter includes additional information, such as SAP Notes, web links, and a list of relateddocuments.Not all important facts that you should take into account in the planning phase of your installationare fully described in this document. As your enterprise makes final preparations to begin the actualimplementation, SAP recommends that you familiarize yourself with the following sources ofinformation, available in SAP Service Marketplace.

1.2.1 General SAP NotesSAP Notes are available on SAP Service Marketplace at service.sap.com/notes.

Check the SAP Service Marketplace regularly to see which SAP Notes are available for theSolution Operations Guide.

List of General SAP Notes

SAP NoteNumber

Title Description

855534 Embedded NetWeaver Components inERP

Contains installation information

701097 SAP NetWeaver '04 Documentation Provides details on documentationerrors

852008 Release Restrictions for SAPNetWeaver 2004s

Provides information on releaserestrictions for the Basis components

845780 Master Guide SAP ERP 6.0 -changes/enhancements

Describes the Software LifecycleManager

852235 Release Restrictions for SAP ERP 6.0 Contains information on releaseplanning

852008 Release Restrictions for SAPNetWeaver 2004s

Describes the release restrictions forthe Basis component

Page 9: SOG_SAPERP60_SR3

Getting Started

9 Dezember 2009

1.2.2 General Web Links

Check SAP Help Portal at help.sap.com and SAP Service Marketplace atservice.sap.com regularly for the following web links.

Documentation Links – SAP Service MarketplaceYou can find the following documentation on SAP Service Marketplace at service.sap.com.

Type ofInformation

Description Quick Link/ Path

SAP ERP 6.0generalinformation

Information aboutbusiness and technicalaspects of SAPEnterprise ResourcePlanning including news,services, events, demos,education, andworkshops

service.sap.com/erp

SAP ERP 6.0installation andupgrade

Comprehensiveinformation about theinstallation and upgradeof SAP ERP 6.0

service.sap.com/erp-inst

SAP ERP 6.0upgrade

Tailored information tofacilitate the preparationof the upgrade decisionsand the execution of theupgrade project

service.sap.com/erp-upgrade

SAP ERP 6.0Master Guide

Detailed informationabout the technicalsystem landscape ofSAP ERP 6.0

service.sap.com/instguides SAPBusiness Suite Applications SAP ERP 6.0

SAP ERP 6.0

SAP ERP 6.0SolutionOperation Guide

Detailed information howyou can operate yourSAP ERP 6.0 systemlandscape

service.sap.com/instguides SAPBusiness Suite Applications SAP ERP 6.0

SAP ERP 6.0

SAP NetWeavergeneralinformation

Information about theapplication andintegration platform

service.sap.com/netweaver

SAP NetWeaver700 releaseinformation

Details about SAPNetWeaver Release 700

service.sap.com/instguidesNW700

SAP NetWeaver700 installation

Installation informationincluding the MasterGuide, TechnicalInfrastructure Guide, andInstallation guides

service.sap.com/installNW700

SAP NetWeaver700 upgrade

Upgrade information,including the UpgradeMaster Guide and

service.sap.com/upgradeNW700

Page 10: SOG_SAPERP60_SR3

Getting Started

Dezember 2009 10

Type ofInformation

Description Quick Link/ Path

Upgrade Guides

SAP NetWeaver700 maintenance

Maintenance information,including the SupportPackage Guides

service.sap.com/MaintenanceNW700

SAP Notes forSAP NetWeaver700

SAP Notes, includingSAP Notes specific toNW 700 installation,upgrade, andimplementation

service.sap.com/SAPNotesNW700

SAP ReleaseStrategy

Release andmaintenance strategy ofSAP

service.sap.com/releasestrategy

SAP BestPractices

Comprehensiveinformation on SAPBusiness SuiteApplications that areaffordable, simple tounderstand, and quicklyimplemented

service.sap.com/bestpractices

Productavailability matrix(PAM)

Quick reference totechnical and releaseplanning information onSAP components

You will find informationon the availability of SAPcomponent releases andmaintenance end dates,as well as releaseinformation based onlanguages, countryversions, DB-platforms,JSE-platforms and so on.

service.sap.com/pam

Hardware sizing Detailed informationabout the calculation ofhardware, includingaccess to the SAP QuickSizer

service.sap.com/sizing

Page 11: SOG_SAPERP60_SR3

Getting Started

11 Dezember 2009

Type ofInformation

Description Quick Link/ Path

Securityinformation

Information on thesecurity infrastructure ofSAP NetWeaver

SAP deliverscomprehensive securitytechnologies to protectthe heterogeneousenvironments of the SAPBusiness Suite.Combined withspecialized partnersolutions, it makes theSAP Business Suite asecure place to dobusiness. In this location,you will finddocumentation, guides,best practices, and toolsfor SAP NetWeaverSecurity.

service.sap.com/security

Security guides Guidelines andrecommendationspertaining to system andnetwork security

service.sap.com/securityguides

Platform andtechnology-related topics

Overview of platform andtechnology-related topics

service.sap.com/platforms

High Availabilitydetails

Information about highavailability aspects withSAP solutions

service.sap.com/ha

Unicodeinformation

Information aboutsupport for multiple local-language characters

service.sap.com/unicode

SAP installation Installation and upgradeinformation

service.sap.com/installation

SAP SolutionManager

Information on SAPSolution Manager

service.sap.com/solutionmanager

Systemadministration

Comprehensiveinformation on technicalinfrastructure issues andnetwork integration

service.sap.com/sysadmin

Support package(SP) stacks

Information on SPstacks, which are sets ofsupport packages andpatches for therespective productversion that must beused in the givencombination

service.sap.com/sp-stacks

Page 12: SOG_SAPERP60_SR3

Getting Started

Dezember 2009 12

Type ofInformation

Description Quick Link/ Path

Softwaredistributioncentre

A software center thatallows you to obtain SAPsoftware electronically bydownloading packages.You can also order CDsand DVDs. You haveaccess to the entiresoftware portfolio of SAPbased on your licenses.

Please note that allcorrective softwarepackages, includingSupport Packages(Stacks) for SAPNetWeaver 700 andsubsequent versions, aswell as all applicationswhich are based on thissoftware (including SAPBusiness Suite 2005),released after April 2,2007, will be availableexclusively through theMaintenance Optimizerin SAP Solution Manager

service.sap.com/swdc

SAP NetweaverBusinessIntelligence(BI)

Information on SAPNetweaver BusinessIntelligence

service.sap.com/bi

SAP StrategicEnterpriseManagement(SEM)

Details about SAPStrategic EnterpriseManagement

service.sap.com/sem

SAP SupplierRelationshipManagement(SRM)

Information on SAPSupplier RelationshipManagement

service.sap.com/srm

SAP ExchangeInfrastructure

Details about theExchange Infrastructure

service.sap.com/xi

SAP EnterprisePortal

Information on SAPEnterprise Portal

service.sap.com/nw-ep

SAP ProductLifecycleManagement

Information on SAPProduct LifecycleManagement

service.sap.com/plm

SAP GUI Information on differentmembers of SAP GUIfamily

service.sap.com/sapgui

Page 13: SOG_SAPERP60_SR3

Getting Started

13 Dezember 2009

Documentation Links – SAP Help PortalYou can find the following documentation on SAP Help Portal at help.sap.com.

Type of Information Description Path

SAP NetWeaver Help Documentationabout SAPNetWeaver

help.sap.com SAP NetWeaver

SAP Technical OperationsManual

Information tooperate yourSAP NetWeaveror SAP ERP 6.0system

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAPNetWeaver 7.0 (2004s) KnowledgeCenter Technical Operations Manual

Solution Manager Documentationon SolutionManager

help.sap.com SAP Solution Manager

SAP ERP 6.0 Help Documentationon SAP ERP 6.0

help.sap.com SAP ERP SAP ERPCentral Component

1.3 History of Changes

Ensure you use the current version of the Solution Operations Guide, which can be located atSAP Service Marketplace service.sap.com/instguides SAP Business SuiteApplications SAP ERP SAP ERP 6.0.

The following table provides an overview of the most important changes in prior versions:

Version Important Changes1.00 First version of the SAP ERP 6.0 Solution Operation Guide2.00 Redesign SAP ERP 6.0 overview slides

Add further information to operate industrie solutionsAmplify several ERP components.

3.00 Redesign structur4.00 Mobile components moved into an own Master

Guide.5.00 Renaming Solution Operation Guide – Support Release 26.00 Renaming Solutions Operation Guide – Support Release 37.00 Content revision – Solution Operation Guide – Support Release 3

Page 14: SOG_SAPERP60_SR3

Getting Started

Dezember 2009 14

1.4 The Main SAP Documentation TypesThe following is an overview of the most important documentation types that you need duringvarious phases in the life cycle of an SAP solution.

Documentation types in the software life cycle

ImplementationImplementation

Master Guide

ConfigurationDocumentation Release Notes

ComponentInstallation Guide

ComponentUpgrade Guide

Upgrade Master Guide

OperationOperation UpgradeUpgrade

Solution ManagementGuide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

1.4.1 Cross-Phase DocumentationSAPterm

SAPterm is the SAP terminology database. It contains SAP-specific vocabulary in over 30languages, as well as many definitions and glossary entries in English and German.

Target group: Relevant for all target groups Current version: Located in the SAP Help Portal at help.sap.com Glossary (direct

access) or Terminology (as terminology CD)

Page 15: SOG_SAPERP60_SR3

Getting Started

15 Dezember 2009

SAP Library

SAP Library is a collection of function and process-oriented documentation for SAP components.The SAP Library also contains the description of integrated business content, which enables you tolearn more about SAP Business Suite Applications.

Target group: consultants, system administrators and project teams for implementationsor upgrades

Current version: Located in the SAP Help Portal at help.sap.com. Also located in theSAP Service Marketplace at service.sap.com/ibc (only the descriptions of integratedbusiness content)

Implementation Guide (IMG)

The Implementation Guide is a tool for configuring the SAP system to meet customer requirements.Its structure and documentation are component oriented.

Target group: Solution consultants and project teams for implementations or upgrades Current version: In the menu of the SAP system under Tools Customizing IMG

Security Guide

The Security Guide describes the settings for a medium security level and offers suggestions forraising security levels. A collective security guide is available for the SAP NetWeaver technologies,such as the SAP NetWeaver Application Server (SAP Web AS). This document contains generalguidelines and suggestions about system security. Other technologies and individual applicationshave their own Security Guide.

Target group: Technology consultants, Solution consultants and Project teams forimplementations or upgrades

Current version: Located in the SAP Service Marketplace atservice.sap.com/securityguide

1.4.2 ImplementationMaster Guide

The Master Guide is the starting point for implementing an SAP application. It lists the requiredSAP components and third-party applications that are required for each Business Scenario. Itprovides scenario-specific descriptions of preparation, execution and follow-up of animplementation. It also offers references to other documents, such as Component InstallationGuides and SAP Notes.

Target group: Technology consultants, System administrators and Project teams forimplementations

Current version: Located in the SAP Service Marketplace at service.sap.com/instguidesSAP Business Suite Applications SAP ERP SAP ERP 6.0

Component Installation Guide

The Component Installation Guide describes the technical implementation of an SAP component,taking into account the combinations of operating systems and databases. It does not describe anybusiness-related configuration.

Target group: Technology consultants and Project teams for implementations Current version: Located in the SAP Service Marketplace at service.sap.com/instguides

SAP Business Suite Applications SAP ERP SAP ERP 6.0

Page 16: SOG_SAPERP60_SR3

Getting Started

Dezember 2009 16

Configuration Documentation in SAP Solution Manager

SAP Solution Manager is a tool with various functions, one of them being the configuration of SAPsolutions and business scenarios. It contains IMG activities and transactions, as well as additionalbackground documentation. Instead of the configuration documentation, there may be separateBusiness Scenario Configuration Guides in the SAP Service Marketplace for earlier shipments ofthe Business Scenarios.

Target group: Solution consultants and Project teams for implementations Current version: Located in SAP Solution Manager or in the SAP Service Marketplace at

service.sap.com/ibc.

1.4.3 Production OperationSolution Operation Guide

The Solution Operation Guide is the starting point for operating an SAP application. The guiderefers users to the tools and documentation that are needed to carry out various tasks, such asmonitoring, backup/restore, master data maintenance, transports and tests. It also refers users toother documents, for example, the SAP Library, the Master Guide and the ComponentManagement Guides.

Target group: System administrators, Technology consultants, Solution consultants andProject teams for implementations or upgrades

Current version: Located in the SAP Service Marketplace at service.sap.com/instguidesSAP Business Suite Applications SAP ERP SAP ERP 6.0

1.4.4 UpgradeMaster Upgrade Guide

The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAPapplication. It provides scenario-specific descriptions of the preparation, execution and follow-up ofan upgrade. It also refers to other documents, such as the Component Upgrade Guides and SAPNotes. Instead of an Upgrade Master Guide, there may be several Business Scenario UpgradeGuides or a Application Upgrade Guide for earlier shipments of the Business Scenarios of an SAPapplication.

Target group: Technology consultants and Project teams for upgrades Current version: Located the SAP Service Marketplace at service.sap.com/instguides

SAP Business Suite Applications SAP ERP SAP ERP 6.0

Component Upgrade Guide

The Component Upgrade Guide describes the technical upgrade of an SAP component, taking intoaccount the combinations of operating systems and databases. It does not describe any businessrelated configuration.

Target group: Technology consultants and Project teams for upgrades Current version: Located in the SAP Service Marketplace at service.sap.com/instguides

SAP Business Suite Applications SAP ERP SAP ERP 6.0

Page 17: SOG_SAPERP60_SR3

Technical System Landscape

17 Dezember 2009

Release Notes

Release notes are documents that contain short descriptions of new features or changes in an SAPcomponent since the previous release. Release notes on ABAP developments enable the SAPsystem to generate delta and upgrade IMG.

Target group: Consultants and Project teams for upgrades Current version: Located in the SAP Service Marketplace at

service.sap.com/releasenotesor in the menu of the SAP system under Help Release information

2 Technical System LandscapeSAP ERP 6.0 is based on SAP NetWeaver 7.0. SAP ERP 6.0 consists of different technicalcomponents, each representing a particular functional piece as described in the Master Guide forSAP ERP 6.0.

You can find the current version of SAP ERP 6.0 Master Guide and SAP ERP 6.0 SolutionOperations Guide on SAP Service Marketplace at service.sap.com/instguides SAPBusiness Suite Applications SAP ERP SAP ERP 6.0.

The following figure gives you an overview of SAP ERP 6.0 technical components.

ERP components overview

Page 18: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 18

Details – ERP Components

ABAP Components - The ABAP components of SAP ERP 6.0 consist of the:

Product instance SAP ERP 6.0 Central component (SAP ECC Server) version 6.0, the SRMServer, as well as different ABAP-based add-on components.

Technical component BI Content. This includes the content required to install the usage typeBusiness Intelligence and is always installed in addition.

Java Components - Java components include:

General Java web applications Content packages for the usage type Portal or usage type PI (Exchange Infrastructure)

These components are always installed in addition to an instance of the usage type Portal or adeployment of PI (Exchange infrastructure). The components included in Java web applications areindependent J2EE components, combined into a single installation tool as a product instance SAPXECO. Therefore, if you want to install one or more of these components, you will require Javacomponents for an ERP installation, which is done by the SAPinst tool.

Additional Components - Additional components include the relevant front-end components.Depending on the key capabilities or business processes you intend to deploy, you install the add-ons shown explicitly within the frame Additional Components. All add-ons are installed using theSAP Add-On Installation Tool (SAINT) or SAPinst.

SAP ERP 6.0 Central Component

The constituent parts of the SAP ERP 6.0 Central Component (SAP ECC 6.0), shown in the figureabove, cannot be installed individually. Nevertheless, support packages for each subcomponentare available. Therefore, each subcomponent, if needed, can be patched separately. Allsubsequent figures in this document that display system landscapes, display only one component,SAP ECC 6.0, which comprises all subcomponents shown in figure above.

Industry Add-Ons

Nearly all former industry solution add-ons are integrated into the product instance SAP ERP 6.0.

For more information, see SAP Notes:838002 (Add-ons (non-IS) integrated into SAP ECC 600)838003 (Industry Add-Ons integrated into SAP ECC 600)

Page 19: SOG_SAPERP60_SR3

Technical System Landscape

19 Dezember 2009

2.1 Landscape DescriptionDepending on the components used, the following areas must be taken into account:

Managing SAP ERP 6.0 application components or scenarios Managing SAP NetWeaver 7.0 Managing the database

SAP ERP 6.0 Components

The following list provides you with a short overview of the SAP ERP 6.0 components as depictedin the figure above.

Usage Type Application Server ABAP

Release Technology Comments

7.0 ABAP The usage type Application Server ABAP can be combinedoptionally with other usage types within one system.

For more information, see:

SAP Help Portal at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) System

Administration Technical Operations Manual

SAP Service Marketplace atservice.sap.com/netweaverORservice.sap.com/instguides

SAP Notes 853571 and 853770

Usage Type Application Server Java

Release Technology Comments

7.0 Java The usage type Application Server Java can be combinedoptionally with other usage types in one system.

For more information, see:

SAP Help Portal at help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical Operations Manual

SAP Service Marketplace at service.sap.com/netweaverORservice.sap.com/instguides

SAP Note 853572

Page 20: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 20

Usage Type Business Intelligence (BI)

Release Technology Comments

7.0 ABAP The usage type Business Intelligence is an integral part of SAPNetWeaver. You can operate it within an existing database, forexample, within the SAP Enterprise Core Component.

If you plan to operate business information warehouse and anERP Central Component on the same system hardware(database), see SAP Note 855534.

A prerequisite to the usage type Business Intelligence is theusage type Application Server ABAP. Usually, scenarios runningon the usage type Business Intelligence also require the usagetypes:

Business Intelligence Java

Application Server Java

Enterprise Portal

However, you can also combine it with other usage types withinone system.For more information, see:

SAP Help Portal at help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) System Administration TechnicalOperations Manual Administration of SAP NetWeaverSystems BI (Business Intelligence)

SAP Service Marketplace at service.sap.com/bi

SAP Notes 853730 and 853507

Page 21: SOG_SAPERP60_SR3

Technical System Landscape

21 Dezember 2009

Usage Type Business Intelligence Java Component

Release Technology Comments

7.0 Java The prerequisites to the usage type Business Intelligence Javaare the usage types:

Application Server Java

Enterprise Portal

Usually, scenarios running on usage type Business IntelligenceJava also require the usage types:

Business Intelligence

Application Server ABAP

However, you can also combine it with other usage types withinone system.

For more information, see:

SAP Help Portal at help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) System Administration TechnicalOperations Manual Administration of SAP NetWeaverSystems BI (Business Intelligence)

SAP Service Marketplace at service.sap.com/bi

SAP Notes 853770, 853765, 853766 and 853767

Usage Type Enterprise Portal (EP)

Release Technology Comments

7.0 Java A prerequisite to the usage type Enterprise Portal is the usagetype Application Server Java. You can also combine the usagetype Enterprise Portal with other usage types within one system.For more information, see:

SAP Help Portal help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) System Administration TechnicalOperations Manual Administration of SAP NetWeaverSystems Enterprise Portal (EP)

SAP Service Marketplace at service.sap.com/nw-ep

SAP Note 853509

Page 22: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 22

Portal Content

Release Technology Comments

-- Java For more information about portal content, see:

SAP Developer Network atsdn.sap.com/irj/sdn/contentportfolio

SAP Note 642775

Usage Type Process Integration (PI)

Release Technology Comments

7.0 ABAP andJava

A prerequisite to the usage type Process Integration (XI) are theusage types:

Application Server ABAP

Application Server Java

However, you can also combine the usage type ProcessIntegration with other usage types within one system. SeveralSAP applications make use of process integration and deliver XIcontent, which is shipped as part of the application.

For more information, see:

SAP Service Marketplace at service.sap.com/xi

SAP Notes 853510, 853768, 853727 and 853726

Usage Type Development Infrastructure

Release Technology Comments

-- Java A prerequisite to the usage type Development Infrastructure isthe usage type Application Server Java. However, you can alsocombine the usage type Development Infrastructure with otherusage types within one system.For more information about the usage type DevelopmentInfrastructure, see section 5.4.1 Usage Type DevelopmentInfrastructure.

J2SE Adapter Engine (PI/XI)

Release Technology Comments

-- Java The J2SE Adapter Engine is used only if you have SAPNetWeaver with the usage type PI in your system landscape.

It must be installed manually with the JDK 1.3.1 or a higherversion. For more information, see the SAP Notes 853768,853727 and 853726.

Page 23: SOG_SAPERP60_SR3

Technical System Landscape

23 Dezember 2009

Knowledge Management (KM)

Knowledge Management comprises the following subcomponents: Content Management (CM) Search and Classification (TREX)

Content Management (CM)

Release Technology Comments

-- AdditionalComponent

For more information, see:

SAP Help Portal at help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) System Administration TechnicalOperations Manual Administration of SAP NetWeaverSystems Enterprise Porta (EP) Knowledge Management

SAP Note 701097

Search and Classification (TREX)

Release Technology Comments

7.0 AdditionalComponent

The Search and Classification (TREX) feature offers anintegrated set of services. TREX services include, search andretrieval in large document collections, text mining, automaticdocument classification, and search and aggregation overstructured data in SAP.

For more information, see SAP Notes 701097 and 853725.

SAP liveCache

Release Technology Comments

700 AdditionalComponent

SAP liveCache is a database engine for managing complexobjects in scenarios where large volumes of data must bepermanently available.For more information, see:

SAP Service Marketplace at service.sap.com/scm

SAP Help Portal help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) System Administration TechnicalOperations Manual Administration of Standalone Engines SAP liveCache Technology

Page 24: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 24

SAP ERP 6.0 Central Component (ECC)

Release Technology Comments

6.0 ABAP SAP ECC consists of the central component and the usage typeApplication Server ABAP. The plug-in is an integral part and isused to connect to, for example, a BI system. After the installationof the product instance SAP ERP 6.0 – SAP ECC Server, thefollowing core industry solutions are available with SAP ERP 6.0:

SAP for Chemicals

SAP for Consumer Products (except the applications listed asextension)

SAP for Industrial Machinery & Components

SAP for Life Sciences

SAP for Logistics Service Providers

SAP for Pharmaceuticals

SAP for Postal Services

SAP for Professional Services

SAP for Public Sector (SAP ERP 6.0 Human Capital Managementfor the Public Sector including SAP Pension Administration forGermany)

SAP for Railway Services

SAP for Retail

SAP for Wholesale Distribution

SAP Self Services (XSS)

Release Technology Comments

6.0 Java XSS is a J2EE application (Web Dynpro), which is deployed withthe ERP Java Components package. XSS contains the followingsoftware components:

PCUI_GP 600 Floor plan Manager, Self-Service Administratorand Utilities

MSS 600 Manager Self-Service

ESS 600 Employee Self-Service

ASR 600 HR Administrative Services

PSS 600 Project Self-Service

IS-HER-CSS 600 Campus Management Self Service ESS,MSS, PSS and PCUI_GP which

This component can be patched individually.

For more information, see:

SAP Service Marketplace at service.sap.com/xss

Page 25: SOG_SAPERP60_SR3

Technical System Landscape

25 Dezember 2009

SAP Strategic Enterprise Management (SEM)

Release Technology Comments

6.0 ABAP SAP SEM and SAP BW can also be operated on two separatesystems. The BW data storage is used. You can operate SAPSEM within an existing database (for example, SAP ECCServer). If you plan to operate a business informationwarehouse and a SAP ERP 6.0 Central Component on thesame system hardware (database), check SAP Note 855534.

Master-Data Synchronization:

Master Data from SAP Consolidation is stored in SAP BW tablesas well as in SAP SEM-specific tables. Master data created inSAP SEM is automatically synchronized with SAP BW butmaster data created in SAP BW, such as legacy data frombefore SAP SEM implementation, is not synchronized with theSAP SEM master data storage.

To prevent such inconsistencies between the SAP SEM and SAPBW master data tables, you must use appropriatesynchronization tools. For more information, see SAP Note578348

Data-Model Synchronization:

Besides inconsistencies in master data, there might be caseswhen the data model becomes inconsistent. This could occurwhen there are changes in the metadata of SAP BWInfoObjects, which are in use within the SAP SEM database. Insuch a case, a data model synchronization tool is provided bySAP.

For more information, see SAP Help Portal at help.sap.comSAP ERP 6.0 SAP Strategic Enterprise Management SAPSEM 6.0 SAP Library SEM-Strategic EnterpriseManagement Business Consolidation (SEM-BCS) DataModel Data Model Synchronizer.

Consistency of Transaction Data:

Another area of potential data inconsistency is related to thesummation data in the transaction InfoCube and in the journalentries in the document ODS. SAP SEM Business Consolidation(BCS) stores journal entries as line items per document numberand in aggregated form as total records. Potential reasons fordata inconsistency and how they can be analyzed and repairedare described in the SAP Note 702189.

For more information, see:

SAP Service Marketplace at service.sap.com/sem

SAP Help Portal at help.sap.com SAP ERP 6.0 SAPStrategic Enterprise Management SAP SEM 6.0 SAPLibrary SEM-Strategic Enterprise Management BusinessConsolidation (SEM-BCS) Data Model Data Basis

SAP Notes 855382, 855383, 852447 and 852448

Page 26: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 26

SAP Extended E-Commerce Components (XECO)

Release Technology Comments

5.0 Java Product instance of SAP XECO consists of the followingcomponents:

SAP E-Commerce

Internet Pricing Configurator (IPC) web applications

Workforce Management

SAP Financial Supply Chain Management (FSCM)

SAP Financial Supply Chain Management comprises the following functions: SAP Biller Direct Financials Basis

SAP Biller Direct

Release Technology Comments

6.0 Java SAP Biller Direct is a J2EE application, which is deployed withthe ERP Java package.

For more information, see SAP Service Marketplace at:

service.sap.com/fscm SAP ERP SAP ERP Financials SAP Financial Supply Chain Management SAP Biller Direct Media Library Operations Management SAP Biller DirectEnglish

Financials Basis

Release Technology Comments

6.0 ABAP This ABAP add-on can be installed on the SAP ECC Server orany other system that is based on SAP NetWeaver 7.0 ABAPStack. All add-ons are installed separately using the SAINT tool.For more information, see:

SAP Service Marketplace at service.sap.com/fscm.

SAP Note 852448

Page 27: SOG_SAPERP60_SR3

Technical System Landscape

27 Dezember 2009

SAP Learning Solution

The SAP Learning Solution comprises the following components: LSOOP (SAP Learning Solution Offline player) LSOAE (SAP Learning Solution Authors environment) LSOCP (SAP Learning Solution Content player) LSOFE (SAP Learning Solution Front End)

For more information, see:

SAP Service Marketplace at service.sap.com/learningsolution Media Library – EnterpriseLearning

SAP Help Portal at help.sap.com SAP ERP SAP ERP Central Component SAPLibrary SAP ERP Central Component Human Resources Leraning Solution

SAP Note 642775 - Composite SAP Note for Business Packages as of EP 6.0 SP1 (includingSAP NetWeaver 7.0).

SAP Developer Network at sdn.sap.com/sdn/contentportfolio.sdn Browse ContentPortfolio Business Packages for Every User Business Package for Learning

LSOOP

Release Technology Comments

600 AdditionalComponent

This component is part of the SAP Learning Solution Release6.0.

LSOOP is a J2EE application, which is deployed with the ERPJava Component package and the Java Development Kit (JDK)1.4.2.

LSOAE

Release Technology Comments

600 AdditionalComponent

This component is part of the SAP Learning Solution Release6.0.

LSOAE is an application used for authoring and can be installedon Windows© NT4.0/2000/XP along with the Java DevelopmentKit (JDK) 1.4.2.For more information, see SAP Help Portal at help.sap.comSAP ERP SAP ERP Central Component SAP Library SAP ERP Central Component Human Resources Leraning Solution

LSOCP

Release Technology Comments

600 Java This component is part of the SAP Learning Solution Release6.0.

LSOCP is a J2EE application, which is deployed with the ERPJava Component package.

Page 28: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 28

LSOFE

Release Technology Comments

600 ABAP This component is part of the SAP Learning Solution Release6.0.

SAP Supplier Relationship Management (SRM)

SAP SRM comprises the following subcomponents: SRM Server SAP Catalog Content Management SRM Server with ECC release 5.5 as add-on

For more information, see SAP Service Marketplace at service.sap.com/instguides SAPBusiness Suite Applications SAP SRM SAP SRM Server 5.5 Solution Operations Guide –SRM 5.0

SRM Server

Release Technology Comments

5.0 ABAP SAP SRM is a separate instance within SAP ERP 6.0 andtherefore cannot be operated within an existing database. Formore information, see SAP Service Marketplace atservice.sap.com/srm

SAP Catalog Content Management

Release Technology Comments

2.0 ABAP SAP Catalog Content Management is used for procurementfunctions. It can be installed as an add-on to SAP ECC Server,SAP SRM, or any SAP NetWeaver 7.0 system (ABAP stack).

Collaboration Projects (cProject) Suite

Collaboration Projects (cProject) Suite comprises the following subcomponents: SAP cProject Suite cProject ECL Viewer

For more information, see: SAP Help Portal at help.sap.com SAP ERP SAP cProject Suite SAP Note 427215

SAP cProject Suite

Release Technology Comments

4.00 ABAP The cProject suite consists of the applications cFolders andcProjects.ABAP add-ons can be installed on SAP ECC Server or anyother system that is based on the SAP NetWeaver 7.0 ABAPStack. All add-ons are installed separately using the SAINT tool.

Page 29: SOG_SAPERP60_SR3

Technical System Landscape

29 Dezember 2009

cProject ECL Viewer

Release Technology Comments

5.1.2 AdditionalComponent

For more information, see:

SAP Service Marketplace at service.sap.com/plm

SAP Note 889078 and 809922

SAP Workforce Management Core

Release Technology Comments

2.0 ABAP ABAP add-ons can be installed on SAP ECC Server or anyother system that is based on the SAP NetWeaver 7.0 ABAPStack. All add-ons are installed separately using the SAINT tool.

SAP E-Recruiting

Release Technology Comments

6.0 ABAP ABAP add-ons can be installed on SAP ECC Server or anyother system that is based on the SAP NetWeaver 7.0 ABAPStack. All add-ons are installed separately using the SAINT tool.

SAP GUI

Release Technology Comments

6.40 AdditionalComponent

SAP GUI is a user interface application.

For more information, see:

SAP Service Marketplace at service.sap.com/sapgui

For an overview of SAP GUI, see SAP Service Marketplace athttps://www.sdn.sap.com/irj/sdn/sap-gui

SAP Service Marketplace athttps://www.sdn.sap.com/irj/sdn/nw-ui

SAP Notes 26417,

SAP Easy Document Management

Release Technology Comments

6.0 AdditionalComponent

For more information, see SAP Service Marketplace atservice.sap.com/plm Life-Cycle Data Management Document Management SAP Easy Document Management

Page 30: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 30

OpenPS for MS Project

Release Technology Comments

2.02 AdditionalComponent

Open PS for Microsoft Project (OpenPS4MSP) is an add-onprogram that allows you to exchange data between the ProjectSystem (PS) and Microsoft ® Project, thus making projectprocessing easier and more flexible.

For more information, see:

SAP Service Marketplace at service.sap.com/swdcDownload Installations and Upgrades Entry by ApplicationGroup Supplementary Components for Cross IndustrySolutions Project Management OpenPS OPENPS FORMS PROJECT

SAP Notes 579761 and 656414

2.2 Example: Communication Structure for SAP Learning Solution

The SAP Learning Solution is an example of how various components interact with each other. Thefollowing figure illustrates the communication structures between individual components of the SAPLearning Solution 6.00 and between components of SAP Enterprise Portal 7.0 and SAP ECC 6.0.

SAP Learning Solution, Communication Structure

Page 31: SOG_SAPERP60_SR3

Technical System Landscape

31 Dezember 2009

2.3 Further InformationThis section includes additional information, such as SAP Notes, Web links, and relateddocuments.

2.3.1 Technical System Landscape SAP Notes

Check SAP Service Marketplace at service.sap.com/notes regularly to see which SAP Notesare available for the Solution Operations Guide.

SAP NoteNumber

Title Description

855534 Embedded NetWeaver Componentsin ERP

Installation information

578348 FIN master data: Synchronizationlocal system with BW

Consulting

702189 SEM-BCS: Analysis of transactiondata

Program error

642775 Composite SAP Note for BusinessPackages as of EP 6.0 SP1

Installation information

701097 SAP NetWeaver '04 Documentation Documentation error26417 SAP GUI Resources: Hardware and

softwareInstallation information

838002 Add-ons (non-IS) integrated in SAPECC 600

Upgrade of add-on component (IS)

838003 Industry Add-Ons integrated in SAPECC 600

Upgrade of add-on component (IS)

855382 Upgrade auf SAP SEM Release 6.0 SAP Strategic Enterprise Management855383 Installation SAP SEM Release 6.0 SAP Strategic Enterprise Management852447 Installation SEM-BW 600 auf SAP

NW AS 7.0SAP Strategic Enterprise Management

852448 SEM-BW 600 und FINBASIS 600:Upgrade auf NetWeaver

Upgrade of add-on components (IS)

642775 Composite SAP Note for BusinessPackages as of EP 6.0 SP 1 a

iView Studio

427215 Overview: Notes on cFolders andcProjects

List of notes

855534 Embedded NetWeaver Componentsin ERP

Installation tools

642775 Composite SAP Note for BusinessPackages as of EP .0 SP 1 a

iView Studio

701097 SAP NetWeaver 7.0 Documentation Basis components853770 Rel. Restr.: SAP NW 2004s - SAP

NetWeaver Developer Workpl.Basis components

853768 Rel. Restr.: SAP NW 2004s - J2SEAdapter Engine (PI/XI)

Basis components

853767 Rel. Restr.: SAP NW 2004s -Standalone Log Viewer

Basis components

853766 Rel. Restr.: SAP NW 2004s - VisualComposer

Basis components

853765 Rel. Restr.: SAP NW 2004s - SAPNetWeaver Developer Studio

Basis components

Page 32: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 32

SAP NoteNumber

Title Description

853764 Rel. Restr.: SAP NW 2004s - SAPGUI for Java

SAP GUI for Java

853763 Rel. Restr.: SAP NW 2004s - SAPGUI for HTML

Internet Transaction Server

853762 Rel. Restr.: SAP NW 2004s - SAPGUI for Windows

Graphical user interface

853761 Rel. Restr.: SAP NW 2004s -Content Server

Basis components

853730 Rel. Restr.: SAP NW 2004s - Pre-calculation Server (BI)

Basis components

853729 Rel. Restr.: SAP NW 2004s - RTCApplication Sharing Server

Basis components

853728 Rel. Restr.: SAP NW 2004s -LiveCache

SAP liveCache

853507 Release Restr.: Usage Type BI ofSAP NetWeaver 2004s

Basis components

853505 Release Restr.: Usage Type BI-Javaof SAP NetWeaver 2004s

Basis components

853727 Rel. Restr.: SAP NW 2004s -Adapter Engine (PI/XI)

Basis components

853726 Rel. Restr.: SAP NW 2004s - PartnerConnectivity Kit (PI/XI)

Basis components

853725 Rel. Restr.: SAP NW 2004s - Searchand Classification (TREX)

TREX

853571 Release Restr.: Usage Type AS ofSAP NetWeaver 2004s

Basis components

853572 Release Restr.: Usage Type AS-Java of SAP NetWeaver 2004s

Basis components

853510 Release Restr.: Usage Type PI ofSAP NetWeaver 2004s

Basis components

853509 Release Restr.: Usage Type EP ofSAP NetWeaver 2004s

Basis components

889078 ECL Viewer - Limitations in Usage Basis components809922 The requirement is to use the ECL

Viewer inside the cFoldersapplication

Basis components

579761 FAQ note on OpenPS for MicrosoftProject

Basis components

656414 You need information on bugs fixedand the expected release dates fornew versions of OpenPS for MSProject.

Basis components

Page 33: SOG_SAPERP60_SR3

Technical System Landscape

33 Dezember 2009

2.3.2 Technical System Landscape Web Links

Check SAP Help Portal at help.sap.com and SAP Service Marketplace at service.sap.comregularly for the following web links.

Documentation Links – SAP Help Portal

You can find the following documentation on SAP Help Portal at help.sap.com.

Type of Information Description Quick Link/Path

Usage type ApplicationServer ABAP

Provides an overview ofthe monitoring and dailyadministration of theSAP Web ApplicationServer (ABAP)

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual Administration of SAPNetWeaver Systems AS ABAP(Application Server for ABAP)

Usage type ApplicationServer Java

Provides an overview ofthe monitoring andmanagement of theApplication Server Java

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual Administration of SAPNetWeaver Systems AS JAVA(Application Server for Java)

Usage type EnterprisePortal

Provides the tools tomanage knowledge. Itallows you to analyzeinformation, interrelate it,share, and collaboratebased on knowledge.

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual Administration of SAPNetWeaver Systems EPC (EP Core)and EP (Enterprise Portal)

Usage type BusinessIntelligence

Provides a starting pointfor generaladministration andoptimal maintenance ofyour BI system. You canfind BI-specificinformation for varioustasks, along with a list ofthe required andassociated tools

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual Administration of SAPNetWeaver Systems BI (BusinessIntelligence)

Usage type ProcessIntegration (PI)

Describes administrationand maintenance tasksspecific to processintegration. It alsoprovides you with areference to the toolsand documentationrequired to performthese tasks.

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual Administration of SAPNetWeaver Systems PI (ProcessIntegration

Database administration Provides supplementaryinformation on routineadministration for the

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical Operations

Page 34: SOG_SAPERP60_SR3

Technical System Landscape

Dezember 2009 34

Type of Information Description Quick Link/Pathfollowing databases:

Oracle

MS SQL Server

IBM DB2 UniversalDatabase for Linux,UNIX and Windows

MaxDB

DB2 UDB for z/OS

IBM DB2 UDB for iSeries

Manual General AdministrationTasks Database Administration

Adaptive Computing Provides information onthe administration ofadaptive computing

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual General AdministrationTasks Adaptive Computing

Usage Type MI Describes administrationand maintenance tasksspecific to processintegration. It alsoprovides you with areference to the toolsand documentationrequired to performthese tasks.

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual Administration of SAPNetWeaver Systems MI (MobileInfrastructure)

Documentation Links – SAP Service MarketplaceYou can also find the following documentation on SAP Service Marketplace at service.sap.com.

Type of Information Description Quick Link/Path

SAP ERP 6.0 Masterguide

- service.sap.com/instguides SAPBusiness Suite Applications SAP ERP

SAP ERP 6.0

Here you can find detailed informationabout the technical system landscape ofSAP ERP 6.0

Installation Guides - service.sap.com/instguides SAPBusiness Suite Applications SAP ERP

SAP ERP 6.0

Here you can find detailed information howyou can install your system landscape ofSAP ERP 6.0

Biller Direct - service.sap.com/fscm SAP ERPFinancials SAP Financial Supply ChainManagement SAP Biller Direct Media Library Solution ManagementGuide or

service.sap.com/erp-inst SAPBusiness Suite Applications SAP ERP

Page 35: SOG_SAPERP60_SR3

Monitoring

35 Dezember 2009

Type of Information Description Quick Link/Path SAP ERP 6.0 Installation -

Installation SAP Biller Direct

Best Practices Provides a list ofexisting best practicesfor applicationmanagement by topicareas, phases, andapplications

service.sap.com/solutionmanagerbpTopic Area (right frame)

SAP GUI Provides an overviewof SAP GUI

service.sap.com/sapguihttps://www.sdn.sap.com/irj/sdn/sap-gui

2.4 SAP Solution ManagerThe SAP Solution Manager is a platform that provides integrated content, tools and methodologiesthat you need to implement, support, operate and monitor your enterprise´s solutions from SAP.SAP Solution Manager enables you to accelerate the implementation process and access fullsupport and continuous improvement offerings from SAP.With SAP Solution Manager, you can:

o Minimize risk and increase the reliability of your IT solutionso Reduce total cost of ownership (TCO) throughout the solution life cycleo Manage your core business processes and link business processes to the underlying

IT infrastructureo Get more on your return-on-investments (ROI), because it supports both SAP and non-

SAP software

For more information about Solution Manager, see SAP Service Marketplace atservice.sap.com/solutionmanager SAP Solution Manager in Detail.

3 MonitoringPurpose

Monitoring works as an early warning system that monitors and displays the status of multiplesystems and independent business components.

BenefitsMonitoring of SAP Technology is an essential task during solution operation of SAP Technology.Deploying a monitoring architecture enables system administrators to get an overview of thesystem infrastructure at a glance and provides an infrastructure to gather and manage systeminformation. The main features of the monitoring architecture are:User-definable alert monitors

Critical system events, displayed as alerts

Method assignments to analyze alerts and react to them automatically

Performance database to display recent performance data graphically

Page 36: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 36

Managing applications or client-server systems of the SAP Business Suite places highdemands on the system administration; demands that increase significantly through theinclusion of the Internet in business processes.

This section provides you with an overview of the general tools used for monitoring, for example,the SAP Solution Manager tool. Furthermore, SAP Notes, documents, and web links are alsoprovided.

3.1 Monitoring Using SAP Solution ManagerThe main functional areas of the Solution Manager are described in section 2.4 SAP SolutionManager.In your SAP ERP 6.0 project, use SAP Solution Manager to:Define your Application Landscape

Connect existing systems to enable EarlyWatch Alert

Define the business processes that are affected by SAP ERP 6.0

Installation Considerations

Listed below are a few installation requirements:Assign each SAP ERP 6.0 system landscape to an installation of SAP Solution Manager. This isrequired, so that in the event of a support-relevant incident within your SAP system landscape,SAP Support can remotely access the SAP Solution Manager that hosts the affected systemlandscape.

Use SAP Solution Manager to manage the application you build with SAP NetWeaver and SAPERP 6.0. In this case, it is highly recommended that you update SAP Solution Manager to the latestversion.

Host separate business applications on each installation, if you have multiple instances of SAPSolution Manager.

Do not install SAP Solution Manager as a central component, if you want to reduce the risk ofunavailability. Instead, operate a two-system landscape with test and production environmentof SAP Solution Manager, especially if you are using time-critical functions such as SupportDesk.If you develop your own content, we recommend that you set-up a three-system landscapewith development, test, and production environment.

3.1.1 SAP Solution Manager DiagnosticsSolution Manager Diagnostics provides an efficient and safe root cause analysis of incidents inbusiness applications powered by SAP NetWeaver. It helps monitor operating systems, logsdatabases, Java application activities, and system performance. Solution Manager Diagnostics alsoreports changes in software and configuration, which can lead to malfunctions and errors.SAP Solution Manager and SAP Solution Manager Diagnostics play key roles with regard tosupporting and monitoring system landscapes. For more information, see the SAP NetWeaverMaster Guide at service.sap.com/instguidesNW70.

Page 37: SOG_SAPERP60_SR3

Monitoring

37 Dezember 2009

Recommendations by SAP

If you use SAP components based on the Java stack, install and use Solution Manager Diagnosticsfor root cause analysis.

If you run applications based on SAP NetWeaver systems with usage type AS Java, install oneSolution Manager Diagnostics application within your SAP application landscape, Agents areresponsible for delivering the data from all productive hosts within your system landscape to theSolution Manager Diagnostics system.

3.1.2 Further InformationThis section includes additional information on monitoring, such as SAP Notes, web links, andrelated documents.

3.1.2.1 SAP Solution Manager SAP Notes

Check SAP Service Marketplace at service.sap.com/notes regularly to see which SAP Notesare available for the Solution Operations Guide.

SAP Notes

SAP NoteNumber

Title Description

521820 Availability Business ProcessMonitoring

Business process monitoring

892412 Upgrading to SAP Solution Manager4.0

903587 Upgrade to SAP Solution Manager 4.0- Post-Processing steps

1161294 Name chg, SAP Solution Manager 4.0to Solution Manager 7.0

987835 How to define solutions in smsy fordiagnostics

Smsy entries in Solution ManagerDiagnostics

780177 Setup of Solution Manager Diagnostics Solution Manager Diagnostics setup

962516 Solution Manager Services Setting up service connections to SAPSolution Manager or Solution ManagerDiagnostics

1163836 Solution Manager Diagnostics requiredfor troubleshooting

troubleshooting

3.1.2.2 SAP Solution Manager Web LinksDocumentation Links – SAP Service Marketplace

Type ofInformation

Description Quick Link/ Path

SAP SolutionManager generalinformation

General informationabout SAP SolutionManager

service.sap.com/solutionmanager

Page 38: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 38

Type ofInformation

Description Quick Link/ Path

SAP SolutionManager systeminformation

Information about systeminfrastructure, scenarios,and installation andconfiguration of SAPSolution Manager

service.sap.com/instguides SAPComponents SAP Solution ManagerGuides

SAP SolutionManager learningmaps

Learning maps for SAPSolution Manager

service.sap.com/rkt-solman orservice.sap.com/solutionmanager

SAP NetWeaverMaster Guide

SAP NetWeaver MasterGuide

service.sap.com/instguidesNW70

Solution ManagerDiagnostics

Benefits and usagescenarios of SolutionManager Diagnostics

service.sap.com/diagnostics

Monitoring andSetup Guide

References themonitoring and setupguide for SolutionManager Diagnostics

service.sap.com/instguidesNW70

3.1.2.3 SAP Solution Manager DocumentsDocumentation Links – SAP Service Marketplace

Type ofInformation

Title Quick Link/ Path

Installation –Guide

Inst. Guide SAP Solution Manager 7.0*

service.sap.com/instguidesInstallation & Upgrade Guides SAPComponents SAP Solution Manager

Release 7.0Master-Guide

Master Guide SAP Solution Manager7.0

service.sap.com/instguidesInstallation & Upgrade Guides SAPComponents SAP Solution Manager

Release 7.0Upgrade-Guide

Upgrade Guide SAP Solution Manager7.0 *

service.sap.com/instguidesInstallation & Upgrade Guides SAPComponents SAP Solution Manager

Release 7.0

3.2 Monitoring Using the Alert MonitorAlerts are displayed in the Alert Monitor, using transaction RZ20. Alerts ease the workload ofsystem administrators, since they then track problem messages, instead of a large volume ofsystem data.The Alert Monitor also provides the administration methods that are required to monitor a system.You can therefore set the threshold values for alerts and add or adjust auto reaction and analysismethods. If an alert is triggered, auto reaction methods react automatically; you can investigate thecause of an alert with an analysis method, without leaving the Alert Monitor.The Operations area contains services to manage your SAP application. Based on your applicationconfiguration, recommendations for these services are triggered dynamically.

Page 39: SOG_SAPERP60_SR3

Monitoring

39 Dezember 2009

Threshold values, methods, detailed help, and four extensive monitor sets with monitors for allaspects of system management are predefined in the monitoring architecture, and areavailable in every SAP system.You can also customize all settings to your own requirements and, for example, configurecustomer-specific monitors so that only the data about your system landscape that is relevantto your needs is displayed.

3.3 CCMS Monitoring ArchitectureThe monitoring of a system landscape is a complex task of significant importance for everycompany that operates one or more SAP systems. The complexity increases with every additionalsystem, component, or extension.With the monitoring architecture of the Computing Center Management System (CCMS), SAPprovides a flexible and universally-usable infrastructure with which you can centrally monitor yourentire IT landscape and which reports problems quickly and reliably.The monitoring architecture is delivered free of cost with every SAP Web Application Server. Thearchitecture runs on every SAP Web Application Server and can easily be extended to includeadditional SAP and non-SAP components.

3.3.1 Monitoring Architecture ToolsThe monitoring architecture also contains tools to manage and archive alerts. Listed below aresome of the available monitoring tools:

Tool Description Quick Link/ PathOperatingSystemMonitor

You can use the operating systemmonitor to monitor the followingoperating system resources: Virtual and physical memory

CPU

File system administration andphysical disks

NetworkTransaction ST06 displays theoperating system data for the localserver. Transaction OS07 displays thedata for the entire system.

help.sap.com SAPNetWeaver SAP NetWeaver7.0 (2004s) SystemAdministration TechnicalOperations Manual Administration of SAP NetweaverSystems AS ABAP(Application Server for ABAP) Monitoring Tools

Page 40: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 40

Tool Description Quick Link/ PathAlert Monitor Use the alert monitor (transaction

RZ20) as the central tool formonitoring your entire systemlandscape. If malfunctions or problemsoccur, alerts are generated. Thesealerts are displayed in variousmonitors in a tree structure, and youcan assign auto-reactions to them. Inthis way, you are informed quickly andreliably about the alert – even if youare not working in the alert monitor atthe time.If you use the alert monitor as theentry point for your central monitoring,you will use the tools listed below inthis table as analysis methods, that is,after an alert is generated, you canstart the appropriate tool for the alertby double-clicking the alert.

help.sap.com SAPNetWeaver SAP NetWeaver7.0 (2004s) SystemAdministration TechnicalOperations Manual Administration of SAP NetweaverSystems AS ABAP(Application Server for ABAP) Monitoring Tools

SAPNetWeaverAdministrator

The SAP NetWeaver Administrator(NWA) unifies the most importantadministration and monitoring toolsboth for Java and for ABAP systems ina new, browser-based user interface.The most important advantages of theNWA are:You no longer need to switch betweendifferent tools for administration,troubleshooting, and problem analysisof your entire SAP NetWeaver systemlandscape.

There is a central administration toolavailable to you landscape-wide forboth Java and ABAP systems forstarting and stopping instances,checking configuration settings andlogs, and monitoring error-freefunctioning of components.

The interface follows the currentguidelines for interface design, iseasy-to-use, task-oriented, andcomplete. By using Web Dynpro, itruns in a browser.

help.sap.com SAPNetWeaver SAP NetWeaver7.0 (2004s) SystemAdministration TechnicalOperations Manual Administration of SAP NetweaverSystems AS ABAP(Application Server for ABAP) Monitoring Tools

Page 41: SOG_SAPERP60_SR3

Monitoring

41 Dezember 2009

Tool Description Quick Link/ PathWorkloadMonitor

The Workload Monitor (transactionST03) displays statistical data for thelocal ABAP system for performanceanalysis. You can also display, forexample, the total values for allinstances, and compare theperformance of particular instancesover a period of time. The largenumber of analysis views andcollected data allow you to quicklydetermine the cause of possibleperformance problems.

help.sap.com SAPNetWeaver SAP NetWeaver7.0 (2004s) SystemAdministration TechnicalOperations Manual Administration of SAP NetweaverSystems AS ABAP(Application Server for ABAP) Monitoring Tools

GlobalWorkloadMonitor

The Global Workload Monitor(transaction ST03G) displaysstatistical records for entirelandscapes, both for ABAP systemsand for DSR components, such asJ2EE Engine, BC, and ITS. You can,for example, display the load datacreated when external componentsare called..

help.sap.com SAPNetWeaver SAP NetWeaver7.0 (2004s) SystemAdministration TechnicalOperations Manual Administration of SAP NetweaverSystems AS ABAP(Application Server for ABAP) Monitoring Tools

SolutionMonitoring

Solution Monitoring allows you toeffectively monitor heterogenuoussystem landscapes in the SAPSolution Manager. This means thatyou can monitor your systems andbusiness processes in one tool.The system monitoring and businessprocess monitoring here are based onthe data of the CCMS monitoringinfrastructure.

help.sap.com SAPNetWeaver SAP NetWeaver7.0 (2004s) SystemAdministration TechnicalOperations Manual Administration of SAP NetweaverSystems AS ABAP(Application Server for ABAP) Monitoring Tools

ICM Monitor You can use the ICM monitor(transaction SMICM) to monitor andadminister the Internet CommunicationManager, which receives and sendsthe requests from or to the Internet (inthe server role, for example, theinbound HTTP requests).

help.sap.com SAPNetWeaver SAP NetWeaver7.0 (2004s) SystemAdministration TechnicalOperations Manual Administration of SAP NetweaverSystems AS ABAP(Application Server for ABAP) Monitoring Tools

Page 42: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 42

Tool Description Quick Link/ PathOther tools formonitoringsystemcomponents

In the SAP system, you find a set oftools for displaying detailedinformation on user sessions, workprocesses, and on the servers in yourSAP system.If you want to work with these tools,choose the path AdministrationSystem Administration on the initialSAP screen, or run transaction S002.The initial screen for systemadministration appears. The tools areavailable under Administration andMonitor.There are also programs that you canuse at operating system level tomonitor the message server or thegateway.For information about other tools formonitoring system components, seethese sections: Overview of SAP Application

Servers Monitoring and Administering the

SAP Message Server Display and Control Work

Processes Displaying and Managing User

Sessions Trace Functions Monitoring RFC Resources on the

Application Server Using the SAP Gateway Monitor in

the SAP System System Log

help.sap.com SAPNetWeaver SAP NetWeaver7.0 (2004s) SystemAdministration TechnicalOperations Manual Administration of SAP NetweaverSystems AS ABAP(Application Server for ABAP) Monitoring Tools

3.4 Scenario Alert MonitoringIn addition to the required monitoring of each component, some additional monitoring objects aredesigned to monitor cross-component communications and other scenario-specific criticalsituations.For more information, see SAP Help Portal at help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS Java (Application Server for Java) Monitoring

3.4.1 SAP E-Commerce in SAP ERP 6.0All web applications of e-commerce are based on the same core functionality, in which monitoringis implemented. To set up the heartbeat for the Java components of e-commerce proceed asdescribed below:

1. Log on into the administration area of the web application you want to monitor (for example,http://localhost:50000/b2b/admin).

Page 43: SOG_SAPERP60_SR3

Monitoring

43 Dezember 2009

Log on using a user of SAP Web AS Java, which is assigned either to the role isaadmin or tothe role administrators.

2. Follow the link to CCMS HEARTBEAT CUSTOMIZING.A list of XCM application configurations available for this web application is displayed.

3. Click on the name of an application configuration.A list of available tests is displayed. The tests correspond to the interactive configurationcomponent tests within the XCM Administrator. For example, the jco test checks theconnection to the backend system. If a test is selected, it becomes part of heartbeat and isexecuted automatically.

4. Select the used webshop and enter the catalog, you want to be monitored.Ensure that you enter the correct spelling.

5. Choose the checkbox in front of the configuration name to select the configuration you wouldlike to heartbeat.

It can take up to one hour before the CCMS agent uploads the customizing file from thisdirectory to the central monitoring system CEN system automatically. If you want toupload the files immediately, proceed as follows:1. Log on to the CEN system.2. Go to transaction GRMG.3. Choose ‘Upload from Agent’ to start the upload.

The Heartbeat name is constructed as follows:GRMG.CRM.<APPLICATION NAME>.<XCM Configuration name>.

The monitoring function is not implemented for administrative web applications such asInternet Sales User Administration, Shop Management, or Extended ConfigurationManagement (XCM).

3.4.2 Example: Configuring GRMG Monitoring for the SAP Learning Solution - Content Player

UseYou use the Generic Request and Message Generator (GRMG) to determine possible server orprocess outages. This automatic availability monitoring can be accessed using CCMS. CCMS usesGRMG to check the availability of the J2EE Engine. If the availability check fails, an alert istriggered in the central monitoring system.

PrerequisitesYou have:Installed the CCMS agent, SAPCCMSR, with the j2ee option on that host where your J2EE Engineruns

Registered the CCMS agent in your central monitoring system (CEN) on SAP NetWeaver AS

Process Flow

GRMG Configuration

Page 44: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 44

1. Switch to the following directory where your J2EE engine runs:Microsoft Windows: <J2EE-Home-Verzeichnis>\JC<Inst.-Nr.>\j2ee\admin\

Unix: <J2EE-Home-Verzeichnis>/JC<Inst.-Nr.>/j2ee/admin/

If you install the J2EE Engine and the ABAP Engine on one host, the charactercombination in your folder JC<Inst.-Nr.> could be different.

2. Start the Visual Administrator.You can do this by triggering the start script go (UNIX) or go.bat (Microsoft Windows). Then,logon as the J2EE Engine administrator.

3. In the navigation bar, choose Cluster Server Services Monitoring, and then choose theGRMG Customizing tab page.

4. Select the scenario sap.com/com.sap.hcm.ls.webapps

5. Choose Upload.

Configuration Check

1. Check GRMG monitoring using the transaction GRMG in your central monitoring system.2. Navigate to Upload/Download Ask CCMS-Agent for an available of scenarios.

Due to hourly reports, it can take up to an hour from the upload of the XML file until themonitored availability data is available in the CCMS Monitor.

3. Choose the description LSCOP600 and the URL http://<host>:<port>/Ims/heartbeat from thescenario list.

4. Choose Start.

5. Start the Alert Monitor using the transaction RZ20 or choose CCMS Control/MonitoringAlert Monitor.

6. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.The activated scenario is displayed in the GRMG check available (Web-component) treestructure.

The GRMG scenario can only used by a J2EE administrator user.

Result

You have the configured the available monitoring for SAP Learning Solution Content Player.

Page 45: SOG_SAPERP60_SR3

Monitoring

45 Dezember 2009

3.5 Detailed MonitoringThe various monitors can be combined according to the selected system landscape. If SAP ECCServer and a BI system are operating one system, then only one monitor is required, for example,to monitor the SAP NetWeaver area.Application-specific monitors must be considered for each application, regardless of whether or notthe components are operating in one system (client).

3.5.1 Monitoring of SAP ABAP ComponentsYou can use the monitoring architecture of the Computing Center Management System (CCMS) tomonitor an SAP system landscape. The concept of the monitoring architecture is to provide allrequired information in a central monitoring system; this system is referred to in this documentation(irrespective of the actual system ID) as CEN.

Problems are displayed in the alert monitor of CEN as soon as they occur; all log files are alsoaccessible from a central location, which reduces the time for error identification and correction.Additional configuration steps allow advanced technologies such as automatic notifications,meaning that administrators no longer need to actively investigate systems for alerts.

Usage Type Monitoring information

Application Server ABAP help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0 (2004s)SAP Library SAP NetWeaver Library Administrator’s Guide Technical OperationsManual for SAP NetWeaver Administrationof SAP NetWeaver Systems ApplicationServer ABAP (AS ABAP) Monitoring

Business Intelligence (BI) help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0 (2004s)SAP Library SAP NetWeaver Library Administrator’s Guide Technical OperationsManual for SAP NetWeaver Administrationof SAP NetWeaver Systems BI (BusinessIntelligence) Administration

Process Integration (PI) help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0 (2004s)SAP Library SAP NetWeaver Library Administrator’s Guide Technical OperationsManual for SAP NetWeaver Administrationof SAP NetWeaver Systems PI (ProcessIntegration) Monitoring Systems PI(Process Integration) Monitoring

.

Page 46: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 46

3.5.1.1 Detailed Monitoring of SAP ERP ComponentsThis section provides detailed information on the monitoring requirements for ERP components.

SAP ECC Server

For SAP ECC Server no individual alert monitoring is required. However, when you use enterpriseextensions of SAP ECC Enterprise Extension Travel Management, SAP recommends that you testthe RFC, the Gateway, the Business Connector, and the XI connections to connected provider on aregular basis.Based on the technologies used by the content provider, SAP standard tools such as, CCMS orspecial Gateway control software can be used. In addition, you can also trace the content partnerconnections using standard SAP XML trace tools. If you plan to use Virtual Machine Container(VMC), see the SAP Note 863354.

SAP industry solution SAP Retail

There are several jobs to schedule so monitoring shall also capture the job status. Have a look atchapter 4.4 periodical tasks for the overview of the jobs to be run.

SAP industry solution SAP Banking

If you use SAP industry solution SAP Banking, then you have to notice the following for:

Business Partner for Financial Services (FS BP)

Data exchange CRMData is exchanged between the Business Partner for Financial Services and the businesspartner in CRM based on the Netweaver Exchange Infrastructure (XI) from Release CRM 5.0.For more information on Monitoring the Exchange Infrastructure, see SAP Help Portal athelp.sap.com Documentation SAP Netweaver Library SAP Netweaver by KeyCapability Process Integration by Key Capability SAP Netweaver Exchange Infrastructure

Integration Processes (ccBPM) Monitoring the Business Process Engine

Data exchange with customer / vendorData is exchanged between the Business Partner for Financial Services and the customer /vendor in ERP based on Customer/Vendor-Integration (CVI) from Release ERP 6.0.The integrated Post Processing Office (PPO) checks whether the required customer andvendors are updated correctly when creating and processing a business partner. This alsoapplies to mass processing.This function is located in the Synchronization Cockpit. You access the SynchronizationCockpit by selecting the following in Customizing: help.sap.com SAP ERP CentralComponent SAP ERP 6.0 SAP ERP Central Component Cross ApplicationComponents Master Data Synchronization

For more information about Customer/Vendor Integration (CVI), see SAP Help Portal athelp.sap.com SAP ERP Central Component SAP ERP 6.0 SAP ERP CentralComponent Cross Application Components Master Data Synchronization

SAP SEM

SAP SEM is an SAP NetWeaver add-on, so the majority of administration is performed using basicadministration. For more information, see:SAP Help Portal at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library System Administration Technical Operations Manual for

Page 47: SOG_SAPERP60_SR3

Monitoring

47 Dezember 2009

SAP NetWeaver Administration of SAP NetWeaver Systems Application Server ABAP (ASABAP) Monitoring

SAP Help Portal at help.sap.com SAP NetWeaver

Described below are the transactions and reports for SAP SEM-specific monitoring issues:

Transaction/report Used for

/BPS_STA0 Analysis of SEM application statistics datawritten by SEM./BPS_STAT1

/BPS_TRACE SEM application trace which you can recordand evaluate for specified end users

Report UC_STAT0 Evaluation of SEM-BCS statistics (see SAPNote 657098

SAP LSOFE (Front End)

You can use the transaction SLG1 Application Log: Display Logs to view errors that occur when thesystem communicates between non-ABAP components of the SAP Learning Solution and theback-end system (SAP ERP).

SRM Server

For information about SAP SRM, see:

SAP Help Portal at help.sap.com SAP Business Suite SAP Supplier Relationship ManagerSAP Architecture and Technology Administration System and Application Monitors.

SAP Service Marketplace at service.sap.com/srm

SAP Service Marketplace at service.sap.com/instguides SAP Business Suite Solutions SAP SRM Using SAP SRM Server 5.5 Solution Operations Guide: SAP Supplier RelationshipManagement

SAP cProject Suite

The communication between SAP cProject Suite and SAP SRM uses the usage type ProcessIntegration (XI). This means that the message monitor of XI contains a list of communication errors.You can solve these errors using built-in XI mechanisms. For queue monitoring, use the transactionSMQ1.

SAP E-Recruiting

Individual alert monitoring required for SAP E-Recruiting. In SAP E-Recruiting the application log(transaction SLG1) and the standard monitoring of SAP Web AS is used.

Page 48: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 48

More information on ERP specific monitoring can be found here:

Usage Type Monitoring information

Monitoring template for an ERP ABAP System(„ERP_ABAP“)

Download at service.sap.com -> softwaredownload -> Release & Upgrade Info ->Installation & Upgrade Guides -> SAP BusinessSuite Applications -> SAP ERP -> SAP ERP6.0 -> ERP Monitoring templates

Monitoring template for performance issues ofan ERP ABAP System (“ERP ABAPPerformance”)

Download at service.sap.com -> softwaredownload -> Release & Upgrade Info ->Installation & Upgrade Guides -> SAP BusinessSuite Applications -> SAP ERP -> SAP ERP6.0 -> ERP Monitoring templates

Monitoring of IS-Automotive help.sap.com SAP ERP SAP ERPCentral Component SAP Library SAPDiscrete Industries and Mill Products SAPfor Automotive Monitors

3.5.2 Database MonitoringDatabase monitoring is not only for a primary ABAP component, but it is essential for thefunctioning of all ABAP components.

A list of database monitoring documentation references is listed below:

Database Documentation ReferenceOracle help.sap.com SAP NetWeaver SAP NetWeaver 7.0

(2004s) System Administration Technical OperationsManual General Administration Tasks DatabaseAdministration Database Administration for Oracle

MS SQL Server help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration Technical OperationsManual General Administration Tasks DatabaseAdministration Database Administration for Microsoft SQLServer

IBM DB2 UDB for Linux, UNIXand Windows

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration Technical OperationsManual General Administration Tasks DatabaseAdministration Database Administration for IBM DB2 forLinux, UNIX and Windows

Max DB help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration Technical OperationsManual General Administration Tasks DatabaseAdministration Database Administration for Max DB

Page 49: SOG_SAPERP60_SR3

Monitoring

49 Dezember 2009

Database Documentation ReferenceDB2 UDB for z/OS help.sap.com SAP NetWeaver SAP NetWeaver 7.0

(2004s) System Administration Technical OperationsManual General Administration Tasks DatabaseAdministration Database Administration for DB2 UDB forz/OS

IBM DB2 Universal Databasefor iSeries

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration Technical OperationsManual General Administration Tasks DatabaseAdministration Database Administration for IBM DB2Universal Database for iSeries

The main CCMS tools for database administration are listed below:

Tool/Function Transaction DescriptionBackup log and status DB12 Enables you to check the status of database

backupsDBA Planning Calendar DB13 Allows you to automatically schedule and

execute database operations. For example, toperform database backups, update statistics,and database checks.

DBA Logs DB14 Enables you to access action logs created byBRSPACE, BRBACKUP, BRARCHIVE,BRCONNECT or an external program

Data Archivingadministration tool

DB15 Allows you to manage archived SAP datausing a systematic display function

Database System Check DB16 andDB17

Enables you to configure and check importantdatabase parameters to recognize criticaldatabase situations in time

Update Statistics DB20 andDB21

Allows you to configure the cost-basedoptimizer, and check and update optimizerstatistics

DB Operations Monitor DB24 Provides you with online monitoring ofdatabase operations, for example, databackups, database checks, and so on

Online Maintenance ofDatabase Parameters

DB26 Allows you to maintain details and history ofdatabase parameters

Maintaining DatabaseConnection Information

DBCO Enables you to maintain information aboutadditional, non-standard databaseconnections

Database PerformanceMonitor

ST04 Provides you with a detailed database ofperformance information and history

Page 50: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 50

3.5.3 Monitoring of SAP Java ComponentsThis section describes the monitoring information required for SAP Java Components. It is dividedinto the following subsections:

Java Monitoring and Management

Detail Monitoring for SAP ERP 6.0 Java Components

3.5.3.1 Java Monitoring and ManagementJava monitoring and management provides developers, supporters and customers with informationabout: Configuration, such as release, version, host and port Monitoring critical conditions for IT operations Detailed performance and status data to detect and diagnose problems Detailed statistics on activity and resource consumption for accounting and auditing, service

level agreement (SLA) reporting, and problem analysis

For more information about monitoring and management of ERP Java components, see SAPService Marketplace at service.sap.com/netweaver NetWeaver in Detail Solution Life-CycleManagement System Management Java Monitoring and Management.Detailed information can also be found on help.sap.com Documentation SAP NetWeaver

SAP NetWeaver 7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems Application Server Java (AS Java) Monitoring

3.5.3.2 Detailed Monitoring for SAP ERP 6.0 JavaComponents

Self-Service (XSS)For more information about XSS, see SAP Help Portal at help.sap.com Documentation SAP NetWeaver SAP NetWeaver 7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver Administration ofSAP NetWeaver Systems EP (Enterprise Portal)You can also investigate the dump log within the SAP ECC Server environment, using transactionST22.If SAP Employee Self Services is installed on a Java Standalone Server then you will have to positthat there is an ABAP central monitoring system somewhere in the vicinity where the monitordefinitions can be uploaded. Then the definitions will need to be tailored to see the data from theJAVA System ID (modification of the system rule in the monitor definition). Locally the Java data isof course visible in the Visual Admin.

SAP Extended E-Commerce Components (XECO)For specific scenario monitoring for XECO, see section 3.5.1 SAP E-Commerce in SAP ERP 6.0

Page 51: SOG_SAPERP60_SR3

Monitoring

51 Dezember 2009

SAP Biller DirectBiller Direct is a J2EE application, which is deployed with the SAP ERP 6.0 Java componentspackage.For more information, see SAP Service Marketplace at:service.sap.com/fscm SAP ERP 6.0 Financials SAP Financial Supply ChainManagement Media Library Documentation Biller Direct Solution Operations Guide SAPBiller Direct 6.0 or service.sap.com/erp-inst SAP ERP 6.0 Operations Operationsmanagement -> SAP Biller Direct

SAP LSOCP (Content player)The SAP Learning Solution does not implement or any specific monitoring tools, besides thestandard tools for monitoring.The content player can be monitored from SAP ECC Server using the heartbeat content playermonitoring (backend monitoring in CCMS).If you want to configure GRMG Monitoring for the SAP Learning Solution - Content Player, seesection 3.5.2 Example: Configuring GRMG Monitoring for the SAP Learning Solution - ContentPlayer.

3.6 Further InformationThis section includes additional information for monitoring, such as SAP Notes, web links, andrelated documents.

3.6.1 Monitoring SAP Notes

Check SAP Service Marketplace at service.sap.com/notes regularly to seewhich SAP Notes are available for the Solution Operations Guide.

SAP NoteNumber

Title Description

645971 EP 6.0 Supportability composite SAPNote

Supportability

636912 Frequent installation problems withSAP Java

Java connector

628962 How to switch on the SAP JCo trace Java connector

598891 Tools for analyzing SAP JCo and RFCerrors in Web AS

Java connector

657098 SEM-BCS: Performance statistics Task execution

746971 Activating JARM for the XI 3.0 adapterframework

J2EE Adapter Framework

777356 Long JARM measuring times in XIadapter framework

J2EE Adapter Framework

516920 Using JARM in the SAP J2EE engine Monitoring

863354 Operation VMC Operation

Page 52: SOG_SAPERP60_SR3

Monitoring

Dezember 2009 52

3.6.2 Monitoring Web LinksThe following information provides you with links to relevant documentation on SAP ServiceMarketplace and SAP Help Portal.

Type ofInformation

Quick Link/ Path Description

SAP SolutionManager

service.sap.com/instguidesSAP Components SAP SolutionManager Guides

Provides information aboutsystem infrastructure, scenarios,installation, and configuration ofSAP Solution Manager

SAP SolutionManager learningmaps

service.sap.com/rkt-solman orservice.sap.com/solutionmanager

Provides details on the learningmaps for SAP Solution Manager

General Informationon SAP SolutionManager

service.sap.com/solutionmanager

Provides general informationabout SAP Solution Manager

SAP NetWeaverMaster Guide

service.sap.com/instguidesNW70

Lists the SAP NetWeaver MasterGuide

Monitoring SetupGuide

service.sap.com/instguidesNW70

Lists the monitoring and setupGuide of SAP Solution ManagerDiagnostics

Solution ManagerDiagnostics

service.sap.com/diagnostics Describes the benefits andusage scenarios of SolutionManager Diagnostics

Monitoring service.sap.com/monitoring Provides additional informationabout monitoring

SAP NetWeaver service.sap.com/netweaver Provides additional informationabout SAP NetWeaver

Industry solution -SAP Retail

help.sap.com SAP ERP 6.0 SAP ERP 6.0 Central Component Logistics

Describes the jobs to monitor forthe industry solution, SAP Retail

Monitoring SAPLiveCache

help.sap.com Documentation SAP NetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAPNetWeaver Library Administrator’sGuide Technical Operations Manualfor SAP NetWeaver Administrationof Standalone Engines SAPliveCache-Technology Management

Information on SAP LiveCachemonitoring related periodicaltasks and tasks on demand aswell as database administrationin CCMS

ERP Monitoringtemplate TREX service.sap.com -> software

download -> Release & Upgrade Info -> Installation & Upgrade Guides ->SAP Business Suite Applications ->SAP ERP -> SAP ERP 6.0 -> ERPMonitoring templates

Location for download of theERP monitoring template forTREX usage

Page 53: SOG_SAPERP60_SR3

Monitoring

53 Dezember 2009

Type ofInformation

Quick Link/ Path Description

Monitoring TemplateERP J2EE

service.sap.com -> softwaredownload -> Release & UpgradeInfo -> Installation & UpgradeGuides -> SAP Business SuiteApplications -> SAP ERP -> SAPERP 6.0 -> ERP Monitoringtemplates

Monitoring TREX help.sap.com Documentation SAP NetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAPNetWeaver Library Administrator’sGuide Technical Operations Manualfor SAP NetWeaver Administrationof Standalone Engines Search andClassification (TREX) TasksPerformed Regularly Monitor TREX

SAP NetWeaver 7.0Technical OperationsManual

help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s)

System Administration TechnicalOperations Manual

Provides details on SAPNetWeaver TechnicalOperations

SAP SolutionManager

help.sap.com Documentation SAP Solution Manager

Provides additional functionalinformation about SAP SolutionManager

3.6.3 Monitoring DocumentsThe following information provides you with links to special documents.

Type ofInformation

Title Quick Link/ Path

SRMSolutionOperationGuide

Solution Operations Guide: SAPSupplier Relationship Management

service.sap.com/instguidesSAP Business Suite Applications SAP SRM SAP SRM Server 5.5 Solution Operations Guide – SRM 5.0

Page 54: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 54

4 Management of SAP TechnologySAP provides an infrastructure that allows your system administration team to administer SAPTechnology effectively. This section describes the related topics on the SAP application level:

Starting and stopping

Backup and restore

System copy

User management

High availability

Archiving

4.1 Starting and StoppingThe procedure for starting and stopping the SAP system depends on:The underlying operating system

The differences between the usage types, for example, the usage type Application Server ABAPversus usage type Application Server Java

In a distributed system landscape, the main difference between ABAP and Java isthat the system database is started automatically when you start the ApplicationServer (ABAP), which is not the same in case of the Application Server (Java).Additional components of SAP ERP 6.0 are not considered in this section.

4.1.1 Detailed Starting and StoppingIn the simplest case, an SAP system consists of only a database and a single application server.You can start and stop the SAP system and its database using operating system tools. There arespecial scripts available or you can use the appropriate program icons to do this. The details areexplained in the installation guides of the respective components.

Start and Stop Sequence

The start sequence of the entire system landscape depends on the applications used and thedistribution of the applications. The following usually applies to start the sequence:The systems that make data available, for example, SAP ECC Server or SAP BW must first bestarted, so that the data is already available at the start for subsequent systems that furtherprocess or display this data.

The sequential order must be reversed accordingly for the stop sequence.If you are using several applications in one instance, then when you start or stop oneapplication of this instance, the same action is performed for all other applications. This meansall applications for the instance start or stop running.

Page 55: SOG_SAPERP60_SR3

Management of SAP Technology

55 Dezember 2009

Resulting Dependencies

Listed below are the resulting dependencies based on the start and stop sequences describedabove:ABAP-based components and add-ons installed in the same instance start and stop in theadministration environment of SAP NetWeaver.

Java applications are started and stopped by starting and stopping the J2EE server.

Additional components such as the Business Connector have their own start and stopmechanisms.

For applications that contain several components, such as SAP Learning Solution and SAP SRM,you can find detailed descriptions in the relevant Guides for these applications.

4.1.1.1 Example: SAP Enterprise PortalThe SAP Enterprise Portal integrates and works with the following systems:A relational database management system (RDBMS)

An existing user storage mechanism, Users Persistence Storage, such as a directory service(LDAP). These systems are prepared before the portal is installed.

Usage type Application Server

Prerequisites

Before you stop or start components in the portal landscape, ensure the following:The portal runs without any issues.

You have administration rights and privileges to start and stop the processes of the components ofthe portal.

ProcessThe following table summarizes the sequence to stop and start components, and therecommended commands or tools to use for each component of the portal, in a UNIX environment.

Software Component SequenceStart Stop

User Persistence Store 1 3Portal system database(for example, Oracle)

2 2

JAVA instances of the SAP WebApplication Server

3 1

The numbers in the Sequence column indicate the order in which you stop or start the components.You must begin with the lowest number.For more information, see SAP Help Portal at help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver Administration ofSAP NetWeaver Systems EP (Enterprise Portal) Portal Management Starting andStopping

Page 56: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 56

4.1.1.2 Starting and Stopping SAP Notes

Check SAP Service Marketplace at service.sap.com/notes regularly to seewhich SAP Notes are available for the Solution Operations Guide.

SAP Note Number Title Description863354 Operation VMC Operation

4.1.1.3 Starting and Stopping Web LinksDocumentation Links: SAP Help PortalThe following table provides links to various related documentation.

Type of Information Quick Link/ Path Description

Adaptive Computing help.sap.com Documentation SAP NetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAPNetWeaver Library Administrator’sGuide Technical Operations Manualfor SAP NetWeaver Administrationof SAP NetWeaver Scenarios SAPNetWeaver Operations AdaptiveComputing Starting or StoppingApplication Services via AdaptiveComputing

Provides information abouthow to start or stop applicationservices using adaptivecomputing

Usage TypeApplication ServerJava

help.sap.comDocumentation SAPNetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of SAPNetWeaver Systems Application Server Java (ASJava) Administration Manual

J2EE Engine Startingand Stopping the J2EE Engine

help.sap.comDocumentation SAPNetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of SAPNetWeaver Systems

Page 57: SOG_SAPERP60_SR3

Management of SAP Technology

57 Dezember 2009

Type of Information Quick Link/ Path DescriptionApplication Server Java (ASJava) Management Tasks Starting and Stoppingthe SAP System

help.sap.comDocumentation SAPNetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of SAPNetWeaver Scenarios Enabling Application-to-Application Processes Tasks Starting and Stopping

Usage TypeEnterprise Portal (EP)

help.sap.comDocumentation SAPNetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of SAPNetWeaver Systems EP(Enterprise Portal) Portal Management Starting andStopping

help.sap.comDocumentation SAPNetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of SAPNetWeaver Systems Application Server Java (ASJava) Administration Manual

J2EE Engine Startingand Stopping the J2EE Engine

Usage Type ProcessIntegration (XI)

help.sap.comDocumentation SAPNetWeaver SAP NetWeaver

SAP NetWeaver TechnicalOperations Manual Administration of SAP

Page 58: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 58

Type of Information Quick Link/ Path DescriptionNetWeaver Systems PI(Process Integration) Management Starting andStopping

help.sap.comDocumentation SAPNetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of SAPNetWeaver Scenarios Enabling Application-to-Application Processes Tasks Starting and Stopping

Usage TypeDevelopmentInfrastructure(DI)

help.sap.comDocumentation SAPNetWeaver SAP NetWeaver7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of SAPNetWeaver Systems Technical Operations Manualfor the SAP J2EE Engine System Landscape Directoryand Name Service Administrative tasks Startand stop the SLD service

Search andClassification (TREX)

help.sap.comDocumentation SAPNetWeaver SAPNetWeaver 7.0 (2004s)SAP Library SAPNetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of StandaloneEngines TREX Startingand Stopping TREX

SAP LiveCache help.sap.comDocumentation SAPNetWeaver SAP NetWeaver

Page 59: SOG_SAPERP60_SR3

Management of SAP Technology

59 Dezember 2009

Type of Information Quick Link/ Path Description7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver Administration of StandaloneEngines SAP liveCache-Technology ManagementTasks on Demand

4.1.1.4 Starting and Stopping DocumentsDocumentation Links: SAP Service MarketplaceThe following table provides a list of special documents for starting and stopping SAP systems.

Type of Information Title Quick Link/ PathUsage Type ApplicationServer ABAP

Installation or UpgradeGuide

service.sap.com/erp-instSAP ERP 6.0 NetWeaverComponents Installation or UpgradeGuide

SAP ECC Installation or UpgradeGuide

service.sap.com/erp-instSAP ERP 6.0 SAP ECC Installation or Upgrade Guide

SRM Server Solution OperationsGuide: SAP SupplierRelationshipManagement

service.sap.com/instguidesSAP Business Suite Solutions SAPSRM Using SAP SRM Server 5.5 Solution Operations Guide: SAPSupplier Relationship Management

SAP FSCM (Biller Direct) Solution OperationsGuide for SAP BillerDirect 6.0

service.sap.com/fscm SAPERP 6.0 Financials SAP FinancialSupply Chain Management MediaLibrary Documentation BillerDirect Solution Operations GuideSAP Biller Direct 6.0 orservice.sap.com/erp-instSAP ERP 6.0 Operations Operationsmanagement SAP BillerDirect

Page 60: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 60

4.2 Backup and RecoveryPurpose

Backup saves important business data of your company. Regular backups keep the downtime ofthe system landscape to a minimum during restoration of the infrastructure and business data.The decision for a suitable backup concept must be made at the top management level within thecompany. The backup concept must be worked out in the implementation phase. The goal is tohave a functional specification that records the requirements. Corporate framework conditionsdetermine the contents of the backup concept, such as: System Information: Requests, degree of high availability, backup and recovery times,

maximum downtime, and so on Costs Involved: How much does downtime cost? How much does the relevant backup or

recovery procedure cost? Scope of Implementation: Which jobs in the company must be included in the decision-making

process?

Backup and Recovery - SAP Systems

Unlike SAP R/3 systems, the SAP Business Suite uses several SAP component systems toimplement cross-system processes. Data is no longer held centrally in a single SAP system;instead, it is distributed between several SAP components.Due to the non-transactional character of the document workflow between the different landscapecomponents involved within one ERP Business Scenario, it is impossible to find a common point ofconsistency across the whole ERP landscape. A distributed business system landscape thereforerequires a detailed Backup and Recovery concept. This concept must account for both thebusiness data, which is contained in databases, and the runtime infrastructure.For more detailed information about the technology, methods and standards used, see SAP HelpPortal at help.sap.com Documentation SAP NetWeaver SAP NetWeaver 7.0 (2004s)SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manualfor SAP NetWeaver

The information in the Technical Operations Manual assumes that you are familiarwith database and administration and therefore does not explain, for example, how tobackup an RDBMS system. If you have questions, contact your IT staff and refer tothe operation manuals provided by your database and operating system vendors.

General Recommendations

You must regularly test your backup and recovery concept. A single backup and recovery test isinsufficient, since the ERP landscape is likely to change and render a given concept redundant.System administrators need an up-to-date Backup and Recovery concept to restore failed systems.SAP recommends that you perform a backup:After the initial installation and configuration of the system landscape

After specific changes, such as changes to the configuration, software upgrade of individualcomponents, or replacement of components made to the system landscape. This of coursedepends on the frequency of such changes.

SAP recommends that you backup the runtime infrastructure of all the components ofthe ERP landscape.

Page 61: SOG_SAPERP60_SR3

Management of SAP Technology

61 Dezember 2009

When you decide which infrastructure components to backup, consider the following factors: Time required for a complete reinstallation Time required for additional configuration Effects of the expected downtime of one or more infrastructure components with regard to

the overall availability of the ERP landscape

A backup process must ensure:

Logical consistency

Restores the ERP system landscape (cross-system data consistency) to a consistent status:The restoration applies at document level at the time of the backup. This includes the successfulrollback of all open business transactions with respect to the exchange of documents.

Physical consistency:Restores individual ERP components to a consistent state, followed by a successful start-up of the restored components, and a successful reconnection to other components.Physical consistency provides a working runtime environment in which newly createdbusiness documents can be exchanged. This is required to develop a transactional conducton user level to react to broken workflows and outdated documents appearing after therestoration.

Recommendations - Backup of Individual Components in the SAP ERP 6.0Landscape

You need to backup your individual components regularly to ensure that you can restore andrecover them if there is a system failure.

You should not use a backup and restore concept for your entire system landscape and singlesystem components just for SAP systems. It should be embedded in all business requirements andtake into account the entire process flow in your enterprise.

Consistency Technology

With the Business Suite, SAP introduces standard business processes, which not only work on thedata of one system, but which uses components of several distributed SAP systems. A SAPBusiness Suite process may start in one system and continue to read or manipulate data in othersystems of a federated system landscape.While this distribution offers advantages with respect to performance, security and load distribution,some tasks like backup or system copy become more demanding than with a single standalonesystem. While it is no problem to create a consistent image of the entire system landscape, if allsystems can be brought down for the backups, this will become a challenging task to performduring online operations.Consistency Technology solves this problem, by allowing you to create a consistent image (orconsistent copy) of a federated system landscape without taking the systems offline. The two typesof consistency technologies available are:

Coordinated database suspensionBy suspending write input and output (I/O)) operations of all database systems during the sameshort period of time, a synchronization point (sync point) can be achieved. A copy of the complete

Page 62: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 62

system landscape taken during this short period, for example with a fast copy storage technology,such as split-mirror or snapshot, represents a consistent image of the complete landscape.

Consistent split technology on a storage levelConsistent Split is a new technology on a storage level. It was originally introduced for maintainingconsistency of a remote mirror in case of rolling disasters. This storage-based technology allowsyou to group arbitrary storage volumes, and even possibly volumes on different storage systems,into a Consistency Group. Consistent Split allows you to split a local or remote mirror of thisconsistency group simultaneously to form a consistent copy for all these volumes. This can bedone without any intervention on application or database level. The copy will be consistent becauseinput and output (I/O) on all volumes is suspended at exactly the same point in time.

4.2.1 Detailed Backup and RecoveryWhen you plan a backup and recovery strategy for application, software, and configuration files,you must consider the following elements: Operating system Database data files Database software SAP software and file systems Log files (SAP and others) Software of other system components (file systems and configuration files)

A component that has application data (a database, for example) usually comprises applicationsoftware and configuration files (runtime infrastructure) that need a backup as well. A component,which contains no application data, may comprise configuration files and software that require abackup.The following table lists various categories of system components and details the necessary datathat needs backup or needs to be restored in each category.

Category ofSystemComponents

CategoryDescription

Data for Backup andRecovery

Example – SystemComponents

I Software only, noconfiguration orapplication data

Data: If data does not exist,then no data backup is required

Software: No backup isnecessary

Software configuration: Nobackup is necessary

Log files: Backup necessary

After a system crash,restoration of initial softwarebackup or a new installationis necessary.

BDoc Modeler

Page 63: SOG_SAPERP60_SR3

Management of SAP Technology

63 Dezember 2009

Category ofSystemComponents

CategoryDescription

Data for Backup andRecovery

Example – SystemComponents

II Software andconfigurationinformation only,no applicationdata

Data: If data does not exist,then no data backup is required

Software: No backup isnecessary.

Software configuration: Nobackup is necessary

Log files: Backup is required

After a system crash, youcan use any of thescenarios to restore youcomponent:

Perform a newinstallation andconfiguration

Restore the backupafter configuration

Communication Station

SAP BusinessConnector

SAP Internet and PricingConfigurator (IPC)

III Replicatedapplication dataonly, where thereplication time issufficient for arestore

Data: No data backup required

Software: Backup is necessary

Software configuration: Backupis required

Log files: Backup is required

SAP Index ManagementService (IMS) / SearchEngine

SAP IPC

Web server

SAP Internet TransactionServer (ITS)

IV Replicatedapplication dataonly. Data notmanaged byRDBMS

Data: Backup the application-specific file system

Software: Backup is necessary

Software configuration: Backupis necessary

Log files: Backup is required

We recommend a backupbecause the replication timeis long.

IMS / SearchEngine

Web server

Page 64: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 64

Category ofSystemComponents

CategoryDescription

Data for Backup andRecovery

Example – SystemComponents

V Replicatedapplication dataonly. Datamanaged byRDBMS.

Data: Backup the database andthe log

Software: Backup is necessary

Software configuration: Backupis necessary

Log files: Backup is required

We recommend a backupbecause the replication timeis long.

SAP IPC

VI Originalapplication dataon a standalonesystem, wherethe data is notmanaged by aRDBMS

Data: Backup the application-specific file system

Software: Backup is necessary

Software configuration: Backupis necessary

Log files: Backup is required

Web server

VII Originalapplication dataon a standalonesystem, wherethe data ismanaged by aDBMS and is notbased on SAPWeb AS

Data: Backup the database andthe log

Software: Backup is necessary

Software configuration: Backupis necessary

Log files: Backup is necessary

VIII Originalapplication dataon a standalonesystem, which isbased on SAPWeb AS

Data:

Backup the database andthe log

Backup the application log,for example, backup joblogs in the file system

Software: Backup is necessary

Software configuration: Backupis necessary

Log files: Backup is required

Standalone SAP

SAP ERP 6.0

Page 65: SOG_SAPERP60_SR3

Management of SAP Technology

65 Dezember 2009

Category ofSystemComponents

CategoryDescription

Data for Backup andRecovery

Example – SystemComponents

IX Originalapplication data,where the data isexchanged withother systems isnot managed bya DBMS

Data: Backup the application-specific file system

Before the backup process,you must take the dataconsistency with othersystems into account

Software: Backup is necessary

Software configuration: Backupis necessary

Log files: Backup is required

X Originalapplication data,where the data is:

Exchanged withother systems

Is managed by aDBMS

Not based onSAP Web AS

Data: Backup the database andlog

Before the backup process,you must take the dataconsistency with othersystems into account

Software: Backup is necessary

Software configuration: Backupis required

Log files: Backup is necessary

SAP liveCache

Workbench

XI Originalapplication data,where the is dataexchanged withother systemsand is based onSAP Web AS

Data:

Backup the database andlog

Backup the application log,for example, the job logs infile system

Before the backup process,you must take the dataconsistency with othersystems into account

Software: Backup is necessary

Software configuration: Backupis necessary

Log files: Backup is required

SAP ERP

SAP CRM

SAP APO

SAP BW

Backup and Recovery – SAP systems

Page 66: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 66

The following table lists the various ERP components, which require a backup and recovery if anRDBMS or SAP Application Server is involved.

ERP ComponentBackup and Recovery

RDBMS SAP ApplicationServer ABAP

SAP Application ServerJava

Usage Type Application ServerABAP

Yes Yes No

Usage Type Application ServerJava

Yes No Yes

Usage Type BI Yes Yes YesUsage Type EP Yes Yes YesUsage type PI Yes Yes YesUsage Type DI Yes No YesKnowledge Management No No NoTREX 7.0 No No NoSAP ECC 6.0 Yes Yes NoSAP XSS 6.0 No No Yes (Web Dynpro)SAP SEM 600 Yes Yes NoSAP XECO 5.0 No No NoSAP FSCM 6.0Biller Direct

No No Yes

SAP FSCM 600Finbasis

Yes Yes No

SAP LSO 600 Yes Yes YesSAP SRM 5.0 Yes Yes NoSAP cProject Suite 4.00 Yes Yes NoSAP Workforce ManagementCore 2.0

Yes Yes No

SAP E-Recruiting 6.0 Yes Yes NoSAP GUI 6.20 No No No

The following sections describe specific information about the various elements you must consider,such as, the operating system used, the database software, and so on, when you plan a backupand recovery strategy for application, software, and configuration files.

4.2.1.1 Operating System, Software and Configuration Data

Apart from business-critical application data (generally held in databases), you can also backup thesystem and application software (including configuration files). If you do this, you do not have toreinstall the system and application software if the software becomes damaged.It is always possible to reinstall the operating system, software, and configuration data. However,reinstallation and configuration can take a long time. Therefore, if a backup of the software andconfiguration is available, you can reduce the time needed to restore your system after a systemfailure.

Online BackupThe data contained in the database can be backed up online; however, it is not possible to do thesame for the runtime infrastructure. An online backup refers to the system landscape and not thedatabases that contain the business-critical application, or the infrastructure components.

If you perform a backup while the server is running, open files may not be backed up.

Page 67: SOG_SAPERP60_SR3

Management of SAP Technology

67 Dezember 2009

File System Backup versus Full System Backup

A file system backup only applies to specific files or files systems, whereas a full system backupapplies to all files and file systems, including the operating system.

After installation of new software components, certain entries in the configuration files of theoperating system cannot be found in the file systems in which the software installation occurred.SAP therefore recommends that you perform a full system backup after installation, and that youbackup the file systems of the installed software and the operating system on a regular basis.

For more information concerning possible backup scenarios, see SAP Service Marketplace atservice.sap.com/atg Advanced Technology Group Backup & Restore Documentation

4.2.1.2 DatabaseSAP recommends that you:

Run the database in archive modeThis means that all actions on the database that modify data are recorded by the database andwritten to a transaction log. With regular full backups of your database (either offline or online), aswell as a complete set of transaction logs since the last backup, it is possible to restore a crasheddatabase to any point in time before the database crashed.

Backup your database every daySince the log files fill up, you must perform several backups of the log files during the day.For more information, see SAP Help Portal at help.sap.com Documentation SAP NetWeaver

SAP NetWeaver 7.0 (2004s) SAP Library SAP NetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems Application Server ABAP (AS ABAP) Management Backup and Recovery Database

Administration <Database Name>.

4.2.1.3 SAP ERP 6.0 ABAP ComponentsSpecific backup and recovery issues for ABAP components in SAP ERP 6.0 are described in thefollowing list:

SAP Industry Solution BankingIf you use SAP industry solution SAP Banking, then you have to notice the following for:

SAP Business Partner for Financial Services (FS BP)If you use SAP Business Partner for Financial Services (FS BP), then you have to noticethe following:In the standard system, the Business Partner for Financial Services uses the existingarchiving function (transaction SARA). You use the archiving object CA_BUPA to archiveall business partners that are flagged for archiving and the relevant master data.You can only set the archiving indicator and archive a business partner if there are noactive contract objects or change document objects, which means these have already beenarchived.

Page 68: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 68

The set residence times must have expired as well. You can set the residence times inCustomizing under SAP Business Partner for Financial Services Settings for FinancialServices Tools Archiving. The system checks these before the archiving indicator isset.You set the archiving indicator in the dialog box on the Status tab page or using thetransaction BUPA_PRE_DA.For more information on archiving, see SAP Help Portal at help.sap.comDocumentation SAP ERP 6.0Central Component Financials SAP Banking SAPBusiness Partner for Financial Services Functions Archiving

Loans Management (FS CML)For more information on archiving for SAP Loans Maangement, see SAP Help Portal athelp.sap.com Documentation SAP ERP 6.0 SAP ERP 6.0Central ComponentRelease 6.0 SAP ERP 6.0Central Component Financials SAP Banking LoansManagement Position Management Periodic Processing Archiving

SAP SEMSAP SEM does not store its own data, but it uses the data storage of the usage type BI.

If SEM is operating on the same system as a BI system than for more information, see the usagetype BI.

If SAP SEM is installed on a different system than the BI system, then SAP SEM must be savedappropriately.

SRM ServerThe only backup type that can guarantee full physical and logical consistency of an SRMlandscape would be an offline backup of the whole landscape. This however, should be doneafter all business users have logged off and the complete business workflow has ended. Toolsthat offer such monitoring of these tasks do not exist yet.You must regularly test your Backup and Recovery concept. A single Backup and Recoverytest is insufficient, since the SRM landscape is likely to change and render a given conceptredundant.

SAP cProject SuiteDocuments, Material, BOMs, MPNs, iPPE Objects

If you lose data in cFolders, it is possible to synchronize the data from the backend system tocFolders using transactions cfe01, cfe02 and cfe03.

In case you lose data in the backend system, you can adjust them by using transactions cfi01, cfi02and cfi03. Data that is changed in cFolders will be transferred to the backend system. All other datais from the backend system.

Virtual Room IntegrationIf you lose data in SAP Enterprise Portal, you must regenerate the relationship in the CollaborationRoom to the cFolders Collaboration manually.

If you lose data in cFolders (Collaboration), the connection to the target (Portal) is lost. Therefore,the empty connection must be deleted manually.

SRM IntegrationIf you back up your SRM system and you lose Shopping Carts in the SRM system, which wereconnected to a cFolders Collaboration, you have to regenerate the Shopping Carts in your cFolderCollaboration.

Page 69: SOG_SAPERP60_SR3

Management of SAP Technology

69 Dezember 2009

If you back up cFolders and you lose cFolders Collaborations, create them again. The connectionbetween the cFolders Collaboration and the Shopping Carts must be regenerated.

SAP E-RecruitingSAP E-Recruiting uses the standard SAP methods of Backup and Recovery. The Backup andRestore concept for SAP E-Recruiting consists of two parts:

Backup and Restore for each component

Cross-system data dependencies and handlingIn addition, the backup concept must cover disaster recovery processes such as loss of thedata center due to fire. In this context, the most important thing to ensure is that backupdevices are not lost as well as normal data storage (by separating storage locations).Based on the type of application data a component holds, you can analyze the backuprequirements of any system component using the categorization scheme for systemcomponents. This allows you to determine an appropriate backup method for the component.

4.2.1.4 SAP ERP 6.0 Additional ComponentsSpecific backup and recovery issues for additional components in SAP ERP 6.0 are described inthe following list:

SAP LSOAE (Authors environment)The Authors Environment stores session data on your PC. These are intermediate results fromyour actual session. Only saved data will be stored in the SAP Knowledge Warehouse; incompletesession data from your actual session will be lost.

4.2.2 Further InformationThis section includes additional information for backup and recovery, such as SAP Notes, weblinks, and related documents.

4.2.2.1 Backup and Recovery SAP Notes

Check SAP Service Marketplace at service.sap.com/notes regularly, to seewhich SAP Notes are available for the Solution Operations Guide.

SAP NoteNumber

Title Description

438820 Point-in-time recovery in the ALEenvironment

Basis components

434645 Point-in-time recovery: prevention andeffects

Basis components

434647 Point-in-time recovery in an SAPsystem group

Basis components

Page 70: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 70

4.2.2.2 Backup and Recovery Web LinksThe following table provides a list of related links for Backup and Restore.

Type ofInformation

Quick Link/ Path Description

Backup and Restorefor SAP BusinessSuite

service.sap.com/solutionmanagerbpTopic Area (right frame) Backup and

Restore for SAP Business Suite

This is a Best Practicesguide to guide you increating a well-designedbackup and restoreconcept to securebusiness-criticalapplication data andincrease systemavailability.

It enables you to fulfillauditing demands andservice level agreements,and helps you to reduceplanned and unplanneddowntime.

Usage TypeApplication ServerABAP

help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems

Application Server ABAP (AS ABAP) Management Backup and Recovery Database Administration

Usage Type BusinessIntelligence (BI)

See Usage Type Application Server ABAP

Usage Type ProcessIntegration (XI)

help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems

PI (Process Integration) Management Backup/Restore and Recovery

Usage TypeApplication ServerJava

help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems

Application Server Java (AS Java) Management Tasks Backing Up andRestoring SAP Web AS Java

Usage Type help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0

Page 71: SOG_SAPERP60_SR3

Management of SAP Technology

71 Dezember 2009

Type ofInformation

Quick Link/ Path Description

Enterprise Portal (EP) (2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems

EP (Enterprise Portal) Portal Management Backup/Restore andRecovery

help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems

EP (Enterprise Portal) Collaboration Management System Handling Backingup and restoring data Backup/Restore andRecovery

Usage Type ProcessIntegration (XI)

help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems

PI (Process Integration) Management Backup/Restore and Recovery

Usage TypeDevelopmentInfrastructure (DI)

help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems

DI (Development Infrastructure) Backing up and Restoring the NWDI

Search andClassification(TREX)

help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of Standalone Engines Search and Classification (TREX) TasksPerformed Regularly Data Backup andRestore for TREX

Page 72: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 72

Type ofInformation

Quick Link/ Path Description

SAP LiveCache service.sap.com/scm SAP SCMTechnology Backup and data consistency

help.sap.com Documentation SAPNetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of Standalone Engines SAP liveCache-Technology Management Tasks on Demand

4.2.2.3 Backup and Recovery DocumentsThe following table provides a list of special documents for backup and recovery of SAP systems.

Type of Information Title Quick Link/ PathSAP liveCache Backupand Restore

Backup and DataConsistency

service.sap.com/scm SAPSCM Technology Backup anddata consistency

SRM Solution Operations Guide:SAP Supplier RelationshipManagement

service.sap.com/instguides SAP Business Suite Solutions SAP SRM Using SAP SRM

Server 5.5 Solution OperationsGuide: SAP Supplier RelationshipManagement

Biller Direct service.sap.com/fscm SAPERP 6.0 Financials SAPFinancial Supply ChainManagement Media Library Documentation Biller Direct Solution Operations Guide SAPBiller Direct 6.0

4.3 System CopyPurpose

Companies are constantly confronted with an ever more rapid growth in application landscapes.This growth often requires changes to operating systems and databases. You can perform asystem copy or a migration at various stages in your application life cycle.You create a copy of your database instance, for example, to set up a standby database or for testor development purposes. This allows you to keep the contents of your database up-to-date.Creating system copies also allows you to start operating the standby instance immediately if youexperience problems with the original instance. This enables the business to carry on workingwithout any lengthy period of downtime.

Features

Page 73: SOG_SAPERP60_SR3

Management of SAP Technology

73 Dezember 2009

There are two types of system copies:Homogeneous System Copy: Both, the operating system and the database system stay thesame during a system copy.Heterogeneous System Copy: One of the following is changed during a system copy:

Operating system: In this case, the system copy is called OS migration, Database system: In this case, the system copy is called DB migration. Operating system and database system: In this case, the system copy is called OS/DB

migration.

For more information, see SAP Service Marketplace at service.sap.com/osdbmigration.

System Copy of SAP Systems

Besides the procedures provided by SAP, there may be other methods such as methods offered byhardware partners, which are used to replicate existing SAP systems.SAP systems copied or migrated with such methods are still supported by SAP, but no support isprovided by SAP for non-SAP procedures. Instead, the corresponding supplier of the procedure, forexample, the hardware partner is in charge of providing support for the non-SAP procedure.

SAP recommends that you perform a system copy if you are planning to set up a testsystem, demo system, or training system.

Procedure

You can copy a mixed ABAP Stack and Java Stack system in a single operation, not juststandalone ABAP or Java systems.

When you perform a system copy, all customizing and software units or usage types in the sourcesystem are copied to the target system.

This means that none of the software units or usage types in the target system can be excludedfrom the system copy, or can you select software units or usage types.

You can perform a Unicode conversion as a part of a homogeneous or heterogeneous systemcopy.

This means your SAP system is converted from non-Unicode to Unicode. This requires specialtasks in front of the system copy. If you want to perform the system copy of a Unicode system,where the source and target systems are Unicode systems, the same procedures can be used asfor copying non-Unicode systems.

For more information, see: SAP Notes 548016, Conversion to Unicode and 79991, Multi-Language and

Unicode support of SAP applications SAP Service Marketplace at service.sap.com/unicode SAP Service Marketplace at service.sap.com/unicode@sap

Page 74: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 74

4.3.1 Detailed System CopyFor more information about homogeneous and heterogeneous system copy for SAP Systemsbased on SAP NetWeaver 7.0 (2004s)(ABAP only, Java only, Double-stack (ABAP+Java)) i.g. SAPERP 6.0, SAP SRM 5.0, SAP CRM 5.0, SAP SCM 5.0. see SAP Note 870863.

4.3.1.1 SAP ERP 6.0 ABAP ComponentsSpecific system copy issues for ABAP components in SAP ERP 6.0 are described in the followinglist:

SAP ECC ServerSAP recommends that you go through the Implementation Guide (IMG) for the configuration ofthe content provider after a system copy. If necessary, these entries must be adjusted.

SAP LSOFE (Front End)After a system copy, SAP recommends that you go through the IMG and if necessary, adjustthe entries for the: Configuration of the content player (LSOCP

Connection to the Front end component (LSOFE)

Connection to the content management system

SAP cProject SuiteAfter creating a system copy of cProjects, there are two references to the same SRM shoppingcart. Both references are valid. However, the XI connection between cProjects and SRM mustbe adjusted to the system copy, so that SRM callbacks reach the copy.If you create an SRM system copy and the process continues in both the original and thecopied system, this can lead to the creation of two purchase orders for materials or resources.

If system-dependent data changes, see SAP Note 762610.

SAP E-RecruitingSAP recommends that you go through the chapter Technical Settings in the IMG and check therelevant entries, after you perform a system copy.For more information, see SAP Note 642115 - Minimum configuration of SAP E-Recruiting.

Page 75: SOG_SAPERP60_SR3

Management of SAP Technology

75 Dezember 2009

4.3.1.2 SAP ERP 6.0 JAVA ComponentsSpecific system copy issues for Java components in SAP ERP 6.0 are described in the followinglist:

SAP LSOCP (Content player)After a system copy, SAP recommends that you go through the IMG and if necessary, adjust theentries for the:

Configuration of the content player (LSOCP)

Connection to the Front end component (LSOFE)

Connection to the content management system

4.3.2 Further InformationThis section includes additional information such as, SAP Notes, web links, and related documentsfor system copy.

4.3.2.1 System Copy SAP Notes

Check SAP Service Marketplace at service.sap.com/notes regularly to seewhich SAP Notes are available for the Solution Operations Guide.

SAP NoteNumber

Title Description

771209 NW04: System copy (supplementarynote)

Basis system and installation

151603 Copying an SQL Server database Microsoft SQL Server

130906 How can versions be transported? Workbench/Customizing Organizer

548016 Conversion to Unicode DB/OS migrations

709140 Recommended JDK and VMSettings for the WebAS630/640

Java Application Server

82478 R/3 OS/DB migration Technical core competence

785848 Hom./Het.System Copy SAP WebAS 6.40 SR1 Java

Installation tools

713685 Hom./Het.System Copy SAP WebAS 6.40

Installation tools

184447 Building a BW-system landscape Source systems

82478 R/3 OS/DB migration Technical core competence

548016 Conversion to Unicode DB/OS migrations

857081 Unicode-Konvertierung: Schätzungder Stillstandszeit (UnicodeConversion: Estimate of theDowntime)

Unicode

762610 System-dependent data is changed Collaboration folders

Page 76: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 76

SAP NoteNumber

Title Description

642115 Minimum configuration of SAP E-Recruiting

E-Recruiting

325525 Copying and renaming systems in aBW environment

Source systems

184447 Building a BW-system landscape Source systems

210564 Copying a complete APO system liveCache applications

457425 Homogenous liveCache copy usingbackup/restore

liveCache

816730 BI-enqueueserver based on SAPliveCache

liveCache applications

816730 BI-enqueueserver based on SAPliveCache

liveCache applications

79991 Multi-Language and Unicode supportof SAP solutions

Internationalization (I18N)

870863 Hom./Het.System Copy SAPNetWeaver 2004s

System Copy SAP NetWeaver 2004s

888718 NW 2004s: Copy Usage EP System Copy SAP NetWeaver 2004s

4.3.2.2 System Copy Web LinksDocumentation Links – Service Marketplace

Type of Information Quick Link/ Path Description

SAP system releasesbased on SAP ERP

service.sap.com/instguidesSAP Components SAP R/3Release<…> R/3 Heterogeneous /Heterogeneous System Copy

Provides information onSAP ERP 6.0basedsystems

SAP system releasesbased on SAP R/3Enterprise

service.sap.com/instguidesSAP Components SAP R/3Enterprise SAP R/3 Enterprise Core4.70 <Release> System Copy SAPSystems Based on SAP Web AS<Release>

Provides information forSAP R/3 Enterprise basedsystems

SAP system releasesbased on SAP WebApplication Server 6.30 orearlier

service.sap.com/instguidesSAP Components SAP WebApplication Server SAP WebApplication Server <Release>System Copy SAP Systems Based onSAP Web AS <Release>

Provides information forSAP Web ApplicationServer 6.30 or earlierbased systems

SAP system releasesbased on SAP NetWeaver04s

service.sap.com/instguidesNW04 Release 04 Installation SAP

Web AS SAP Web AS 6.40 / SAPWeb AS 6.40 SR1 and RelatedInformation Homogeneous andHeterogeneous System Copy

Describes SAP NetWeaver04s based systems

System Copy andMigration

service.sap.com/systemcopy Provides information aboutsystem copy

Page 77: SOG_SAPERP60_SR3

Management of SAP Technology

77 Dezember 2009

Type of Information Quick Link/ Path Description

OS/DB Migration service.sap.com/osdbmigration

and

Media Library SAP OS/DB MigrationPlanning Guide

Describes the OS/DBmigration

OS/DB Migration service.sap.com/migrationkey Provides information aboutthe migration key.

If you change theoperating system or thedatabase system duringthe copy (heterogeneoussystem copy), you need amigration key.

JRE versions check service.sap.com/platformsProduct Availability Matrix SAPNetWeaver SAP NetWeaver 04 JSE Platforms

Provides information onthe JRE versions releasedfor SAP Web AS and forSAP systems

Advanced TechnologyGroup

service.sap.com/atg AdvancedTechnology Group System Copy

Provides information aboutthe Advanced TechnologyGroup

Unicode conversations service.sap.com/unicode Describes Unicode andimplementing Unicode.

Implementing the Unicodestandard enables a singlesoftware product or asingle web site to beaccessed across multipleplatforms, languages, andcountries without the needfor re-engineering.

Unicode service.sap.com/unicode@sap Provides information aboutUnicode at SAP

Usage Type ApplicationServer ABAP

help.sap.comDocumentation SAPNetWeaver SAPNetWeaver 7.0 (2004s)SAP Library SAPNetWeaver Library Administrator’s Guide Technical OperationsManual for SAPNetWeaver GeneralAdministration Tasks System Copy

Usage Type BusinessIntelligence (BI)

SAP Notes 325525 and 184447 help.sap.comDocumentation SAPNetWeaver SAPNetWeaver 7.0 (2004s)SAP Library SAPNetWeaver Library

Page 78: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 78

Type of Information Quick Link/ Path DescriptionAdministrator’s GuideTechnical OperationsManual for SAPNetWeaver Administration of SAPNetWeaver Systems BI(Business Intelligence) Administration

Usage Type ProcessIntegration (XI)

help.sap.comDocumentation SAPNetWeaver SAPNetWeaver 7.0 (2004s)SAP Library SAPNetWeaver Library Administrator’s Guide Technical OperationsManual for SAPNetWeaver Administration of SAPNetWeaver Systems PI(Process Integration) Management

Usage Type ApplicationServer Java

help.sap.comDocumentation SAPNetWeaver SAPNetWeaver 7.0 (2004s)SAP Library SAPNetWeaver Library Administrator’s Guide Technical OperationsManual for SAPNetWeaver GeneralAdministration Tasks System Copy

Usage Type EnterprisePortal (EP)

SAP Note 888718 help.sap.com Documentation SAPNetWeaver SAPNetWeaver 7.0 (2004s)SAP Library SAPNetWeaver Library Administrator’s Guide Technical OperationsManual for SAPNetWeaver Administration of SAPNetWeaver Systems EP(Enterprise Portal)

Page 79: SOG_SAPERP60_SR3

Management of SAP Technology

79 Dezember 2009

4.3.2.3 System Copy DocumentsDocumentation Links – SAP Service Marketplace

Type of Information Title Quick Link/ PathSAP system releases Homogeneous and

Heterogeneous System Copyfor SAP Systems Based onSAP NetWeaver ‘04s

service.sap.com/instguidesNW2004sHomogeneous andHeterogeneous System Copyfor SAP Systems Based onSAP NetWeaver ‘04s

SAP liveCache System Copyinformation

Installation, Upgrade,Migration, System Copy,Client Dependencies

service.sap.com/scmSAP SCM Technology Installation, Upgrade,Migration, System Copy,Client Dependencies

SAP liveCache System CopyGuides

System Management /Solution Operations Guide

service.sap.com/scmSAP SCM Technology System Management /Solution Operations Guide

SRM Solution Operations Guide:SAP Supplier RelationshipManagement

service.sap.com/instguides SAP Business SuiteSolutions SAP SRM Using SAP SRM Server 5.5

Solution Operations Guide:SAP Supplier RelationshipManagement

4.4 Periodic tasksThis chapter describes all tasks required to run periodically in oder to keep the application runningsmoothly over time. Such tasks may be required on component level and are therefore relevant foreach scenario that uses the component. Ít is important to monitor the successful execution of thesetasks on a regular basis.Please find all relevant tasks in the following list:

o SAP industry solution SAP Retail

If you use the SAP industry solution SAP Retail to store merchandise management, in-storecustomer relationship management, and store connectivity, then you must schedule thefollowing jobs according to the assortment list specified below:

RWDBBINI: Initialization and Full version RWDBBMAN: Direct Request RWDBBMAN_HPR: Direct Request (high performance) RWBBVCRE_HPR: Creation of versions from IDocs RWBBINI_HPR: Initialization and Full version (high performance) RWDBBMIG: Migration of the HPR project for the assortment list RWDBBRCV_HPR: Recover the dumped packets RWDBBUPD: Change message RWDBBUPD_HPR: Change message (high performance) RWDPOSAN: Direct request for POS Outbound RWDPOSIN POS: Outbound: Initialization RWDPOSRS: Reorganization of status entries POS and assortment list RWDPOSTG: Creation of trigger files for all open status entries in WDLS RWDPOSUP POS: Interface-Outbound - Change message

Page 80: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 80

RWPOS_PARA_ENQUEUE: Dispatcher for POS Inbound IDocs RBDAPP01: Initial processing of IDocs ready for hand over R_SRS_PDC_ASSORT_STRUCT_OUT: Export of assortment list structure data to

Business Connector R_SRS_PDC_GM_DATA_OUT: PDC Vendor and Plant Data R_SRS_PDC_GM_CUST_OUT: PDC Customizing Data R_SRS_PDC_GR_CREATE: PDC: Automatic posting from WGMH-SRS/WGMP-

SRS R_SRS_PDC_GR_CUSTOMIZING_OUT: PDC: Export Goods Receipt Customizing

Data R_SRS_PDC_GR_DOCUMENT_OUT: PDC: Export Goods Receipt relevant

Documents R_SRS_PDC_MATDATA_OUT: PDC; Export Material Master data for Assortment list R_SRS_PDC_SO_DISP_DATA_OUT: Export of replenishment (dispo) data to

Business Connector R_WSAO_STOREORDER_GEN: Generation of follow-on documents For more information about these jobs, see SAP Help Portal at help.sap.com SAP

ERP SAP ERP Central Component 6.0 Logistics

o SAP industry solution SAP Banking

If you use SAP industry solution SAP Banking, then you have to notice the following:

Batch JobsActivating planned changes (time periods that are valid in the future) If time dependencyhas been activated for central data, addresses, bank details, or business partner roles, andif the business partner data is to also be exchanged with other systems that are not timedependent, you need to start the report BUPTDTRANSMIT daily. You find this inCustomizing under help.sap.com SAP ERP SAP ERP Central Component 6.0 Cross-Application Components SAP Business PartnerThis report activates planned changes on the key date and transfers

these changes to the connected system.

For more information about the report BUPTDTRANSMIT, see SAP Help Portal athelp.sap.com SAP ERP Central Component SAP ERP 6.0 SAP ERP CentralComponent Financials SAP Banking Release Notes for SAP ERP 6.0 CentralComponent 6.0 Chapter 29: Time Dependency od business partner address; Timedependency of bbusiness partner role.

o SAP Loans Management (FS CML)

If you use SAP Loans Management (FS CML), then you have to notice that there are noadditional specific functions in SAP Loans Management (FS CML) other than the standardfunctions described above.

Batch Jobs

Technically required batch jobsThese batch jobs are required to ensure the flow logic is correct and vary depending onthe business processes of your financial institution.Some jobs are technically necessary, for example the report FNRB (Update plannedrecords).For more information on updating planned records, see SAP Help Portal at:help.sap.com SAP ERP Central Component SAP ERP 6.0 SAP ERP CentralComponent Financials SAP Banking Loans Management (FS-CML) PositionManagement Periodic Processing Updating Planned Records from Worklist

Page 81: SOG_SAPERP60_SR3

Management of SAP Technology

81 Dezember 2009

Recommended batch jobsThese batch jobs vary depending on the business processes of your financialinstitution. The report S_ALR_87015193 (Loans/Financial Accounting: ReconciliationList) is one of the recommended reports, for example.For more information on the reconciliation list, see SAP Help Portal at: help.sap.com

SAP ERP Central Component SAP ERP 6.0 SAP ERP Central Component Financials SAP Banking Loans Management Information System Reports

Accounting Balance Reconciliation List

Batch jobs required by business processesThese batch jobs are derived from the flow logic of your business processes, whichmeans they provide the expected results for each of the business processes.Business processes require the following reports, which must be executed in thefollowing order:

1. FNM1 (Post Planned Records)2. F110 (Automatic Payment Transactions – Customer)3. FNRA (Accrual/Deferral)4. FNSA (Valuation of Foreign Currency Loans)5. F.24 (Overdue Items)6. FNBT (Balance Sheet Transfer)

For more information on the reconciliation list of reports, see SAP Help Portal at:help.sap.com SAP ERP Central Component SAP ERP 6.0 SAP ERP CentralComponent Financials SAP Banking Loans Management (FS-CML)Accounting

Change pointer and ALE export

7. FNCP1 (Generating Change Pointers Manually)8. FNCP3 (Displaying Change Pointers)9. FNCP4 (Reorganize Change Pointers))10. FNEXP (Export Interface Loans)

For more information on change pointers, see SAP Help Portal at: help.sap.comSAP ERP Central Component SAP ERP 6.0 SAP ERP Central Component Financials SAP Banking Loans Management (FS-CML) EnvironmentChange Pointers and ALE Export

o SAP Collateral Management (FS CMS)

If you use SAP Collateral Management (FS CMS), then you have to notice that there areno additional specific functions in Collateral Management other than the standardfunctions described above.

Batch Jobs

Revaluation of collateral objectsDepending on the needs of your financial institution, the single security accountitems and therewith the whole securities account for the collateral object SecuritiesAccount need to be revalued once daily or multiple times daily.To be able to import the necessary flow, bank, and class data for the securitiespositions from an external system (such as Reuters) to your collateral managementsystem, you need to have implemented the following Business Add-Ins (BadIs):

CMS_SEC_VAL_ONLN CMS_SEC_BANK_ID CMS_SEC_GET_ADD_DATA

Page 82: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 82

You can determine how often the above-named data is transferred to CollateralManagement according to the internal requirements of the bank.For more information on securities accounts, see SAP Help Portal at: help.sap.comSAP ERP Central Component SAP ERP 6.0 SAP ERP Central Component Financials SAP Banking Collateral Management System (CM) Collateral ObjectsManagement (OM) Collateral Objects Securities Account Creating a SecuritiesAccount

Exporting data to a downstream system

Collateral Management uses extraction reports that make Collateral Management dataavailable to downstream systems, such as Bank Analyzer or Business Warehouse (BW),for example.From Release ERP 2004 the extraction reports in ERP must be started from CollateralManagement and need to be planned in regular intervals according to the bank’s internalrequirements.You must run both reports in the following order:

1. RCMS_CREATE_CHG_PTR_FOR_CONST (Create change pointer for entities inthe constellation)The results of this report are necessary for the following report to be able to run.

2. RCMS_BII_DATA_EXTRACTION (Data extraction)

Both of the reports are not required to keep data within Collateral Management current.For more information on extraction reports, see SAP Help Portal at: help.sap.com SAPERP Central Component SAP ERP 6.0 SAP ERP Central Component Financials

SAP Banking Collateral Management (CM) Interfaces to External Systems

4.5 SAP User ManagementWith the user administration, you create the prerequisites for your employees being able to work inthe SAP system. Create a user master record for every employee that contains all of theinformation about this user. In addition to technical administration data, this includes theauthorizations included in roles and profiles that allow the user to execute an action in the SAPsystem.User and role maintenance and the User Information System are available for maintaining the usermaster records.

4.5.1 Detailed SAP User ManagementMeeting Your Own Security Requirements: Security Policy

Your security requirements are not limited to the SAP NetWeaver platform, but to your entiresystem landscape. SAP therefore recommends that you establish a security policy that reflects thesecurity issues that apply at a company-wide level. Your security policy should cover aspects suchas:

User authentication

Authorizations

Data integrity

Privacy

Auditing and Logging

Page 83: SOG_SAPERP60_SR3

Management of SAP Technology

83 Dezember 2009

Once you have established your security policy, you can implement and enforce security for thoseproducts that you use within the SAP NetWeaver platform.

User Management – Roles and Profiles

You must create a user and assign a role to the user’s master record before you can use the SAPSystem. Roles are collections of activities, which allow a user to use one or more businessscenarios of an organization.Assigning roles ensures the integrity of business data. Authorization profiles are generated whichrestrict the activities of users in the SAP System, depending on the activities in the roles.A user can only log on to the system if he or she has a user master record.

A user menu and authorizations are assigned to the user master record via one or more roles. Thetransactions, reports and Web-based applications in the roles are accessed using user menus.User menus should only contain the typical functions in the daily work of a particular user.

User Management ToolThe tools available to perform identity management functions depend on the type of installation youhave. Listed below are some tools for various SAP systems:

User Administration and Identity Management in ABAP SystemsThe tools for user management on ABAP systems are:

User Maintenance (transactions SU01, SU10)

Role Maintenance (transaction PFCG)

Indirect role assignment using HR-ORG

User Information System (transaction SUIM)

Central User Administration (transactions PFCG, SM59, SU01, SCUA, SCUM, SCUG,SUGR, SCUL)

User Administration for SAP Java SystemsThe User Management Administration Console is used for user administration on SAP Javasystems. The user management administration console is a Web-based tool that providesadministrators with the functions they need to manage users, groups, roles, and user-related datain SAP User Management Engine (UME). It is available in three forms: Standalone Web tool If you are using UME with SAP Enterprise Portal, the administration console is integrated in the

User Administration role Security Provider service of the Visual Administrator

The J2EE Engine supports the architecture defined in the Sun J2EE 1.3 Specification.Although you can create and modify users both in the UME administration console and inthe Visual Administrator, SAP recommends that you use the UME administration console.

The SAP NetWeaver Security Guide provides an overview of the security-relevantinformation that applies to SAP NetWeaver. It contains an overall overview of security withSAP NetWeaver as well as links to the individual guides for each of the usage types,standalone engines, connectivity, and interoperability technologies, database and operatingsystem platforms and the various scenarios.

Page 84: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 84

Security Guides for SAP NetWeaver Scenarios

The security aspects and recommendations for the SAP NetWeaver scenarios primarily use theinformation provided with the security guides listed below. For more information about how todetermine which of these guides apply in particular for each scenario, see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) System Administration –Security Guide.

To get an overview about relevant Web Links at this side look the following tables.

Introduction to Security with the SAP NetWeaver Platform

Topic Quick Link/ PathTechnical System Landscape For more information, see SAP Service Marketplace at

service.sap.com/instguides. See the documentsunder SAP NetWeaver <Release> Planning

User Administration andAuthentication

For more information, see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver7.0 (2004s) System Adminisration – Security Guide User Administration and Authentication

Network and Transport LayerSecurity

For more information, see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver7.0 (2004s) System Administration – Security Guide

Network and Communication Security

Security Guides for SAP NetWeaver According to Usage Types

Usage Type Quick Link/ PathApplication Server ABAP /JAVA For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guide for Usage Type AS

SAP NetWeaver Application Server ABAP SecurityGuideSAP NetWeaver Application Server Java Security GuideSecurity Settings for the SAP Message ServerSAP Interactive Forms by Adobe Security GuideInternet Transaction Server SecuritySAP Knowledge Warehouse Security GuideComposite Application Framework Core Security GuideVirus Protection and SAP GUI Integrity ChecksSAP Web AS with Integratrated ITS

Enterprise Portal (EP) andEnterprise Portal Core (EPC)

For more information, see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guide for Usage Types EPC and EP

Portal Security GuideKnowledge Management Security GuideCollaboration Security GuideSecurity Guide for Guided ProceduresSAP Netweaver Visual Composer Security GuideUniversal WoroklistPDK for .NET Security Guide

Page 85: SOG_SAPERP60_SR3

Management of SAP Technology

85 Dezember 2009

Usage Type Quick Link/ PathBusiness Intelligence (BI) For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guide for Usage Type BI

Security Guide for SAP NetWeaver BIDevelopment Infrastructure (DI) For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guide for Usage Type DI and OtherDevelopment Technologies

Security of the SAP NetWeaver DevelopmentInfrastructureThe SAP NetWeaver Developer Studio: SecurityAspectsDeployment Authorizations When Using Deploy ServiceSecurity Aspects of Web Dynpro for JavaSecurity Issues in Web Dynpro for ABAPSecurity Aspects for BSP

Process Integration (PI) For more information, see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guide for Usage Type PI

SAP NetWeaver Process Integration Security Guide

Security Guides for Standalone Engines

Engine Quick Link/ PathSearch and Classification (TREX) For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guide for Standalone Engines, Clients andTools

Search and Classification (TREX) Security GuideSAP Content Server For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guide for Standalone Engines, Clients andTools

SAP Content Server Security Guide

Security Guides for Connectivity and Interoperability Technologies

Technology Quick Link/ Path

Page 86: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 86

Technology Quick Link/ PathRemote Function Calls (RFC) orInternet CommunicationFramework (ICF)

For more information, see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guides for Connectivity andInteroperability Technologies

RFC/ICF Security GuideApplication Link Enabling (ALE) For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guides for Connectivity andInteroperability Technologies

Security Guide ALE (ALE Applications)Connectivity with the J2EE Engine For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guides for Connectivity andInteroperability Technologies

Security Guide for Connectivity with the J2EE EngineWeb services For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guides for Connectivity andInteroperability Technologies

Web Services SecurityIntegrated CommunicationInterfaces (ICI) - BusinessCommunication Broker (BCB)

For more information, see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guides for Connectivity andInteroperability Technologies

Security Guide for Communication InterfacesSAP Gateway For more information, see SAP Help Portal at

help.sap.com SAP NetWeaver SAP NetWeaver 7.0(2004s) System Administration – Security Guide Security guides for SAP NetWeaver According to Usagetypes Security Guides for Connectivity andInteroperability Technologies

Security Settings in SAP Gateway

Security Guides for Operating System and Database Platforms

OS Platform Quick Link/ PathUNIX/LINUX For more information, see SAP Help Portal at

help.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide SAP System Security Under UNIX/LINUX

Page 87: SOG_SAPERP60_SR3

Management of SAP Technology

87 Dezember 2009

OS Platform Quick Link/ PathWindows For more information, see SAP Help Portal at

help.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide SAP System Security Under Windows

DB Platform Quick Link/ Path

Oracle For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide

Oracle Under UNIXOracle Under Windows

Microsoft SQL Server For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide Microsoft SQL Server Under Windows

IBM DB2 Universal Database forUNIX and Windows

For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide

IBM DB2 UDB for UNIX and Windows under UNIXIBM DB2 UDB for UNIX and Windows under Windows

MySQL Max DB For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide MySQL MaxDB Security Guide

IBM DB2 Universal Database foriSeries

For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide IBM DB2 Universal Database for iSeries

IBM DB2 Universal Database forz/OS

For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide SAP Security Guide for IBM DB2 UDB forz/OS

Informix For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide

Informix Under UNIXInformix Under Windows

Page 88: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 88

Security Aspects for System Management

Topic / Product Quick Link/ PathSolution Manager Diagnostics For more information, see SAP Help Portal at

help.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide Security Guide for the Solution ManagerDiagnostics

SAP NetWeaver Administrator For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide SAP NetWeaver Administrator SecurityRoles

Computing Centre ManagementSystem (CCMS)

For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide

Background ProcessingPrint and Output ManagementAlert Management (ALM)Central Monitoring with CCMS

SAP System Landscape Directory(SLD)

For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide Security Guide for the SAP SystemLandscape Directory

Software Lifecycle Manager(SLM)

For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide SLM Security Roles

Archiving For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide

Security Guide for ADK-Based Data ArchivingSecurity Guide for XML-Based Data Archiving

Auditing and Logging For more information, see SAP Help Portal athelp.sap.com Documentation SAP NetWeaver SAP NetWeaver SAP Library Administrator’s Guide –Security Guide Auditing and Logging

Page 89: SOG_SAPERP60_SR3

Management of SAP Technology

89 Dezember 2009

4.5.1.1 SAP ERP 6.0 ABAP ComponentsSpecific SAP user management issues for the ABAP components in SAP ERP 6.0 are described inthe following list:

SAP ECC ServerThe tool used for user management is the Central User Administration (CUA) tool. This toolallows you to maintain users centrally for multiple ABAP-based systems. Synchronization witha directory server is also supported.If you plan to use Virtual Machine Container (VMC), check the SAP Note 863354.

SAP SEMThe data from SAP SEM is stored in BW tables as well as in SEM-specific tables. For moreinformation about authorization specifications for BI systems, see the Usage Type BI.SAP SEM also uses the Central User Administration (CUA) tool for user management.

SRM ServerFor more information about user management, see SAP Service Marketplace atservice.sap.com/instguides SAP Business Suite Solutions SAP SRM UsingSAP SRM Server 5.5 Solution Operations Guide: SAP Supplier Relationship Management

SAP E-RecruitingSAP E-Recruiting uses the Central User Administration (CUA) tool for user management. Thistool allows you to maintain users centrally for multiple ABAP-based systems. Synchronizationwith a directory server is also supported.

4.5.1.2 SAP ERP 6.0 JAVA ComponentsSpecific user management issues for Java components in SAP ERP 6.0 are described in thefollowing list:

Self-Service (XSS)The J2EE Engine uses the Visual Administrator for user management. This tool allows you tomaintain users and roles on the J2EE Engine.The J2EE Engine also supports a plug-in user store concept. The UME is the default user store.

4.5.1.3 SAP ERP 6.0 Additional ComponentsSpecific SAP user management issues for additional components in SAP ERP 6.0 are described inthe following list:

SAP liveCacheFor information about user management in SAP liveCache, seeSAP Help Portal at help.sap.com Documentation SAP NetWeaver SAP NetWeaver 7.0(2004s) SAP Library SAP NetWeaver Library Administrator’s Guide TechnicalOperations Manual for SAP NetWeaver Administration of Standalone Engines SAPliveCache-Technology Management See also MaxDB Security Guide Authorizations

Page 90: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 90

4.5.2 Further InformationThis section includes additional information, such as SAP Notes, web links and related documentsfor user management.

4.5.2.1 SAP User Management SAP Notes

Check SAP Service Marketplace at service.sap.com/notes regularly.

SAP NoteNumber

Title Description

863354 Operation VMC Operation

4.5.2.2 SAP User Management Web LinksDocumentation Web Links

Type of Information Quick Link/ Path Description

Security service.sap.com/security Provides information about SAPsecurity

Adaptive Computing help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Scenarios SAP NetWeaver Operations Adaptive Computing

Describes the administration ofAdaptive Computing

Usage Type ApplicationServer ABAP

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver GeneralAdministration Tasks Securityand User Administration UserAdministration and IdentityManagement UserAdministration and IdentityManagement in ABAP Systems

Page 91: SOG_SAPERP60_SR3

Management of SAP Technology

91 Dezember 2009

Type of Information Quick Link/ Path Description

Usage Type ApplicationServer Java

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Systems AS-Java Management Tasks

J2EE Engine Security

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver GeneralAdministration Tasks Securityand User Administration Additional System Security

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver GeneralAdministration Tasks Securityand User Administration UserAdministration and IdentityManagement UserAdministration on SAP Web ASJava

Usage Type BusinessIntelligence (BI)

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Systems BI(Business Intelligence)

Usage Type ProcessIntegration (PI)

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Scenarios Enabling Application-to-ApplicationProcesses AdditionalInformation Security Guide for

Page 92: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 92

Type of Information Quick Link/ Path DescriptionUsage Type PI

Usage Type DevelopmentInfrastructure (DI)

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Systems DI(Development Infrastructure) Technical Operations Manual forthe SAP J2EE Engine UserManagement in the SAPNetWeaver JDI Configuring theUser Management of the SAPNWDI

Usage Type EnterprisePortal (EP)

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Systems EP(Enterprise Portal) Portal Management Basic PortalAdministration Tasks

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Systems EP(Enterprise Portal) Portal Management UserManagement

help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Systems EP(Enterprise Portal) KnowledgeManagement Tasks TasksPerformed as Required Management Security Guide

help.sap.com Documentation SAP NetWeaver SAP

Page 93: SOG_SAPERP60_SR3

Management of SAP Technology

93 Dezember 2009

Type of Information Quick Link/ Path DescriptionNetWeaver 7.0 (2004s) SAPLibrary SAP NetWeaver Library

Administrator’s Guide Technical Operations Manual forSAP NetWeaver Administrationof SAP NetWeaver Systems Collaboration Management Modification of the Functions forSearching and Displaying UserData User Management Engine

4.5.2.3 SAP User Management DocumentsDocumentation Links

Type ofInformation

Title Quick Link/ Path

SRM Solution Operations Guide:SAP Supplier RelationshipManagement

service.sap.com/instguidesSAP Business Suite Solutions SAPSRM Using SAP SRM Server 5.5 Solution Operations Guide: SAP SupplierRelationship Management

Biller Direct service.sap.com/fscm SAP ERP6.0 Financials SAP Financial SupplyChain Management Media Library Documentation Biller Direct SolutionOperations Guide SAP Biller Direct 6.0

4.6 High AvailabilityPurpose

High availability applications allow you to maximize downtime security and minimize downtimes.You can achieve this objective controlling the growth of redundant data and by implementingsuitable logic to control redundant systems.

Overview

At SAP, the focus on high availability (HA) is always directed at business applications and theirrelated components. SAP relies on the high availability applications of partner products with regardto the components such as, the operating system, database, and hardware, which are mandatoryfor implementing the infrastructure.

For more information, see SAP Service Marketplace at service.sap.com/ha.

To gain competitive advantage, you must think of a collaborative business. This means integratingexisting heterogeneous system landscapes to include business partners, customers, and suppliers.The responsibilities concerning the use of a high availability application should be divided betweenCustomers, Partners, and SAP as described below:

Page 94: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 94

CustomerDecision for and against high availability applications

Operation of a high availability environment

PartnerProvisions for hardware, infrastructure, and high availability applications

Implementation of a high availability application at customer using their own and technology or SAPtechnology

SAPSupports and provides technologies to enable the implementation of partner high availabilityapplications

No certification of high availability applications of individual partners

For more information, see SAP Service Marketplace atservice.sap.com/partners

The trend is towards open system architectures in which end-to-end business processes combinedwith Web services run on multiple distributed application components. Such environments demandhigh availability not only for single components, but also for entire scenarios.

SAP, along with partners, has developed a range of high availability applications,which many customers have already in use. The applications you choose will varyaccording to your system landscape. Ensure that you discuss your plans with yourSAP consultant and hardware partner before implementation.

4.6.1 DowntimesDowntime defines the time during which you cannot use a system or a resource productively.Irrespective of how the SAP system landscape is defined (with or without a high availabilityapplication); a breakdown of one or several components always requires action. To cope with theseexceptional situations, it is imperative to ensure that the necessary resources are available in theevent of malfunctions, problems, queries, such as an SAP specialist or a network administrator.There are two types of Downtimes described in the following chapters.

4.6.1.1 Planned DowntimesPlanned downtime is the time for scheduled maintenance and upgrade during which a systemcannot be used for normal productive operations. This time is used for a variety of purposes so thata system can function optimally and reliably. Some of the possible causes of planned downtime areas follows:

Hardware maintenance

Upgrades to new releases of SAP application components, database or operating system

Database reorganization

Database backup

Archiving of SAP business objects

Page 95: SOG_SAPERP60_SR3

Management of SAP Technology

95 Dezember 2009

Preparation

You must:Agree upon a planned downtime in close cooperation between the IT department and therespective departments.This is the only way of defining the timeframe for the necessary downtimes, without restrictionsbeing placed on the way the application works.Inform all those involved in advance about the upcoming system downtime

Keep the downtime as brief as possible

SAP System – Planned Downtime

The following table lists the possible changes in SAP systems and the downtimes, which can beplanned in each case to rectify the problem:

Action Downtime DetailsSAP system parameterchanges

Conditional Since SAP system parameters are partly kept inthe shared memory, they can be changed online.Transactions used:SM50

RZ12

SMGW

RZ11SAP reports - RSMEMORY

Changes in thefollowing ERP profiles:Start profile

Default profile

Instance profile

Mandatory SAP recommends that you carry out thecorresponding changes using the integratedprofile administration in the SAP system. Thetransaction used is RZ10.Advantages of using the integrated profileadministration are:Centralized management: Profiles of all instancescan be administered and maintained centrally.

Version management: Every saved change to oneof the profiles is saved as a version in thedatabase of the SAP system.

Consistency checks: After changes, theconsistency of the respective profile can bechecked.

Kernel Patch Mandatory The SAP Kernel should be exchanged at regularintervals.The available patches can be used to correctproblems or errors, which are closely connectedto the stability of SAP systems.

SAP Support Packages Mandatory The Support Packages should be imported atregular intervals.Support Packages are needed to correct errors inthe different software components and consist ofa number of corrected SAP objects.

Page 96: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 96

Action Downtime DetailsSAP Upgrades Mandatory For more information about the upgrade of SAP

Systems, see SAP Help Portal at help.sap.com Documentation SAP NetWeaver SAP

NetWeaver 7.0 (2004s) SAP Library SAPNetWeaver Library Administrator’s Guide Technical Operations Manual for SAP NetWeaver

General Administration Tasks HighAvailability SAP High AvailabilityDocumentation Planned and UnplannedDowntime Upgrades to new releases of SAPapplication components, database, or operatingsystem.

Maintenance of the:Operating system

Database

Server

Memory

Network

Optional Enhancements or changes can be made toexisting software or hardware for various reasonssuch as:Parts of the hardware are defective (yet server isstill working)

Parts of the hardware should be modified

Disk capacity needs to be enhanced

Physical memory needs to be enhanced

Changes to the disk configuration, for example,from RAID1 to RAID5

4.6.1.2 Unplanned DowntimesUnplanned downtime is the time during which a system cannot be used for normal productiveoperations due to unforeseen failure in hardware or software components, or operator mistakes.Unplanned downtime can be extremely costly to an organization. The source of unplanneddowntime can be in any of the layers that make up the complete software and hardwareenvironment:Front-end and middleware services for connection to the web, including the Internet TransactionServer (ITS), the SAP Web Application Server (SAP Web AS), and the SAP Enterprise Portal.

SAP system services of the individual application components of the SAP Business Suite – such asthe Business Warehouse (BW), Business-to-Business Procurement (BBP) – and the SAP kernel.

Underlying hardware and software services, such as the database services, network and operatingsystem services, and various hardware services, including servers, disks, memory, anduninterruptible power supply (UPS).

The risk of unplanned downtimes occurring can be minimized by avoiding single point of failures(SPOFs) in a complex system landscape. For the different components in a complex systemlandscape, there are several ways of avoiding these SPOFs. No measures for avoiding unplanneddowntimes specified in the following list are a safeguard against logical errors. You can only protectagainst logical errors by implementing the appropriate backup and recovery measures.The following table provides a list of SAP components, their SPOFs, and their corresponding highavailability applications.

Component Single Point ofFailure

High Availability Applications

Application server Application server Redundant application server

Page 97: SOG_SAPERP60_SR3

Management of SAP Technology

97 Dezember 2009

Component Single Point ofFailure

High Availability Applications

Database Database Cluster, replication technologyOperating system Operating system Cluster technologyServer Server Redundant server; Cluster technologyMemory (hard disks) Memory (hard disks) Hard disk imaging; Storage Area Network

(SAN) technologyNetwork Network components Redundant network architecture

4.6.2 Detailed High AvailabilityAs more and more customers deploy SAP systems in SAP Business Suites for their globaloperations, the need for maximized system availability becomes more and more crucial. Highavailability is a technically complex area, and implementation considerations vary according to thenature of your system setup. This section illustrates the possibilities available.

SAP does not offer customized high availability applications. You must develop thisaccording to your business requirements. However, you can contact your SAPconsultant, hardware supplier, or the SAP Competence Centre for technical guidancewhen developing a high availability strategy or while implementing a specific productor feature.

For more information about the high availability of SAP Systems, see SAP Help Portal athelp.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) System Administration Technical Operations Manual for SAP NetWeaver General Administration Tasks HighAvailability

https://www.sdn.sap.com/irj/sdn/ha

4.6.3 Further InformationThis section includes additional information such as, SAP Notes, web links, and related documentsfor high availability.

4.6.3.1 High Availability SAP Notes

Check SAP Service Marketplace at service.sap.com/notes regularly to seewhich SAP Notes are available for the Solution Operations Guide.

SAP NoteNumber

Title Description

853571 Release Restr.: Usage Type AS ABAPof SAP NetWeaver 2004s

Chapter High Availability

853572 Release Restr.: Usage Type AS JAVAof SAP NetWeaver 2004s

Chapter High Availability

853509 Release Restr.: Usage Type EP ofSAP NetWeaver 2004s

Chapter High Availability

951910 NW 2004s High availability UsageType PI

Chapter High Availability

Page 98: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 98

4.6.3.2 High Availability Web LinksDocumentation Web Links

Type of Information Quick Link/ Path Description

High availability service.sap.com/ha Providesinformationabout highavailability

SAP on the Microsoft platform service.sap.com/msplatforms Detailsinformationabout SAP onthe Microsoftplatform

SRM high availability service.sap.com/instguides SAPBusiness Suite Solutions SAP SRM SAP SRM Server 5.5 Solution OperationsGuide: SAP SRM 5.0

Detailedinformationabout SRM-specific highavailabilityissues

SAP NetWeaver 7.0 (2004s) help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual General Administration Tasks High Availability

Detailedinformationabout highavailability forNetWeaver 7.0(2004s)

Usage Type Application ServerABAP

help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual for SAP NetWeaver GeneralAdministration Tasks High Availability

SAP High Availability documentation SAP NetWeaver AS ABAP: High Availability

Usage Type Application ServerJava

help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) System Administration TechnicalOperations Manual for SAP NetWeaver General Administration Tasks HighAvailability SAP High Availabilitydocumentation SAP NetWeaver AS JAVA:High Availability

SAP LiveCache help.sap.com SAP Business Suite SAP Supply Chain Management

help.sap.com SAP NetWeaver SAPNetWeaver 7.0 (2004s) SystemAdministration Technical OperationsManual for SAP NetWeaver GeneralAdministration Tasks Administration ofStandalone Engines SAP liveCache-Technology

Page 99: SOG_SAPERP60_SR3

Management of SAP Technology

99 Dezember 2009

4.6.3.3 High Availability DocumentsDocumentation Links

Type ofInformation

Title Quick Link/ Path

High Availabilityoptions for SAPliveCache

Backup, Recovery, and HighAvailability for SAP APO

service.sap.com/scm SAPSCM Technology SystemManagement / Solution OperationsGuide Best Practices for SAP SCMSolution Management BestPractices for Solution Management:SAP SCM Backup, Recovery andHigh Availability for SAP APO

SRM Solution Operations Guide:SAP Supplier RelationshipManagement

service.sap.com/instguidesSAP Business Suite Solutions SAPSRM Using SAP SRM Server 5.5

Solution Operations Guide: SAPSupplier Relationship Management

Biller Direct service.sap.com/fscm SAPERP Financials SAP FinancialSupply Chain Management SAPBiller Direct Media Library Solution Management Guide

4.7 ArchivingDefinition

Data Archiving allows you to remove data from the database and store it in a consistent and securemanner. The archived data is stored in a file system and from there can be moved to other, morecost efficient storage media.

Purpose

Generally large amounts of database data is produced in the production system of a businessapplication, which often times is reflected in a deterioration of system performance and anincreased use of resources. Costs can also be negatively affected by large data volumes, sinceresources and efforts spent on database administration go up as a result.Therefore, data from closed business processes, meaning data that is no longer needed in everyday business processes, should be moved out of the database, in order to gain a reduction incosts, and improve performance and system availability. Simply deleting this data is often not avalid option, due to legal data retention requirements. This means that the data has to be removedfrom the database and stored in such a way that it is always accessible for reading if necessary.This is the task of SAP Data Archiving, which allows you to removed data from the database andstore it in a consistent and secure manner. The archived data is stored in a file system and fromthere can be moved to other, more cost efficient storage media.

Page 100: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 100

4.7.1 Detailed ArchivingData archiving is an administrative task that must be done regularly. How often you archive largelydepends on the growth rate of your database tables. The technological foundation of data archivingis located in SAP NetWeaver and is available in two different variations:

Archive Development Kit (ADK)-based Archiving

The Archive Development Kit (ADK) is the technical framework and basis for an SAP data archivingapplication. ADK is a development environment and an application program interface between SAPapplications, the database, and the archive files where your data is stored. It is available in everystandard SAP application and is used by SAP.

ADK ensures that data archiving is independent of hardware and release changes and providesyou with the tools you need for data archiving. ADK includes: Archive administration functions (transaction SARA):

Enables you to administer all your archiving programs (write, delete, read, and reload) andgenerate background jobs for these programs.

An application programming interface (API):You can use this API to develop your own archiving programs

Archiving-specific function modules:Function module such as, automatic job scheduling and compression during archiving

XML-based Archiving

XML-based data archiving has the same purpose as ADK-based archiving. Both are used toremove complete business data, which is data no longer needed in online business processes,from the database. It stores the data in such a way that it is still accessible for future use. XMLarchiving is used primarily for XML archiving objects implemented by ABAP applications with XMLinterfaces. It is based on the following principles:

Comprehensive use of standards

XML: A generally accepted markup language and exchange format for complexobjects, especially business objects, which are supported by a wide range of tools.Compared to ADK, this format is used to archive data objects as whole objects (notbroken down into different records). XML schema used to validate and describe thestructures of XML documents

HTTP: This protocol is used for secure communication between the application systemand the XML data archiving service (XML DAS).

WebDAV: This is used as a model for the hierarchical organization of archived dataand as a general (not SAP-specific) protocol for connecting storage systems includingarchive systems.

JAVA: This programming language is a platform-independent and used outside theSAP world.

J2EE: Is used as a standard for the development of JAVA-based enterpriseapplications.

Flexible data access, which is available even in long term

Page 101: SOG_SAPERP60_SR3

Management of SAP Technology

101 Dezember 2009

Independent from the application system that generates the data. This is in case a system has ashorter life cycle than the data to be archived.

Independent from the application system technology, which is also relevant for JAVA applications

Basis for cross-system data accesses and searches

Centralized archiving service to minimize administration efforts for system landscapes withseveral components

Both the ADK and XML Archive API provide basic functions and services for development andexecution of archiving programs.

For more information about archiving, see:SAP Help Portal at help.sap.com SAP NetWeaver SAP NetWeaver 7.0 (2004s) SystemAdministration Technical Operations Manual General Administration Tasks Data Archiving

SAP Service Marketplace service.sap.com/atg Advanced Technology Group Archiving

4.7.1.1 SAP ERP 6.0 ABAP ComponentsSpecific archiving issues for ABAP components in SAP ERP 6.0 are described in the following list:

Data Archiving for SAP UtilitiesIn IS-U you can now archive billing documents, print documents and budget billing plans. Pleasehave a look at help.sap.com SAP ERP SAP ERP Central Component ERP CentralComponent SAP Library SAP Utilities Tools Data Archiving in SAP Utilities

Data Archiving for SAP MediaYou can find specific archiving information on SAP Media at help.sap.com SAP ERP SAPERP Central Component ERP Central Component SAP Library SAP Media Archiving

Data Archiving for IS-PS-CAThere is some special information on data archiving of Contract Accounts Receivable and Payable.You can output the logs of all archiving objects of Contract Accounts Receivable and Payable andthe corresponding additional information as a classic list or by means of the application log. The logshows the number of entries archived per table as detailed information for each success messageof the data object.The system variants that SAP delivers for deletion jobs that are used in the deletion programs write– depending on whether you choose the test or productive mode – a details or minimal output inthe application log.To archive the master data, you have to adjust the variants that you have created yourselfmanually.Please have a look at help.sap.com SAP ERP SAP ERP Central Component SAPLibrary Collection and Disburesment (PSCD) Archiving

Data Archiving for SAP Catch Weight ManagementBased on the ERP system, the SAP Catch Weight Management solution provides industry-specificfunctions in the area of Financial Accounting.Archiving in Inventory Accounting uses the archiving functions of the classic solution in SAP ERP.When Inventory Accounting is used, the system generates data in Inventory Accounting in additionto the documents in SAP ERP. Since downstream processes run on the SAP ERP data, this data cannot be deleted until the downstream processes have finished.

Page 102: SOG_SAPERP60_SR3

Management of SAP Technology

Dezember 2009 102

In Inventory Accounting you cannot archive a production order with a WIP balance until you haverun the WIP clearing function.The same applies to WIP or GR/IR with subcontracting and to GR/IR with purchase orders,purchase order items, material documents, or the service entry sheet.Please have a look at help.sap.com SAP ERP SAP ERP Central Component SAPLibrary SAP Catch Weight Management Accounting Financial Accounting InventoryAccounting (FIN-BAC-INV) Archiving

Data archiving in SAP Discrete Industries and Mill ProductsThere is some more information given on archiving of IS-Automotive data. You can find a list ofarchiving objects available for IS-Automotive at help.sap.com SAP ERP SAP ERP CentralComponent SAP Library SAP Discrete Industries and Mill Products SAP for Automotive IS-A Data Archiving

Data archiving in SAP Oil & GasYou can find some special information on archiving in Production and Revenue Accounting athelp.sap.com SAP ERP SAP ERP Central Component SAP Library SAP Oil & Gas

SAP Oil & Gas (PRA – Production and Revenue Accounting PRA Archving

SRM ServerFor more information about archiving in SRM, seeSAP Service Marketplace at service.sap.com/instguides SAP Business Suite Solutions

SAP SRM Using SAP SRM Server 5.5 Solution Operations Guide: SAP SupplierRelationship Management

4.7.2 Further InformationThis section includes additional information such as, web links and related documents for archiving.

4.7.2.1 Archiving Web LinksDocumentation Web LinksType of Information Quick Link/ Path Description

Advanced Technology Group service.sap.com/atgAdvanced Technology Group

Archiving

Information about theAdvanced Technology Group

4.7.2.2 Archiving DocumentsDocumentation Links

Type of Information Title Quick Link/PathSAP Supplier RelationshipManagement

Solution Operations Guide:SAP Supplier RelationshipManagement

service.sap.com/instguides SAP Business SuiteSolutions SAP SRM Using SAP SRM Server 5.5

Solution Operations Guide:SAP Supplier RelationshipManagement

Usage Type ProcessIntegration (XI)

help.sap.com SAPNetWeaver SAPNetWeaver 7.0 (2004s)

Page 103: SOG_SAPERP60_SR3

Software Change Management

103 Dezember 2009

System AdministrationTechnical Operations Manual

Administration of SAPNetWeaver Systems PI(Process Integration) Management DataArchiving

5 Software Change ManagementPurpose

Software Change Management standardizes and automates software distribution, maintenance,and testing procedures for complex software landscapes and multiple software developmentplatforms. These functions support your project teams, development teams, and applicationsupport teams.Software change management establishes consistent, application-wide change management thatenables specific maintenance procedures, global rollouts including localizations, and openintegration with third-party products.Once you have installed and configured your software landscape, you must keep adapting it tochanging requirements. For example, you may need to react to changes in the organization of yourenterprise, provide new functions, or implement any improvements to the quality of SAPcomponents shipped by SAP at regular intervals.

5.1 Software Change Management SAPNotes

Check SAP Service Marketplace at service.sap.com/notes regularly to seewhich SAP Notes are available for the Solution Operations Guide.

SAP NoteNumber

Title Description

802987 TREX 7.0: Central Note BC-TRX147519 Maintenance strategy / deadlines

'SAPGUI'Front end Services

66971 Supported front end platforms Graphical User Interface

858005 SAP ERP 6.0 SP Stack 1 (10/2005)Release and Information Note

Release planning

863354 Operation VMC Operation

5.2 Software Change Management Web LinksDocumentation Web Links

Type of Information Quick Link/ Path

Software Logistics help.sap.com Documentation SAP NetWeaver SAPNetWeaver 7.0 (2004s) SAP Library SAP NetWeaver

Page 104: SOG_SAPERP60_SR3

Software Change Management

Dezember 2009 104

Type of Information Quick Link/ PathLibrary Administrator’s Guide Technical OperationsManual for SAP NetWeaver General Administration Tasks Software Logistics (Overview)

Software Logistics BusinessIntelligence

help.sap.com Documentation SAP NetWeaver SAPNetWeaver Technical Operations Manual for SAP NetWeaver

Administration of SAP NetWeaver Systems BusinessIntelligence (BI) Software Logistics

Software Logistics ProcessIntegration

help.sap.com Documentation SAP NetWeaver SAPNetWeaver Technical Operations Manual for SAP NetWeaver

Administration of SAP NetWeaver Systems ProcessIntegration (PI) Software Logistics

Software Logistics EnterprisePortal

help.sap.com Documentation SAP NetWeaver SAPNetWeaver Technical Operations Manual for SAP NetWeaver

Administration of SAP NetWeaver Systems EnterprisePortal (EP) Portal Software Change Management

Software Logistics TREX help.sap.com Documentation SAP NetWeaver SAPNetWeaver Technical Operations Manual for SAP NetWeaver

General Administration Tasks Software Logistics(Overview) Search and Classification (TREX) SoftwareLogistics

Support Package Manager service.sap.com/spmanager

SAP Notes service.sap.com/notes

Support Packages andpatches

service.sap.com/swdcandservice.sap.com/patches

Support Packages Stacks service.sap.com/sp-stacks

Language Transports help.sap.com Documentation SAP NetWeaver SAPNetWeaver 7.0 (2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide Technical OperationsManual for SAP NetWeaver Administration of SAPNetWeaver Systems Application Server ABAP (AS ABAP)Software Logistics Language Transport

Release and QualityManagement of SoftwareChanges

help.sap.com Documentation SAP NetWeaver SAPNetWeaver 7.0 (2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide Technical OperationsManual for SAP NetWeaver Administration of SAPNetWeaver Systems Application Server ABAP (AS ABAP)Software Logistics Releasing Software Changes and QualityManagement

Usage Type – DevelopmentInfrastructure

help.sap.com Documentation SAP NetWeaver SAPNetWeaver 7.0 (2004s) SAP Library SAP NetWeaverLibrary Administrator’s Guide Technical OperationsManual for SAP NetWeaver Administration of SAPNetWeaver Systems DI (Development Infrastructure)

SAP FSCM service.sap.com/fscm

SAP liveCache service.sap.com/upgradeNW2004s

Page 105: SOG_SAPERP60_SR3

Glossary

105 Dezember 2009

Type of Information Quick Link/ Path

SAP Notes for the component SAP BC-DB-LVC

SAP GUI service.sap.com/installations

service.sap.com/patches

5.3 Software Change ManagementDocuments

Documentation Links

Type of Information Title Quick Link/ PathSAP Supplier RelationshipManagement

Solution Operations Guide:SAP Supplier RelationshipManagement

service.sap.com/instguides SAP Business SuiteSolutions SAP SRM Using SAP SRM Server 5.5

Solution Operations Guide:SAP Supplier RelationshipManagement

6 GlossaryIdentificationcode

Detail Section

ABAP Advanced Business ApplicationProgramming

ADK Archive Development Kit 4.4.1 Detailed SAP User Management4.6.1 Detailed Archiving

API Application ProgrammingInterface

AS Application ServerASR HR Administrative Services 2.1 Landscape DescriptionBI Business IntelligenceCBS Component Build Service 5.1.4 Usage Type Development

InfrastructureCCMS Computing Centre Management

System3 Monitoring

CMS Change Management Service 5.1.4 Usage Type DevelopmentInfrastructure

CRT Conflict Resolution Transport 5.1.5 Software MaintenanceCTS Change and Transport System 5.1.1 Transport and Change ManagementCUA Central User Administration 4.4.1.1 User Management SAP ERP 6.0

ABAP ComponentsDAS Data Archiving Service 4.6.1 Detailed ArchivingDI Development InfrastructureDSR Distributed Statistical Records 3.4 CCMS Monitoring ConsoleDTR Design Time Repository 5.1.4 Usage Type Development

InfrastructureEP Enterprise PortalERP Enterprise Resource Planning

Page 106: SOG_SAPERP60_SR3

Glossary

Dezember 2009 106

Identificationcode

Detail Section

ECC ERP Central ComponentFSCM Financial Supply Chain

ManagementGRMG Generic Request and Monitoring

Generator3.7.2.2 Java Problem Detection andAnalysis

http Hypertext Transfer ProtocolIGS Internet Graphics ServiceIS-HER-CSS Campus Management Self

Service2.1 Landscape Description

J2EE Java 2 Platform, EnterpriseEdition

JARM Java Application Response TimeManagement

3.4.2.1 Java Monitoring and Management5.1.5 Monitoring Usage Type DevelopmentInfrastructure (DI)

JMS Java Message Service 3.7.2.1 Java Monitoring and ManagementJMX Java Management Extensions 3.7.2.1 Java Monitoring and ManagementJSPM Java Support Package Manager 5.1.5 Software MaintenanceLSO Learning SolutionLSOAE Learning Solution, Authoring

EnvironmentLSOFE Learning Solution, Front endLSOCP Learning Solution, Contend

PlayerLSOOP Learning Solution, Offline PlayerMSS Manager Self-Service 2.1 Landscape DescriptionOCS Online Correction Service 5.1.5 Software MaintenanceODS Operational Data Store 2.1 Landscape DescriptionPAG Problem Analysis Guide 3 MonitoringPCUI_GP Floor plan Manager, Self-Service

Administrator and Utilities2.1 Landscape Description

PI Process IntegrationPSA Persistent Staging Area 3.7.1.Detail Monitoring SAP ABAP

ComponentsPSS Project Self-Service 2.1 Landscape DescriptionRDBMS Relational Database

Management System4.2 Backup and Recovery

RIN2 Release- and Information Note 5.1.8 Support Packages StacksSAN Storage Area Network 4.5.1.2 Unplanned DowntimesSAP Systems, Applications, Products

in Data ProcessingSAINT SAP Add-On Installation Tool 2 Technical System LandscapeSEM Strategic Enterprise ManagementSLD System Landscape Directory 4.4.1 Detailed SAP User Management

5.1.4 Usage Type DevelopmentInfrastructure

SLM Software Lifecycle Manager 4.4.1 Detailed SAP User ManagementSPAM Support Package Manager 5.1.5 Software MaintenanceSPOF Single Point of Failure 4.5.1.2 Unplanned DowntimesSRM Supplier Relationship

ManagementTMS Transport Management System 5.1.3 Release and Quality Management of

Software ChangesVMC Virtual Machine ContainerXECO extended e-selling componentXI Exchange Infrastructure

Page 107: SOG_SAPERP60_SR3

Glossary

107 Dezember 2009

Identificationcode

Detail Section

XML Extensible Markup Language 4.6.2 Detailed ArchivingXSS Self Services