63868572 configuration guide sap solution manager as of sp12

CONFIGURATIONGUIDE

SAP SolutionManager 4.0 as ofSP12

Scenarios:Service DeskImplementation of SAP SolutionsUpgrade of SAP SolutionsChange ManagementSolution MonitoringDelivery of SAP ServicesRoot Cause AnalysesSAP Solution Support Enablement packageSAP Quality Center by HPOne Transport Order (OTO)

June, 2007

© Copyright 2004 SAP AG. All rights reserved.

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

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

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® andSQL Server® are registered trademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®,MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries,pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,Netfinity®, Tivoli®, Informix and Informix® Dynamic Server

TM are

trademarks of IBM Corp. in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif ® are registered trademarks ofthe Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,WinFrame®, VideoFrame®, MultiWin® and other Citrix product namesreferenced herein are trademarks of Citrix Systems, Inc.

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

JAVA® is a registered trademark of Sun Microsystems, Inc.

J2EE™ is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,used under license for technology invented and implemented byNetscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP BusinessWorkflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,Management Cockpit, mySAP, mySAP.com, and other SAP productsand services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. MarketSet and EnterpriseBuyer are jointly owned trademarks of SAP Markets and CommerceOne. All other product and service names mentioned are thetrademarks of their respective owners.

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

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

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

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

Configuration Guide: SAP Solution Manager 4.0

June, 2007 3

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on thescreen. These include field names,screen titles, pushbuttons as well as

menu names, paths and options.Cross-references to other documentation

Example text Emphasized words or phrases in bodytext, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. Theseinclude report names, program names,

transaction codes, table names, andindividual key words of a programminglanguage, when surrounded by body

text, for example, SELECT andINCLUDE.

Example text Screen output. This includes file anddirectory names and their paths,

messages, names of variables andparameters, source code as well asnames of installation, upgrade and

database tools.

Example text Exact user entry. These are words orcharacters that you enter in the system

exactly as they appear in thedocumentation.

<Example text> Variable user entry. Pointed bracketsindicate that you replace these words

and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example,function keys (such as F2) or the

ENTER key.

Icons

Icon MeaningCaution

Example

Note

Recommendation

Syntax

Configuration Guide: SAP Solution Manager 4.0 as of SP12

4 June, 2007

Contents

1. CONFIGURATION SAP SOLUTION MANAGER 4.0 ................................................6

1.1 General Remarks................................................................................................................................................. 6

1.2 Implementation Guide (IMG) ............................................................................................................................. 6General Information........................................................................................................................................... 6Create IMG Project............................................................................................................................................ 7

2. SCENARIOS AND THIRD PARTY INTEGRATION ...................................................9

3. TECHNICAL REQUIREMENTS ...............................................................................10

3.1 All Scenarios .......................................................................................................................................................103.1.1 SAP GUI for Windows..............................................................................................................................103.1.2 Microsoft Office ........................................................................................................................................103.1.3 Web Browser.............................................................................................................................................103.1.4 Support Package Levels............................................................................................................................10

3.2 Service Desk........................................................................................................................................................11

3.3 Implementation of SAP Solutions ......................................................................................................................113.3.1 Check the Word Security Settings............................................................................................................113.3.2 Support Package Levels for Implementation ...........................................................................................113.3.3 Support Package Levels for Customizing Distribution ............................................................................123.3.4 Support Package Levels for Upgrading with Solution Manager .............................................................12

3.4 Service Data Control Center ..............................................................................................................................123.4.1 Support Package Levels............................................................................................................................12

3.5 Change Request Management............................................................................................................................133.5.1 Support Package Levels............................................................................................................................13

3.6 Solution Monitoring ...........................................................................................................................................133.6.1 Support Package Levels............................................................................................................................133.6.2 Single Sign-On in SAP Service Marketplace............................................................................................14

3.7 Delivery of SAP Services ....................................................................................................................................143.7.1 Support Package Levels............................................................................................................................14

3.8 Root Cause Analysis ...........................................................................................................................................143.8.1 Requirements for Solution Manager Diagnostics.....................................................................................143.8.2 Software Requirements for Monitored Satellite Systems.........................................................................14

3.9 Software Requirements for Satellite Systems for Reverse Business Engineer (RBE) ......................................15

3.10 SAP Quality Center (QC) by HP......................................................................................................................15

3.11 One Transport Order (OTO) ...........................................................................................................................15

4. ROLES AND AUTHORIZATIONS............................................................................16

4.1 General ...............................................................................................................................................................16


June, 2007 5

4.2 Copy and adjust roles.........................................................................................................................................16

4.3 Roles and Profiles in the SAP Solution Manager System ..................................................................................17

4.4 Roles and Profiles in the Satellite Systems .........................................................................................................21

4.5 SLD (System Landscape Directory) User...........................................................................................................25

4.6 Automatically Generated Profiles/Roles for Set Background Users..................................................................25

5. ADDITIONAL INFORMATION..................................................................................27

6. OTHER DOCUMENTATION FOR SAP SOLUTION MANAGER.............................28

7. TRAINING COURSES...................................................................................................29

8. APPENDIX ...............................................................................................................30

SAP Notes .................................................................................................................................................................30All Scenarios ......................................................................................................................................................30Service Desk.......................................................................................................................................................30Implementation and Distribution......................................................................................................................30Change Request Management...........................................................................................................................30Solution Monitoring ..........................................................................................................................................30SAP Support Services........................................................................................................................................30Root Cause Analyses: Solution Manager Diagnostics.......................................................................................30SAP Solution Support Enablement Package.....................................................................................................31Knowledge Warehouse ......................................................................................................................................31

RFC Destinations SAP Solution Manager ...............................................................................................................31

Periodic Jobs ............................................................................................................................................................32


6 June, 2007

1. Configuration SAP Solution Manager 4.01.1 General RemarksThis guide describes the steps required to complete the configuration of a SAP Solution Manager 4.0system.

If you are upgrading a SAP Solution Manager 3.2 system to SAP Solution Manager 4.0, refer tothe Upgrade Guide for SAP Solution Manager 4.0 and the FAQ Upgrade (Step by Step). Youcan download these documents from the SAP Support Portal: service.sap.com/instguidesSAP Components SAP Solution Manager Release 4.0In addition see SAP notes: 892412 Upgrade to SAP Solution Manager 4.0

903587 Upgrade to SAP Solution Manager 4.0 Postprocessing908186 SAP Notes for SAP Solution Manager 4.0 SP01 (12/2005)939897 SAP Solution Manager Usage Data

Ensure that: you are working with the most recent version of this and other installation/upgrade guides, which you

can download from the SAP Service Marketplace: service.sap.com/instguides Tools and MethodsSAP Components SAP Solution Manager

In addition, please refer to SAP note 903494 (Configuration Guide for Solution Manager: LatestChanges) if you are working with a higher Support Package Level than SP12.

you have the most recent Support Packages and Add-Ons. You can download the items you needfrom the SAP Support Portal: service.sap.com/swdc

1.2 Implementation Guide (IMG)General Information

We strongly recommend before being able to work with the individual scenarios to configure thenecessary steps in the IMG activities in the SAP Solution Manager system.

System Configuration is done using transaction SPRO (SAP Reference IMG) in SAP Solution Managersystem and the according Configuration Guide. The IMG Reference Guide is structured as follows:

1. GENERAL IMPORTANT INFORMATION

We strongly recommend, before starting to configure, please read the general informationsection READ ME (General Information) on preparatory activities for Solution Manager andSatellite systems and how to proceed.

For any changes of individual activities due to Support Package Levels, please refer to SAP note 903274.

2. BASIC SETTINGS

To use the Solution Manager, you must first execute all Basic Settings before configuring the scenario-specificfunctionality. There are two ways of performing this basic Solution Manager configuration:

http://www.service.sap.com/instguides

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=000892412






http://www.service.sap.com/swdc



June, 2007 7

o Wizard-based Configuration

Simple initial configuration of most important required basic settings.

o Standard Configuration

Detailed configuration of all required basic settings.

3. SCENARIO-SPECIFIC SETTINGS

Before you can start to configure scenario-specific settings you need to have all basic settings configured.The IMG activities for the configuration of Service Desk, Preconfiguration for Service Provider and ICWebClient are STANDARD Configuration.

We strongly recommend, that when you plan to execute additional configuration andtherefore modify the Standard configuration for the described individual scenarios, youshould do this within a project and with according consulting.

Create IMG ProjectIn the IMG you can document customizing parameters and set processing statuses as well as go to theactivities. The documentation function lets you record information about the customizing settings in theactivity, which can later (e.g. in a Business Improvement Project) make business process parameterchanges easier. The processing status gives the project leader an overview of project progress in the projectanalysis.

If you upgrade from SAP Solution Manager 3.1 or 3.2 to 4.0 we recommend you create anUpgrade or Delta IMG project as described underneath.Note that, if you have already created an IMG project and you upgrade to stack 12, make sure toset the status values for all activities in this IMG project before upgrading. After the upgrade,recreate your IMG project again by following the description underneath.

1. Choose transaction SPRO_ADMIN.2. Create a new project by choosing button Create.3. Enter all necessary data.4. Go to tab Scope.5. Choose button Change Selection.6. Choose Service Solution Manager and confirm. (In case you have upgraded to stack 12,

check if your scope is still set).7. Choose the button Generate project.8. Go to tab Project Views.9. Choose the button Create.10. In the dialog box, enter a project view name.If you create an Upgrade or Delta IMG project proceed as follows:

a. Select the criterion for Release Customizing.b. Confirm twice.c. In the screen selection on Release Customizing choose the relevant Upgrade or

Delta customizing activities.d. Choose component ST (SAP Solution Manager Tool).e. Specify the Upgrade Releases from and to.f. Save your settings.


8 June, 2007

g. Select the project view and choose Generate View.You can view your IMG now by choosing Display View IMG.

If you recreate your existing IMG project after upgrading to stack 12 proceed as follows:a. Select the criterion for Manual selection in Project IMG.b. Confirm twice.c. In the screen selection on Manual selection in Project IMG choose Select.d. For your Project IMG select in the displayed tree the relevant IMG nodes.e. Confirm.f. Save your settings.g. Select the project view and choose Generate View IMG.You can view your IMG now by choosing Display View IMG.


June, 2007 9

2. Scenarios and Third Party IntegrationSAP Solution Manager 4.0 supports the following scenarios:

Service Desk Implementation of SAP Solutions Upgrade of SAP Solutions Change Management Solution Monitoring Delivery of SAP Services Root Cause Analyses SAP Solution Support Enablement Package SAP Quality Center by HP One Transport Order (OTO)

These scenarios are described in the Master Guide for SAP Solution Manager 4.0, which you can downloadfrom the SAP Service Marketplace: service.sap.com/instguides Tools & Methods SAP ComponentsSAP Solution Manager.

Beware that the following scenarios are NOT core functionality of SAP Solution Manager. Youhave to order them separately:- SAP Solution Support Enablement Package (For more information, see: service.sap.com/sep)- SAP Quality Center by HP (For more information, see: service.sap.com/solutionmanager ->spotlight section)


http://service.sap.com/sep

http://service.sap.com/solutionmanager


10 June, 2007

3. Technical Requirements3.1 All Scenarios3.1.1 SAP GUI for WindowsInstall at least the complete SAP GUI 6.40 with the most recent Support Package level.

3.1.2 Microsoft OfficeOne of the following must be installed:

Microsoft Office 2000, Service Pack 1 (minimum requirement) or later Microsoft Office 2002 (Office XP)

To ensure that the English language is installed in your system:1. In Windows 2000, choose Start Programs Microsoft Office 2000 Microsoft Office Tools

Microsoft Office Language Settings.2. Select English and confirm.This setting is also recommended for Office 2000 on Windows NT.

For more information about the correct settings for Microsoft Word, see SAP Note 199123(Word Settings).

3.1.3 Web BrowserThe SAP Solution Manager is compatible with Microsoft Internet Explorer 5.5 or higher.

Netscape Navigator is no longer supported.SAP Internet Transaction Server (SAP ITS) is no longer supported; the Internet CommunicationManager (ICM) of the SAP Web AS is supported instead.

3.1.4 Support Package Levels3.1.4.1 General

Generally, it is recommended that you install the most recent Support Package Stack for the SAP SolutionManager. Patches are available from the SAP Service Marketplace: service.sap.com/swdc.

SAP Note 892412 (Upgrade Solution Manager 4.0) includes an overview of software components andSupport Package levels that must be installed in your SAP Solution Manager system.

For BBPCRM, you can only load Support Packages, for which Conflict Resolution Transports(CRTs) for the SAP Solution Manager exist. This implies that there are periods in time in which aSupport Package for BBPCRM can not be applied. The Support Package Stack definitionrecommends when to load specific Support Packages.


http://www.service.sap.com/swdc



June, 2007 11

3.1.4.2 Automatic Generation of RFC DestinationsThe optional function for Automatic Generation of RFC Destinations requires the following Support Packagelevels in the satellite systems:

Release Software Component Support Package46B / 46B SAP_BASIS / SAP_ABA SP56

46C / 46C SAP_BASIS / SAP_ABA SP37

46D / 46D SAP_BASIS / SAP_ABA SP26

610 / 50A SAP_BASIS / SAP_ABA SP25

620 / 620 SAP_BASIS / SAP_ABA SP10



Table 1: Support Package Levels for Satellite Systems for Automatic Generation of RFC Destinations

For satellite systems:- Releases earlier than 46B are not supported.

See SAP Note (optional):128447 (Trusted/Trusting Systems), describes how to define a trusted/trusting systemrelationship between two R/3 Systems and how to use this relationship.

3.2 Service DeskFor information about requirements for satellite systems, see SAP Note 388814 (Extending the feedbackfunctions). For missing customizing for Service Desk, see SAP Note 824640 (Missing customizing forService Desk in Solution Manager).

3.3 Implementation of SAP Solutions3.3.1 Check the Word Security SettingsSee SAP Note 368861 (KW and security levels under MS Office)

3.3.2 Support Package Levels for ImplementationThe following Support Package Levels are the minimum requirements for satellite systems:

Release Software Component Minimum Support Package Level46B / 46B SAP_BASIS / SAP_ABA SP56

46C / 46C SAP_BASIS / SAP_ABA SP29






Table 2: Minimum Support Package Levels for Satellite Systems (Scenario: Implementation andDistribution)






12 June, 2007

Releases earlier than 46B are not supported.

3.3.3 Support Package Levels for Customizing DistributionCustomizing distribution can be used to compare and synchronize Customizing settings between differentSAP R/3 Systems as well as between different software components. For example,The optional Initial Distribution function and delta distribution in the Implementation and Distributionscenario requires the following minimum Support Package levels in the satellite systems:

Release Software Component Support Package46B / 46B SAP_BASIS / SAP_ABA SP56

46C / 46C SAP_BASIS / SAP_ABA SP38(SP48 for local locks in satellite systems)



620 / 620 SAP_BASIS / SAP_ABA SP12(SP44 for local locks in satellite systems)

640 / 640 SAP_BASIS / SAP_ABA SP00(SP09 for local locks in satellite systems)


Table 3: Support Package Levels for Satellite Systems for Initial Distribution and Delta Distribution(Scenario: Implementation and Distribution)

Releases earlier than 4.6B are not supported.

3.3.4 Support Package Levels for Upgrading with Solution ManagerTo use the Upgrade Flag in the appropriate scenario, you need the following Support Package Levels(SAP_BASIS):(SP levels of the satellite system: target release and SP after technical upgrade)

Release Support Package620 SP42

640 SP04

700 SP00

Table 4: Support Package Levels for Satellite Systems for Upgrading with Solution Manager

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

3.4 Service Data Control Center3.4.1 Support Package LevelsThe new Service Data Control Center (transaction SDCCN) is available with the latest ST-PI Add-On (ST-PI2005_1_<release>).


June, 2007 13

3.5 Change Request Management3.5.1 Support Package Levels

In all systems where transports are controlled by Change Request Management (satellite systems), and in allsystems where the TMS domain controllers run (as of SAP Web AS 6.10), make sure that you install at leastthe following Support Packages:

for the component SAP_BASIS:

Release Support Package46C SP48 (recommended SP51)

46D SP42

610 SP43

620 SP51

640 SP12

700 SP06 (see SAP Note 907768)

Table 5: Support Package Levels for Satellite Systems running TMS domain controllers

for the Transport Domain Controller:

Release Support Package46C Not supported

610 SP43

620 SP51

640 SP12

700 SP06 (see SAP Note 907768)

Table 6: Support Package Levels for Satellite Systems running the Transport Domain Controller

Before you begin to configure SAP Change Request Management, make sure that you read the requiredSAP Notes (see Appendix).

3.6 Solution Monitoring3.6.1 Support Package LevelsUse the most recent version of the ST-PI Add-On (ST-PI 2005_1_<release>) and ST-A/PI.

See also SAP Note 539977 (Release strategy for add-on ST-PI) and SAP Note 69455(Service Tools for Applications Plug-In ST-A/PI).For satellite systems that do not meet the requirements for importing the ST-PI Add-On, seeSAP Note 560630 (ST-PI: Solution Tools plug-in – prerequisite not met).






14 June, 2007

3.6.2 Single Sign-On in SAP Service MarketplaceTo access the SAP Service Marketplace from the SAP Solution Manager without having to enter a user andpassword each time, use Single Sign-On. When you log on using Single Sign-On, you are automatically andsecurely authenticated to the system.To install Single Sign-On go to: service.sap.com/sso-smp

3.7 Delivery of SAP Services3.7.1 Support Package LevelsUse the most recent version of the ST-SER Add-On (ST-SER 700_2005_2) with the following SupportPackage Levels for SAP_BASIS (optional: in addition see SAP Note 892412 Upgrade to SAP SolutionManager 4.0):

Release Support Package700 SP05

Table 7: Support Package Levels for Delivery of SAP Services

3.8 Root Cause Analysis3.8.1 Requirements for Solution Manager DiagnosticsYou need the following Support Package Level (SAP_BASIS):

Release Support Package700 SP 08 (ABAP Kernel Patch 80)

Table 8: Support Package Levels for Solution Manager Diagnostics

Platform-dependent information is available on service.sap.com/pam, refer to SAP WebAS 7.00.

3.8.2 Software Requirements for Monitored Satellite SystemsFor systems monitored by Solution Manager Diagnostics, make sure to apply the mentionedprogram versions or newer versions. The following table lists the requirements:

Software Component RequirementSAP NetWeaver 2004 WebAS JAVA 6.40 SP Stack 14Other SAP NetWeaver 2004 systems WebAS JAVA 6.40 SP Stack 14SAP Netweaver 2004S systems WebAS 7.00 SP Stack 6

ABAP Basis SP5 (SAPKB70005)

Table 9: Support Package Levels for Monitored Systems

http://www.service.sap.com/sso-smp


http://www.service.sap.com/pam


June, 2007 15

3.9 Software Requirements for Satellite Systems for ReverseBusiness Engineer (RBE)

Releases beneath 4.6C are not supported.

3.10 SAP Quality Center (QC) by HPThe SAP Solution Manager adapter for SAP Quality Center by HP provides the integration for the testingsolution SAP Quality Center by HP with SAP Solution Manager. It is delivered by a process integrationpackage for SAP Solution Manager. Therefore, it is non-core SAP Solution Manager functionality.

For more information on this topic see the according Master Guide, Installation Guide and ConfigurationGuide on the Service Marketplace/instguides -> SAP Components -> SAP Solution Manager -> Release 4.0.

3.11 One Transport Order (OTO)For more information on this topic see Configuration Guide for One Transport Order (OTO) on ServiceMarketplace/solutionmanager -> Media Library->Technical Papers.

http://service.sap.com/instguides




16 June, 2007

4. Roles and authorizations4.1 GeneralRoles and Profiles exist for the following components:

SAP Solution ManagerSatellite SystemsBackground User

4.2 Copy and adjust rolesBefore you assign the relevant roles and profiles to your users, we recommend that you copy and specify thesetting for SAP standard roles and profiles. SAP ships the roles with default values. For default values thatare missing, you need to configure the authorizations. Perform the following steps:To load roles or profiles from Client 000 either:1. transport from Client 000 (for ABAP roles) into your target Client (roles and profiles) or2. choose Upload and Download (for roles in transaction PFCG)To copy the roles to customer namespace:1. Call transaction PFCG (Role Maintenance).2. Specify a role and choose Copy role.3. In the to role field, specify a name (customer namespace) for the new role and choose Copy all.4. Save.To specify all the allowed settings for the roles:3. Go to the tab authorizations.4. Choose Maintain authorizations.5. Double-click the yellow traffic lights.

The authorizations are displayed in green. You have now assigned full authorizations for the activities.You can also make further changes to the authorizations in accordance with your specific requirements.

6. Save your changes.7. Generate the profile.To assign a (new) role to the user master data:8. Call transaction PFCG.9. Choose the Users tab.10. Specify the user.11. Execute the User Comparison.12. Save.


June, 2007 17

4.3 Roles and Profiles in the SAP Solution Manager SystemDue to the system landscape of SAP Solution Manager System and Satellite Systems, it is necessary toassign users with corresponding roles in the SAP Solution Manager including Diagnostics as well as in theSatellite System (so-called Monitored Systems in respect to Diagnostics).

For details on all roles concerning Diagnostics, refer to Diagnostics (Advanced Guide) on theSAP Service Marketplace: service.sap.com/installation Installation and Upgrade Guides.For more information on the concept and authorization objects, see: Authorization ConceptSolution Manager 4.0.

The table below provides an overview of the roles and profiles for SAP Solution Manager system. For the ASJava, the default user store is the ABAP database, thus users have to be created within transaction SU01 only.For the according scenarios, users have to be also assigned in the Satellite Systems with the correspondingroles (see chapter 4.4).

Users who are required to log on by using trusted RFC destinations must also assign trustedsystem authorizations. In particular, you have to assign the profile S_RFCACL (as of < SAPNetWeaver AS 7.00) or the role SAP_S_RFCACL (as of SAP NetWeaver AS 7.00) whichcontains the authorization object S_RFCACL. S_RFCACL consists of a number of authorizationfields which allow a trusting trusted relation between SAP Solution Manager and any Satellitesystem. Due to the high potential risk of such an RFC connection the authorization objectS_RFCACL is not included in SAP_ALL.

Scenario/Functionality Role Purpose

IMPLEMENTATION AND DISTRIBUTION

SAP_SOL_PM_COMP 1) Composite role: Organizing and planning a project inIMG

SAP_SOL_AC_COMP 1) Composite role: Create Business content and thedocumentation of operational activities

SAP_SOL_BC_COMP 1) Composite role: Development of customer-specificprograms and authorizations

SAP_SOL_TC_COMP 1) Composite role: Installing systems and providingtechnical support

SAP_SOL_RO_COMP 1) Composite role: Read-only authorizations for SAPSolution Manager

SAP_SOL_RE_COMP 1) Composite role: Read user according to status(document management)

SAP_SOL_LEARNING_MAP_DIS For restricted authorization for user SOLARSERVICE,which is used for accessing HTTP services in theSolution Manager without login, e.g. for displaying HTMLLearning Maps (1); see Basic settings in IMG.

Implementation andUpgrade

SAP_DMDDEF_DIS For restricted authorization for user SOLARSERVICE,which is used for accessing HTTP services in theSolution Manager without login, e.g. for displaying HTMLLearning Maps (1)

Changing of Roadmaps SAP_RMDEF_RMAUTH_EXE For administrator purposes: change of roadmaps

http://www.service.sap.com/installation


18 June, 2007

SAP_RMDEF_RMAUTH_DIS For display purposes: change of roadmaps.

SAP_SOL_TRAINING_ALL Single role (included in SAP_SOL* Composite roles),needed to use E-Learning Management tool.

E-Learning Management

SAP_SOL_TRAINING_EDIT Single role (included in SAP_SOL* Composite roles),needed to use E-Learning Management tool.

SERVICE DESK

SAP_SUPPDESK_ADMIN 2) Authorizations needed to configure the Service Desk,IC WebClient and IMG. In addition, it contains theauthorizations for the rolesSAP_SUPPDESK_PROCESS,SAP_SUPPDESK_DISPLAY, andSAP_SUPPDESK_CREATE,

SAP_SUPPDESK_PROCESS 2) Authorizations needed for message (notification)processing, including the use of the solution database

SAP_SUPPDESK_CREATE 2) Create support messages from the satellite systems orin the central SAP Solution Manager system. If a genericRFC user is used to create notifications in the SAPSolution Manager system (that is, the user is specified inthe RFC destination in transaction SM59 in the satellitesystems), the role will only need to be assigned to thisgeneric RFC user.

Service Desk-Messagesand IC WebClient

SAP_SUPPDESK_DISPLAY 2) Display user

SAP_SUPPCF_ADMIN Administrator authorization for creating and processing,and IMG, see: SAP Note 834534.

SAP_SUPPCF_CREATE Key user (IT-Operator) authorization to createmessages, see: SAP Note 834534.

Preconfiguration for ServiceProviders

SAP_SUPPCF_PROCESS Support Employee authorization to process messages,see: SAP Note 834534.

SAP_SV_SOLUTION_MANAGER Full authorization

SAP_SV_SOLUTION_MANAGER_DISP Display authorization

SAP_SUPPDESK_ADMIN 2) 4) For EXPERTMODEAuthorizations needed to configure the Service Desk. Inaddition, it contains the authorizations for the rolesSAP_SUPPDESK_PROCESS,SAP_SUPPDESK_DISPLAY, andSAP_SUPPDESK_CREATE

SAP_SUPPDESK_PROCESS 2) For EXPERTMODEAuthorizations needed for message (notification)processing, including the use of the solution database

Issue Tracking

SAP_SUPPDESK_DISPLAY 2) For EXPERTMODEDisplay user

CHANGE MANAGEMENT

SAP_CM_CHANGE_MANAGER_COMP 1) Approving or rejecting change requests

SAP_CM_DEVELOPER_COMP 1) Corrections in the development system; Corrections inthe maintenance and development systems

SAP_CM_TESTER_COMP 1) Testing corrections in the test system¸ Testing andvalidating corrections

SAP_CM_OPERATOR_COMP 1) Import corrections into the production system; Task lists

SAP_CM_PRODUCTIONMANAGER_COMP1)

Import corrections into the production system; Approveimports into the production systems

SAP_SOCM_REQUESTER Create change requests

Change RequestManagement -> ScheduleManager; Service Desk,cProjects

SAP_CM_ADMINISTRATOR_COMP 1) Customize and check Change Request Managementfunctions; Administrative and technical maintenance

SAP_MAINT_OPT_ADMIN Full authorization for Maintenance OptimizerMaintenance Optimizer

SAP_MAINT_OPT_DISP Display authorization for Maintenance Optimizer





June, 2007 19

SOLUTION MONITORING

SAP_SDCCN_ALL Service Data Control Center Administration, changesetup

SAP_SDCCN_DIS Service Data Control Center Display only

Service Data ControlCenter

SAP_SDCCN_EXE Maintain Service Data Control Center

SAP_SOLMAN_DIRECTORY_ADMIN Administer Data in Solution Directory

SAP_SOLMAN_DIRECTORY_EDIT Maintain Data in Solution Directory

Solution Directory

SAP_SOLMAN_DIRECTORY_DISPLAY Display Data in Solution Directory

SAP_SV_SOLUTION_MANAGER Full authorization for all functionalities within transactionSOLUTION_MANAGER, display authorization for

Implementation and Distribution and IMG

SAP_SV_SOLUTION_MANAGER_DISP Display authorization for all functionalities withintransaction SOLUTION_MANAGER, display

authorization for Implementation and Distribution

SAP_SETUP_DSWP Full authorization for all sessions in area operationssetup

SAP_SETUP_DSWP_SLRFull authorization for session Service Level Reporting in

area operations setup (according to Bundled)

SAP_SETUP_DSWP_SM Full authorization for session System Monitoring in areaoperations setup (according to BundleID)

SAP_SETUP_DSWP_BPM Full authorization for session Business ProcessMonitoring in area operations setup (according to

BundleID)

SAP_SETUP_DSWP_CSA Full authorization for session Central ServiceAdministration in area operations setup (according to

BundleID)

SAP_OP_DSWP Full authorization for all sessions in area operations

SAP_OP_DSWP_SLR Full authorization for session Service Level Reporting inarea operations (according to BundleID)

SAP_OP_DSWP_SM Full authorization for session System Monitoring in areaoperations setup (according to BundleID)

SAP_OP_DSWP_EWA Full authorization for session EarlyWatch Alert in areaoperations (according to BundleID)

SAP_OP_DSWP_BPM Full authorization for session Business ProcessMonitoring in area operations (according to BundleID)

Operations

SAP_OP_DSWP_CSA Full authorization for session Central ServiceAdministration in area operations (according to

BundleID)

REPORTING

SAP_SOL_REP_ADMIN Authorization for reporting, maintaining systemavailability data, BI Reporting

Solution Reporting

SAP_SOL_REP_DISP Authorization for report execution and display only.

SAP_SM_ALEREMOTEAuthorization for background user in Solution ManagerClient, according to profile S_BI-WX_RFC (see SAPNote 150315)

BI Reporting 3)

SAP_BW_SOLUTION_MANAGER Authorization for transaction RRMX

SERVICE CONNECTION and SOLUTION TRANSFER

Service Connection SAP_SERVICE_CONNECT Authorizations for Service Connection

Solution Transfer SAP_SOLUTION_TRANSFER Authorization to transfer a solution from one SAPSolution Manager system to another SAP SolutionManager system.

DIAGNOSTICS

Root Cause Analyses SAP_SOLMANDIAG_SAPSUPPORT Contains the required authorizations for using the



20 June, 2007

Diagnostics for user SAPSUPPORT, see also SAPNote 828533

SAP_SOLMANDIAG_E2E RFC Calls for Diagnostics

SAP_SMDIAG_WIZARDAuthorization for using the Diagnostics Wizard totransfer data from Solution Manager to Diagnostics

SAP_SMDIAG_TEMPLATEAuthorization to edit templates for Diagnostics

THIRD PARTY INTEGRATION

SAP_QC_BY_HP_ADMIN 5) Full authorization to configure, send and receive datato/from Quality Center; needs to be assignedadditionally with respective role for Implementation andDistribution scenario, e.g. SAP_SOL_PM_COMP

SAP_QC_BY_HP_EXE 5) Authorization to work on the QC tab in SOLAR01/02,needs to be assigned additionally with respective role forImplementation and Distribution scenario, e.g.SAP_SOL_AC_COMP etc.

SAP_QC_BY_HP_DISP 5) Display Authorization; ; needs to be assignedadditionally with respective role for Implementation andDistribution scenario, e.g. SAP_SOL_RO_COMP

SAP Quality Center by HP

SAP_QC_INTERFACE 5) Authorization for background communication user

Service Desk Interface SAP_SUPPDESK_INTERFACE Authorization for bidirectional interface andconfiguration; needs to be assigned additionally withrespective roles for Service Desk scenario, e.g.SAP_SUPPDESK_ADMIN

1) Composite roles with naming convention _COMP consist of a number of single roles, whichyou may also use individually.2) For several use cases it is necessary to assign a SAP Support Portal contact to SAP SolutionManager users who will communicate with SAP Support Portal via RFC-Destination SAP-OSS.The contact you maintain corresponds to the S-user in SAP Support Portal without 'S'. An S-User is a user ID for the SAP Support Portal. You request your user ID for the SAP SupportPortal via www.service.sap.com.

In SAP Solution Manager, you need maintenance authority for authority group 'AISU' for thisactivity (authority object S_TABU_DIS). The role SAP_SUPPDESK_ADMIN has this authority.

In the SAP Support Portal, the S-User needs to have the following authorizations:For scenario Support Desk and EoD:- Create message: ANLEG: Create SAP message- Send message: GOSAP: Send to SAP WAUFN: Reopen SAP message- Confirm message: QUITT: Confirm SAP message- SAP notes search: NOTES: Search for notes- Display/change Secure Area: PWDISP Display Secure Area PWCHGE Change Secure AreaFor scenario Service Connection:- Open Service Connections:


http://www.service.sap.com/


June, 2007 21

SVER Open Service Connection- Setup/migrate a Service Connection: SVER Open Service Connection INSTPROD Maintain System DataFor function SAP HotNews:- SAP notes search: NOTES: Search for notes3) In the BI-Client (system) the following profiles are required:- Administrator (IMG): Profile S_RS_ALL (according role SAP_S_RS_ALL)- Backgrounduser ALEREMOTE: Profile S_BI-WHM_RFC (according roleSAP_BI_ALEREMOTE)4) To maintain actions, you need the additional role SAP_PPF_CONFIGURATOR5) New with Stack 12.

For more information:

SAP Solution Manager Roles SAP Note 834534 (SAP Solution Manager Roles)

Role Maintenance online documentation: Choose Help Application HelpSolution Manager Projects Project PreparationRoles in Solution Manager

Change Request Management Roles Online documentation (in SAP Solution Manager system):Help Application Help SAP Solution ManagerChange Request Management Roles in Change RequestManagement

4.4 Roles and Profiles in the Satellite SystemsYou need to create users in the satellite systems to enable SAP Solution Manager users to access andconfigure these systems and perform test activities. Users are created in a satellite system using the UserMaintenance tool (transaction code SU01) in that system. In each satellite system, you need to assignauthorizations to users for IMG and the Customizing configuration transactions as well as the applicationtransactions to be configured.

For details on all roles concerning Diagnostics, refer to Diagnostics (Advanced Guide) on theSAP Service Marketplace: service.sap.com/installation Installation and Upgrade Guides.For SAP R/3 Releases lower than SAP Web Application Server 6.10, the profiles listed in thetable are available, but not the roles. Therefore, you have to explicitly assign the authorizationprofiles to the relevant users.Users who are required to log on by using trusted RFC destinations must also assign trustedsystem authorizations. In particular, you have to assign the authorization profile S_RFCACL(<SAP NetWeaver AS 7.00) or role SAP_S_RFCACL (as of SAP NetWeaver AS 7.00). For anexplanation of authorization fields of this object see reference to S_RFCACL under heading 4.2.


http://www.service.sap.com/installation


22 June, 2007

The table below provides an overview of the roles and profiles for Satellite systems:

Scenario Role (Release >= 610) Profile (Release<610)

Purpose

CHANGE MANAGEMENT

SAP_CHANGEMAN_DEVELOPER S_TMW_DEVELO Authorizations for developers

SAP_CHANGEMAN_OPERATOR S_TMW_OPERA Authorizations for operators

Change RequestManagement

SAP_CHANGEMAN_ADMIN S_TMW_ADMIN Authorizations for administrators

SOLUTION MANAGER

For Basis WebAs >=610SAP_SDCCN_ALL

For Basis 4*S_SDCCN_ALL

Service Data Control CenterAdministration, change setup

For Basis WebAs >=610SAP_SDCCN_EXE

For Basis 4*S_SDCCN_EXE

Maintain Service Data ControlCenter

Service Data ControlCenter

For Basis WebAs >=610SAP_SDCCN_DIS

For Basis 4*S_SDCCN_DIS

Service Data Control CenterDisplay only

IMPLEMENTATION AND DISTRIBUTION

SAP_BC_CUS_ADMIN Administration of Customizingprojects;

in addition: Authorization objectS_RFC is missing and needs to

be maintained (transactionPFCG).

values:ACTI: 16

RFC_NAME:S_SOLAR_RFC_00RFC_TYPE: FUGR

SAP_BC_CUS_CUSTOMIZER Changing customizing settingssee SAP_BC_CUS_ADMIN

Customizing Distributionand Comparison

S_CUS_CMP See also Online Documentation:SAP Solution Manager ->Projects -> Customizing

Distribution and Comparisonsystem settings

SAP_SOLAR_SATELITE_SCOUT Customizing ScoutCustomizing Scout andSystem Landscape

SAP_SOLAR_SATELITE_SMSY System Landscape

SAP_BC_CAT_TESTER Testing with CATTCATT

SAP_BC_CAT_TESTORGANIZER Testorganization with CATT

eCatt See SAP note 519858

SAP_TWB_TESTER Testing with test workbench

SAP_TWB_COORDINATOR Coordination with testworkbench

Testworkbench

SAP_TWB_ADMINISTRATOR Administration with testworkbench

SAP_BCS_ACTIV Activation BC Sets; see SAPnote 505603

SAP_BCS_CREAT Creating BC Sets

BC Sets

SAP_BCS_ADMIN Administration of BC Sets

DIAGNOSTICS



June, 2007 23

SAP_JAVA_SUPPORT Authorization for Diagnostics. Allusers of Diagnostics have to beassigned this role

SAP_JAVA_NWADMIN_CENTRAL_READONLY All users of Diagnostics have tobe assigned this role

SAP_SLD_GUESTFor read-only access to the SLDapplication, the user must belongto the group having the LcrUserJ2EE server role (e.g. a groupnamed SAP_SLD_GUEST).

SAP_XI_DISPLAY_USEROnly for XI systems

SAP_XI_MONITOROnly for XI systems

Root Cause Analyses

SAP_SATELLITE_E2E_DISPDisplay Diagnostics transactionsST-PI

To enable Single Sign-On, the user for Diagnostics on the monitored satellite system has tohave the same name as the user on the Diagnostics Server. By using the Monitored SystemSetup Wizard of the Diagnostics all roles for J2EE server are assigned automatically.

Regarding Change Request Management, the following table shows which transport methods are assignedto the background users in the target client and in client 000. In addition, the table indicates which roles arerequired for real users when using trusted RFC destinations:

(*) If you want developers within the Change Request Management scenario to start imports intoa test system automatically, you must add the profile S_TMW_IMPORT to the user TMSADM inclient 000 of the test system. You have to assign it the authorizations S_CTS_IMPALL andS_CTS_IMPSGL which are contained in S_CTS_ADMI.Do not use this method in production systems or in any other security-critical systems.The system where you want to start the import automatically must share the same transportdirectory as its preceding system.


24 June, 2007

For more information:

Role Maintenance Online documentation (in the SAP Solution Managersystem): Choose Help Application Help SolutionManager Projects Project Preparation Roles inSolution Manager

Change Request Management Roles Online documentation (in SAP Solution Manager system):Help Application Help SAP Solution ManagerChange Request Management Roles in Change RequestManagement

Authorizations for Customizing Online documentation for IMG (transaction SPRO) ->chapter Create Solution Manager Configuration User.

Authorizations for Customizing Distribution Online documentation (in the SAP Solution Manager)(transaction SCDT_SETUP) -> Help Application HelpCustomizing Distribution Customizing DistributionSystem Settings


June, 2007 25

4.5 SLD (System Landscape Directory) UserIf you have installed SAP Solution Manager and you have attached the SAP System Landscape Directory,you need to generate roles for set SLD users for the communication of ABAP and JAVA:

SLD User Role PurposeSLDAPIUSER No role required To send data from SAP Solution Manager to

SLD

SAPJSF (Service User) SAP_BC_JSF_COMMUNICATION_RO To read data from SLD

SAP_BC_AI_LANDSCAPE_DB_RFC Context: Application integrationinfrastructureThis role enables write access to thedatabase tables of the SAP SystemLandscape Directory (SLD). The role has tobe assigned to the user who makes theRFC calls from the SLD.

J2EE_ADMIN (Service User)

SAP_J2EE_ADMINRole that is assigned to the users that are tohave administrator rights in a connectedSAP J2EE Engine. Used to attach a localUME to the central ABAP usermanagement.

J2EE_GUEST (Service User) SAP_J2EE_GUESTRole that is assigned to the users that are tohave guest authorizations in a connectedSAP J2EE Engine.

4.6 Automatically Generated Profiles/Roles for Set BackgroundUsersWhen RFC connections are generated within transaction SMSY the system automatically createsbackground users for each kind of RFC connection in the Satellite system and assigns the relevant profiles.

If you want to use an already existing user from your Satellite system as your background useryou need to enter this user in the according popup when generating the RFC connections intransaction SMSY in the SAP Solution Manager in order for both users to be able tocommunicate. In this case, if the basis release of your Satellite system is (see table):

lower than WEB Application Server 610 you need to assign the according profiles to thisuser

higher than WEB Application Server 610 you need to assign the according roles to thisuser (copy and adjust roles).

User Role (Release >= 6.10) in Satelliesystem

Profile (< 6.10) inSatellite system

Purpose

SAP_S_CUS_CMP S_CUS_CMP Data read access

SAP_S_CMSREG S_CMSREG Central system repository data

SAP_S_BDLSM_READ S_BDLSM_READ SDCCN data

SAP_SATELLITE_E2E S_AI_SMD_E2E End-to-End Diagnose (SolutionManager Diagnostics)

SOLMAN<SystemID of SAPSolution Manager><CLNT>

SAP_SM_S_USER_GRP S_USER_GRP User Group Display of all usersfor Licence AdministrationWorkbench (LAW) and BusinessPartner


26 June, 2007



SAP_S_BDLSM_READ S_BDLSM_READ Read SDCCN data

SAP_S_TMW_CREATE S_TMW_CREATE Create task in developmentsystem

SOLTMW<SystemID ofSAP SolutionManager><CLNT>

SAP_S_TMW_IMPORT S_TMW_IMPORT Import task into testsystem



SAP_SV_FDB_NOTIF_BC_ADMIN Service Desk Messages

SAP_SUPPDESK_CREATE Needs to be added manually

SOLMAN<SystemID ofSatellitesystem><_Version>

SAP_S_BDLSM_READ S_BDLSM_READ SDCCN data

SMD agent communicationuser

SAP_IS_MONITORING S_IS_MONITOR For SMD agent communicationuser to read ABAP Snapshotdata via RFC. The user iscreated via setup of themanaged system in SMD


June, 2007 27

5. Additional InformationFor information about… Go to…

SAP Solution Manager functionality service.sap.com/solutionmanager

Sizing service.sap.com/solutionmanager -> Installation Guides -> Release 4.0.

Customizing tools service.sap.com/customizing

Support Area service.sap.com/solutionmanager SAP Solution Manager Functions in DetailSupport Area

Support Package Stacks service.sap.com/patches Downloads SAP Software Distribution Center SAPSupport Packages and Patches Entry by Application Group SAP Technology

Components SAP Solution Manager

service.sap.com/patches Downloads SAP Software Distribution Center SAPSupport Packages and Patches Entry by Application Group Plug-Ins SAP

Solution Tools Plug-In

Installation service.sap.com/installations Downloads SAP Software Distribution CenterSAP Installations and Upgrades Entry by Application Group SAP TechnologyComponents SAP Solution Managerservice.sap.com/installations Downloads SAP Software Distribution CenterSAP Installations and Upgrades Entry by Application Group Plug-Ins SAP

Solution Tools Plug-In

SAP Active Global Support and SupportServices

service.sap.com/support

Sending feedback to SAP service.sap.com/messageCreate a message for component SV-SMG.

E-Learning SAP Online Knowledge Products for Solution Implementation and Management:service.sap.com/rkt-solman

SAP offers a free, limited license for the SAP Tutor and access to Best Practicedocuments for end user training.

To find out more:13. Call transaction SOLUTION_MANAGER.14. Choose Operations Change Management Upgrade Best Practice.15. Choose Goto Request SAP Tutor.

The following web page is opened: SAP Tutor for SAP Solution Managercustomers

SAP Notes service.sap.com/notes

Technical infrastructure(for example, hardware sizing, platforms,

network security)

service.sap.com/ti

System Landscape Directory (SLD) service.sap.com/sld Media Library Post-Installation Guide – System LandscapeDirectory

Maintenance Optimizer service.sap.com/mopz

SEP Paket service.sap.com/sep

Table 10: Information Resources Online

http://www.service.sap.com/solutionmanager


http://service.sap.com/customizing


http://www.service.sap.com/patches

http://www.service.com/patches

http://www.service.sap.com/installations

http://www.service.sap.com/installations

http://www.service.sap.com/support

http://www.service.sap.com/message

http://www.service.sap.com/rkt-solman

http://www.service.sap.com/notes

http://www.service.sap.com/ti

http://www.service.sap.com/sld

http://www.service.sap.com/mopz

http://www.service.sap.com/sep


28 June, 2007

6. Other Documentation for SAP Solution ManagerBelow is an overview of the documents relevant for the SAP Solution Manager.These documents are updated regularly. Ensure that you are working with the most recent versions.

Document Go to...Master Guide, Installation Guides, Configuration

Guide, Migration Guide, Solution ManagerDiagnostics Guides

service.sap.com/installation Installation and Upgrade Guides

Implementation Guide (IMG) Note: IMG is available only in the SAP system, not on the SAP Service Marketplace

SAP Library The SAP Help Portal (help.sap.com) offers all the releases of a mySAP.comcomponent.

help.sap.com Documentation SAP NetWeaver Solution ManagerSolution Manager 4.x

Change Request Management:Configuration Guide: cProjects 3.10

service.sap.com/instguides mySAP Business Suite Solutions mySAP PLMUsing cProject Suite 4.00 Configuration Guide Collaboration Projects (cProjects)

Online Documentation: SAP TransportManagement System

Transaction STMS Help Application Help

different variants for installing the SAPdocumentation

service.sap.com/instguides Solution Life-Cycle Management C InstallationInstallation and Upgrade Guides SAP Library

how to use the SAP Library tool (transactionSR13)

Installation Guide for the SAP Library

Table 11: Overview of Documentation for SAP Solution Manager

All quick links are listed on the SAP Service Marketplace: service.sap.com/quicklinks

http://help.sap.com/


June, 2007 29

7. Training CoursesSAP’s training course offerings cover the installation and basic functionality of the SAP Solution Manager.For details and booking, see service.sap.com/solutionmanager Training.


30 June, 2007

8. AppendixSAP NotesSAP Notes:

relevant to the SAP Solution Manager can be found under component SV-SMG. contain the most up-to-date information and corrections to the installation documentation.

All ScenariosNumber Title

948871 Solution Manager: Cross-Scenario Related SAP Notes

Service DeskNumber Title

949292 Solution Manager: Service Desk Related SAP Notes

Implementation and DistributionNumber Title

949220 Solution Manager: Implementation Scenario Related SAP Notes

Change Request ManagementNumber Title

907768 General note for Change Request Management 4.00

1024932 Maintenance Optimizer

Solution MonitoringNumber Title

949293 Solution Manager: Solution Monitoring Related SAP Notes

420213 Composite SAP Note: Central monitoring of mySAP.com

SAP Support ServicesNumber Title

91488 SAP Support Services: Central preparation note

Root Cause Analyses: Solution Manager DiagnosticsNumber Title

829218 Composite SAP note about Solution Manager











June, 2007 31

976054 Availability of EWA for Non ABAP components

SAP Solution Support Enablement PackageNumber Title

1014987 Information about Custom Development Optimization

1014986 Installation of Custom Development Optimization

Knowledge WarehouseNumber Title

368861 KW and security levels under MS Office

368963 Use signed macros in Knowledge Warehouse

Make sure that you have the most recent version of each SAP Note.

RFC Destinations SAP Solution Manager

RFCDestinationName

Target HostName

SystemNumber

LogonClient

Logon User(Password)

Use How Created

SAPNet R/3 FrontendSAPOSS /H/SAPROUTER

/S/<XX>/sapserv<X>/H/oss001

01 001 OSS_RFC(CPIC)

Notes Assistant Maintain technicalsettings in

transaction “OSS1”

SAP-OSS /H/SAPROUTER/S/<XX>/sapserv

<X>/H/oss001

01 001 S-User(Customer-

specific)

Exchange problem messageswith SAP

TransactionSOLUTION_MANAGER; Menu path:

Edit->GlobalSettings

SAP-OSS-LIST-O01

/H/SAPROUTER/S/<XX>/sapserv

<X>/H/oss001

01 001 S-User(Customer-

specific)

Retrieve information aboutwhich messages have been

changed at SAP

Transaction SM59

SDCC_OSS (will begenerated) See

SAP Note763561

Used by the Service DataControl Center to

communicate with the SAP NetR/3 Frontend system

A copy of theSAPOSS

destination toSDDC_OSS; a

new user is used.

Satellite SystemSM_<SID>CLNT<c

lient>_LOGINSatellite System Customer-

specificCustomer-

specificempty Execute Transactions

Scenarios: Solution Monitoringand Implementation and

Distribution

Transaction SMSY

SM_<SID>CLNT<client>_READ

Satellite System SatelliteSystem-specific

SatelliteSystemspecific

Default user:SOLMAN<SID><Client> (will be

generated)

for read access Scenarios:Solution Monitoring and

Implementation andDistribution

Transaction SMSY

SM_<SID>CLNT<client>_TRUSTED


SatelliteSystem-specific

empty Log on through a trustedconnection

Scenarios: Solution Monitoringand Implementation and

Transaction SMSY







32 June, 2007

RFCDestinationName

Target HostName

SystemNumber

LogonClient

Logon User(Password)

Use How Created

Distribution

SM_<SID>CLNT<client>_TMW


SatelliteSystemspecific

Default user:SOLTMW<SID><Client> (will begenerated)

for creating, releasingtransport requests

Transaction SMSY

Local System (Solution Manager)BPM_LOCAL_<clie

nt>empty empty Client used

for BusinessProcess

Monitoring

CSMREG(Customer-

specific)

Profile:S_CSMREG (as

of SP03 addauthorization

object:S_RZL_ADM) (=

Role:SAP_S_CSMRE

G) + roles:SAP_SUPPDESK_CREATE andSAP_IDOC_EVE

RYONE

Business Process Monitoring During BusinessProcess

Monitoring Setup

Used TCP/IP Default Ports for Solution Manager Diagnostics

System Ports used on Solution ManagerDiagnostics Server

Ports used on each monitoredSatellite System

Open inSAProut tab

ABAP Gateway 33nn (nn: instance no.), e.g. 3301

HTTP Port ofJ2EE Engine

5nn00 (nn: instance no. of SMD), e.g. 50100 5nn00 (nn: instance no. of managedsystem), e.g. 50200

X

P4 5nn04 nn: instance no. of SMD), e.g. 50104

Database depends on DBMS, e.g. 1433 on MS SQLServer

Introscope 6001 (Listener port) 6001

LoadRunner 5001 (Load Generator)

J2EEstandalonelogviewer

26000 For details, refer to AdvancedDiagnostics Setup Guide

Periodic JobsThe configuration of jobs delivered by SAP can be displayed in table DSWPJOB. You should not change thistable. See also SAP Note: 894279.


63868572 configuration guide sap solution manager as of sp12

Documents