ERP Operation Guide

7/31/2019 ERP Operation Guide

1/83

Document Version 3.0

October 2004


2/83

Neurottstrae 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20

Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and

other SAP products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP AG

in Germany and in several other countries all over the world. All other

product and service names mentioned are the trademarks of their

respective companies. Data contained in this document serves

informational purposes only. National product specifications may

vary.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies ("SAP Group")

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or

omissions with respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in the express

warranty statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an additional

warranty.

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 IBM

Corporation 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 the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered trademarks of

Citrix Systems, Inc.

Disclaimer

Some components of this product are based on Java. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C, World Wide Web Consortium, Massachusetts

Institute of Technology. Any Java Source Code delivered with this product is only to be used

by SAPs Support Services and may not be modified or altered in any

way.Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape. Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet address:MaxDB is a trademark of MySQL AB, Sweden.


3/83

Typographic Convent ions

Type 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 other

documentationExample text Emphasized words or phrases

in body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded bybody text, for example,

SELECT and INCLUDE.Example text Screen output. This includes

file 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 the

documentation.

Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

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

I cons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax


4/83

Solution Operation Guide mySAP ERP 2004

Contents

1.SAP Documentation Types......................................................7

2.Getting Started..........................................................................9

2.1. Target Audience......................................................................9

2.2. Further Information...............................................................10

2.3. Important SAP Notes ............................................................10

2.4. History of Changes ...............................................................11

3.Technical System Landscape................................................12

3.1. Landscape Description.........................................................14

3.1.1. Example Comm. Structure: SAP Learning Solution..............18

3.1.2. Related Information..................................................................18

3.2. Related Documentation........................................................19

3.3. SAP Solution Manager..........................................................20

4.Monitoring of mySAP ERP.....................................................22

4.1. General Monitoring Overview...........................................25

4.1.1. General Monitoring Solution Manager.................................25

4.1.2. Monitoring Adapting CCMS..................................................28

4.1.3.

Detail Monitoring......................................................................314.1.3.1. ERP ABAP Components............................................................................31

4.1.3.2. ERP Java Components..............................................................................33

4.1.4. WebAS Monitors.......................................................................42

4.1.5. ABAP Monitors .........................................................................46

4.2. Summary Monitoring............................................................48

5.Management of mySAP Technology.....................................50

5.1. Starting and Stopping...........................................................50

5.1.1. Example: mySAP ERP Self-Service Scenario ........................51

5.1.2. Example: SAP Enterprise Portal .............................................53

5.1.3. Related Documentation: ..........................................................54

5.2. Backup & Restore and Recovery.........................................55

5.2.1. System Components And Data Need To Be Backed Up.......57

5.2.2. Operating System, Software and Configuration Data ...........57

5.2.3. Database ...................................................................................58

5.2.4. SAP NetWeaver Backup Summary .........................................59

5.2.5. SAP ERP Components and Backup Action ...........................59

5.2.6. Backup and Recovery Methods ..............................................60

5.3. System Copy .........................................................................63

5.3.1. Homogeneous System Copy...................................................63

4 Oktober 2004


5/83


5.3.2. Java Copy Tool.........................................................................65

5.4. SAP User Management.........................................................65

5.4.1. User Management Tools..........................................................66

5.5. Downtimes .............................................................................665.5.1. Planned Downtimes .................................................................67

5.5.2. Unplanned Downtimes.............................................................68

5.6. High Availability ....................................................................69

6.Software Change Management .............................................71

6.1. Transport and Change Management ABAP .......................72

6.2. Software Maintenance ABAP...............................................73

6.2.1. Support Packages....................................................................73

6.2.2. Add-On Installation Packages.................................................73

6.2.3. SAP Notes.................................................................................73

6.3. Transport and Change Management Java..........................74

6.3.1. SAP NetWeaver Java Development Infrastructure (JDI).......74

6.3.2. SAP NetWeaver Developer Studio ..........................................75

6.3.3. Change Management Service (CMS) ......................................75

6.3.4. Component Model....................................................................75

6.3.5. Component Build Service (CBS).............................................76

6.3.6. Design Time Repository (DTR)................................................76

6.3.7. Software Deployment Manager (SDM)....................................78

6.3.8. Java Dictionary.........................................................................786.4. Software Maintenance Java .................................................80

6.5. Example: Planning the Support Packages StackInstallation for ECC/SRM................................................................80

7.Archiving.................................................................................81

7.1. Archiving SAP BW ................................................................81

7.1.1. General Information .................................................................81

7.1.2. SAP BW Data Archiving...........................................................82

7.1.3. SAP SEM Data Archiving.........................................................83

October 2004 5


6/83


DisclaimerThis Solution Operation Guide will be updated on a regular basis. The History of Changessection contains an overview of the various versions.

For up-to-date information, see the latest Guide at service.sap.com/ERP-INST mySAP ERP 2004.

6 Oktober 2004
http://service.sap.com/ERP-INSThttp://service.sap.com/ERP-INST


7/83


1. SAP Documentation TypesSeveral documents have been created to assist you in installing, implementing, operating and

upgrading your SAP solutions. The Solution Master Guide (this document) is the firstdocument you obtain. Although strongly related to each other, the different documentationtypes should help you solve problems on different levels at different solution phases. Thefollowing figure shows an overview of the most important documentation types that youneed in the various phases in the life cycle of an SAP solution.

Implementation

Master Guide

ConfigurationDocumentation

Release Notes

Component

Installation Guide

ComponentUpgrade Guide

Upgrade Master Guide

Operation Upgrade

Solution Operation Guide

Implementation Guide (IMG) Delta and Upgrade IMG

Security Guide

SAP Library

SAPterm

Figure 1: Documentation Types in the Software Life Cycle

As shown in the figure, SAPterm, SAP Library and Implementation Guide (IMG) are cross-phase documentation.

SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over30 languages, as well as many definitions and glossary entries in English andGerman.

To use SAPterm, visit SAP Service Marketplace at service.sap.com/sapterm.

The SAP Library is a collection of function- and process-oriented documentation forSAP components. It is located on SAP Help Portal at help.sap.com. SAP Library

also contains Business Scenario Descriptions. These are found on SAP ServiceMarketplace at service.sap.com/ibc.

The Implementation Guide (IMG) is a tool for configuring the SAP system to meetcustomer requirements. Its structure and documentation are component-oriented. It is

located In the SAP menu of the SAP system under ToolsCustomizingIMG.

The Security Guide describes the settings for a medium security level and offerssuggestions for raising security levels. A collective security guide is available for the SAPNetWeaver technologies such as SAP Web Application Server (SAP Web AS). This

document contains general guidelines and suggestions about system security. Othertechnologies and individual applications have a Security Guide of their own.

October 2004 7
http://service.sap.com/saptermhttp://service.sap.com/ibchttp://service.sap.com/ibchttp://service.sap.com/sapterm


8/83


The current version of the Security Guide is located on SAP Service Marketplace atservice.sap.com/securityguide.

The Component Installation Guide describes the technical implementation of an SAPcomponent, taking into account the combinations of operating systems and databases. It

does not describe any business-related configuration. The Component Installation Guides forthe different components can be found on SAP Service Marketplace atservice.sap.com/instguides.

The Configuration Documentation is contained in the SAP Solution Manager, which ismentioned in Section 3.4. of this document. SAP Solution Manager is a tool with variousfunctions, one of its main functions being the configuration of SAP solutions and BusinessScenarios. It contains IMG activities, transactions, and so on, as well as documentation.Instead of the configuration documentation in SAP Solution Manager, there may be separateBusiness Scenario Configuration Guides in SAP Service Marketplace for earlier shipments ofthe Business Scenarios.

The Master Guide provides a central starting point for the technical implementation ofmySAP ERP, particularly if your enterprise plans to upgrade to mySAP ERP. The current

version is located on SAP Service Marketplace at service.sap.com/erp-inst.

The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of anSAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as the Component Upgrade Guidesand SAP Notes. Instead of an Upgrade Master Guide, there may be several BusinessScenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the BusinessScenarios of an SAP solution. The current version is located on SAP Service Marketplace atservice.sap.com/instguides.

The Component Upgrade Guide describes the technical upgrade of an SAP component,taking into account the combinations of operating systems and databases. It does notdescribe any business-related configuration. The current version is located on SAP ServiceMarketplace at service.sap.com/instguides.

Release notes are documents that contain short descriptions of new features or changes inan SAP component since the previous release. Release notes about ABAP developmentsenable the SAP system to generate delta and upgrade IMGs. The current version is locatedon SAP Service Marketplace at service.sap.com/releasenotesor in the SAP menu of

the SAP system underHelpRelease information.

Upon reviewing this description of the supplementary information sources at your disposal,you will be ready to get started.

8 Oktober 2004
http://service.sap.com/securityguidehttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/erp-insthttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/releasenoteshttp://service.sap.com/releasenoteshttp://service.sap.com/instguideshttp://service.sap.com/instguideshttp://service.sap.com/erp-insthttp://service.sap.com/instguideshttp://service.sap.com/securityguide


9/83


2. Getting Started

This guide does not replace the daily operations handbook that we recommendcustomers to create for their specific productive operations.

About This Guide

Designing, implementing, and running your mySAP solution at peak performance 24 hours a dayhas never been more vital for your business success then today.

This guide provides a starting point for managing your mySAP solutions and keeping them up andrunning optimally. It contains specific information for various tasks, and lists the tools that you canuse to carry them out. It also refers to documentation required for these tasks. You can use thisguide only in connection with other guides such as the Master Guide, Technical Infrastructure

Guide, and the SAP Library.

Unlike SAP R/3 systems, mySAP.com solutions use several SAP component systems to implementcross-system processes. Data is no longer held centrally in a single SAP system; instead it isdistributed between several SAP components.

This guide provides an overview of the technical runtime scenarios which result from the setting upof the corresponding business scenarios. For example, if you use a business self-service scenario,then from a technical perspective, the technical runtime scenario starts with the Browser includingthe iViews, displaying data generated from the WebDynpro Runtime and the SAP Enterprise Portal,running on the SAP NetWeaver Java runtime, and then getting the business-relevant data from aSAP back-end system. To ensure the operation of this technical runtime scenario, you mustunderstand the different steps and dependencies.

The Technical System Landscapesection provides an overview of the architecture of the mySAPERP 2004 components.

The Monitoring of mySAP ERPsection describes the standard monitors and the specific monitorsfor the different components and provides you with information about necessary tasks for detailedmonitoring.

The Managing of mySAP Technologysection describes the related topics on the mySAP solutionlevel, such as starting and stopping, backup and restore, and so on.

The Software Change Managementsection summarizes the two areas of Transport ChangeManagement and Software Maintenace.

2.1. Target AudienceThis documentation contains both high level information on solution level and very detailedtechnical information. It is intended for:

Technical consultants

Solution consultants

Business process owners

Support specialists

System administrators

October 2004 9


10/83


2.2. Further Information mySAP ERP Masterguide

For up-to-date information, see SAP Service Marketplace atservice.sap.com/ERP-

INSTmySAP ERP 2004. Here you can find detailed information about the technicalsystem landscape of mySAP ERP 2004.

SAP NetWeaver Technical Operations Manual (TOM)

There are a lot of hyperlinks referring to the SAP Technical Operations Manual.This

manual can be found in the SAP Help Portal at help.sap.comSAP NetWeaver

Release '04EnglishSAP LibrarySAP NetWeaverSAP NetWeaver TechnicalOperations Manual.

Support Package Stacks

For the latest component version and patch level requirements, see SAP ServiceMarketplace at service.sap.com/sp-stacks.

Product Availability Matrix

For technical and release planning information on SAP components for quick reference.For information about the availability of SAP component releases and maintenance enddates, as well as platform, language and country version availability, see SAP ServiceMarketplace at service.sap.com/pam.

Planning the System Infrastructure

For comprehensive information on technical infrastructure issues and network integration,see SAP Service Marketplace at service.sap.com/ti.

For guidelines and recommendations that pertain to system and network security, see SAPService Marketplace at service.sap.com/securityguide.

2.3. Important SAP Notes

Check regularly which SAP Notes are available for the Solution ManagementGuide.

Important SAP Notes

SAP Note Number Title

605326 Solution Installation Manager 3.1 (Ramp-up)

608277 Additional add-ons for the SAP Solution Manager

394616 Release strategy for Solution Manager Tool (ST)

110910 Deleting the language load

416101 Number range object DNO_NOTIF is missing

128447 Trusted/Trusting Systems

10 Oktober 2004
http://service.sap.com/ERP-INSThttp://service.sap.com/ERP-INSThttp://service.sap.com/sp-stackshttp://service.sap.com/pamhttp://service.sap.com/tihttp://service.sap.com/securityguidehttp://service.sap.com/securityguidehttp://service.sap.com/tihttp://service.sap.com/pamhttp://service.sap.com/sp-stackshttp://service.sap.com/ERP-INSThttp://service.sap.com/ERP-INST


11/83


746576 SAP ERP Central Component 5.0: Installation/upgrade with SP

631042 Release Strategy for Implementation Content (ST-ICO)

408398 Managing problem messages for the test workbench

492908 Scout: Authorizations in remote systems

532699 Application Help on connection to Solution Manager

529769 System copy of the SAP Solution Manager

613061 Solution Manager: 'No authorization for function group'

733534 Installation SAP Dispute Management 3.0 for FI-AR

Table 1

2.4. History of Changes

Make sure you use the current version of the Solution Operation Guide.

The current version of the Solution Operation Guide can be found on the SAP Service Marketplace

under service.sap.com/ERP-INST mySAP ERP 2004.

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

Version Important Changes

1.0 First version of the mySAP ERP Solution Operation Guide

2.0 Second version of the mySAP ERP Solution Operation Guide containsnew sections on the following topics:

SAP SEM

SAP E-Recruiting

SAP Learning Solution

SAP Supplier Relationship Management

3.0 Third version of the mySAP ERP Solution Operation Guide

Structure revised

Further information added

Feedback included

Table 2

October 2004 11


12/83


3. Technical System LandscapeAs described in the Master Guide for mySAP ERP 2004, there are several ways of distributing

individual components of mySAP ERP 2004 in the system landscape. (The current version ofmySAP ERP Master Guide can be found on the SAP Service Marketplaceunder

service.sap.com/ERP-INST mySAP ERP 2004.)

The various components are implemented based on SAP NetWeaver '04.

An essential criterion for ensuring normal operation status is the successful implementation of SAPWeb Application Server, which is part of SAP NetWeaver, the mySAP ERP 2004 application andthe database. All must be taken into consideration for the operation of mySAP ERP 2004.

Figure 2 shows the various mySAP ERP components.

mySAP ERP 2004 Software Components

ECC 5.0

SAP_HR 500

SAP_APPL 500

EA-APPL 500

EA-DFPS 500

EA-FINSERV 500

EA-GLTRADE 500

EA-HR 500

EA-PS 500

EA-RETAIL 500

EA-IPPE 300

PI 2004_1_500

WFM Core

110_640

Learning Solution3.0 (Frontend)

SEM-BW 4.0

FINBASIS 3.0

BI CONT 3.52

E-Recruiting 3.0

cProject Suite 3.1

ABAP Components

NW 04 ABAP Stack

Internet Pricer &Configurator (J2SE)

SAP XSS 5.0

LSO Content

Player 3.0

Biller Direct 3.0

IPC WebApp 4.0

ISA WAC 4.0

Java Web Applications

Java Components

NW 04 Java Stack

IPC 4.0

Catalog ContentManagement 1.0

SAP SRMServer 5.0

Add-ons based on

NW ABAP

SAP SRM

Portal Content

Business

Packages

Additional Components

Mobile Infrastructure Client 2.5

SAP ITS 6.20

SAP Business Connector

4.6 /4.7

XI Content

XI Content forApplications

SAP Solution Manager 3.1

Mobile Time Sheet 1.6

Mobile Travel Expenses 1.6

LSOOP 3.0 Offline Player

Mobile

Front End

LSOAE 3.0

SAP GUI

Mobile Sales for HH (ECC) 2.0

Mobile Asset Management 2.5

Mobile Direct Store Delivery 2.0

NetWeaver 04Additional Components

Figure 2: mySAP ERP Components

Three different types of component are explained briefly here:

ABAP Components

For the ABAP components, you distinguish between components that are connected withSAP NetWeaver as installations and are always installed as independent instances (forexample, SAP ECC and SAP SRM) and ABAP add-on components. ABAP add-on

components are installed on pre-existing systems (instances) using the SAP Add-On

12 Oktober 2004


13/83


Installation Tool (SAINT). These systems can be either pure NetWeaver systems (Web AS)or application systems (for example, SAP ECC). The existence of other components in thesame system is necessary for the installation of certain add-on components. Thesedependencies are described in the Installation Guide for the relevant components. Forfurther details, see mySAP ERP Master Guide at SAP Service Marketplaceunder

service.sap.com/ERP-INST mySAP ERP 2004.

Java Components

Within the Java Stack there are Java applications that are deployed in the runtime of SAPNetWeaver Java and that contain content for the relevant applications, such as the IPC asstand-alone application (not in SAP NetWeaver Java).

Additional Components

The additional components contain all other components such as SAP ITS, SAP BusinessConnector, the mobile and frontend components.

The technology determines which components can be installed in a runtime environment.

SAP XI is an application that requires both SAP NetWeaver ABAP and SAP NetWeaver Javaruntimes (Add-In installation). A meaningful distribution must be selected for the other components.

The type of component (ABAP, Java, and so on) and the type of installation in the actual systemlandscape are both important for the technical operation. For example, all components that areinstalled in the same instance (system) are forced to stop together when the instance is stopped. Inaddition, other dependencies result, for example in the areas of software logistics, monitoring,backup, and so on. Other sections of this Guide contain more detailed information about thesedependencies.

It is also important to include the issue of technical operation when you plan the systemlandscapes.

Here follows an example of a possible distribution of various components in a system landscape:

In Figure 3, mySAP ERP 2004 components are distributed for the self-service scenario for mySAPERP 2004. The components are executed on different servers for this scenario.

SAP ERP Central Component (SAP ECC) and SAP Business Information Warehouse (SAP BW)run in the ABAP SAP Web Application Server.

The SAP Enterprise Portal runs in the Java SAP Web Application Server.

The mySAP ERP component SAP XSS 5.0 (XSS = Self Services) is a Web Dynpro application.The Web Dynpro runtime is executed in the Java SAP Web Application Server.

SAP XSS 5.0 is a J2EE application component, which is deployed with the package ERP JavaComponents.

SAP XSS is based on the NetWeaver 04 Java Stack and connects to the backend functions in theECC System.

Related Documentation:

See SAP Service Marketplace at service.sap.com/erp-inst mySAP ERP 2004ERP

Java ComponentsInstall ERP Java Components.

October 2004 13
http://service.sap.com/ERP-INSThttp://service.sap.com/erp-insthttp://service.sap.com/erp-insthttp://service.sap.com/ERP-INST


14/83


Figure 3: Distributed System Landscape, mySAP ERP 2004 Self-Services Example

For all other scenario-specific solutions, see mySAP ERP Master Guide at SAP Service

Marketplaceunder service.sap.com/ERP-INST mySAP ERP 2004.

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

Managing mySAP ERP 2004 application components or scenarios

Managing SAP NetWeaver

Managing the database

The following table contains an overview of the various components, their prerequisites and

important comments:

ABAPComponents

Prerequisites Comments

SAP ECC SAP NetWeaver ABAP The ECC consists of the ECC application andthe ABAP SAP Web Application Server. Theplug-ins are an integral part, which are usedto connect for example to SAP BW.

SAP BW SAP NetWeaver ABAP

BI Content

SAP BW is an integral part of SAPNetWeaver

You can operate it within an existing

14 Oktober 2004


15/83


database (for example, SAP ECC)

Remark: Operating Business InformationWarehouse and ERP Central Component in

the same system and in a productionenvironment is solely supported on a projectbasis. If you are interested in implementingthis setup, contact your Ramp-up manager.A common client for SAP BW 3.5 and ERPCentral Component 5.0 is not supported.

SAP SEM SAP NetWeaver ABAP

BI Content

Finbasis 3.0

SEM BW 4.0

SAP SEM and SAP BW can also beoperated in two separate systems.The BW data storage is used.

You can operate it within an existingdatabase (for example, SAP ECC)

Remark: Operating Business Information

Warehouse and ERP Central Component inthe same system and in a productionenvironment is solely supported on a projectbasis. If you are interested in implementingthis setup, contact your Ramp-up manager.A common client for SAP BW 3.5 and ERPCentral Component 5.0 is not supported.

SAP SRM SAP NetWeaver ABAP SAP SRM is a separate instance withinmySAP ERP 2004 and therefore cannot beoperated within an existing database.

SAP LearningSolution 3.0

(Frontend)

SAP NetWeaver ABAP This component is part of the LearningSolution 3.0.

ABAP add-on that can be installed on theSAP ECC System or any other system that isbased on the NetWeaver 04 ABAP Stack. Alladd-ons are installed separately by using theSAINT tool.

SAPE-Recruiting 3.0

SAP NetWeaver ABAP ABAP add-on that can be installed on theSAP ECC System or any other system that isbased on the NetWeaver 04 ABAP Stack. Alladd-ons are installed separately by using theSAINT tool.

SAP

Catalog ContentManagement 1.0

SAP NetWeaver ABAP The SAP Catalog Content Management can

be installed as an add-on to the SAP ECCsystem, the SAP SRM system or anyNetWeaver 04 system (ABAP stack). It isused for procurement functions.

cProject Suite3.1

SAP NetWeaver ABAP ABAP add-on that can be installed on theSAP ECC System or any other system that isbased on the NetWeaver 04 ABAP Stack. Alladd-ons are installed separately by using theSAINT tool.

The SAP cProject Suite 3.10 consists of theapplications cFolders 3.10 and cProjects3.10.

October 2004 15


16/83


SAP WFM Core SAP NetWeaver ABAP ABAP add-on that can be installed on theSAP ECC System or any other system that isbased on the NetWeaver 04 ABAP Stack. Alladd-ons are installed separately by using the

SAINT tool.FINBASIS 3.0 SAP NetWeaver ABAP ABAP add-on that can be installed on the

SAP ECC System or any other system that isbased on the NetWeaver 04 ABAP Stack. Alladd-ons are installed separately by using theSAINT tool.

BI CONT 3.52 SAP BW Content for SAP BW

Table 3

JavaComponents


ISA WAC 4.0 SAP NetWeaver Java ISA WAC is a J2EE application which isdeployed with the package ERP JavaComponents.

Biller Direct 3.0 Sap NetWeaver Java Biller Direct is a J2EE application which isdeployed with the package ERP JavaComponents.

The Java component SAP Biller Direct has noown persistence. The database of the ECCback.end system is used (FI-AR or FI-CA)

and the database of SAP Web AS 6.40 Javacan be used for user management.

SAP XSS 5.0 Sap NetWeaver Java XSS is a J2EE application (WebDynpro)which is deployed with the package ERP JavaComponents.

XSS contains the software components ESS,MSS and PCUI_GP which can be patchedindividually.

LSO ContentPlayer 3.0

Sap NetWeaver Java This component is part of the LearningSolution 3.0.

It is a J2EE application which is deployed with

the package ERP Java Components.

SAP IPC 4.0 Java Development Kit(JDK) 1.4.2

(Standalone Javaapplication)

The SAP IPC (IPC 4.0) for Internet Salesscenarios requires its own database. This IPCcannot be used for SRM procurement.

The SAP IPC (IPC 4.0) for SRM procurementdoes not need an own database. This IPCcannot be used for Internet Sales scenarios.

IPC WebApp 4.0 SAP NetWeaver Java The IPC Web Application 4.0 is alsonecessary for the Internet Sales scenarios. Itis a J2EE application which is deployed with

16 Oktober 2004


17/83


the package ERP Java Components.

SAP EnterprisePortal Content

BusinessPackages

SAP NetWeaver Java(SAP Enterprise Portal)

Business packages contain pre-assembled,role-based content for completing businesstasks.

ERP Business Packages can be found onSAP Service Marketplaceservice.sap.com/swdc under

Download Installations and Upgrades

Entry by Application Group SAP

Application Components SAP ERP SAP

ERP 2004 SAP Business Packages.

XI Content forApplications

SAP NetWeaver(SAP XI)

Several SAP Applications make use of XI anddeliver XI content which is shipped as part ofthe application.

Table 4

AdditionalComponents


SAP ITS 6.20 Stand-alone application SAP ITS 6.20 is necessary to run ITS-basedESS services. These services are notsupported with SAP ITS 6.40.

SAP BusinessConnector

4.6 /4.7

Stand-alone application See SAP Note 571530 inservice.sap.com/notes.

SAP MobileInfrastructureClient 2.5

Client installation

(includes a Web serverand a database layer)

The SAP MI Client Component is installedlocally on mobile devices.

Mobile Sales forHH (ECC) 2.0

SAP NetWeaver ABAP

SAP NetWeaver Java

Any SAP NetWeaver-based system can beconfigured as a Mobile Infrastructuremiddleware system.

Mobile TimeSheet 1.6

SAP NetWeaver ABAP

SAP NetWeaver Java


Mobile Travel

Expenses 1.6

SAP NetWeaver ABAP

SAP NetWeaver Java

Any SAP NetWeaver-based system can be

configured as a Mobile Infrastructuremiddleware system.

Mobile AssetManagement 2.5

SAP NetWeaver ABAPSAP NetWeaver Java


Mobile DirectStore Delivery2.0

SAP NetWeaver ABAPSAP NetWeaver Java


LSOOP 3.0Offline Player

Java Development Kit(JDK) 1.4.2

This component is part of the LearningSolution 3.0.

It is an offline frontend application and can be

October 2004 17


18/83


installed on Windows NT4.0/2000/XP.

LSOAE 3.0 Java Development Kit(JDK) 1.4.2

This component is part of the LearningSolution 3.0.

It is a frontend application for authoring andcan be installed on WindowsNT4.0/2000/XP.

SAP GUI Standalone Frontend application

Table 5

3.1.1. Example Comm. Structure: SAP LearningSolution

Certain solutions or business scenarios require several components so that they can be realized.

These components communicate with each other and affect each other. The Learning Solution isan example of this:

The following graphic illustrates the communication structures between the individual componentsof the SAP Learning Solution and between the components, the Enterprise Portal, and the ECC5.0.

Figure 4: SAP Learning Solution, Communication Structure

3.1.2. Related InformationSAP Enterprise Portal

SAP NetWeaver Technical Operations ManualAdditional Administration of PortalPlatform

SAP Web Application Server (ABAP)

18 Oktober 2004
http://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htm


19/83


SAP NetWeaver Technical Operations ManualGeneral Administration of SAP

NetWeaverAdministration of the SAP Web Application Server (ABAP)

SAP Web Application Server (Java)

SAP NetWeaver Technical Operations ManualGeneral Administration of SAPNetWeaverAdministration of the SAP Web Application Server (Java)

Database administration

SAP NetWeaver Technical Operations ManualGeneral Administration of SAP

NetWeaverDatabase AdministrationAdministration of

SAP BW

help.sap.comDocumentationmySAP ERPmySAP ERP 2004SAP

NetWeaverInformation IntegrationSAP Business Information WarehouseBI

PlatformBusiness Planning and Simulation

SAP Learning Solution

service.sap.com/ERP-INSTmySAP Business SuitemySAP ERPmySAP

ERP 2004SAP Learning Solution 3.0

SAP Security Guides

service.sap.com/security

For up-to-date information, see SAP Service Marketplace at service.sap.com/ERP-INSTmySAP ERP 2004. Here you can find detailed information about the technical system landscape ofmySAP ERP 2004.

3.2. Related DocumentationThe following table indicates where you can find more information about the technical systemlandscape.

Topic Guide/Tool Quick Link to theSAP ServiceMarketplace(service.sap.com)

Central overviewdocumentation formySAP ERP

mySAP ERP 2004 Master Guide ERP-INST

Technology componentssuch as SAP WebApplication Server

Installation Guides ERP-INST

Sizing Quick Sizer Tool Sizing

Technical configuration Technical Infrastructure Guide Ti

Scalability Technical Infrastructure Guide Ti

High availability Technical Infrastructure Guide Ti

Security Technical Infrastructure Guide Ti

security

October 2004 19
http://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/http://service.sap.com/ERP-INSThttp://service.sap.com/securityguidehttp://service.sap.com/ERP-INSThttp://service.sap.com/ERP-INSThttp://service.sap.com/securityguidehttp://service.sap.com/ERP-INSThttp://help.sap.com/http://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htm


20/83


3.3. SAP Solution ManagerManaging your entire SAP solution landscape is a challenging task, but SAP has the answer: SAPSolution Manager.

The SAP Solution Manager is a platform that provides the integrated content, tools, andmethodologies that you need to implement, support, operate, and monitor your enterprise'ssolutions from SAP.

With SAP Solution Manager, companies can minimize risk and increase the reliability of their ITsolutions.

SAP Solution Manager helps reduce TCO throughout the solution life cycle.

SAP Solution Manager helps companies manage their core business processes and link businessprocesses to the underlying IT infrastructure.

SAP Solution Manager supports both SAP and non-SAP software and helps companies get more

from their existing IT investments.

Due to an ongoing spread of distributed systems and dependencies of business processes beyondsingle system boundaries, the need for a new efficient support infrastructure is obvious.Integration aspects covering technical as well as business (applications) needs of theseheterogeneous environments are more crucial than ever and need to be mastered perfectly.Software change management has to be taken into consideration including all aspects of singlecomponent upgrade and release strategies as well as the development and the modification ofstandard scenarios.Minimization of potential risks during operations and early establishment of operation concepts isthe key to avoid unforeseen financial investments and lower the operation cost to a minimum.

Implementation Tools, Content, and Methodologies to Efficiently Implement SAP SolutionsThe SAP Solution Manager gives you access to the tools, content, and methodology youneed to implement and optimize your SAP solutions - from both a functional and atechnical perspective.

Solution Monitoring From System Monitoring to Business Process Monitoring

The SAP Solution Manager helps you meet the performance and availability expectationswith solution monitoring which monitors the entire business process across multiplecomponents. The following monitoring functions are available: SAP EarlyWatch Alert,system monitoring, interface monitoring and business process monitoring, service levelreporting.

Operations Services to Manage Your SAP Solution

The operations area of the SAP Solution Manager provides access to SAP SupportServices, including remote services, on-site services, self-services, and best practicedocuments. Based on your solution configuration, recommendations for these services aretriggered dynamically.

Support Desk Support Every Step of the Way

The support desk of the SAP Solution Manager offers a complete infrastructure fororganizing and operating a solution-wide support organization at your site. This promoteseffective user support in your SAP solution landscape every step of the way - from the end-users to your internal support organization and, when necessary, to SAP.

20 Oktober 2004
https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000415888&_SCENARIO=01100035870000000202https://websmp204.sap-ag.de/~sapidb/011000358700000430152003Ehttps://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000416009&_SCENARIO=01100035870000000202https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000416016&_SCENARIO=01100035870000000202https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000416016&_SCENARIO=01100035870000000202https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000416009&_SCENARIO=01100035870000000202https://websmp204.sap-ag.de/~sapidb/011000358700000430152003Ehttps://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000415888&_SCENARIO=01100035870000000202


21/83


Figure 7: SAP Solution Manager Life-Cycle Approach

October 2004 21


22/83


4. Monitoring of mySAP ERPMonitoring of mySAP Technology is an essential task within the Solution Operation of mySAP

Technology.

With the monitoring architecture, SAP provides a flexible and universally usable infrastructure withwhich you can centrally monitor your entire IT landscape and which quickly and reliably reportsproblems that occur.

For more information about System Monitoring and Alert Management (Alert Monitor), see SAP

Service Marketplace at service.sap.comSAP NetWeaver.Alerts are a central element of the monitoring. These quickly and reliably report problems - such asa value exceeding or falling below a particular threshold value, or an IT component being inactivefor a defined period of time (see service.sap.com/monitoring ).

Managing distributed mySAP.com solutions or client-server systems places high demands on thesystem administration - demands that increase significantly through the inclusion of the Internet in

business processes. Using the Monitoring Architecture of the Computing Center ManagementSystem (CCMS), SAP provides a flexible and universally applicable infrastructure, with which youcan monitor the entire IT landscape centrally and which quickly and reliably reports problems thatoccur.

The Monitoringof mySAP ERPsection provides you with an overview of the general tools anddescribes them in detail. The following monitors that are valid for the ABAP area and non-ABAParea provide an improved overview of monitoring in the ERP area. The various monitor views areshown in the graphic below.

ABAP Non-ABAP

The monitoring components thatsupport you when operating yoursystem landscape are introducedbelow.

In ECC the Operating SystemMonitor, Alert Monitor, WorkloadMonitor, ICM Monitor, CCMS (seeCCMS Monitoring Console)

SAP Web Application Server Javaprovides a centralized system forlogging and tracing data.- Logging API- Log Configurator Service- Log Manager- Log Viewer, Standalone Log ViewerDetail Monitors ITS, IGS, TREX

Figure 8: Monitoring in the ABAP and non-ABAP areas

In addition, the following section contains information on how you can connect the CCMS using theSolution Manager and how the individual monitors can be connected as well.

Overview Monitoring ABAP Components: :Solution Manager(help.sap.com/saphelp_erp2004/helpdata/en/02/5ec13690581b20e10000009

b38f839/frameset.htm )

In the Solution Manager area Operating Processing, functions such as creating a monitor,integration of solutions and service administration are described under the SystemMonitoringsection.

In addition, there is an example illustrating how to set up a CCMS monitor.

22 Oktober 2004
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7da1505211d189550000e829fbbd/frameset.htmhttp://service.sap.com/monitoringhttp://help.sap.com/saphelp_erp2004/helpdata/en/02/5ec13690581b20e10000009b38f839/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/02/5ec13690581b20e10000009b38f839/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/02/5ec13690581b20e10000009b38f839/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/02/5ec13690581b20e10000009b38f839/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/02/5ec13690581b20e10000009b38f839/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/02/5ec13690581b20e10000009b38f839/frameset.htmhttp://service.sap.com/monitoringhttp://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7da1505211d189550000e829fbbd/frameset.htm


23/83


Overview Monitoring Non-ABAP Components:

CCMS Monitoring for Java:SAP NetWeaver Technical Operations ManualSAP NetWeaver-Application

Platform (SAP Web Application Server) Java Technology in SAP Web

Application ServerAdministration ManualServer AdministrationLogging Monitoring J2EE Log Files in the CCMS.

For more information see the Portal Administration Guide under Monitoring withthe SAP Solution Manager and for more information about the properties of theservices Overview, see Monitoring.

In the Individual Monitors area you have information on the third-party componentssuch as TREX, IST or IGS, each of which has their own monitor. To clarify thedifference, Figure 9 illustrates how the WebAS with central monitoring is used tolog and trace the various Java components.

o Monitoring TREX:

SAP NetWeaver Technical Operations Manual TREX monitor.

Monitoring systems such as CCMS can analyze these files and make systemadministrators aware of new error messages. If TREX is connected to the SAPSolution Manager, a CCMS agent analyzes the alert files and makes themonitoring system aware of changes. The monitoring system stages the alerts sothat system administrators become aware of them.

Trace files contain messages that the TREX components return during routineoperation. With the standard configuration, the trace files only contain errormessages. By default, the trace files are located in the directory\trace .

Transactions such as SM51 (Check Application Servers), RZ20 (Alerts), SM50(Work Processes), and SM13 (Update Records) are used for the ERP system.

o Monitoring:

SAP NetWeaver Technical Operations ManualGlobal Workload Monitor

SAP NetWeaver Technical Operations ManualWorkload Monitor

SAP NetWeaver Technical Operations ManualCCMS MonitoringConsole

Note: The abbreviation TOM is used for SAP NetWeaver Technical Operations Manual.

October 2004 23
http://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/cd/4f1a403233dd5fe10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/1a/40f83ee0e66856e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/1a/40f83ee0e66856e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/1c/0bfc3f48ecc742e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/eb/aaa0af02a0734a82c0241f5f62cb67/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/48/1e443cfb06e532e10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/2d/b8be3befaefc75e10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/8e/de192d2884ff4298b960be23a2494b/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/8e/de192d2884ff4298b960be23a2494b/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/8e/de192d2884ff4298b960be23a2494b/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/8e/de192d2884ff4298b960be23a2494b/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/2d/b8be3befaefc75e10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/48/1e443cfb06e532e10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/eb/aaa0af02a0734a82c0241f5f62cb67/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/1c/0bfc3f48ecc742e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/1a/40f83ee0e66856e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/1a/40f83ee0e66856e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/cd/4f1a403233dd5fe10000000a155106/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htm


24/83


Area Link

ABAP General Administration of SAP NetWeaver:

(help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/frameset.htm)

Non-ABAP Genaral Visual Administrator:

TOM Management of the SAP Web Application Server (Java) Management of the SAP Web Application Server (Java) AdministrationTools for the SAP J2EE Engine Online Administration: Visual Administrator

Use the Config Tool to do this.

You can use the Deploy Service of the Visual Administrator to deploy andupdate your applications, and so on.

TOM Management of the SAP Web Application Server (Java) Administration Manual Server Administration J2EE EngineAdministration Tool Visual Administrator or

help.sap.com/saphelp_erp2004/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm

Table 1

Further links relating to non-ABAP NetWeaver:

Components Links

SAP NetWeaver help.sap.comSAP NetWeaverRelease 04

SAP Enterprise Portal SAP NetWeaver Technical Operations Manual (TOM) Administrationof the SAP Web Application Server (ABAP) Monitoring

TOMAdditional Administration of SAP NetWeaver Components

PortalMonitoring Monitoring Technology and Logging

SAP Web ApplicationServer (Java)

TOMGeneral Administration of SAP NetWeaverAdministration of

the SAP Web Application Server (Java)Monitoring and ErrorHandling of the SAP Web AS Javaand Database Administration

TOMGeneral Administration of SAP NetWeaverDatabase

AdministrationAdministration of

Table 2

24 Oktober 2004
http://help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/cb/6acf38422f0244b960236643e3cc46/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htmhttp://help.sap.com/http://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/5a/84b83b3683094be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/5a/84b83b3683094be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/http://help.sap.com/saphelp_erp2004/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/cb/6acf38422f0244b960236643e3cc46/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/e8/f48b33f9a3423c9e688dfa56330e79/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/frameset.htm


25/83


4.1. General Monitoring OverviewThe following graphic illustrates the three areas that are relevant for monitoring.

The settings from the Solution Manager in the Operating area enable you to view the alerts that aretransferred from CCMS to the Solution Management system.

After the CCMS was configured for the relevant systems, you can request information from there.The CCMS agents provide you with the information.

The individual monitors are introduced in the third area. With an additional configuration, individualmonitors can also be connected through CCMS.

General Monit or ing - Overview-

I. Solution Manager(4.1.1)

Implementation

Operation Alerts

II. Adapting CCMS(4.1.2)

Classify the processes

Performance critical

informations

III. Detail for Monitoring(4.1.3)

Figure 9: General Monitoring Overview

4.1.1. General Monitoring Solution ManagerThe following information is based on Figure 9, section I. Solution Manager.

The operation area contains services to manage your SAP solution. Based on your solutionconfiguration, recommendations for these services are triggered dynamically.

Recommended Links:General Solution Manager (help.sap.com/saphelp_sm310sp12/helpdata/en/index.htm )

Configuration SAP Solution Manager 3.1 (SP12): service.sap.com/solutionmanager Installation Guides Solution Monitoring

Alerts SAP NetWeaver Technical Operations ManualAlerts

Table 3

Alert Description:

Alerts are a central element of monitoring. They report faults quickly and reliably such as when areported value exceeds or falls below a particular threshold value, or an IT component is inactivefor a defined period of time.

October 2004 25
http://help.sap.com/saphelp_sm310sp12/helpdata/en/index.htmhttp://help.sap.com/saphelp_sm310sp12/helpdata/en/index.htmhttp://service.sap.com/solutionmanagerhttp://help.sap.com/saphelp_sm310sp12/helpdata/en/1a/ce0de7d1910e4f8c5a880adee5b764/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7dae505211d189550000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7dae505211d189550000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_sm310sp12/helpdata/en/1a/ce0de7d1910e4f8c5a880adee5b764/frameset.htmhttp://service.sap.com/solutionmanagerhttp://help.sap.com/saphelp_sm310sp12/helpdata/en/index.htmhttp://help.sap.com/saphelp_sm310sp12/helpdata/en/index.htm


26/83


These alerts are displayed in the Alert Monitor (transaction RZ20). This eases the workload on thesystem administrators, as they then track problem messages only, instead of a large quantity ofsystem data.

General Information: You can find general information about the alert monitor in the SAP Help

Portal at help.sap.comSAP NetWeaverRelease '04EnglishSAP LibrarySAPNetWeaverSolution Life Cycle ManagementSolution MonitoringMonitoring in CCMSAlert Monitoring.

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

The CCMS Monitoring Console (MC) allows the clear display of monitoring data for centralmonitoring of SAP system landscapes. This data comes from the following sources:

CCMS monitoring architecture

Kernel statistics

Process Monitoring Infrastructure

Both the configuration of the landscapes and the display of the monitored components are sointuitive that the MC can be operated easily by less specialized employees without training or longperiods of adjustment.

CCMS Monitoring Architecture

Figure 10: CCMS Monitoring Architecture

The CCMS Monitoring Architecture is not a monolithic monitoring and administration program.Rather it offers a flexible framework into which extensive monitoring and administration functionscan easily be added.

For more information, see SAP NetWeaver Technical Operations ManualAdministration of the

SAP Web Application Server (ABAP) MonitoringThe Alert MonitorThe Monitoring

Architecture: Concept.

26 Oktober 2004
http://help.sap.com/saphelp_erp2004/helpdata/en/c3/0843f838f3c34785d207874c89614f/content.htmhttps://websmp103.sap-ag.de/~sapidb/011000358700011052542001Ehttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7da1505211d189550000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7da1505211d189550000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7da1505211d189550000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7da1505211d189550000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttps://websmp103.sap-ag.de/~sapidb/011000358700011052542001Ehttp://help.sap.com/saphelp_erp2004/helpdata/en/c3/0843f838f3c34785d207874c89614f/content.htm


27/83


CCMS via Alert Monitor

The monitoring architecture, a solution within mySAP technology, centrally monitors any ITenvironments - from individual systems to networked mySAP.com solutions to complex ITlandscapes consisting of several hundred systems. It is available in every mySAP.com solution and

can be used immediately after installation. You can easily extend the architecture with SAP andnon-SAP components.

Alerts are a central element of monitoring that quickly and reliably report problems such as when avalue exceeds or falls below a particular threshold value, or an IT component is inactive for aspecified length of time. These alerts are displayed in the Alert Monitor; this reduces the workloadof the system administrators, as they are only responsible for problem messages as opposed tohaving to monitor vast amounts of system data.

The Alert Monitor is therefore a central tool with which you can efficiently administer and monitordistributed mySAP.com solutions or client-server systems. The Alert Monitor displays problemsquickly and reliably.

The Alert Monitor provides the following functions:

You have complete and detailed monitoring of all SAP and non-SAP systems, the host systems,and the database.

All errors generate alerts which are displayed in a tree structure.

The alerts contain a status indicator with a color and a numerical value. Yellow represents awarning, red represents a problem, and the numerical value represents the severity of a possibleerror. In the tree structure, the most severe alerts are displayed upwards in the display hierarchy. Ifa tree node does not display an alert, this means that no errors have occurred in the branch belowit.

You can assign analysis methods and auto-reaction methods to the alerts. These assist you inprocessing the error quickly. If you double-click the alert, the monitoring architecture starts theassigned analysis method (for example, the job management transaction for a job that has

terminated prematurely). An auto-reaction method, on the other hand, starts automatically as soonas the alert occurs. Auto-reaction methods include executing operating system commands, andsending an e-mail or SMS message to the system administrator.

The Alert Monitor contains various views in which either the current or the open (that is, those thathave not yet been analyzed) problem messages are displayed. Alerts are also archived.

Threshold values, methods, and detailed help for a large number of monitoring attributes, and threeextensive monitor sets with monitors for all aspects of system management are predefined in themonitoring architecture on the basis of best practices and are available for you to use in every SAPsystem.

October 2004 27


28/83


4.1.2. Monitoring Adapting CCMSThe following information is based on Figure 9, section II. Adapting CCMS.

CCMS can be operated independently or together with the Solution Manager. In this constellation,CCMS delivers the Solution Manager with the required information about error messages orperformance problems.

The monitoring technology in the SAP Solution Manager is based on functions of the ComputingCenter Management System (CCMS):

Figure 11: CCMS with Solution Manger Monitoring Overview

You can download the SAP Solution Manager from the SAP Service Marketplace at no cost. Youneed Version 3.1.

A general description of monitoring follows in this section. The ERP standard components in theABAP area and non-ABAP are then described with their links and supplements.

The entire monitoring is covered in the ABAP area using CCMS.

The CCMS includes settings for the following: system management (start, stop, reconfiguration ofthe system), background processing, performance, system profiles management, databasemanagement, system monitors, and more. Using the Monitoring Architecture of the CCMS, SAPprovides a flexible and universally applicable infrastructure, with which you can monitor the entireIT landscape centrally and which quickly and reliably reports problems that occur. You can alsoview the non-ABAP components.

The architecture runs on all SAP Web Application Servers and can easily be extended with SAPand non-SAP components. CCMS agents are used to include components that are monitoredremotely. These have the following properties:

Connection to the central monitoring system using RFC to provide greater downtimesecurity and universal usability

Use of a push mechanism to proactively report alerts and data to the central system

28 Oktober 2004


29/83


Integration of the SAPOSCOL operating system collector to transfer data for the operatingsystem level (from CPU utilization and fill levels of file systems to details of individualmonitored processes)

Connection of systems with SAP Basis 3.X and components on which no SAP Web

Application Server is installed

Monitoring of any log files

Example

The following example illustrates setting up CCMS.

To create a new monitor, RFC connections are necessary.

1. Create RFC _RZ20_ANALYZE to target System (TA SM59) (Logon CurrentUser)

2. Create RFC _RZ20_COLLECT to target System (TA SM59)

(Communication User)

3. Create Monitoring Entry: TA RZ21

4. Save.

5. Activate CCMS Monitor Set Maintenance (TA RZ20):

6. Create new Monitor Set :

For information about configuring CCMS agents, see the CCMS Agents: Features, Installation, and

Operation manual underservice.sap.com/monitoring

Monitoring in Detail.

October 2004 29
http://service.sap.com/~sapidb/011000358700003240702001ehttp://service.sap.com/~sapidb/011000358700003240702001ehttp://service.sap.com/monitoringhttp://service.sap.com/monitoringhttp://service.sap.com/~sapidb/011000358700003240702001ehttp://service.sap.com/~sapidb/011000358700003240702001e


30/83


CCMS Agents:

Agents are useful if there is no ABAP stack running as well and the information has to be forwardedto CCMS.

For more information, see the aforementioned CCMS Agents: Features, Installation, and OperationGuide.

CCMS Agents Description

SAPCCMSR SAPCCMSR creates the connection between the host and the CEN. ASAPCCMSR agent program is required on each host where a CRMcomponent is installed other than an SAP Basis based system, for example,SAP J2EE or SAP IPC hosts, and so on.

SAPCCMSx A SAPCCM4X agent program on each host on which a SAP System isrunning. If more than one application server is running on a host, install aSAPCCM4X agent for each application server.

SAPOsCol The SAPOsCol is responsible for gathering the information about thecomponents on operating system level. (There is an own guide for SAPOsColin the monitoring area.)

Table 4

Recommendation: Parameter Settings for Using Multiple Monitors

If you use multiple monitors, we recommend that you set the rdisp/tm_max_no parameter to

1000. You can then display all permitted connections using transaction SM21.

ABAP:

The following is a summary of the transactions necessary for checking the system thoroughly.

Transaction Description

DB12 Backup (see section 4.1.5)

DB02 DB ok, tablespaces

SM50, SM51 Work processes running/ runtime

SM21 System log

SM37 Check jobs

SM12 Locks

AL08, SM04 User

SP01 Spooler

ST22 ABAP Dumps

ST06 System information

Table 5

30 Oktober 2004


31/83


4.1.3. Detail MonitoringThe following information on the individual software components for monitoring is based on Figure9, section III. Detail for Monitoring.

SAP NetWeaver ABAP

Non ABAP components

C-Project

ITS

WFM

BusinessConnector

IPC

SRM IPC

LSOOP

Mobile

ComponentOverview

SAP ECC

SAP BW

SAP xSS

SAP SRM

Finbasis

SAP ERec.

LSOCP /FE

CCM

ABAP components

NW

Portal

MSS

FSCMBiller

Paragraph 4.1.3.1 Paragraph 4.1.3.2

Figure 12: ERP Component Overview

The various monitors can be combined according to the selected system landscape. If ECC andSAP BW are operating in one system, then only one monitor is required, for example, to monitorthe NetWeaver area. Application-specific monitors must be considered for each application,regardless of whether or not the components are operating in one system (client).

For more information about BW Monitoring, see SAP NetWeaver Technical Operations Manual

Additional Administrator of SAP Business InformationMonitoring the SAP BW BW Monitorin CCMS.

For more detailed information about the various system landscape combinations, see the ERP

Master Guide under service.sap.com/ERP-INST mySAP ERP 2004.

4.1.3.1. ERP ABAP ComponentsThis section provides you with an overview of the ABAP ERP components with links andreferences to further information and any relevant supplements.

For more information, see SAP NetWeaver Technical Operations Manual and SAP ServiceMarketplace at service.sap.com/monitoring .

October 2004 31
http://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c3/0dec3b6e011341e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c3/0dec3b6e011341e10000000a114084/frameset.htmhttp://service.sap.com/ERP-INSThttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://service.sap.com/monitoringhttp://service.sap.com/monitoringhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://service.sap.com/ERP-INSThttp://help.sap.com/saphelp_nw04/helpdata/en/c3/0dec3b6e011341e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c3/0dec3b6e011341e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htm


32/83


Components Description

ECC TOMGeneral Administration of SAP NetWeaverAdministration of the

SAP Web Application Server (ABAP)Monitoring.

BW TOMAdditional Administrator of SAP Business InformationMonitoring the

SAP BWBW Monitor in CCMS.

Additional Administrator Workbench (see BW-AWB):

The Administrator Workbench is a supplement for the area SAP BW. In SAPBW, the administration area tasks are stored in various data sources, forexample. The Administrator Workbench is the central administration tool inSAP BW and is used for modeling data, retrieving data, and for storing data.The Administrator Workbench is used to control the entire data retrievalprocess, which ranges from extracting data from the source system to savingthis data in InfoCubes, and organizing the maintenance and administration of

datasets. The Administrator Workbench is also used to schedule and monitorthe loading of data. The most important task, namely the creation and filling ofdata targets is the prerequisite for being able to use queries for reporting.

To activate the BW functionality you can either import the required BI Contentor process the transaction of the BW Administration Workbench.

ESS SAP NetWeaver Technical Operations ManualGeneral Administration of

SAP NetWeaverAdministration of the SAP Web Application Server (ABAP)Monitoring.

For information about Special Claims Monitor, see help.sap.com

DocumentationmySAP ERPEnglishSAP ERP Central ComponentHuman ResourcesPersonnel Management (PA)Benefits Administration

(PA-BN).

SEM For information about Monitoring SAP NetWeaver ABAP, see TOMAdditional Administrator of SAP NetWeaver ComponentsSAP BusinessWarehouseMonitoring the SAP

Additional SEM-FinBasis:

SAP SEM is subdivided into various SEM components which contain certainbusiness scenarios.

For information about SEM, see Business Planning and Simulation(SEM-BPS)(help.sap.com/saphelp_nw04/helpdata/en/53/155c3ce7055a37e10

000000a11405a/frameset.htm ).

For more information about SAP SEM, see SAP Help Portal underhelp.sap.commySAP Business Suite SAP Strategic Enterprise Mgmt.

SAP SEM-BW 4.0 English SEM Strategic Enterprise Management.

This is an SAP NetWeaver add-on, so the majority of administration isperformed using basic administration.

The following describes the transactions and reports for SAP SEM specificmonitoring issues:

SEM Components: SEM-BPS (BSP = Business Planning and Simulation):

Transaction: BPS_STAT0, BPS_STAT1; Analysis of SEM application statisticsdata written by SEM.

Transaction: BPS_TRACE: SEM application trace which you can record and

32 Oktober 2004
http://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/78/92e145e557114187e85957b29fcae1/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c3/0dec3b6e011341e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/78/92e145e557114187e85957b29fcae1/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/7e/8a5f70545711d1891c0000e8322f96/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/7e/8a5f70545711d1891c0000e8322f96/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/53/155c3ce7055a37e10000000a11405a/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/53/155c3ce7055a37e10000000a11405a/frameset.htmhttp://help.sap.com/http://help.sap.com/http://help.sap.com/saphelp_nw04/helpdata/en/53/155c3ce7055a37e10000000a11405a/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/53/155c3ce7055a37e10000000a11405a/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/7e/8a5f70545711d1891c0000e8322f96/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/7e/8a5f70545711d1891c0000e8322f96/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/78/92e145e557114187e85957b29fcae1/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/c3/0dec3b6e011341e10000000a114084/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/78/92e145e557114187e85957b29fcae1/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htm


33/83


Components Description

evaluate for specified end users.

SEM Components: SEM-BCS (BCS = Business Consolidation)

Report UC_STAT0: Evaluation of SEM-BCS statistics (see SAP Note 657098).

SRM For information on SAP Enterprise Buyer4.0, see SAP Help Portal at

help.sap.com mySAP Business Suite mySAP Supplier RelationschipManager SAPArchitecture and TechnologyAdministration.

The following software components exist: SRM 4.0 using SRM Server 5.0 andBW 3.5.

E-Recruiting For SAP E-Recruiting there is no individual alert monitoring necessary/required.In SAP E-Recruiting the application log (transaction SLG1) and the standardmonitoring of the SAP WebAS are used.

For monitoring of the search functionality inside SAP E-Recruiting the portal

component of NetWeaver 04 TREX is used. For further information, see thecorresponding section in the Master Guide and SAP Service Marketplace atservice.sap.com/notes SAP Note 717803.

LSO For information about SAP Learning Solution, see help.sap.com

DocumentationmySAP Business SuiteSAP Learning SolutionTraining Management in the SAP Learning Solution and AuthoringEnvironment.

You can use the transaction SLG1 Application Log: Display Logsfor errors thatoccur when communicating between non-ABAP components of the SAPLearning Solutionand the back-end system (ERP system).

Table 6

4.1.3.2. ERP Java ComponentsFor information about ERP Java components, see SAP Service Marketplace at

service.sap.com/monitoring SAP NetWeaverSolution Life-Cycle Management

System ManagementJava Monitoring and Management.

The task of Non-ABAP Monitoring and Management is to provide developers, supporters andcustomers with information about

Configuration information, such as release, version, host, port, and so on

Critical conditions monitoring for IT operations

Detailed performance and status data for detecting and diagnosing problems Detailed statistics on activity and resource consumption for accounting and auditing, SLA

reporting, and problem analysis

Java Monitoring:

Describes the general concepts of the monitoring system, the type of monitored data, how tointerpret it, and how to configure the system or the applications running on J2EE Engine accordingto the monitoring signals.

For information about Java Monitoring, see help.sap.comSAP NetWeaver 04SAPNetWeaver --> Application Platform (SAP Web Application Server --> ABAP Technology --> Java

October 2004 33
http://help.sap.com/saphelp_ls200/helpdata/en/30/e63a3c24b4a00ae10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_ls200/helpdata/en/e6/c9e81df5ed11d5997000508b6b8b11/frameset.htmhttp://help.sap.com/saphelp_ls200/helpdata/en/e6/c9e81df5ed11d5997000508b6b8b11/frameset.htmhttp://service.sap.com/monitoringhttp://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000468268&http://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000468268&http://service.sap.com/monitoringhttp://help.sap.com/saphelp_ls200/helpdata/en/e6/c9e81df5ed11d5997000508b6b8b11/frameset.htmhttp://help.sap.com/saphelp_ls200/helpdata/en/e6/c9e81df5ed11d5997000508b6b8b11/frameset.htmhttp://help.sap.com/saphelp_ls200/helpdata/en/30/e63a3c24b4a00ae10000000a11402f/frameset.htm


34/83


Technology in SAP Web Application Server Platform (SAP Web Application ServerAdministration ManualServer AdministrationMonitoring

Log Monitoring: all important events that occur in a cluster node of the J2EE cluster are recorded in

log files. All SAP Web AS Java components use the same infrastructure for logging. The logging issimplified using a uniform configuration and a common display program (Log Viewer). The LogViewer allows you to search quickly and efficiently for log files with certain error and eventinformation over several servers. The log monitoring can be performed using the VisualAdministrator or the CCMS.

LogViewer Description

Standalone Logviewer

Server

The standalone LogViewer Server monitors the log files that areregistered for that server. It must be installed on every host of thesystem landscape. The LogViewer servers run completely independent

from each other and from the J2EE engine. Logs can be viewed even ifthe J2EE engine is not running.

LogViewer Client The LogViewer client connects to one or more LogViewer servers anddisplays the logs. Network traffic is minimized because only thedisplayed portions of the log files are transmitted. The client and theserver are installed using the same installation package - the client isneeded on the central monitoring server, the server on all physicalservers where log files are to be read.

Table 7

Further links relating to ERP non-ABAP components:

Components Links

SAP NW For information about the administration of SAP NetWeaver, see TOM underGeneral Administration of SAP NetWeaver.

SAP Web Application Server (Java):

For more information, see TOM under General Administration of SAP NetWeaver

Administration of the SAP Web Application Server (Java)Monitoring andError Handling of the SAP Web AS Java.For information about Database

Administration, see TOM under General Administration of SAP NetWeaver

Database AdministrationAdministration of .

SAP

EnterprisePortal

For information about SAP Enterprise Portal, see TOM under Additional

Administration of Portal Platform

Monitoring) and Monitoring Technologyand Logging.

Administration Guide(help.sap.com/saphelp_nw04/helpdata/en/34/76bd3b6e74d708e10000000a11402f/frameset.htm )

SAP NetWeaver How-To Guides in SAP Service Marketplace(service.sap.com/nw-howtoguides )

For more detailed information, see SAP Service Marketplace at

service.sap.com/nw-howtoguides Portal, KM and Collaboration.See also SAP Note 741847 LogAdmin is not delivered with NW SPStack 4.

34 Oktober 2004
http://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/68/f4bc3deaf28d33e10000000a11405a/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/e2/f410409f088f5ce10000000a155106/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/57/5f1140d72dc442e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/2e/30e93adccb444b871f3d4e7f905b84/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/2e/30e93adccb444b871f3d4e7f905b84/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/29/7d4ed11dc11d45a73850df6e8a1bac/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/2e/30e93adccb444b871f3d4e7f905b84/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/5a/84b83b3683094be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/5a/84b83b3683094be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/34/76bd3b6e74d708e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/34/76bd3b6e74d708e10000000a11402f/frameset.htmhttp://service.sap.com/nw-howtoguideshttp://service.sap.com/nw-howtoguideshttp://help.sap.com/saphelp_nw04/helpdata/en/34/76bd3b6e74d708e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/34/76bd3b6e74d708e10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/5a/84b83b3683094be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/5a/84b83b3683094be10000000a11402f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/2e/30e93adccb444b871f3d4e7f905b84/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/29/7d4ed11dc11d45a73850df6e8a1bac/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/2e/30e93adccb444b871f3d4e7f905b84/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/2e/30e93adccb444b871f3d4e7f905b84/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_erp2004/helpdata/en/aa/464671df1bc642bddde55f686f2f8c/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/ec/9e1802dd600947abafd2248518697f/frameset.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/57/5f1140d72dc442e10000000a1550b0/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/e2/f410409f088f5ce10000000a155106/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/68/f4bc3deaf28d33e10000000a11405a/content.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/0d/a3bb3eff62847ae10000000a114084/content.htm


35/83


Components Links

IPC Information TechnologyInternet Sales A

Date post:	05-Apr-2018
Category:	Documents
Upload:	ofrq
View:	224 times
Download:	0 times

ERP Operation Guide

Documents