Solman master guide.pdf

8/22/2019 Solman master guide.pdf

http://slidepdf.com/reader/full/solman-master-guidepdf 1/12

Master Guide

April 1, 2005



© 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.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software vendors.

Microsoft®

, WINDOWS®, NT

®, EXCEL

®, Word

®, PowerPoint

®and

SQL Server®

are registered trademarks 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

®, Informix and Informix

®Dynamic Server

TM

are

trademarks of IBM Corp. in USA 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®, the Citrix logo, ICA

®, Program Neighborhood

®, MetaFrame

®,

WinFrame®, VideoFrame

®, MultiWin

®and other Citrix product names

referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered

trademarks of W3C®

, World Wide Web Consortium, Massachusetts

Institute of Technology.

JAVA®

is a registered trademark of Sun Microsystems, Inc.

J2EE™ 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.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business

Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,

Management Cockpit, mySAP, mySAP.com, 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. MarketSet and Enterprise

Buyer are jointly owned trademarks of SAP Markets and Commerce

One. All other product and service names mentioned are the

trademarks of their respective owners.

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.

Any Java™ Source Code delivered with this product is only to be used

by SAP’s Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:

Neurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20



Type Style Represents

Example Text Words or characters that appearon the screen. These includefield names, screen titles,pushbuttons as well as menunames, paths and options.

Cross-references to other

documentation

Example text Emphasized words or phrases inbody text, titles of graphics andtables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, table names,and individual key words of aprogramming language, whensurrounded by body text, forexample, SELECT andINCLUDE.

Example text Screen output. This includes fileand directory names and theirpaths, messages, names ofvariables and parameters,source code as well as names ofinstallation, 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.

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

Icon Meaning

Caution

Example

Note

Recommendation

Syntax



Master Guide: SAP Solution Manager 3.2

4 April, 2005

Contents

1. GETTING STARTED..............................................................................5

Installation Procedure ...........................................................................................................................5

Upgrade Procedure........................................................... ........................................................... ..........6

Overview of Guides........................................................... ........................................................... ..........7

2. SYSTEM INFRASTRUCTURE...............................................................9

Software Components............................................................................................................................9

Hardware Requirements .................................................. ........................................................... ..........9

3. SCENARIOS ........................................................................................10

Service Desk..........................................................................................................................................10

Implementation and Distribution ........................................................ ...............................................10

Upgrading SAP Solutions........................................................... .........................................................10

Change Request Management.............................................................................................................10

Solution Monitoring.......................................................... ........................................................... ........11

4. SAP NOTES.........................................................................................12




April, 2005 5

1. Getting StartedThis Master Guide provides an overview of the documents and information resources thatyou will need for the installation and configuration of SAP Solution Manager 3.2.

To learn more about SAP Solution Manager, go to the SAP Service Marketplace:service.sap.com/solutionmanager

This Master Guide and other related guides are updated frequently. Before youbegin an installation or an upgrade, ensure that you have the latest versions ofeach relevant guide. You can download the guides from the SAP Service

Marketplace: service.sap.com/instguides → SAP Components → SAP Solution

Manager → Release 3.2

You can find information on managing and running the SAP Web ApplicationServer in the Technical Operations Manual for mySAP Technology in the SAPLibrary under mySAP Technology Components .

Installation ProcedureIf you are installing a new system, follow the steps below to install and configure SAPSolution Manager 3.2:

1. Install SAP Solution Manager 3.2.

The installation steps are described in the SAP Solution Manager 3.2 InstallationGuide. An installation guide is available for each supported combination of operatingsystem and database.

Ensure that you have the most recent software component patches. These patches are

available from the SAP Software Distribution Center: service.sap.com/patches → SAP Software Distribution Center

2. To complete the configuration of the SAP Solution Manager 3.2, you will need to performsome additional steps.

The Implementation Guide (IMG) for Solution Manager in the SAP Solution Managersystem 3.2 will lead you through the configuration steps.

As of:

Support Package Level 6, choose the following path: SAP Reference IMG → SAP Web Application Server -> SAP Web Application Server ->SAP Solution Manager

Support Package Level 7, choose the following path: SAP Reference IMG →SAP

Solution Manager Implementation Guide →SAP Solution Manager.

For general information on the Implementation Guide SAP Solution Manager 3.2,see SAP Note 814853 (Implementation Guide SAP Solution Manager 3.2).

SAP Solution Manager 3.2 Configuration Guide provides additional information.




6 April, 2005

For an overview of recent changes to the configuration guide, see SAP Note782384 (Configuration Guide for Solution Manager 3.2: Latest Changes).

This SAP Note provides an overview of changes from Support Package 6.

Before you configure SAP Solution Manager 3.2, you must first create a newclient by making a copy of client 001.

The selected profile should be SAP_ALL; the initial user: SOLMAN (password:solman).

Do not make any changes to the pre-installed client 001.

Upgrade ProcedureIf you are upgrading from SAP Solution Manager 3.1 to 3.2, perform the steps describedbelow. Before you start the technical upgrade of SAP Solution Manager, some configurationsteps are required in SAP Solution Manager 3.1.

The upgrade procedure from SAP Solution Manager 3.1 to 3.2 is described in the UpgradeGuide: SAP Solution Manager 3.1 to 3.2.

After you have completed the steps described in the Upgrade Guide, follow the stepsprovided in the Implementation Guide SAP Solution Manager 3.2: SAP Reference IMG in theSolution Manager 3.2 system.

See also Overview of Guides [Page 7]

If you are migrating your SAP Solution Manager from Release 2.x to 3.2, youneed to first upgrade to SAP Solution Manager 3.1. Refer to the MigrationGuide: SAP Solution Manager 3.1. You can download this and other relevantguides from the SAP Service Marketplace: service.sap.com/instguides → SAP

Components → SAP Solution Manager → Release 3.1




April, 2005 7

Overview of Guides

The following guides are available for the installation of SAP Solution Manager 3.2. You candownload these guides from the SAP Service Marketplace: service.sap.com/instguides →

SAP Components → SAP Solution Manager → Release 3.2

Installation

Each Installation Guide for SAP Solution Manager 3.2 comprises two separate documents:Part 1 (Planning and Preparation) and Part 2 (Installation and Post-Installation).

Installation Guides for SAP Solution Manager 3.2 are available for the following databasesand operating systems:

AIX/DB2

AIX/DB6

AIX/Informix

AIX/MaxDB

AIX/Oracle

HP Tru64/Informix

HP Tru64/MaxDB

HP Tru64/Oracle

HP-UX/DB6

HP-UX/InformixHP-UX/MaxDB

HP-UX/Oracle

Linux/DB2

Linux/DB6

Linux/Informix

Linux/MaxDB

Linux/Oracle

Solaris/DB6

Solaris/Informix

Solaris/MaxDB

Solaris/Oracle

Windows/DB2

Windows/DB6

Windows/Informix

Windows/iSeries

Windows/MaxDB

Windows/Oracle




8 April, 2005

Windows/SQL

iSeries

z/OS/DB2

Upgrade

Upgrade Guide: SAP Solution Manager 3.1 to 3.2

Configuration

SAP Reference IMG

SAP Solution Manager 3.2: Configuration Guide

Scenarios:

• Service Desk

• Implementation and Distribution

• Upgrading SAP Solutions

• Change Request Management

• Solution Monitoring

Table 1: Overview of Guides for Installing or Upgrading to SAP Solution Manager 3.2




April, 2005 9

2. System InfrastructureThe SAP Solution Manager runs in a separate central system, to which all other SAPsystems are connected. Systems that are administered using the SAP Solution Manager are

referred to as "satellite systems".

P01

T01

Q01

BW1

AP1

SAP Solution Manager

System

SAPNet – R/3 Frontend

Satellite Systems

RFC connection:

- Send and update messages

- Service update and delivery

SAP Service Marketplace

Internet connection

- Order services

- Search SAP Notes

Customer Solution Landscape

SAProuter

RFC connections for data transfer:

- Solution monitoring (CCMS, EarlyWatch

Alert)- Configuration

- Distribution issues (Customizing, templates)- Change Request Management

Figure 1: Solution Landscape with the Central SAP Solution Manager System

Software ComponentsSAP Note 770200 (Upgrade Solution Manager 3.1 to 3.2) includes an overview of softwarecomponents and Support Package levels that must be installed in your SAP Solution

Manager system.

For information about new releases, delta upgrades, and Support Packages, see the SAPSoftware Distribution Center: service.sap.com/swdc

Hardware RequirementsHardware requirements, such as network bandwidth, physical memory, CPU power, and I/Ocapacity, are influenced by both business and technological requirements. You need to takeinto account the number of users using the various application components and the loadpalced on the network.

To determine the hardware requirements of your SAP Solution Manager system, go to the

SAP Service Marketplace: service.sap.com/sizing




10 April, 2005

3. ScenariosThe SAP Solution Manager supports the following scenarios:

•

Service Desk• Implementation and Distribution

• Upgrading SAP Solutions

• Change Request Management

• Solution Monitoring

These scenarios are described below.

Service DeskThe Service Desk allows you to create support messages, send them to SAP, and receive

replies from SAP. Issue tracking provides follow-up functionality for the Service Desk.

The basic Service Desk scenario needs to be configured as a prerequisite for theImplementation and Distribution, the Change Request Management, and theSolution Monitoring scenarios.

Implementation and Distribution

The Implementation and Distribution scenario supports the implementation of customerprojects and the definition of template projects and upgrade projects.

This scenario includes an implementation roadmap, an editor for creating and maintainingbusiness blueprints, access to the Implementation Guides (IMG), and tools for testing,monitoring and distributing Customizing.

Upgrading SAP SolutionsTo configure SAP Solution Manager for the Upgrading SAP Solutions scenario, follow thesteps to configure the Implementation and Distribution scenario. Note that the technicalrequirements apply only to the Release of the SAP solution that you are upgrading.

Change Request ManagementThe Change Request Management scenario consists of a workflow for implementing urgentcorrections and ….. The scenario uses interfaces between SAP Solution Manager, SAPChange Manager, and the Schedule Manager (and, optionally, cProjects).




April, 2005 11

Solution MonitoringThe Solution Monitoring scenario provides support for functionality such as Service-LevelReporting, EarlyWatch Alert, Business Process Monitoring, System Monitoring, Central

System Administration, System Landscape Reporting, as well as user-defined alerts.The Monitoring functionality allows you to:

• Monitor multiple solution landscapes

The SAP Solution Manager can be used to monitor the satellite systems in a landscape,as well as all the business processes running on them.

• Communicate with SAP Support Back Office

The SAP Solution Manager has a connection to the SAPNet R/3 Frontend and the SAPService Marketplace. Note that the SAP Solution Manager does not connect directly tothe SAP Service Marketplace, but uses Internet Explorer to display items from the SAPService Marketplace on the user's desktop.

• Document an entire solution landscape in one central system




12 April, 2005

4. SAP NotesBefore you begin the installation, collect and read the relevant SAP Notes. They contain late-breaking information regarding installation, as well as corrections to the installation

documentation.

Ensure that you are working with the most recent version of each SAP Note. Youcan download SAP Notes from the SAP Service Marketplace(service.sap.com/notes) or SAPNet - R/3 Frontend.

Number SAP Note Title

770200 Upgrade Solution Manager 3.1 to 3.2

782384 Configuration Guide for Solution Manager 3.2: Latest Changes

608277 Installing and Updating Content for the SAP Solution Manager

394616 Release strategy for Solution Manager (ST)

662441 Solution Manager: Notes for Support Packages

Table 2: General SAP Notes for SAP Solution Manager Installation

Documents

Solman master guide.pdf