configuration guide sap solution manager 7.0 ehp 1 and sp 19

EhP1 (SP19)Configuration Guide

Target Audience

n Technical consultantn Application consultant

PUBLICDocument version: 1.1 ‒ 03/30/2009

Document History

Caution

Before you start the configuration, make sure you have the latest version of this document. Youcan find the latest version at the following location: http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release>

The following table provides an overview of the most important document changes.

Version Date Description

SP15 2/6/2008 n Topic on authorization moved to security guide and/or IMG (transaction SPRO), for instance roles moved to additional documentation in IMG documents(roles for function: Issue Management can be found either in overview on rolesin the security guide or in more detail in the according IMG documentationfor Issue Management), see also SAP Solution Manager Security Guideon: http://service.sap.com/instguides SAP Components SAP SolutionManager <current release>

n Sections on minimum Support Package Levels for managed systems for eachscenario moved to according relevant IMG documentation (exception: ChangeRequest Management)

n Additional list of all SAP Notes included in SAP Reference - IMG for SAPSolution Manager.

n Additional list on information for additional componentsn Detailed description on how-to create an initial IMG - project, how-to create a

Delta (Upgrade) IMG - project

SAP En-hance-mentPackage1

12/15/2008 n Section on minimum Support Package Levels for managed systems for ChangeRequest Management moved to according relevant IMG documentation

n Detailed descriptions on how-to create an initial IMG - project, how-to create aDelta (Upgrade) IMG - project moved to separate How-to documents on theService Marketplace: http://service.sap.com/solutionmanager MediaLibrary Technical Papers

n New sections on:l basic configuration and scenario-specific configuration, see new sections

on Configuring SAP Solution Managerl SAP NetWeaver Business Clientl Configuration after support package updatel Configuration tasks during operationl Appendix

2/72 PUBLIC 03/30/2009

http://service.sap.com/instguides






http://service.sap.com/solutionmanager



Version Date Description

SP19 3/30/2009 n new IMG—activities, see section: Configuration After Support Packagen changed IMG— activities, see new section Using Guided Procedure (Transaction:

SOLMAN_SETUP)—Automated Update Configuration for basic settings update, andnew section Using IMG (Transaction: SPRO)—Manual Update Configuration as wellas SAP Note 1260646 for updates of scenario-specific, cross— scenario specific,and Service — Provider — specific settings

n IMG— structure change for Service— Provider— specific settings

03/30/2009 PUBLIC 3/72

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=SAP Note 1260646&_NLANG=en&_NVERS=0

Table of Contents

Chapter 1 Configuration Guide . . . . . . . . . . . . . . . . . . . . 7

Chapter 2 Getting Started . . . . . . . . . . . . . . . . . . . . . . 92.1 Target Group of This Guide . . . . . . . . . . . . . . . . . . 92.2 SAP Solution Manager Scenarios and Functions . . . . . . . . . . . 92.3 Integration of Functions . . . . . . . . . . . . . . . . . . . . 102.4 Additional Information . . . . . . . . . . . . . . . . . . . . 112.4.1 Links for Additional Components on Service Marketplace . . . . . . . 112.4.2 Relevant SAP Notes . . . . . . . . . . . . . . . . . . . . . 132.5 Using SAP Solution Manager as Service Provider . . . . . . . . . . . 192.6 Conceptual Prerequisites . . . . . . . . . . . . . . . . . . . 192.7 How to Use This Guide . . . . . . . . . . . . . . . . . . . . 20

Chapter 3 Configuring SAP Solution Manager . . . . . . . . . . . . . . 253.1 Configuration Concept . . . . . . . . . . . . . . . . . . . . 253.2 Basic Settings . . . . . . . . . . . . . . . . . . . . . . . . 273.2.1 Automatic Basic Settings Configuration . . . . . . . . . . . . . . 273.2.2 Manual Basic Settings Configuration . . . . . . . . . . . . . . . 303.3 Scenario—Specific and/or Service Provider—Specific Settings . . . . . . 303.4 Activating Solution Manager Enhancements . . . . . . . . . . . . 313.5 Configuration After Support Package Update . . . . . . . . . . . . 323.5.1 Using Guided Procedure (Transaction: SOLMAN_SETUP) — Automatic

Update Configuration . . . . . . . . . . . . . . . . . . . . . 323.5.2 Using IMG (Transaction: SPRO)—Manual Update Configuration . . . . 333.5.3 How to Update Authorizations after Support Package Upgrade . . . . . . 343.5.4 How to Create Users and Business Partners for End Users . . . . . . . . 343.5.5 How to Connect a Managed SAP System . . . . . . . . . . . . . . 363.5.6 How to Adapt Work Center Queries . . . . . . . . . . . . . . . 373.5.7 How to Create End User Roles . . . . . . . . . . . . . . . . . . 383.5.8 How to Assign Roles to Users . . . . . . . . . . . . . . . . . . 393.5.9 How to Adjust Upgrade of Managed System . . . . . . . . . . . . . 393.5.10 How to Update BI Reporting . . . . . . . . . . . . . . . . . . 403.5.11 How to Translate Your Own Customizing Entries . . . . . . . . . . 41

Chapter 4 Configuring Business System Connections . . . . . . . . . . . 43

4/72 PUBLIC 03/30/2009

4.1 Technical Prerequisites for Configuration Tracks (Activate CTC Runtime) . 434.2 Example 1: Type of Configuration Track: Double Stack and ABAP Stack . . 444.3 Example 2: Type of Configuration Track: External J2EE . . . . . . . . 474.4 How to Connect Business Systems . . . . . . . . . . . . . . . . 49

Chapter 5 Configuring SAP NetWeaver Business Client 1.0 . . . . . . . . . 53

Chapter 6 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 556.1 Basic Technical Settings for Basic Functions . . . . . . . . . . . . . 556.2 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 576.2.1 Terminology: System Landscape and Related Terms . . . . . . . . . 576.2.2 Terminology: Solution and Related Terms . . . . . . . . . . . . . 61

Chapter A Reference . . . . . . . . . . . . . . . . . . . . . . . . . 65A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . 65

03/30/2009 PUBLIC 5/72

6/72 PUBLIC 03/30/2009

1 Configuration Guide


Caution

The following note ONLY applies to SAP customers in Germany and AustriaThe extent of the usage of the software package „SAP Enhancement Package 1 for SAP SolutionManager 7.0“ depends upon the type of maintenance contract you have signed. If you have a signedcontract for:

n SAP Enterprise Support

n Product Support for Large Enterprises

n SAP Premium Support

n SAP MaxAttention

you are authorized to use all functions in the software package, without any restrictions.If you have signed exclusively standard support contracts, you are allowed to install this softwarepackage, but you are only allowed to use a restricted functionality. You are not allowed to use thefollowing Enterprise Edition functions:

n Business Process Change Analyzer

n Quality Gate Management

n Custom Development Management Cockpit

Der folgende Hinweis betrifft NUR SAP Kunden in Deutschland und ÖsterreichDie Nutzungsmöglichkeiten des Softwarepaketes „SAP Enhancement Package 1 for SAP SolutionManager 7.0“ sind von Ihrem Pflegevertrag abhängig.Wenn Sie über einen Vertrag über:

n SAP Enterprise Support

n SAP Product Support for Large Enterprises

n SAP Premium Support

n SAP MaxAttention

verfügen, sind Sie berechtigt, alle Funktionen des Softwarepaketes ohne Einschränkungenzu nutzen.Wenn Sie ausschließlich Standard Support-Verträge abgeschlossen haben, dürfen Sie diesesSoftwarepaket installieren und mit eingeschränktem Funktionsumfang nutzen. Die im folgendenaufgeführten Funktionen, die Bestandteil der Enterprise Edition sind, dürfen nicht genutzt werden:

n Business Process Change Analyzer

n Quality Gate Management

03/30/2009 PUBLIC 7/72


n Custom Development Management CockpitThis configuration guide is updated with each new Support Package and SAP Enhancement Packagein the SAP Service Marketplace at: http://service.sap.com/instguides SAP Components SAPSolution Manager <current release> . For information due to corrections in between Support Packages,see SAP Note 1294313.

IntegrationConfiguration topics are relevant for the following phases:

n Configurationn Operationn Upgrade

Recommendation

We recommend using this guide during all phases. For a detailed overview on which documentationis relevant for each phase, see also SAP Note 1088980. We strongly recommend that you use thedocuments described in this note.

ConstraintsAll support packages based on SAP Enhancement Package 1 (EhP1) of SAP Solution Manager 7.0 arebased on CRM 5.0 and SAP Enhancement Package 1 for SAP NetWeaver 7.0 , so the guides for theseproducts also apply to SAP Solution Manager.

Caution

Up to support package level SP17, SAP Solution Manager 7.0 is based on CRM 5.0 and SAP NetWeaver7.0. Use the configuration guides for these products.

8/72 PUBLIC 03/30/2009






2 Getting Started

2 Getting Started

This guide introduces the configuration of SAP Solution Manager. The actual configuration is donevia SAP Reference Implementation Guide (IMG). It has the following sections:

n Getting Started with information on the function/modularity concept, and a step by stepprocedure to use this guide, including a list of links for additional products, and all SAP notesneeded to configure SAP Solution Manager.

n Configuring SAP Solution Manager with an overview of the Solution Manager configurationconcept, short explanations of the automatic and manual configuration of basic settingsconfiguration, scenario—specific configuration, and the activation of enhancements. It alsocontains sections on configuration tasks after an update and during operation.

n Configuring Business System Connections with a detailed description of how to activate theCTC runtime environment for the two types of configuration tracks, including examples. It alsocontains a short step by step procedure to configure the business system connections.

n Configuring SAP NetWeaver Business Client 1.0 with a short description on how to configurethe SAP NetWeaver Business Client.

2.1 Target Group of This Guide

The target groups of this guide are readers who are already familiar with SAP Solution Manager andconfiguration procedures in an implementation and/or upgrade project, that is technical consultants,system administrators and/or application consultants.

n technology consultants: working with technical processes supported by SAP software duringimplementation, when deciding which settings to make

n system administrators: optimizing the system during and after implementationn application consultants: mapping a company’s actual business processes to the processes and

functions supported by SAP software during implementation, and when deciding which settingsto make

2.2 SAP Solution Manager Scenarios and Functions

SAP Solution Manager is a tool which supports the entire product life-cycle of your business processesand systems, within a system/platform. The product life-cycle can be regarded as a set of scenarios. A

03/30/2009 PUBLIC 9/72

2 Getting Started2.3 Integration of Functions

scenario is a group of business process—related functions which support the sequential and logicalrelationships of processes within the life-cycle of the product. We differentiate between scenarios(for instance: Implementation/Upgrade of SAP Solutions or Service Desk), processes relating to these scenarios(for instance: Roadmap) and functions that can be used in one or more scenarios (for example,the function Document Management can be used in the scenario Implementation and/or the scenario TestManagement). The configuration of SAP Solution Manager uses this scenario-related approach.

Note

Usage data about the functions and scenarios used by the customer is sent to SAP. See: SAP Note939897 (How to prevent this transfer).

More InformationIf you have insifcient understanding of SAP Solution Manager and its applica-tions, see the master guide for SAP Solution Manager in the Service Marketplacehttp://service.sap.com/instguides SAP Components SAP Solution Manager <current release>

and the according application help on the Help Portal http://help.sap.com/solutionmanager .

2.3 Integration of Functions

The life cycle of a product comprises various phases, such as implementation, operation, upgrade,and so on. Tools can be used to realize a process within these phases. The tools integrate stronglywith each other to support seamless document and information flow over the whole life cycle. Thework center approach demonstrates this integration. To realize this integrated approach and atthe same time allow you the freedom to build and configure according to your company’s needs,configuration and SAP template roles are function—related. Configuration and authorizations forintegrated functions are based on a modular approach.

Example

All delivered template roles for end users contain only authorizations that are relevant for thefunction they describe. Therefore, roles of different functions can be assigned to one user. Youmust know which functions you want to use.

Before you can work with a scenario/function in the Solution Manager systems, you need to make allrelevant systems, databases, and servers known, and maintain primary units such as solutions andlogical components, and your business processes. This guide refers to all these as infrastructure. Theappendix of this guide contains a detailed definition of these terms. Infrastructure comprises allentities that are the basis for scenarios.

10/72 PUBLIC 03/30/2009






http://help.sap.com/solutionmanager



2 Getting Started2.4 Additional Information

Example

Roles are structured according to functions in scenarios and infrastructure. Roles for infrastructureinclude roles for systems, roles for solutions, roles for Service Data Control Center, and so on.

PrerequisitesFor a detailed description of scenarios and functions, see the master guide for SAP Solution Managerhttp://service.sap.com/instguides SAP Components SAP Solution Manager <current release> .

2.4 Additional Information

Here, you find:

n links to documentation about SAP Solution Manager—relevant additional components.n a list of all SAP Notes that are included in the IMG.

2.4.1 Links for Additional Components on ServiceMarketplace

Your Solution Manager system is the platform for administrative tasks in implementing, operatingand upgrading systems in your system landscape. It relies heavily on mandatory and optionalcomponents implemented in addition to SAP Solution Manager. The following table gives youan overview of these additional components.

Recommendation

To ensure a smooth integration of these components, familiarize yourself with their installation,configuration, and operation.

FeaturesAdditional Components

Component Where in the Service Marketplace? IMG Activities andOther InformationSources

System Landscape Directory (SLD) http://service.sap.com/sld

or http://sdn.sap.com SAP NetWeaverCapabilities Lifecycle Management ApplicationManagement System Landscape Directory

Information andCongurationPrerequisites SLD

(technical name:SOLMAN_SLD_INFORMATI)

03/30/2009 PUBLIC 11/72




http://service.sap.com/sld

http://service.sap.com/sld

http://sdn.sap.com



Software Life-Cycle Manager (SLM) http://service.sap.com/slm andhttp://help.sap.com/nw70 Functional

View Solution Life Cycle Management SoftwareLife Cycle Management

Information andCongurationPrerequisites ChangeControl scenario(technical name:SOLMAN_MOPZ_SLM_INFO)

Adobe Document Services (ADS) http://service.sap.com/adobe Information andConfigurationPrerequisites ADSsetup (technical name:SOLMAN_ADS_INFO)

Business Intelligence (BI) http://service.sap.com/bi Information andCongurationPrerequisites BI(technical name:SOLMAN_BI_CLIENT_INF)

SAP Quality Center by HP http://service.sap.com/solutionmanager

SAP Quality Center by HPInformation andCongurationPrerequisites ThirdParty (technical name:SOLMAN_THIRDPARTY_IN)

SAP Redwood Job Scheduling service.sap.com/job-scheduling Information andCongurationPrerequisites ThirdParty (technical name:SOLMAN_THIRDPARTY_IN)

One Transport Order service.sap.com/solutionmanager MediaLibrary Technical Papers

TREX http://help.sap.com/nw2004s Information andConfigurationPrerequisites TREX(technical name:SOLMAN_TREX_INFO)

SAP TAO http://service.sap.com/saptao

Master Data Management (MDM) —MDM Administration Cockpit

http://service.sap.com/mdm andhttp://service.sap.com/installmdm

Used in SystemAdministration WorkCenter

SAP NetWeaver Administrator http://service.sap.com/nwa Used in SystemAdministration WorkCenter

12/72 PUBLIC 03/30/2009

http://service.sap.com/slm

http://service.sap.com/slm

http://help.sap.com/nw70

http://help.sap.com/nw70

http://service.sap.com/adobe

http://service.sap.com/adobe

http://service.sap.com/bi

http://service.sap.com/bi



http://help.sap.com/nw2004s

http://help.sap.com/nw2004s

http://service.sap.com/saptao

http://service.sap.com/saptao

http://service.sap.com/mdm

http://service.sap.com/mdm

http://service.sap.com/installmdm

http://service.sap.com/installmdm

http://service.sap.com/nwa

http://service.sap.com/nwa



Adaptive Controlling (ACC) n for general informationhttp://sdn.sap.com/irj/sdn/adaptive

n for application help, such as startingand stopping an application service:http://help.sap.com

n for installation informationhttp://service.sap.com/instguides

Used in SystemAdministration andSystem LandscapeManagement WorkCenters

Wily Introscope http://bis.wdf.sap.corp:1080/twiki/bin/view/Main/IntroScopeUsed in Root CauseAnalysis and SystemMonitoring WorkCenter

More InformationFor a comprehensive overview and to find out which additional components are relevantfor the configuration of your scenarios, see master guide for SAP Solution Managerhttp://service.sap.com/instguides SAP Components SAP Solution Manager <current release>

2.4.2 Relevant SAP Notes

Summary of all relevant SAP Notes mentioned in the IMG for SAP Solution Manager (transactionSPRO) per basic settings, cross-scenario settings, scenario-specific settings and Service Provider-specificsettings.

IMG SAP Note Number SAP Note Title

903274 Changes to Solution Manager IMG7.0 after SP01

199123 Word Settings

948871 Solution Manager: Cross-ScenarioSAP Notes

892412 Upgrading to SAP SolutionManager 7.0

539977 Release strategy for Add-On ST-PI

69455 Service tools for ApplicationsST-A/PI

560630 ST-PI: Solution Tools plug-in -prerequisite not met

900000 NetWeaver Business Client - FAQ

READ ME (preparingconfiguration)

03/30/2009 PUBLIC 13/72

http://sdn.sap.com/irj/sdn/adaptive

http://help.sap.com



http://bis.wdf.sap.corp:1080/twiki/bin/view/Main/IntroScope






1029940 Release restrictions for theNetWeaver Business Client

1260646 Changes to Solution Manager IMG

after EhP1

1271965 Incomplete documentation file -SAP Solution Manager EhP1

1172948 SAP Solution Manager — basicfunctions

1166931 Workload Data Collection for PI/XIin Solution Manager

Central Correction Note

797147 Wily Introscope Installation forSAP Customers

BASIC SETTINGS

Guided Procedure forAutomatic Basic Configuration

1236420 Automatic role generation fromtemplates

434918 Configuration for fully—qualifiedhost names for BSP

817529 Checking the SSO configuration

781163 Variant SAP does not work forRNOTIFUPDATE01

824554 ICM and SAP Web DispatcherTime-out Parameter

795131 FAQ: How to establish secure FTPcommunication with SAPFTP

General

130106 Using SAPFTP for data transfer

33135 Guidelines for OSS1

766505 OSS1: Changes to the RFC

connection to SAPOSS

Connection to SAP

182308 Incorrect logon data in RFC

destination SAPOSS

1088980 Documentation: SAP SolutionManager 7.0

368861 KnowledgeWarehouse and securitylevels under MS Office

Documentation

368963 Use signed macros in KnowledgeWarehouse

14/72 PUBLIC 03/30/2009



834534 SAP Solution Manager roles inRelease 7.0

128447 Trusted/Trusting Systems

Authorizations

987835 How to define Solutions in SMSY forDiagnostics

764393 Configuration of the SAP SystemLandscape Directory

768452 Troubleshooting SLDCHECK

894279 Background processing in SAPSolution Manager 7.0

1082010 Administration of several customernumbers

993775 Synchronizing system data withSAP Support Portal

System Landscape

1050693 Several IP addresses when yousynchronize system

91488 SAP Support Services - Centralpreparatory note

763561 Service Data Control Center(SDCCN) - FAQ

Service Data Control Center(SDCCN)

727998 Complete Replacement of ServiceDefinitions for SDCC/SDCCN

EarlyWatch Alert (EWA) 976054 Availability of EWA for Non ABAP

components

898614 Solution Manager Service Desk:BC Sets

903528 Solution Manager 7.0 issue trackingand service plan: BC Sets

1019583 DSWP: Customizing for issues andtop issues

BC Sets

1024932 Maintenance Optimizer: CollectiveNote

68854 DB2 UDB: SQL0101N The statementis too long, or specify databaseparameter)

410952 Creating a source system: ErrorRSAR 059

Business Intelligence (BI) —Setup

983845 Using MaxDB 7.6 for BW 3.x / BI 7.x

03/30/2009 PUBLIC 15/72



1259828 MDM 5.5 Setup in SMD: ManualSteps in Managed Systems

1169441 Introscope trace enabling for DuetEnd-to-End Trace

1085464 EnableDuet JMSQueueMonitoringwith Wily Introscope

1126554 EnableDuet JMSQueueMonitoringwith Wily

Diagnostics (Root CauseAnalysis)

1261987 EnableDuet JMSQueueMonitoringwith Wily

CROSS-SCENARIO SETTINGS

Solution ManagerEnhancements

588364 Prerequisites for activatingextensions

Client Copy 806819 sap* logon not available (problemswith client copies)

368861 KnowledgeWarehouse and securitylevels under MS Office

368963 Use signed macros in KnowledgeWarehouse

710711 Solution Manager: Using aContent Server

389366 Relocation of documents

750728 Error when relocating documents

777089 Creating a business blueprintdocument/configuration Guide

510007 Setting-up SSL on the WebApplication Server ABAP

612670 SSO for local BSP calls using SAP

GUI HTML Control

436430 Prerequisites for the DocumentModeling Workbench

350535 Knowledge Warehouse - modelingWork Center

314568 SAP GUI for HTML functionality /Limitations / SP / Behaviour

458731 Internet Graphics Server

454042 IGS: Installing and Configuring theIGS

Document Management

16/72 PUBLIC 03/30/2009



918236 WD ABAP ALV create print version

458731 Internet Graphics Server

454042 IGS: Installing and Configuring theIGS

1028690 True Type Fonts delivered with IGS

Internet Graphics Server (IGS)

596825 GFWCHART configuration file

1225976 (added Eh1) Creating custom printforms for Job Documentation

Adobe Documentation Services(ADS) Setup

944221 (added Eh1) Troubleshooting ofproblems in forms

Adaptive Computing 1008828 ACC 7.1 PI / Adaptive ComputingController tool Collective Note

1238929 MOPZ: Solution Is Not Selected inWork Center

Work Center

1246549 Status was reset to step 1 afterDownload Basket

System Availability withCCMSPING

1175058 Problems with CCMSPING with SAPSolution Manager

SCENARIO-SPECIFIC SETTINGS

949220 Solution Manager: Implementa-tion Scenario—Related SAP NotesTabs

Implementation

1244713 Installation of CustomDevelopment ManagementCockpit

1113726 Test Workbench: BC Set forWorkflow (Solution Manager /ET)

Test Management

1027579 Extend SAP Solution Manager toManage New Object Types Testing

949292 Solution Manager: Service DeskRelated SAP Notes Service Desk

830882 DSWPNOTIFCREATE URL initializationparameters

Service Desk

1050148 Troubleshooting for Service Deskconfiguration

03/30/2009 PUBLIC 17/72



949293 Solution Manager: SolutionMonitoring—Related SAP Note

199123 Word settings

420213 Composite SAP note: Centralmonitoring of mySAP.components

System Administration andSystem Monitoring

1223266 CCMSBI Reporting

1096782 CCMS: Configuration of monitoringpauses

823941 SAP Start Service on Unix

455140 Configuration of e-mail, fax, pagingand SMS using SMTP

Downtime Management

455142 SAPconnect: Configuration paging/ SMS via HTTP

1111310 Job Scheduling Management:Extended Configuration

1225906 Customizing of the Job Requestapplication

Job Scheduling Management

1230837 Creating a custom scheduledocumentation application

Change Request ManagementStandard Configuration

903527 Solution Manager ChangeManagement: BC sets

Change Control 1137683 Maintenance Optimizer and SLM

THIRD PARTY INTEGRATION

1111310 Job Scheduling Management:Extended Configuration

SAP Central Process Schedulingby Redwood

1118440 Copy default change transaction toa customer namespace

1034901 Installation of BMC AppSight for SAPClient Diagnostics

BMC AppSight for SAP ClientDiagnostics

1034902 FAQ: BMC AppSight for SAP ClientDiagnostics

SERVICE PROVIDER-SPECIFIC SETTINGS

18/72 PUBLIC 03/30/2009

2 Getting Started2.5 Using SAP Solution Manager as Service Provider


616946 Support Desk: support teamdetermination using SAPComponents Service Provider

388814 Extending the feedback functions

898616 Solution Manager corporatemessage: BC Sets

Service Provider

903530 Solution Manager: Customizingfor corporate function

1083136 SP: Report AI_SDK_SP_UPDATE_BP

970042 Service Desk: Enhancements forservice providers

Service Provider: Value AddedReseller

1281504 Authorization check for ICFServices

1125580 Customizing for Software PartnerSolution Database

Service Provider: SoftwarePartner

951145 Duplicate KB entries - Clearinconsistent data

2.5 Using SAP Solution Manager as Service Provider

As a Service Provider, you provide services to your customers using Solution Manager. See thesection Service Provider and Service Provider Customer Specification. For more information on Service Providerscenarios and definition, see the master guide for SAP Solution Manager in the Service Marketplace:http://service.sap.com/instguides SAP Components SAP Solution Manager <current release> .

2.6 Conceptual Prerequisites

Before starting configuration, you should take some strategic decisions, for example:

n How is your system landscape structured?l If you have Java systems in your landscape, you need to configure Root Cause Analysis for

Java systems.l Do you use the System Landscape Directory (SLD)?

n What are your most important business processes and in which systems do they run?n How is your solution landscape structuredl Howmany solutions do you want to create, depending on the number and role of your systems

and/or business processes?n How are additional functions integrated?

03/30/2009 PUBLIC 19/72




2 Getting Started2.7 How to Use This Guide

l Do you use BI Reporting? If so, do you already have an existing BI system or do you want touse a Solution Manager client as BI client?

l If you use Document Management, do you need to install TREX or do you operate an externalSearch Engine?

n Do you want to integrate Third Party Products?n Do you want to use work centers in Solution Manager (via Web Browser or SAP NetWeaver

Business Client?)

These and other questions determine how you configure your Solution Manager system.

Recommendation

Having a conceptual perspective helps you to configure your scenarios quickly.

PrerequisitesYou have familiarized yourself with:

1. SAP Solution Manager scenarios, architecture and concepts, see SAP Solution Manager MasterGuide, in the Service Marketplace: http://service.sap.com/instguides SAP ComponentsSAP Solution Manager <current release> .

2. sizing parameters for the scenarios you want to configure, see SAP Solution Manager SizingGuide, in the Service Marketplace: http://service.sap.com/instguides SAP ComponentsSAP Solution Manager <current release>

3. recommendations on SLD connectivity, see the for SAP Solution Manager installation guide, in theService Marketplace: http://service.sap.com/instguides SAP Components SAP SolutionManager <current release>

IntegrationWhile configuring, you are asked questions about the security of Solution Manager, see SAP SolutionManager Security Guide, in the Service Marketplace: http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release>

More Information

n about terms and glossary, see section Appendix.n about the documentation concept for SAP Solution Manager, see SAP Note 1088980.

2.7 How to Use This Guide

The following paragraph contains a step by step procedure to use this guide.

20/72 PUBLIC 03/30/2009















System configuration is performed via the SAP Reference Implementation Guide (IMG). This additionalconfiguration guide gives you an overview of the configuration concept for Solution Manager, asdisplayed in the IMG.It also addresses configuration tasks outside the initial configuration, that is, configuration tasksthat need to be performed after you have implemented a new support package or enhancementpackage, and configuration tasks during the operational use of Solution Manager.The following step by step procedure tells you how to proceed in initial (first) configuration,and update of configuration.

ProcedureInitial Configuration

Step Description Remarks

1 Define your system landscape see master guide for SolutionManager. http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release>

2 Define which additionalcomponents are needed, andhow they are setup

see master guide for SolutionManager. http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release>

3 Get to know the Solution Managerconfiguration concept

see this guide, section Configuration Concept

4 Generate SAP Load run transaction SGEN

see installation guide for SolutionManager. http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release>

5 Create configuration user inSolution Manager system andmanaged systems

see security guide for SolutionManager. http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release> sectionHow to Create/Delete Users Created / Used During Conguration in theManaged System/s: for automatic basic settings conguration,the conguration user must only be created in the managedsystem (for instance SOLMAN_ADMIN)

6 Assign authorizations to theconfiguration user in the managedsystem

see security guide for SolutionManager. http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release> sectionRoles for Basic Conguration in Managed Systems

7 Configure basic settingsusing roles for basic settingsconfiguration

use either:n automatic basic settings configuration procedure in

transaction SOLMAN_SETUP

n manual steps in transaction SPRO

see this guide, section Basic Settings and security guide for So-lution Manager. http://service.sap.com/instguides

SAP Components SAP Solution Manager <current release>(section Roles for Basic Conguration in Solution Manager)

03/30/2009 PUBLIC 21/72















8 Define which scenarios andfunctions you use

see master guide for SolutionManager. http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release>

9 Get to know the concept ofintegration of functions

see this guide, section Integration of Functions

10Recommendation

Create an IMG project

see this guide, section Scenario—Specific and/or ServiceProvider—Specific Settings

11 Configure scenario—specificfunctions for your scenarios

see this guide section Scenario—Specific and/or ServiceProvider—Specific Settings and security guide for SolutionManager. http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release> sectionHow to Create Roles for Scenario—Specific Configuration in SolutionManager

NoteWithout an IMG project, use transaction SPRO.

Update Configuration



see in this guide, section Solution Manager Configuration Update

2 Activate Release Notes in SAPReference IMG


3 Update authorizations intransaction SU25


4 Update basic settings use either:n automatic basic settings configuration procedure in

transaction SOLMAN_SETUP

n manual steps in transaction SPRO that are flagged ReleaseNotes.

5 Check active Release Notes forScenario—Specific Settings,Cross—Scenario Settings


22/72 PUBLIC 03/30/2009







6Recommendation

Create an Upgrade IMG project

see document How to Create Customiz-ing Projects in the Service Marketplace:


Media Library Technical Papers

7 Configure scenario—specificfunctions for your scenarios

see this guide, section Scenario—Specific and/or ServiceProvider—Specific Settings and security guide for SolutionManager. http://service.sap.com/instguides SAPComponents SAP Solution Manager <current release> sectionHow to Create Roles for Scenario—Specific Configuration in SolutionManager

NoteWithout an IMG project, use transaction SPRO.

ExampleInitial configuration of SystemMonitoring (including KPI Reporting and IT Performance Reporting)using the work center approach, in SAP NetWeaver Business Client.

Caution

This example is a suggestion of how to configure this scenario, from the configuration—relevantperspective. The same example is used in the security guide, from security—relevant perspective.


1 Define your system landscape two productive managed systems, SLD, BI client is SolutionManager client

2 Define which additionalcomponents are needed, andhow they are setup

System Landscape Directory, see in this guide, sectionAdditional Components in the Service Marketplace

3 Get to know the Solution Managerconfiguration concept

see this guide, section Configuration Concept


5 Create configuration user inSolution Manager system andmanaged systems

create configuration user (for instance: SOLMAN_ADMIN) inmanaged systems

6 Assign authorizations to theconfiguration user in the managedsystem

assign roles to configuration user:n for authorization object S_RFCACLn SAP_SDCCN_ALL

7 Configure basic settingsusing roles for basic settingsconfiguration

use of automatic basic settings configuration viaSOLMAN_SETUP ( role for configuration user SOLMAN_ADMIN isgenerated automatically). Includes the setup of SolutionManager and both managed systems

03/30/2009 PUBLIC 23/72







8 Define which scenarios andfunctions you use

System Monitoring and Reporting; Service Desk, formessage creation

9 Get to know the concept ofintegration of functions

n System Monitoring (sessions)n KPI Reporting and IT Performance Reporting (BI)n work center for System Monitoringn Service Desk message creationn SAP NetWeaver Business Client

10Recommendation

Create an IMG project

create an IMG project for IMG node System Monitoring and ServiceDesk, in transaction SPRO_ADMIN

11 Configure scenario—specificfunctions for scenarios

see created IMG project

12 Configure cross—scenariosettings for your scenario

for instance:n Work Centern IGS setupn Adaptive Computingn Central CCMS setupn System availability with CCMSPING

n Automatic e-mailn Business Partners

Configure SAP NetWeaver BusinessClient 1.0 for your end users

see in this guide, section SAP NetWeaver Business Client

24/72 PUBLIC 03/30/2009

3 Configuring SAP Solution Manager

3 Configuring SAP Solution Manager

The system is configured in transaction SPRO (SAP Reference IMG) in the SAP Solution Managersystem. Basic SAP Solution Manager settings are first initially configured, then scenarios areconfigured. Some scenarios allow third—party integration. Activation tasks for some of thesethird—party products must be performed. This activation displays all dependent IMG activities. Youmay need to change business processes during operation. This can require changes in configuration,or even new configuration tasks, such as adding and switching systems or creating new users. Thefollowing sections give an overview of these topics.

3.1 Configuration Concept

The SAP Reference Implementation Guide (IMG) gives you access to all activities that you needto configure your SAP Solution Manager system. Since SAP Solution Manager is based on SAPNetWeaver 7.0 EhP1 and CRM 5.0, this includes activities for Customer Relationship Management(CRM) and SAP NetWeaver.

PrerequisitesYou are familiar with SAP Solution Manager architecture and main concepts. You have clarified thefollowing points about the overall infrastructure:

n which systems you want to connect to Solution Managern which logical components you want to create and which systems you want to includen which solutions you want to create and which logical components you want to include per

solution

Caution

Check whether you have SAP Note 1244225 in your Solution Manager system. Note: until SP17use SAP Note 662441 instead.

FeaturesThe IMG is hierarchically structured, i.e. it is a top—down step—by—step guided procedure. It isstructured by six main topics, the first two of which contain vital information about prerequisites,depending on your infrastructure, such as systems, system types, and so on. Configuration is thensplit into basic configuration and scenario—specific configuration. The former is mandatory, as itsets all prerequisites for scenario configuration. The scenario—specific configuration depends on

03/30/2009 PUBLIC 25/72



3 Configuring SAP Solution Manager3.1 Configuration Concept

which Solution Manager functions you want to use. Cross—scenario settings are settings which arerelevant for more than one scenario. They are linked to in the scenario—specific functions. Settingsfor Service Provider are only required by service providers. The IMG structure is as follows:

Figure 1: SAP Solution Manager IMG (Example: EhP1)

1. ReadMe: This is an organizational activity. It gives you all the information you need to startconfiguration with the current enhancement package, for instance:n how to use the IMG

n how to prepare your Solution Manager system and managed systems2. Central Note: This is an organizational activity. See the SAP note mentioned, before starting to

configure.3. Basic Settings: see section Basic Settings.4. Cross-Scenario Settings: These activities include all configuration steps for functions which are

relevant for more than one scenario.5. Scenario-Specific Settings: see section Scenario-Specific and/or Service Provider-Specific Settings.6. Service Provider-Specific Settings: see section Scenario-Specific and/or Service Provider-Specific Settings.

You can access the SAP Reference IMG as follows:

n SAP GUI: Transaction SPRO

n SAP NetWeaver Business Client (NWBC): In the Business Client, choose Create ImplementationGuide and SAP-Reference IMG.

Recommendation

Configure your scenario-specific system settings using a project IMG. Using a project IMG, you canchoose from the application components. This results in individual customizing projects forimplementing the SAP system in your company. When you upgrade the system you can then easilydefine new IMG activities.

26/72 PUBLIC 03/30/2009

3 Configuring SAP Solution Manager3.2 Basic Settings

ConstraintsIn the IMG activities, you find further information links to additional information you might need,for instance on security topics or third-party-specific references.

3.2 Basic Settings

The basic settings in Solution Manager configuration are all technical settings you have to maintain,and all settings that are relevant for major functions that run in your Solution Manager system (seesection Appendix). These functions are:

n Maintenance Optimizer, to download Support Packages for all SAP systems in your system landscapen Early Watch Alert, to create Early Watch Alert reports and send them to SAPn Root Cause Analysis, to perform root cause analysisn Basic Service Desk, to send messages to SAPn Expert on Demand, to get an SAP expertn Basic Business Blueprint and Configuration, to generate business blueprint documents and configuration

guides for your solutions

You can make the basic settings automatically or manually. All steps performed duringautomatic configuration are also relevant for manual configuration. The following sectionsgive an overview of both types of basic settings configuration. For SAP Solution Managerconcepts and architecture, see master guide for SAP Solution Manager in the Service Marketplace:http://service.sap.com/instguides SAP Components SAP Solution Manager <current release>.

3.2.1 Automatic Basic Settings Configuration

You can initially configure your basic settings with the basic settings wizards.

Note

Automatic basic settings configuration can also be used when upgrading the Solution Managersystem, see also section Using Guided Procedure (Transaction: SOLMAN_SETUP) — Automatic UpdateConfiguration.

This quickly configures all main settings in a guided procedure. The automatic configuration isaccessed via a Web Dynpro application which is called by transaction SOLMAN_SETUP. All settingsfor this Web Dynpro application are made during the installation of SAP Solution Manager. Allactivities in this wizard are linked to the corresponding IMG activities in the standard basic settingsconfiguration, in the SAP Reference IMG (transaction SPRO). The configuration consists of three mainparts with individual steps:

1. Initial Setup

03/30/2009 PUBLIC 27/72





You prepare the SAP Solution Manager system for further configuration by creating accordingconfiguration users, configuring all necessary settings for your system landscape, as for instanceconnecting ABAP and Java.

Note

On users, see security guide for SAP Solution Manager on the Service Marketplace:http://service.sap.com/instguides SAP Components SAP Solution Manager <current

release> .

2. Basic ConfigurationYou configure all basic settings to ensure that all basic functionality runs immediately, see as wellsection Basic Technical Settings for Basic Functions. In addition, you create a project and a related solution.

3. Managed System ConfigurationYou create all necessary connections to/from managed systems.

In addition, the application provides anOverview on which activities are already performed, whichstill need to be performed, and which need to be updated, see section Using Guided Procedure (Transaction:SOLMAN_SETUP) — Automatic Update Configuration.

Caution

The automatic configuration of Solution Manager basic settings makes additional system settingsthat differ from manual configuration via IMG, for instance all created users are automaticallyassigned a user group with the following naming convention <SAP_SM_>, additional business partnersfor SAP Service and Support, and so on. For more information, see security guide for SAP SolutionManager in the Service Marketplace: http://service.sap.com/instguides SAP ComponentsSAP Solution Manager <current release> .

PrerequisitesProfile ParametersCreate the following profile parameters in the instance profile:

n login/create_sso2_ticket = 2n login/accept_sso2_ticket = 1n icm/host_name_full = fully qualified server name

This parameter must be attributed to the fully qualified server name (for example,wdfd002568.wdf.sap). The name must contain at least two periods, see also SAP Note 434918.

n icm/server_port_1 = PROT=SMTP,PORT= <> 0; for example: 25000n login/no_automatic_user_sapstar = 0n icm/conn_timeout; for example: 20000n icm/keep_alive_timeout; for example: 240n SAPLOCALHOSTFULL = fully qualified server name

28/72 PUBLIC 03/30/2009









For the parameters to be used by the system, the system must be restarted.Authorization Update

Note

See SAP Note 1236420

Transport Management System (TMS)Transport Management System must be configured.

ProcedureCall transaction SOLMAN_SETUP and follow the guided procedure. Use the on-screen help and onlinehelp in the Service Marketplace at: http://help.sap.com SAP Solution Manager <current release> .

Note

The step-by-step procedure provides a separate protocol for each individual step.

ResultYou have performed all activities for the initial basic settings configuration. The system has set a statusfor all performed activities. Now you can start to configure scenarios and/or Service Provider settings.See section How to Configure Scenario-Specific and/or Service Provider-Specific Settings.

Caution

Do not you start configuring scenarios before you have completely configured all the basic settings

More Information

n on how to use transaction SOLMAN_SETUP, see tutorial on Solution Manager Configuration at: :http://service.sap.com/~sapidb/011000358700001735062008E .

n installation procedure for SAP Solution Manager, see installation guides for SAP Solution Managerin the Service Marketplace: http://service.sap.com/instguides SAP Components SAPSolution Manager <current release>.

n security issues, see chapter Roles for Configuration in SAP Solution Manager Security Guide in the ServiceMarketplace: http://service.sap.com/instguides SAP Components SAP Solution Manager<current release>.

03/30/2009 PUBLIC 29/72


http://help.sap.com

http://service.sap.com/~sapidb/011000358700001735062008E









3 Configuring SAP Solution Manager3.3 Scenario—Specific and/or Service Provider—Specific Settings

3.2.2 Manual Basic Settings Configuration

You can configure basic settings in the transaction SPRO for initial configuration. You can also createnew settings and change existing settings. See also the sections Configuration Concept and ConfigurationTasks During Operation.

Recommendation

You should use the basic settings wizard to configure the initial basic settings. However, if youonly want to configure one of the functions above, you need to configure the basic settings in thetransaction SPRO. The IMG activity node Information and Configuration Prerequisites, tells you whether thissection is relevant for your needs. See also the section Basic Technical Settings for Basic Functions in theAppendix.

ChecklistCall transaction SPRO.

ResultYou have performed all activities for the basic settings. You can now start to configure scenariosand/or Service Provider settings, see section Scenario-Specific and/or Service Provider-Specific Settings.

Caution

Do not start to configure scenarios before you have completely configured all the basic settings

More Informationabout installation procedure for SAP Solution Manager, see installation guides for SAP SolutionManager in the Service Marketplace: http://service.sap.com/instguides SAP ComponentsSAP Solution Manager <current release>.

3.3 Scenario—Specific and/or Service Provider—SpecificSettings

You can configure your scenarios using IMG (transaction SPRO), which contains all configurationactivities for each function. Functions which are in more than one scenario are linked via IMGdocumentation. They are in the IMG node Cross-Scenario Settings.

30/72 PUBLIC 03/30/2009




3 Configuring SAP Solution Manager3.4 Activating Solution Manager Enhancements

Note

If you want to configure only a subset of all available functions, you can decrease the size of IMGactivities, using:

n IMG customizing projects

n the Business Process Repository (BPR)

PrerequisitesYou have configured the basic settings for Solution Manager, see section Basic Settings.

ProcedureChoose your scenario and perform all required IMG activities, step by step.

Recommendation

Create a customizing project or use an existing customizing project.

More Information

n how to create customizing projects in IMG, see How to Create Customizing Projects in the ServiceMarketplace: http://service.sap.com/solutionmanager Media Library Technical Papers .

n how to use the Business Process Repository in SAP Solution Manager, see How to Use the BusinessProcess Repository, in the Service Marketplace: http://service.sap.com/solutionmanager

Media Library Technical Papers .

3.4 Activating Solution Manager Enhancements

SAP Solution Manager enhancements must be activated separately, via IMG ( IMG transaction SPROSAP Solution Manager Cross-Scenario Settings Activate Solution Manager Enhancements (technical name:SOLMAN_ACTIVATE_KEY). Technically, the components are packages that are based on the standard SAPSolution Manager, without interdependencies.

PrerequisitesYou have downloaded the add-ons for the enhancements.

FeaturesActivation makes only technical settings for the component functionality of the following SAPSolution Manager enhancements:Third—Party Product Integration

n SAP Solution Manager Adaptor for SAP Quality Center by HPn SAP Central Process Scheduling Adaptor by Redwood

03/30/2009 PUBLIC 31/72







3 Configuring SAP Solution Manager3.5 Configuration After Support Package Update

n SAP Productivity Pak by RWD

IntegrationActivated enhancements are compatible with all SAP Solution Manager functions.

ExampleThe IMG for enhancements for configuring third—party product integration, for instance SAPQuality Center by HP or SAP Central Process Scheduling by Redwood, is visible after the enhancementis activated.

3.5 Configuration After Support Package Update

After you have implemented a new support package or support package stack (SAP EnhancementPackage), you need to check your configuration settings for new and updated configuration tasks.This is especially important for the basic settings. For instance, with every newly—shipped WebDynpro application, its ICF service needs to be activated. You can update your basic settingsconfiguration by either:

n re - running the Guided Procedure for Automatic Basic Configuration (recommended)n checking for new or changed IMG activities in the SAP Reference IMG.

3.5.1 Using Guided Procedure (Transaction: SOLMAN_SETUP)— Automatic Update Configuration

You can use the guided procedure for the basic settings configuration for updating your basic settings.To do this, check all activities in the Overview area in transaction SOLMAN_SETUP, and use yourinitially created project to track update changes (see section Automatic Basic Settings Configuration). In thefollowing, we give an overview of both procedures.

PrerequisitesYou have:

n initially configured all basic settings using the guided procedure for the automatic basic settingsconfiguration

n updated your authorizations, see SAP Note 1236420

FeaturesUsing the Overview for Update Activities

1. Call transaction SOLMAN_SETUP.

32/72 PUBLIC 03/30/2009



2. In the Overview, the system displays a configuration table with all activities you need to performafter updating your system. If you select an entry in this table, in Open Activities column you canview the steps you need to execute.In the area of Basic Configuration, this may be activity Activate BC Sets. The system updates this listautomatically.

3. In the case of an update, you can specify here whether you have to re-execute activities thathave already been executed.

Using the Implementation Project to Track Update ActivitiesYou can use the existing implementation project to track all information about the setup progress ofyour basic settings. Call transaction SOLAR02 and choose your project.

Note

For more information on how to use transaction SOLAR02 and/or Work Center Implementationand Upgrade in SAP Solution Manager, see Online Help on the Service Marketplace at:http://help.sap.com SAP Solution Manager <current release> .

More Information

n on how to use transaction SOLMAN_SETUP, see tutorial on Solution Manager Configuration at: :http://service.sap.com/~sapidb/011000358700001735062008E .

3.5.2 Using IMG (Transaction: SPRO) — Manual UpdateConfiguration

You can update basic settings configuration and scenario-specific configuration using the IMG.

Recommendation

We recommend to update your basic settings using the automated guided procedure, see sectionUsing Guided Procedure (Transaction SOLMAN_SETUP)— Automated Update Configuration.

Features

1. Activate Release NotesDisplay release notes by choosing Release Notes. The system flags the release information with a blueinformation icon in front of the IMG activity.

Caution

SAP Note 903274 for details of new IMG activities, changed IMG activities, and deleted IMG activitiesup to SP17. As of later support packages, see the release notes and SAP Note 1260646.

03/30/2009 PUBLIC 33/72

http://help.sap.com







3.5.3 How to Update Authorizations after Support PackageUpgrade

After the new installation and an update of your SAP Solution Manager system, you need to updateyour tables with new default field values for authorization objects, in transaction SU25. This isespecially relevant for all new authorization objects delivered with an update.

Caution

When you update your system, you must import new roles and profiles from client 000 into yourproductive client.

Procedure

1. Call transaction SU25.2. Choose Information.

The dialog explains in detail what you need to do.

Recommendation

Perform at least the first step.

3.5.4 How to Create Users and Business Partners for EndUsers

The following lists give an overview of functions that require users in Solution Manager system andmanaged systems, and functions that require business partner users in the Solution Manager system:Functions Requiring End Users for SAP Solution Manager and Managed Systems

n Implementation: if you use Implementation and subsequently Customizing Distribution to centrallyconfigure your managed systems. Implementation and Customizing Distribution use TrustedRFC connections, which always require users in both systems.

n Test Management: if testers have to test in managed systems. Test Management uses Trusted RFC

connections, which always require users in both systems.n Service Desk: for Key User (end user), see example belown System Administration and System Monitoring (and Business Process Operations): if the system administrator

needs to check transactions inmanaged systems via SAP SolutionManager trusted RFC connection.n Change Request Management: if the users in the Change Request Management process log on to the

managed systems via Solution Manager.n Root Cause Analyses: user SAPSUPPORT is automatically created in the Solution Manager system as

well as the managed systems during Root Cause Analysis configuration.

Functions Requiring Business Partners Based on Users in SAP Solution Manager

34/72 PUBLIC 03/30/2009


n Delivery of SAP Services: if you use Issue Management.n Service Desk: for Key User (end users) and processors of service desk messages, see example

underneath.n Change Request Management

n Job Scheduling Management

n Change Control: functionality Maintenance Optimizer

ProcedureCreate Users Using Transaction SU01This paragraph tells you which area in User Management (transaction SU01) needs attention, and why.

1. Enter your user and choose change.2. Enter the required data and save.

Address Data

n First Name and Last Namel Function: Digital Signature

n E-Mail

l Function: Business Process Operationsl Function: Issue Managementl Function: Service Desk

l Function: E-Learning ManagementThe user can receive and send e-mails. This e-mail address can be any address, as long as it isknown to the mail server.

Note

Business Process Operations: for use of auto—reaction methods.

Create Business Partner Using Transaction BP_GEN

1. Choose User list -> Add system.2. Select a system from which you want to create business partners.3. Select users.4. Choose Edit -> Create Business Partner.5. Confirm your entries.

ExampleYou want to create end users for Service Desk functionality. The system landscape consists of SAPSolution Manager and two managed systems, three systems in total.You have to create all end users known to Solution Manager as Business Partners, in the SolutionManager system and the managed systems.

1. Create users for all end users in all three systems, as described above.

03/30/2009 PUBLIC 35/72


2. Create business partners for end users, in the Solution Manager system, as described above.

Note

If you change e-mail addresses for users, you need to update your business partners in transactionBP_GEN.

More Informationon how to create business partners, see IMG activity Create Key User (technical name:SOLMAN_SUP_BUSPART)

3.5.5 How to Connect a Managed SAP System

You can connect managed systems to Solution Manager either manually, in transaction SPRO BasicSettings System Landscape , or in automatic basic settings configuration in transaction SOLMAN_SETUP.Details of the guided procedure in the automatic configuration for managed systems are given below.

PrerequisitesIf you have a production SLD attached, maintain your system in this SLD, or maintain your system,server and database directly in the Solution Manager system in transaction SMSY.

ProcedureCall transaction SOLMAN_SETUPChoose viewManaged Systems Configuration, and choose the technical system you want to connect. Startconfiguration by choosing Configure.

1. Connect managed systema) To be able to enter data, choose Change.b) Enter the users with which you want to make the connection.

Note

The users must have the same name and password in both systems, and at least authorizationobject S_RFCACL assigned, see section RFC Connection: Trusted.

c) To decide which RFC connections the system should create, select the RFCs. See section RFCConnections READ, TMW, BACK.

d) To start the creation of RFCs, choose Create RFC.The system automatically:n creates the selected RFC connections

n creates technical users, see sections on technical users

36/72 PUBLIC 03/30/2009


n activates Service Data Control Center in the managed system, adds the BACK destination, anddefines the Solution Manager system as master system

2. Check PrerequisitesCheck all prerequisites and continue in the guided procedure to the next step.

3. Manual ConfigurationFor all activities, read the IMG documentation, execute the steps manually, and set the status.Continue to the next step in the guided procedure.

4. Diagnostics ConfigurationIf your managed system contains a Java stack, for all activities: read the IMG documentation,execute the step manually, and set the status. Continue to the next step in the guided procedure.

5. Wily Introscope ConfigurationIf your managed system contains a Java stack, for all activities, read the IMG documentation,execute the step manually, and set the status. Continue to the next step in the guided procedure.

6. Create Logical ComponentCreate a new logical component for your connected managed system.

ResultYou have attached a newmanaged system. Check whether SAP EarlyWatch Alert Reports are createdand executed by the Solution Manager system.

Caution

Passwords for technical users are set by the system, automatically. If you encounter problems withRFC connections, check passwords and attached profiles. For profiles, see sections on technicalusers for infrastructure.

3.5.6 How to Adapt Work Center Queries

System administrators and end users can adjust work centers to their needs.

ProcedureEnd UserSee document How to Adapt a Work Center View, in the Service Marketplace:http://service.sap.com/solutionmanager Media Library Technical Papers .

Administrator

n configuring query settings for all end users or customize the logon screen for Web Dynproapplications, see document How to Adapt a Work Center View, in the Service Marketplace:http://service.sap.com/solutionmanager Media Library Technical Papers

n deleting queries from database: execute program POWL_D01

n refreshing active POWL queries: execute program POWL_WLOAD

03/30/2009 PUBLIC 37/72








More Informationsee IMG activity Adjust Queries (technical name: SOLMAN_WC_QUERY)

3.5.7 How to Create End User Roles

You need to grant authorizations for which SAP does not ship template roles, in the SolutionManagerand managed systems. To be able to assign the correct authorization you can create a dedicatedrole for them. This section describes how to create your own roles, using the example of criticalauthorizations of transactions SU01 (User Management) and PFCG (Role Management).

Features

1. Create a Role in Transaction PFCGa) Choose transaction PFCG.b) Enter a role name in your namespace, for instance: ZSU01_PFCG, and choose Single Role.c) Enter a description for your role, for instance: Full authorization for SU01 and PFCG.d) Go to tab menu and enter transactions SU01 and PFCG.

Note

The authorization objects required in role creation are maintained using transactions. Whenyou enter a transaction in the menu tab in your role, the system traces all authorizationobjects required for this transaction.

e) Save your role.

Note

You are asked for a transport request.

2. Maintain Authorization ObjectsDefault authorization objects delivered by SAP contain only minimal authorizations. To grantfull authorization to authorization objects, you must edit thema) Choose the Authorizations tab in the Role Maintenance.b) Choose Change.c) Maintain all activity values per authorization object, according to your needs, for instance if

you want to grant full authorization, always choose all activities.

Caution

All authorization objects need to have a green traffic light. If you are not sure about thefunction of the authorization object, double-click the green line. The system opens thedocumentation for this object in a separate window.

38/72 PUBLIC 03/30/2009


d) Generate the profile.e) To assign this profile to a user, choose tab User, add your user in the table and perform the

user comparison.f) Save.

3.5.8 How to Assign Roles to Users

After you have generated profiles from roles, assign the role to your users in one of the two waysexplained below.

Procedure

n Transaction SU011. Choose transaction SU01.2. Enter the user and choose edit.3. Go to Roles tab.4. Enter your role.5. Save.

n Transaction PFCG1. Choose transaction PFCG.2. Enter your role and choose edit.3. Go to Users tab.4. Enter the user name.5. Choose the button User Comparison.6. Save.

Note

For more information on User Comparison, see SAP Note 1272331.

3.5.9 How to Adjust Upgrade of Managed System

You have upgraded a managed system. This section explains how to adjust your settings for thissystem in the SAP Solution Manager.

PrerequisitesYou have:

n SAP Solution Manager projects and solutions in productive usen SLD attached to SAP Solution Manager

03/30/2009 PUBLIC 39/72



Procedure

1. Adjust Product Versiona) To adjust the new product version for your upgraded managed system, go to transaction SMSY

and choose your system.b) Go to Header Data tab, and choose Installed Product Version.

In the dialog box, choose the product version you have upgraded to.c) Save.

2. Adjust Logical Componenta) Create a new logical component for your upgraded managed system.b) In SAP Solution Manager, go to transaction SOLUTION_MANAGER and deactivate any solutions

that contain the managed system.

Note

If you monitor business processes in this system, deactivate the business process monitoringsessions for it.

c) Go to transaction SOLUTION_DIRECTORY and your solutions, and exchange your outdatedlogical component for your new logical component.

d) Activate your business process monitoring session and solutions again.

Note

In an implementation project, you may want to leave the outdated logical component inyour project, for documentation purposes.

More Informationabout how to use individual applications, see application help for SAP Solution Manager in the HelpPortal: http://help.sap.com .

3.5.10 How to Update BI Reporting

If you update your SAP Solution Manager system, the system adds new info cubes. You need toactivate the BI—related function again. This is relevant for KPI reporting, IT performance reportingand test management reporting.

Procedure

1. Go to the work center. See:n Work Center System Monitoring

n Work Center Test Management2. Run the setup/settings for BI reporting again.

40/72 PUBLIC 03/30/2009

http://help.sap.com


3.5.11 How to Translate Your Own Customizing Entries

For some configuration tasks, you create your own modified entries and you need to translate them.Use the following procedure to translate your own customizing entries in customizing tables.

PrerequisitesYou have installed all required languages.

Procedure

1. Log on to your SAP Solution Manager system in your original language.2. Choose the transaction and enter the customizing table:n SM30 for table/viewn SM34 for view cluster

3. ChooseMaintain.4. Choose the line of the object you want to translate.5. In the menu, choose: Goto Translate .6. In the dialog box, choose the language into which you want to translate the object.7. Translate the object.8. Save your settings.

ExampleIn function Job Scheduling Management, you maintain the following tables AGS_REGION_CUST andAGS_ORGUNIT_CUST.

More Informationabout how to translate object types in the system, see the Help Portal: http://help.sap.com ,search for SE63.

03/30/2009 PUBLIC 41/72

http://help.sap.com

This page is intentionally left blank.

4 Configuring Business System Connections

4 Configuring Business SystemConnections

You can connect business systems in your system landscape using SAP Solution Manager asmanagement platform. Before starting to configure, you define configuration tasks and configurationtracks. Configuration tracks are lines between technical systems. There are two types of configurationtracks, depending on whether an application runs on an external Java stack or not. The followingsections give an overview of the technical prerequisites for executing configuration tracks. In addition,two examples are given of how to proceed for the different types of configuration tasks.To access the application, choose Automatic Technical Configuration in the System Landscape Managementwork center. The application help for this topic contains a detailed description of how to use thisapplication, for example which configuration tracks to use, configure, and display the status of yourconfiguration tasks, and so on. You can access the application help in the Service Marketplace:http://help.sap.com Solution Manager .

4.1 Technical Prerequisites for Configuration Tracks(Activate CTC Runtime)

To be able to perform automatic configuration tasks, such as connecting business systems using CTCtemplates (configuration tasks), the CTC runtime environment is a prerequisite for the followingfunctions:

n Automatic Basic Settings Configuration of the Solution Manager systemThe system automatically activates the CTC runtime on the J2EE stack of Solution Manager,immediately before you execute the CTC template (configuration task) for the initial setup ofSolution Manager. See section Basic Settings.

n Connectivity of Business Systems (Automatic Technical Configuration)You activate the CTC runtime before you execute the required CTC template (configuration task).

Note

You must activate the CTC runtime only once per type of configuration track.

During activation, the system automatically creates and/or checks two RFC connections:

n from Solution Manager to the J2EE engine on which you want to activate the CTC runtimen from the J2EE engine on which you want to activate the CTC runtime, to Solution Manager.

03/30/2009 PUBLIC 43/72

http://help.sap.com

4 Configuring Business System Connections4.2 Example 1: Type of Configuration Track: Double Stack and ABAP Stack

The system assigns a technical user to each RFC connection, see sections on technicalusers in the security guide for SAP Solution Manager in the Service Marketplace:http://service.sap.com/instguides SAP Components SAP Solution Manager <current release> .

Recommendation

The system displays default values on the activation process screens. You can overwrite these values,but you should use them

PrerequisitesCheck that you have created:

n an administration user (dialog user) in Solution Manager, with administration authorization(profile SAP_ALL). As default, you can use user DDIC which is assigned profile SAP_ALL.

n an administration user (for instance user J2EE_ADMIN) for the J2EE engine on which you want toactivate the CTC runtime.

You have accessed the applicationAutomatic Technical Configuration, in the System LandscapeManagementwork center.

More Information

n about installation, see installation guides for SAP Solution Manager in the Service Marketplace:http://service.sap.com/instguides SAP Components SAP Solution Manager <current release> .

n about automatic technical configuration, see Application Help in the Help Portal:http://help.sap.com .

n about technical users and authorizations, see security guide for Solution Manager in the ServiceMarketplace http://service.sap.com/instguides SAP Components SAP Solution Manager<current release> .

4.2 Example 1: Type of Configuration Track: Double Stackand ABAP Stack

This example shows how to configure the connection between two technical systems when neither ofthem is solely based on an external stand-alone Java stack, such as:

n SAP CRM (single ABAP stack) and SAP ERP (single ABAP stack), orn SAP NetWeaver Process Integration (PI) (double stack) and AS ABAP (single ABAP stack)

In both cases, the CTC runtime on the SAP Solution Manager J2EE stack must be the default runtime.

Note

The following procedure is also described in SAP Note 1254502.

44/72 PUBLIC 03/30/2009







http://help.sap.com






ProcedureScreen: Connect CTC runtime environment

1. Navigate to Automated Technical Configuration applicationChoose System Landscape work center, and the link Automated Technical Configuration.

2. Call CTC runtime activation screenTo call the CTC runtime activation screen, add suffix UI_MODE=D to the URL.

3. Connect CTC runtime environmentSelect the Java system component for your Solution Manager system (in this example, the systemID is JBS) and choose Connect CTC runtime environment.

4. If necessary, log on to the Java stack with your J2EE administration user (user J2EE_ADMIN).Result: the system starts the procedure to connect the required CTC runtime.

Figure 2: Screen: Connect CTC runtime environment

Screen: Enter Destination Details

1. Enter details for SAP Solution Manager

n Host

n System Numbern Client

n Administrator User, for instance DDIC (dialog user with administrator authorization profileSAP_ALL)

03/30/2009 PUBLIC 45/72


n Administrator Password2. Enter details for SAP J2EE Runtime

n Host

n HTTP Port

n Administrator User

n for instance J2EE_ADMINn Administrator Password

3. Choose Next.

Figure 3: Destination Details

Screen: Technical User

1. EnterMaster PasswordEnter one master password for all required users. You can set separate passwords for each technicaluser.

Caution

The password must be alphanumerical.

2. Choose Next.

46/72 PUBLIC 03/30/2009

4 Configuring Business System Connections4.3 Example 2: Type of Configuration Track: External J2EE

Figure 4: Technical Users

ResultYou have activated CTC runtime on the J2EE stack of the SAP Solution Manager. You can nowperform your configuration task.

4.3 Example 2: Type of Configuration Track: External J2EE

This example shows how to configure the connection between two technical systems when one ofthem uses an external J2EE, such as:

n ADS (external J2EE) and AS ABAP (ABAP stack), orn BI Java (external J2EE) and AS ABAP (ABAP stack)

In this example, the CTC runtime on the external J2EE stack must be activated.

PrerequisitesYou start the CTC runtime activation via the configuration track line.

ProcedureScreen: Enter Destination Details

1. Enter details for SAP Solution Manager

n Host

n System Numbern Client

n Administrator User, for instance DDIC (dialog user with administrator authorization profileSAP_ALL)

03/30/2009 PUBLIC 47/72

4 Configuring Business System Connections4.3 Example 2: Type of Configuration Track: External J2EE

n Administrator Password2. Enter details for SAP J2EE stack

n Host

n HTTP Port

n Administrator User

n for instance J2EE_ADMINn Administrator Password

3. Mark ABAP UME configured.

Figure 5: Enter Destination Details

ABAP UME

1. Enter the data for the ABAP stack against which the UME is configured.n Host (UME ABAP Host)n System Number (UME ABAP Sysnr)n Client (UME ABAP Client)n User (ABAP User)n Password

n Password Confirmation2. Choose Next.

Screen Technical User

1. EnterMaster PasswordEnter one master password for all required users. You can set separate passwords for each technicaluser.

48/72 PUBLIC 03/30/2009

4 Configuring Business System Connections4.4 How to Connect Business Systems

Caution

The password must be alphanumerical.

2. Choose Next.

Figure 6: Technical User

ResultYou have activated CTC runtime on the J2EE stack. You can now perform your configuration task.

4.4 How to Connect Business Systems

You can configure the connections between your business systems in SAP Solution Manager.For more information, see online help for SAP Solution Manager in the Service Marketplace:http://help.sap.com SAP Solution Manager <current release> J

PrerequisitesYou have configured the basic settings in Solution Manager and activated the CTC—runtime (seeexamples). To be able to configure the business connectivity, the application user needs authorizationsSAP_SMSY_ALL and SAP_BC_CTC. For more information on users and authorizations, see security guidefor SAP Solution Manager in the Service Marketplace: http://service.sap.com/instguides

SAP Components SAP Solution Manager <current release> .

ProcedureScreen: RFC Destination Details

03/30/2009 PUBLIC 49/72

http://help.sap.com





Enter the data for the administration users in each business system. The configuration should beperformed with an administration user, assigned profile SAP_ALL. Alternatively, you can use userDDIC, which is set as default value.

Figure 7: RFC Destination Details

Screen: Technical User

1. EnterMaster PasswordEnter one master password for all required users. You can set separate passwords for each technicaluser. You can assign ABAP roles or profiles to each technical user.

Caution

The password must be alphanumeric.

2. Choose Next.

50/72 PUBLIC 03/30/2009


Figure 8: Technical User

ResultYou have configured the RFC connections for two business systems.

03/30/2009 PUBLIC 51/72

5 Configuring SAP NetWeaver Business Client 1.0

5 Configuring SAP NetWeaver BusinessClient 1.0

The user interface frontend of SAP NetWeaver Business Client (NWBC) integrates classic SAP GUI-basedtransactions and newWeb Dynpro applications. To use the Business Client, install it, add and connectyour productive systems.

PrerequisitesYou have installed the SAP NWBC 1.0. For information about installing SAP NWBC, see:http://help.sap.com Search Documentation. Search for Business Client Installation in

application SAP NetWeaver.

Note

See SAP Note 900000 for minimal prerequisites and SAP Note 1029940 for release restrictions.

Procedure

1. Enter System Dataa) Choose System Preferences .b) Enter the following data:n System namen Type: SAP All-in-One (ERP)n Protocol

n Server/Host:n Port:

n Path: /sap/bc/dal/demoAn Client

n Languagen User name

c) Confirm.2. Connect to System

a) Mark the line for your system.b) Choose button Switch to.

The Business Client should connect to your system. If it does not connect, check your Protocolsettings.

03/30/2009 PUBLIC 53/72

http://help.sap.com


http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=SAP Note 1029940 &_NLANG=en&_NVERS=0

5 Configuring SAP NetWeaver Business Client 1.0

More Information

n for more detailed documentation about architecture and use of SAP NetWeaver Business Client,see the Service Marketplace: http://help.sap.com Search Documentation . Search for NWBC inapplication SAP NetWeaver.

54/72 PUBLIC 03/30/2009

http://help.sap.com

6 Appendix

6 Appendix

6.1 Basic Technical Settings for Basic Functions

After the basic settings configuration, some main functions need to run immediately. You need toconfigure all basic settings, so that all these basic functions can run and SAP Support is able to fullysupport you. In some cases, though, it might be necessary to either only configure one specificfunction or check individual IMG activities, for a specific function to run.

FeaturesMaintenance Optimizersee How to Congure Maintenance Optimizer in the Service Marketplacehttp://service.sap.com/solutionmanager Media Library Technical Papers .

EarlyWatch Alert for ABAP systemsIn transaction SPRO for Solution Manager IMG nodes, execute:

n all IMG activities in section General tasks

n all IMG activities in section Connection to SAP

n all IMG activities in section Authorizations

n IMG activity: Background Jobsn in section HTTP Services

l IMG activity: Activate Solution Manager Services

n all IMG activities in section System Landscape

n all IMG activities in section Service Data Control Center

EarlyWatch Alert for Java systems (Root Cause Analysis)This section only applies if you have Java systems in your landscape.In transaction SPRO for Solution Manager IMG nodes, execute:

n all IMG activities in section General tasks




l Activate Solution Manager Servicesn all IMG activities in section System Landscape

n all IMG activities in section Service Data Control Center

n all IMG activities in section Root Cause Analysis

03/30/2009 PUBLIC 55/72




6 Appendix6.1 Basic Technical Settings for Basic Functions

Basic Service DeskIn transaction SPRO for Solution Manager IMG nodes, execute:

n the first IMG activity Activate Service Desk BC Set in section Basic BC Sets for Configuration

n all IMG activities in section General Tasks



n IMG activity Background Jobsn in section HTTP Services

l Activate Solution Manager Servicesl Create Alias for Business Server Pages

n in section System Landscape

l Put Systems in Landscapel Synchronize with SAP Support Portal

Expert on DemandIn transaction SPRO for Solution Manager IMG nodes, execute:

n in section Basic BC Sets for Configuration

l Activate Service Desk BC Set

l Activate Issue Management BC Setsn all IMG activities in section General Tasks




l Activate Solution Manager Servicesn in section System Landscape

l Put Systems in Landscapel Define Solution Landscapel Synchronize with SAP Support Portal

Basic Business Blueprint and ConfigurationIn transaction SPRO for Solution Manager IMG nodes, eExecute:

n all IMG activities in section General Tasks




l Activate Solution Manager Servicesl Create Alias for Document Management Service

n in section System Landscape

l Put Systems in Landscape

56/72 PUBLIC 03/30/2009

6 Appendix6.2 Glossary

l IMG activity Create Logical Components in section Define Solution Landscapel Synchronize with SAP Support Portal

6.2 Glossary

6.2.1 Terminology: System Landscape and Related Terms

The Solution Manager is based on a system in a system landscape. Different terms are used to refer to this,depending on how the system landscape is viewed. There are two semantic levels:

n overall view of systems and their role in the system landscape, andn the technical level, referring to the technical attributes of a system, not its purpose in the system

landscape.

It depends on whether the focus is on a system’s purpose or on its technical properties. There areseveral possible perspectives:

n general perspectiveTerm: System

n Solution Manager perspective (Solution Manager as the central management platform)Terms: Managing System, Managed System

Figure 9:

03/30/2009 PUBLIC 57/72


n business process—oriented perspective (business process as main focus)Term: Business System

Figure 10:

n technical perspective (technical attributes as main focus)Term: System Type, System Component, System Component Type, Technical System

58/72 PUBLIC 03/30/2009


Figure 11:

FeaturesThe following table contains definitions of how these term are used in documentation.Definitions Infrastructure: System

Term Definition Additional Remarks

System Neutral definition from a generalperspective. The name of the system isbased on the SAP product definition. Itcan be defined more closely (see above),for example, managed system, businesssystem and/or technical system.

Used in general documentation, inoverviews and so on.

ExampleIn your system landscape youmaintainseveral systems.

Managing System The central managing system, usuallythe Solution Manager system, fromthe Solution Manager perspective. Amanaging systemusuallymanages othersystems, which are called managedsystems.

Used in general Solution Managerscenario and function documentationin the system landscape.Synonym: Central System(CCMS-related)

ExampleYour managing system is SAP SolutionManager.

03/30/2009 PUBLIC 59/72



Managed System Any system that is managed by anothersystem, usually the central SolutionManager system platform, from theSolution Manager perspective. In thissense, the Solution Manager system canalso be a managed system.

Used in general Solution Managerscenario and function documentationin the system landscape. Synonym:Remote System (CCMS-related)

ExampleYou monitor your managed systemsregularly, using SAP Solution Manager.

Business System Any system used in a business scenario,from a business perspective.

Used in general Business Suite andSolution Manager documentation, forBusiness Suite—related topics.

ExampleYou monitor all business systems onwhich the business process steps run,regularly.

System Type The type which the system can be, froma technical perspective:n ABAP

n Javan ABAP and Java

Used in general Solution Managersystem landscape documentation,with reference to the general systemarchitecture.

ExampleThe SAP Solution Manager system isbased on system types AS ABAP and ASJava.

System Component A technical unit of a system whichis itself defined by a main instance,depending on the application view (thebusiness purpose), from a technicalperspective,.

The main instance can be defined inmore detail by server, client, softwarecomponent and so on. It can be installedindependently.

ExamplePlease change the data of the maininstance for system componentSolution Manager Diagnostics.

60/72 PUBLIC 03/30/2009



System Component Type The underlying technology of thesystem component, from a technicalperspective.

ExampleSystem component Solution ManagerDiagnostics is of system componenttype Java.

Technical System A technical unit based on one or moreinstances, from a technical perspective.Main instances can be installed inone system, but also as independent(technical) systems with independentsystem IDs. It is defined by technicalattributes, depending on the systemcomponent type, such as:n System IDn Clientn Installation Numbern ...

ExampleSAP Solution Manager is running on(technical) system: SMP Client 200Solution Manager Diagnostics isrunning on (technical) system: SMD

6.2.2 Terminology: Solution and Related Terms

The life—cycle of a product comprises different phases, such as implementation, operation, andoptimization, which are all supported by SAP Solution Manager. In the operational phase, SAPSolution Manager uses the technical unit Solution to bundle systems according to various criteria:

n related business process stepsn related systems by administration purpose

The term is related to another primary concept, the Logical Component. Technical systems are stored inlogical components, which are then referenced in the solution. The solution is uniquely defined byits Leading System Role.

FeaturesThe following table contains definitions of how these term are used in documentation.Definitions Infrastructure: Solution

03/30/2009 PUBLIC 61/72



Solution A group of systems administered in SAPSolution Manager, which are managedtogether. Solutions are independentof one another, e.g. all systems of onesubsidiary.

Used in general documentation, inoverviews and so on. The solutionis defined in the Solution Directory(transaction SOLMAN_DIRECTORY). Here,all information about included systemsand business processes running onthese systems is stored. It forms thebasis for subsequent applications,such as Monitoring, Job SchedulingManagement or Issue Management.

ExampleSee document Solution Concept andDesign on SAP Service Marketplace at:http://service.sap.com/solutionmanager


Logical Component A set of technical systems with thesame SAP product release and maininstance, to be able to use these systemsin a system landscape uniformly invarious SAP Solution Manager usescenarios, i.e. in implementation,operational processing, and permanentoptimization. It separates theabstract component level fromthe physical system level, allowingsystem-independent business processdefinition.

Used in general documentation.

ExampleSee document Logical Componentson SAP Service Marketplace at:http://service.sap.com/solutionmanager


Leading system role The system role of the business processesdocumented in a solution, for instanceproduction system or developmentsystem. The default system role isproduction, so all business processesdefined for this solution run in systemswith the system role: productive system.

Used primarily in documentation forSolution Directory.

Navigation role Used only for business processoperations: specifies the system roleused for navigation (checks, display) toobjects in managed systems.

Used in relation to business processoperations documentation.

NoteChange of navigation role isuser—specific and valid for allsolutions in the Solution Directory.

ExampleUser <XY> wants to check objects inthe development systems. The leading

62/72 PUBLIC 03/30/2009







role of the solution is productionsystem. The user specifies developmentsystem as navigation role.

03/30/2009 PUBLIC 63/72

A Reference

A Reference

A.1 The Main SAP Documentation Types

The following is an overview of themost important documentation types that you need in thevarious phases in the life cycle of SAP software.

Figure 12: Documentation Types in the Software Life Cycle

Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, aswell as many glossary entries in English and German.

n Target group:l Relevant for all target groups

n Current version:l On SAP Help Portal at http://help.sap.com Additional Information Glossary (direct

access) or Terminology (as terminology CD)l In the SAP system in transaction STERM

03/30/2009 PUBLIC 65/72

http://help.sap.com

A ReferenceA.1 The Main SAP Documentation Types

SAP Library is a collection of documentation for SAP software covering functions and processes.

n Target group:l Consultants

l System administratorsl Project teams for implementations or upgrades

n Current version:l On SAP Help Portal at http://help.sap.com (also available as documentation DVD)

The security guide describes the settings for a medium security level and offers suggestions forraising security levels. A collective security guide is available for SAP NetWeaver. This documentcontains general guidelines and suggestions. SAP applications have a security guide of their own.

n Target group:l System administratorsl Technology consultantsl Solution consultants

n Current version:l On SAP Service Marketplace at http://service.sap.com/securityguide

Implementation

Themaster guide is the starting point for implementing an SAP solution. It lists the requiredinstallable units for each business or IT scenario. It provides scenario-specific descriptions ofpreparation, execution, and follow-up of an implementation. It also provides references to otherdocuments, such as installation guides, the technical infrastructure guide and SAP Notes.

n Target group:l Technology consultantsl Project teams for implementations

n Current version:l On SAP Service Marketplace at http://service.sap.com/instguides

The installation guide describes the technical implementation of an installable unit, takinginto account the combinations of operating systems and databases. It does not describe anybusiness-related configuration.

n Target group:l Technology consultantsl Project teams for implementations


Configuration Documentation in SAP Solution Manager ‒ SAP Solution Manager is a life-cycleplatform. One of its main functions is the configuration of business and IT scenarios. It containsCustomizing activities, transactions, and so on, as well as documentation.

66/72 PUBLIC 03/30/2009

http://help.sap.com

http://service.sap.com/securityguide










n Target group:l Technology consultantsl Solution consultants

l Project teams for implementationsn Current version:l In SAP Solution Manager

The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system.The Customizing activities and their documentation are structured from a functional perspective.(In order to configure a whole system landscape from a process-oriented perspective, SAP SolutionManager, which refers to the relevant Customizing activities in the individual SAP systems, is used.)

n Target group:l Solution consultants

l Project teams for implementations or upgradesn Current version:l In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation

The technical operations manual is the starting point for operating a system that runs on SAPNetWeaver, and precedes the solution operations guide. The manual refers users to the tools anddocumentation that are needed to carry out various tasks, such as monitoring, backup/restore,master data maintenance, transports, and tests.

n Target group:l System administrators


The solution operations guide is used for operating an SAP application once all tasks in thetechnical operations manual have been completed. It refers users to the tools and documentationthat are needed to carry out the various operations-related tasks.

n Target group:l System administratorsl Technology consultantsl Solution consultants


Upgrade

The upgrade master guide is the starting point for upgrading the business and IT scenarios of anSAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of anupgrade. It also refers to other documents, such as the upgrade guides and SAP Notes.

03/30/2009 PUBLIC 67/72








n Target group:l Technology consultantsl Project teams for upgrades


The upgrade guide describes the technical upgrade of an installable unit, taking into accountthe combinations of operating systems and databases. It does not describe any business-relatedconfiguration.

n Target group:l Technology consultantsl Project teams for upgrades


Release notes are documents that contain short descriptions of new features in a particular releaseor changes to existing features since the previous release. Release notes about ABAP developmentsare the technical prerequisite for generating delta and upgrade Customizing in the ImplementationGuide (IMG).

n Target group:l Consultants

l Project teams for upgradesn Current version:l On SAP Service Marketplace at http://service.sap.com/releasenotesl In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

68/72 PUBLIC 03/30/2009







http://service.sap.com/releasenotes



Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example n Words or characters quoted from the screen. These include field labels, screen titles,pushbutton labels, menu names, and menu options.

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

03/30/2009 PUBLIC 69/72

http://www.sap.com

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2009 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 permissionof 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 othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof 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 othersoftware vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated 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 registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.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 implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

70/72 PUBLIC 03/30/2009

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

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

03/30/2009 PUBLIC 71/72

https://service.sap.com/instguides



SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2009 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 bechanged without prior notice.

configuration guide sap solution manager 7.0 ehp 1 and sp 19

Documents