SAP Guides

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Landscape Verification 1.0 for SAP Solution Manager

July 2010

Typog graphic Conv c vention ns

Type Style Re epresents Words or char W racters that a appear on the screen. These inclu n . ude fie names, screen titles, eld pu ushbuttons a well as me as enu na ames, paths and options. . Cr ross-referenc to other ces do ocumentation n Em mphasized w words or phra ases in bo text, titles of graphics and ody s tables Na ames of elem ments in the sy ystem. These include rep e port na ames, progra names, am tra ansaction codes, table na ames, an individual key words o a nd of pr rogramming language, when su urrounded by body text, f y for ex xample, SELECT and IN NCLUDE. Sc creen output This includes file t. an directory n nd names and their pa aths, messag ges, names o of va ariables and parameters, so ource code a well as nam of as mes ins stallation, up pgrade and da atabase tools s. Ex xact user ent These ar try. re wo ords or chara acters that yo ou en in the sy nter ystem exactly as y they appear in the n do ocumentation n. Va ariable user entry. Pointe ed br rackets indica that you ate re eplace these words and ch haracters with appropriate e en ntries. Ke on the ke eys eyboard, for ex xample, func ction keys (su as uch F2 or the ENT 2) TER key.

Icons
Icon n M Meaning C Caution Example Note R Recommenda ation Syntax

Example T Text

Example te ext

EXAMPLE TEXT

Example te ext

Example t text

<Example text>

EXAMPLE TEXT

Landscape Verification 1.0 for SAP Solution Manager Table of Contents 1. 2. 3. 3.1. 3.2. 3.3. 3.4. 4. 5. 5.1. 5.2. 5.3. 5.4. 6. 6.1. STRUCTURE OF THIS DOCUMENT INTRODUCTION TO LANDSCAPE VERIFICATION CONCEPT OF LANDSCAPE VERIFICATION Motivation Architecture Parts of the Landscape Description that Are Checked Problems Determined Using Landscape Verification INSTALLING LANDSCAPE VERIFICATION OPERATING LANDSCAPE VERIFICATION Initializing and Configuring Landscape Verification Starting Landscape Verification Displaying the System Landscape Displaying the Errors Detected in the System Landscape APPENDIX Message of the landscape verification
6.1.1. Technical system not registered properly in SMSY 6.1.2. Product system has no technical system assigned 6.1.3. Technical system is not assigned to a product system 6.1.4. Technical system is a 'SIDECAR', although more than one product system was assigned 6.1.5. Technical system is a 'HUB', although only one product system was assigned 6.1.6. Product system has no active standalone product version 6.1.7. Authorization error when checking RFC connection 6.1.8. Internal error when checking RFC connection 6.1.9. RFC connection is not defined 6.1.10. RFC connection is defined with a wrong connection type 6.1.11. System failure when calling RFC connection 6.1.12. Communication failure when calling RFC connection 6.1.13. Automatic data transfer to SMSY is not configured via SLD 6.1.14. Internal error when checking job schedule for periodic landscape fetch 6.1.15. No periodic landscape fetch job planned 6.1.16. No OSS connection defined in the system 6.1.17. Some software components not covered by configured product instances 6.1.18. Product system contains technically inappropriate product instances

5 6 7 7 7 8 9 10 11 11 12 13 14 16 16
16 17 17 18 19 20 20 21 21 22 23 24 25 25 26 26 27 28

July 2010

Landscape Verification 1.0 for SAP Solution Manager

6.1.19. Java Stack of Technical system &1 (dual stack) is not available in SMSY 6.1.20. Technical system (system type ABAP) is not available in SMSY 6.1.21. Product system configured with non-existent product SAP ECC 29 29 30

6.2.

Glossary

30

July 2010

Landscape Verification 1.0 for SAP Solution Manager

1.

Structure of This Document

This document describes the purpose and operation of landscape verification 1.0 for SAP Solution Manager, an Add-On for improving the quality of your system landscape description in SAP Solution Manager. The individual sections of this document have the following contents: Section 2 contains a short introduction to landscape verification, its purpose, and how it works. Section 3 contains an introduction to the underlying concepts of landscape verification; the ways in which an application of this type is useful, a brief outline of the architecture, and a summary of the errors in your landscape description that landscape verification can determine. Section 4 contains information about installing landscape verification. Section 5 contains information about operating and configuring landscape verification and a description of the user interface. Section 6 contains an appendix with the long texts of the messages that can be displayed about your system landscape description and a short glossary of the terms used.

July 2010

Landscape Verification 1.0 for SAP Solution Manager

2.

Introduction to Landscape Verification

The error-free and complete mapping of your system landscape in SAP Solution Manager (transaction SMSY) is of critical importance for your maintenance processes. This is because, as of SAP Business Suite Enhancement Package 4, the Maintenance Optimizer (http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/46/418970cdb45fabe10000000 a1553f7/frameset.htm) is a mandatory prerequisite for installation; correct configuration of your system landscape is, in turn, is an important prerequisite for the correct execution of the Maintenance Optimizer. Experience shows, however, that the landscape data that is available to you in transaction SMSY is not always complete and error-free, particularly if data has been entered manually. This is where landscape verification 1.0 for SAP Solution Manager is useful. It analyzes the description of your system landscape and, with the help of information from the SAP support system, searches for inconsistencies. Based on the results of these checks, a clear user interface shows an overview of all problems, gaps, and inconsistencies in the description of your system landscape. Each of these errors is described in detail; the descriptions also contain procedures for solving the problem. In this way, landscape verification supports you in lowering your TCO by increasing the quality of your landscape description and therefore helping to ensure a smooth installation of the SAP Business Suite Enhancement Packages. The most important steps in the context of an installation process of this type are shown below:
Maintainance of System Landscape Data Update SAP Solution Manager 7.0 to Latest SP Level

Register Systems in SLD and Transfer Data to Solution Manager Run the Landscape Verification 1.0 (optional) Maintain System Landscape Data in SMSY

Selection and Download of Files

Create Maintenance Transaction in the Maintenance Optimizer: Select the Software Packages Calculation of Stack Configuration File (.xml) Download EHP, SPS, Stack Configuration File

Installation

Provide Files to Enhancement Package Installer Install Enhancement Package on SAP System

July 2010

Landscape Verification 1.0 for SAP Solution Manager

3.

Concept of Landscape Verification

3.1. Motivation
Many SAP customers operate a large number of SAP applications, which usually consist of many different systems. Many of these applications are therefore distributed across different technical systems and exist as development, test, and production systems. You therefore need to take into account the following points during maintenance or upgrades of applications of this type: To perform an upgrade of all elements of these applications, you need to handle the corresponding groups of technical systems as a unit. When upgrading technical systems that are used in more than one application, you need to consider all of the roles of these systems. To be able to do any of these things, it is vital to have a correct and complete landscape description, which forms the basis for the maintenance of your applications. This landscape description is the system landscape of SAP Solution Manager (transaction SMSY). However, parts of this landscape description are created manually, and can therefore contain errors, which can, in turn, lead to errors when maintaining your applications. To determine these errors and to provide support in solving them, landscape verification for SAP Solution Manager is available to you. Landscape verification analyzes your landscape description in your SAP Solution Manager, finds errors, and displays information about how to solve them. This means that you can perform your maintenance processes more quickly with fewer errors and lower costs.

3.2. Architecture
In your system landscape, your managed systems report their data to the System Landscape Directory (SLD), which, in turn, forwards this data to the system landscape of SAP Solution Manager (transaction SMSY). Landscape verification reads this data and compares it to information in the SAP product catalog from the central SAP support system, and detects errors and inconsistencies through this comparison of the locally-available information and the information available centrally at SAP.

July 2010

Lan ndscape Ve erification 1 for SAP Solution Manager 1.0 P M

Lan ndscape V Verification Archite n ecture and Data Flow w

SAP S Solution Mana ager

Sys stem Landscape of e SAP Solution Manger P SMSY

landscape verification e
Web D Dynpro Layer

SAP Sup pport System

Processing Ba ackend (AddOn)

Proces ssing Backend SAP Prod duct Catalog

System S Data

Softwa are Data a

Product Systems

Technical Systems

System Landscape Dir m rectory

De efinitions from the SA Product AP Catalog

Computer Systems

3.3 Parts of the L 3. Landscap Descr pe ription th Are C hat Checked

Lan ndscape veri ification che ecks the par of your la rt andscape de escription in SAP Solut n tion Man nager that is required fo upgrade and mainten s for nance proce esses. Spe ecifically, on the follo nly owing eleme of the landscape a relevant for the chec ents l are cks: Product system t Technic system cal Product instance t For F a defini ition of thes terms, ref to the Glossary [pag 30]. se fer ge

Relevant Parts of th Landsca Descri t he ape iption

Pr roduct Instanc ce 1..* Installe on ed 1

Tec chnical System m 1..* Landscape Patter rn Hub (H or Sidecar) 1..*

Product System S

Produ Version uct

July 2010 y

Landscape Verification 1.0 for SAP Solution Manager The concept of a landscape pattern is also supported (http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/2b/5fad0d1f8549609efddabca9 c7f65d/frameset.htm), that is, a description of the extent to which a technical system is used in only one or in multiple product systems. The following landscape patterns exist: Hub Sidecar Space

3.4. Problems Determined Using Landscape Verification

Landscape verification determines problems in the following areas of your landscape description: Infrastructure (technical prerequisites), such as the connection to the SAP support system or the connection of your SAP Solution Manager to the System Landscape Directory (SLD) Technical systems, such as incorrect assignment of product instances on the basis of the installed software component versions Product systems, such as incorrect or missing assignment to a product version These problems could, for example, have been caused by the following errors: Incomplete or incorrect configuration for data suppliers that report system data to the SLD Configuration of the transfer of data from the SLD to SAP Solution Manager (Landscape Fetch) is incomplete, or the transfer is not working correctly The assignment of product instances or product systems in your description of the system landscape is incorrect, for example, due to manual entries Landscape patterns have been incorrectly set

July 2010

Landscape Verification 1.0 for SAP Solution Manager

4.

Installing Landscape Verification

Landscape verification 1.0 is an Add-On for SAP Solution Manager 7.0 EhP1 as of Support Package 18. To install landscape verification, first download the relevant archive from the SAP Service Marketplace. 1. The archive is available in the SAP Software Distribution Center of the SAP Service Marketplace (http://service.sap.com/swdc). Log on with your SAP Service Marketplace ID. 2. In the navigation bar, choose Download Installation and Upgrade Installation and Upgrade - Entry by Application Group SAP Technical Components LV FOR SOLUTION MANAGER LV 1.0 FOR SAP SOLUTION MANAGER Installation, and download the archive. 3. The rest of the procedure is described in the documentation for the Add-On Installation Tool (transaction SAINT). The information that is most important for you is available by following the links below: Loading Installation Packages (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/78/d18d38e9cf9e67e1000 0009b38f842/frameset.htm) Installing and Upgrading Add-Ons (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/18/e08d38dfc44765e1000 0009b38f842/frameset.htm)

July 2010

10

Lan ndscape Ve erification 1 for SAP Solution Manager 1.0 P M

5.

Oper rating L Landsca Verification ape n

To T be able t use lands to scape verification, your user must have the ro r ole SAP_SMSY_ _LV_ALL. Note N that th role is ba his ased on the equivalent standard ro for SMSY ole Y (SAP_SMSY Y_ALL), and you must therefore ha implem d t ave mented this role in your system In additio to the ref y m. on ferenced SM MSY role, th role for he landscape v l verification contains on the autho nly orizations to execute o transactions LVSM and LVSM_LOA . t s AD

5.1 Initial 1. lizing and Config guring La andscape Verific cation

To m make all of the functions of landsc f cape verific cation availa to you, you first ne to able eed run a job that c checks the entire system landscape that is avai m e ilable to you through th u he syst landsca of SAP Solution Manager (tran tem ape nsaction SM ) for pos MSY ssible errors gaps, s, or in nconsistenc cies. The job compares, among oth things, lo b , her ocally-avail lable produc ct instances with the product instances t are tech t that hnically possible based on the insta alled soft tware component versio This in ons. nformation is determine from the central SAP i ed P supp system port m. Note N that th job can h he have a runtim of sever hours. me ral Star rting the C Check Job To s start this job proceed a follows: b, as 1. Start transa action LVSM M_LOAD. 2. From the m menu, choose Program Execute in Backgro e ound. p fication, if y activate the indicator for the se you ending of an en 3. In the group box Notif mail, you a informed as soon as the job is complete. are d s c Sett ting the Co onfiguration Paramete n ers You can also se a number of configu u et r uration param meters in th transactio You can make his on. n the following s settings: In the g group box P Product Insta ance detect tion: cleanup of results, you can up determi the circu ine umstances in which che results a overwri eck are itten if a new check w is perfo ormed. By d default, this function is set to the in ndicator Act tivate Clean nup; if this ind dicator is act tive, you ca use the in an nput field Delete result older than to define t age as of which resu are to be overwritt by the re the ults b ten esults of a new n check. You can ensure tha a check is performed for the technical syste in the system n at s d ems s landsca of SAP Solution Manager for which there are no chec results. This is ape w e ck T particul larly import if you h tant have added new technic systems to your sys cal stem landsca ape.

July 2010 y

11

Lan ndscape Ve erification 1 for SAP Solution Manager 1.0 P M This fun nction is als activated by default, using the i so d , indicator Ex xecute detec ction if no detection result is availabl for a technical system in the gro box Pro t le m oup oduct Instance detection: update of results. : You Y should normally l d leave this in ndicator acti ivated. It is only meani ingful to deactivate t indicator and execu the job a d the ute again if you want to del all lete check results that have exceeded the retention period spe c e t n ecified abov ve. You can ensure tha you are always infor n at rmed when a check of y your system m landsca is compl ape lete. An e-m of this type is sent using SAPconnect (more mail t informa ation: SAPc connect (BC C-SRV-COM M), http://he elp.sap.com m/saphelp_n nw70ehp1/h helpdata/en/2 2b/d925bf4 4b8a11d189 94c0000 e8323c4 4f/frameset t.htm). This fun nction is als activated by default, using the i so d , indicator Se email end notifica ation after P Product Inst tance detect tion is finish in the N hed Notification group box.

5.2 Starti 2. ing Land dscape V Verificatio on

To s start landsca verifica ape ation, enter t transact the tion code LV . The ap VSM pplication is s open in a sep ned parate window. If the jo has not yet been started when y start ob y you tran nsaction LVS , the syste displays a correspo SM em s onding mess sage. The erefore start this job in good time b before your intended first use of la andscape veri ification. In addition to calling tran n o nsaction LV and givi an appro VSM ing opriate resp ponse to the message me entioned ab bove, you ca also start this job by calling the configurati of an t y ion land dscape verif fication (tra ansaction LV VSM_LOAD) (more infor rmation: Ini itializing an nd Con nfiguring La andscape Verification [ [page 11]), a choosing the comma Program and m Exe ecute in Bac ckground fro the men om nu. If I the result of this check are inco ts omplete or o obsolete, th system di he isplays a correspondi message this mess c ing e; sage also co ontains the e expected rem maining runtime of t job. r the On the main sc creen of land dscape verif fication, you can switch between t display types two y by c choosing the relevant ta page: e ab System Landscape (more infor rmation: Di isplaying th System L he Landscape [p page 13]) This dis splay shows an overvie of your system land s ew s dscape; if er rrors have been determi ined, these a displaye for each landscape e are ed element (pro oduct versio ons, product systems, and technica systems). t al Errors (more infor rmation: Dis splaying the Errors Det e tected in the System e Landsca [page 14]) ape This dis splay shows all errors d s detected in your system landscape in a flat lis y m e st. To T display t detected errors, cho the d oose the Ver button. rify July 2010 y 12

Lan ndscape Ve erification 1 for SAP Solution Manager 1.0 P M In b both views, you can see the errors and problem that land e ms dscape verif fication has dete ected in the description of your sys n stem landsc cape. To dis splay more d detailed info ormation for one of these messages, choose th relevant m r he message. A separate window appears, contai ining a detai long text that cont iled tains the cau and also informatio about use o on how to correct the problem w m. The problems a not corrected within this applic e are n cation, at le in this v east version 1.0, but rath where th cause of a error is, t is, for example, in transaction SMSY or in the her he an that e n conn nection of t managed system to the SLD. the d If I you have corrected t cause of a detected problem, yo can repe the e the f ou eat check by starting the a c application again. The s a simplest wa to do this is by ay choosing th Refresh b c he button in you browser. ur

5.3 Displa 3. aying the System Landsc e m cape

In th display t his type, the de etected error and incon rs nsistencies a displaye grouped by the are ed elem ments of you system la ur andscape product ver rsions, prod systems and techn duct s, nical syst tems (more information Glossary [page 30]). n: . In the n navigation a on the l area left, there is a two-level hierarchy of product version and produ systems. The nodes All Systems (all techni systems in ns uct . s ical s your sy ystem landsc cape) and U Unassigned Technical S T Systems (tec chnical syste that ems are not assigned to any produc system) are also disp o ct a played. A status is displaye for each of these ent s ed tries. If the status is yellow or red, this , means t the land that dscape verif fication che detected errors or w eck d warnings for the r selected product ve d ersion or co orresponding product sy g ystem. A red o yellow sta is inher or atus rited upward in the hier d rarchy; if th check sta of he atus an object is unknow (for exa wn ample, if not all checks have yet be perform t een med), the corresponding obje is indica with a gray status. ect ated g The det area on the right co tail onsists of tw subareas. The upper subarea contains a wo . table with the techn nical system that are assigned to the product version or product ms a t system selected in the navigat tion area. Th lower sub he barea displa product ays t instance and any d es detected me essages (errors and war rnings) for t technica the al system selected fro the table in the upper subarea. om e

July 2010 y

13

Landscape Verification 1.0 for SAP Solution Manager

Landscape Verification Overview of the User Interface

Technical system assigned to the selected product system or version

Navigation Area

Details Area

Product system grouped by Product version Errors specific to the selected technical system Product instances installed on the selected technical system

5.4. Displaying the Errors Detected in the System Landscape

You can also display the messages determined in your system landscape in an overview list. The following information is displayed for each message: Status of the message: Red (error) or yellow (warning) Object and category to which the message relates (for example, Technical System) Short text of the message; if you want to display the long text of the message, which also contains a procedure for correcting the error, choose the short text

July 2010

14

Landscape Verification 1.0 for SAP Solution Manager

Landscape Verification Overview of Detected Errors

Severity of the message: red (error) or yellow (warning)

Short text of the message; click on the message to display the long text

Object and category (e.g. technical system) to which the message refers

July 2010

15

Lan ndscape Ve erification 1 for SAP Solution Manager 1.0 P M

6.

Appe endix

6.1 Message of th landsc 1. he cape ver rification n

The following appendix co e ontains a co omplete list of the mess sages for lan ndscape veri ification, wh are displayed duri the chec of your sy hich ing ck ystem lands scape if corr responding errors or pr roblems are detected:

6.1.1. Tech hnical sys stem not registere properly in SMS ed SY

Dia agnosis The Landscape verification tool check among other things the compl e e ks, o s, leteness of the data t that exists in th Solution Manager (tr t he ransaction SMSY) for technical sy S ystems in yo our syst landsca tem ape. In th case, the technical d for a te his e data echnical sys stem is incomplete - req quired data is missing. A list below show the fields for which there is no data. Perha you ente ws s aps ered the data for the tec a chnical syste manually and incom em mpletely. System Response Sinc the system landscap forms the basis for working with the SAP S ce pe e w h Solution Ma anager, with hout comple data, ma importa functions are not av ete any ant s vailable to y for this system, you s or a only ava are ailable on a r restricted ba asis. Pro ocedure Che the relev data fo this techn eck vant or nical system To do this follow the procedure below: m. s, e 1. Start transa action SMSY Y. 2. Choose the affected technical syst from th list of lan e tem he ndscape com mponents. If it has the system type ABAP expand th product s s m P, he system with the same name in h n the list, and, from t list of pr the roduct insta ances, choos the produ instance with se uct e this nam me. If it has another sy s ystem type, e expand the list of techn nical system and choo the ms, ose appropr riate technic system f cal from the list t. he Data tab pa check th entries, a make th necessary age, he and he y 3. Switch to th Header D changes by adding the missing en y ntries. This T error p primarily oc ccurs if you manually e entered the d for a te data echnical system in tr ransaction S SMSY. We therefore re ecommend t that, as far as a possible, yo let the da be determ p ou ata mined by th registratio of the technical he on systems wit the Syste Landscap Director (SLD). In this case, the th em pe ry n t system data is automat a tically transferred to the Solution M Manager sy ystem landscape b a job that runs at reg l by t gular interva als. More inform M mation abou registerin ABAP an Java syst ut ng nd tems: Configuring Systems t Connect to SLD g to t (http://help.sap.com/sa aphelp_nw7 70ehp1/help pdata/en/48/ /b6812896655295e 10000000a4 42189b/fram meset.htm). . July 2010 y 16

Landscape Verification 1.0 for SAP Solution Manager

6.1.2. Product system has no technical system assigned

Diagnosis A product system is not assigned a technical system in the system landscape of the Solution Manager (transaction SMSY). System Response Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your product systems are incorrectly assigned, many important functions are not available to you, or are only available on a restricted basis. Procedure Assign one or more technical systems to your product system. More information: Create Technical Systems and Assign them to Product Systems (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/b6812896655295e10000000a421 89b/frameset.htm). This documentation consists of two sections: Creating a technical system Assigning the technical system to a product system In this case, only the section about assigning the technical system to a product system is relevant, since data collectors are used to automatically collected the information about your technical systems in the assigned System Landscape Directory (SLD).

6.1.3. Technical system is not assigned to a product system

Diagnosis A technical system is not assigned to a product system in the system landscape of the Solution Manager (transaction SMSY). System Response Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your technical systems are incorrectly assigned, many important functions are not available to you, or are only available on a restricted basis. Procedure Assign your technical system to a product system. If this desired product system does not yet exist, create it. For information about creating product systems, refer to Create Product Systems (http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/9c/efa9068cce4149a40 d7991ad2113f3/frameset.htm). Information about assigning a technical system to a product system is also available in the SAP Solution Manager documentation. For this information, refer to Create Technical Systems and Assign them to Product Systems (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/b6812896655295e100000 00a42189b/frameset.htm). This documentation consists of two sections: Creating a technical system July 2010 17

Landscape Verification 1.0 for SAP Solution Manager Assigning the technical system to a product system In this case, only the section about assigning the technical system to a product system is relevant, since the information about your technical systems is automatically collected in the assigned System Landscape Directory (SLD) using data collectors.

6.1.4. Technical system is a 'SIDECAR', although more than one product system was assigned
Diagnosis A landscape pattern characterizes the relationship between a technical system and one or more product systems. If you classify technical systems using a landscape pattern, you determine the procedure for this technical system for maintenance processes that you start in the associated product system: Sidecar Technical systems that you have assigned the landscape pattern Sidecar are used by exactly one product system with an active product version. During upgrades, the Maintenance Optimizer handles the system as a standalone system, and all possible patches or upgrades are installed for both the application and for the underlying SAP NetWeaver.

Hub Technical systems that you have assigned to the landscape pattern Hub are used by multiple product systems. During upgrades, the Maintenance Optimizer handles the system as a shared system, and only application updates are installed, while the underlying SAP NetWeaver is upgraded to the minimal required version. More information about landscape patterns: Landscape Pattern (http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/2b/5fad0d1f8549609efddabca9 c7f65d/frameset.htm). In this case, the landscape pattern Sidecar is assigned to the technical system, although it is assigned to more than one product system. System Response An incorrect landscape pattern assignment can lead to problems during upgrades of product systems. Procedure Change the assignment of the landscape pattern for the specified technical system in the system landscape of the Solution Manager (transaction SMSY). To do this, proceed as follows: 1. Choose the technical system from the list of landscape components. If it has the system type ABAP, expand the product system with the same name in the list, and, from the list of product instances, choose the product instance with this name.

July 2010

18

Landscape Verification 1.0 for SAP Solution Manager If it has another system type, expand the list of technical systems, and choose the appropriate technical system from the list. 2. Switch to change mode. 3. Switch to the Other Attributes tab page and, for the Landscape Pattern attribute, assign the value HUB. 4. Save your changes.

6.1.5. Technical system is a 'HUB', although only one product system was assigned
Diagnosis A landscape pattern characterizes the relationship between a technical system and one or more product systems. If you classify technical systems using a landscape pattern, you determine the procedure for this technical system for maintenance processes that you start in the associated product system: Sidecar Technical systems that you have assigned the landscape pattern Sidecar are used by exactly one product system with an active product version. During upgrades, the Maintenance Optimizer handles the system as a standalone system, and all possible patches or upgrades are installed for both the application and for the underlying SAP NetWeaver.

Hub Technical systems that you have assigned to the landscape pattern Hub are used by multiple product systems. During upgrades, the Maintenance Optimizer handles the system as a shared system, and only application updates are installed, while the underlying SAP NetWeaver is upgraded to the minimal required version. More information about landscape patterns: Landscape Pattern (http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/2b/5fad0d1f8549609efddabca9 c7f65d/frameset.htm). In this case, the landscape pattern Hub is assigned to the technical system, although it is assigned to only one product system. System Response An incorrect landscape pattern assignment can lead to problems during upgrades of product systems. Procedure Change the assignment of the landscape pattern for the specified technical system in the system landscape of the Solution Manager (transaction SMSY). To do this, proceed as follows: 1. Choose the technical system from the list of landscape components. If it has the system type ABAP, expand the product system with the same name in the list, and, from the list of product instances, choose the product instance with this name. July 2010 19

Landscape Verification 1.0 for SAP Solution Manager If it has another system type, expand the list of technical systems, and choose the appropriate technical system from the list. 2. Switch to change mode. 3. Switch to the Other Attributes tab page and, for the Landscape Pattern attribute, assign the value SIDECAR. 4. Save your changes.

6.1.6. Product system has no active standalone product version

Diagnosis The landscape verification tool checks, among other things, the assignment of product systems to product versions in the system landscape of the Solution Manager (transaction SMSY). In this case, it could not determine an assignment for product system to an active standalone product version. System Response Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your product systems are incorrectly registered, many important functions are not available to you, or are only available on a restricted basis. This is especially true for the use of the Maintenance Optimizer, if you want to perform an upgrade for a product system. Procedure Make the correct assignment in transaction SMSY, and set the indicator Active for the desired standalone product version. More information about the assignment of products and product versions to product systems: Change the Assignment of a Product System to a Product/Product Version (http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/45/5913de5d851ee3e10000000 a155369/frameset.htm).

6.1.7. Authorization error when checking RFC connection

Diagnosis The landscape verification tool checks include checking the RFC connections from the SAP Solution Manager system to the SAP support system OSS and the assigned System Landscape Directory (SLD). The relevant RFC destinations have the following naming convention: Connection to the SAP support system OSS: SAPOSS This RFC connection is used, among other things, to transfer information about existing SAP products, product versions, associated product instances, and software components to your SAP Solution Manager. You can use this information to check your system landscape. Connection to the System landscape Directory (SLD): SAPSLDAPI

July 2010

20

Landscape Verification 1.0 for SAP Solution Manager This RFC connection is used to provide the system landscape of the Solution Manager (transaction SMSY) with information about the systems in your landscape that are registered with your SLD. In this case, it was not possible to check the existence and correct functioning of the RFC destination specified in the short text, since your current user does not have sufficient authorization to do so. System Response Since the RFC connection SAPOSS or SAPSLDAPI forms one of the foundations for working with SAP Solution Manager, many important functions will not be available to you, if this destination is not working correctly. Procedure Ensure that your user has sufficient authorizations. Specifically, the user requires authorization object S_RFC_ADM with activity 03.

6.1.8. Internal error when checking RFC connection

Diagnosis The landscape verification tool checks include checking the RFC connections from the SAP Solution Manager system to the SAP support system OSS and the assigned System Landscape Directory (SLD). The relevant RFC destinations have the following naming convention: Connection to the SAP support system OSS: SAPOSS This RFC connection is used, among other things, to transfer information about existing SAP products, product versions, associated product instances, and software components to your SAP Solution Manager. You can use this information to check your system landscape. Connection to the System landscape Directory (SLD): SAPSLDAPI This RFC connection is used to provide the system landscape of the Solution Manager (transaction SMSY) with information about the systems in your landscape that are registered with your SLD. In this case, an internal error occurred when checking that the RFC destination specified in the short text was functioning correctly. It was not possible to determine the actual cause of this error. System Response Since the RFC connection SAPOSS or SAPSLDAPI forms one of the foundations for working with SAP Solution Manager, many important functions will not be available to you, if this destination is not working correctly. Procedure Contact SAP Support by creating a customer message under application component SVSMG-LV.

6.1.9. RFC connection is not defined

Diagnosis July 2010 21

Landscape Verification 1.0 for SAP Solution Manager The landscape verification tool checks include checking the RFC connections from the SAP Solution Manager system to the SAP support system OSS and the assigned System Landscape Directory (SLD). The relevant RFC destinations have the following naming convention: Connection to the SAP support system OSS: SAPOSS This RFC connection is used, among other things, to transfer information about existing SAP products, product versions, associated product instances, and software components to your SAP Solution Manager. You can use this information to check your system landscape. Connection to the System landscape Directory (SLD): SAPSLDAPI This RFC connection is used to provide the system landscape of the Solution Manager (transaction SMSY) with information about the systems in your landscape that are registered with your SLD. In this case, the RFC destination specified in the short text does not exist in the SAP Solution Manager system. The associated functions are therefore not available to you. System Response Since the RFC connection SAPOSS or SAPSLDAPI forms one of the foundations for working with SAP Solution Manager, many important functions will not be available to you, if this destination is not working correctly. Procedure Follow the appropriate procedure below, depending on which RFC destination does not exist: If the RFC connection SAPOSS does not exist, create it. Use transaction OSS1 to do so; for more information, refer to SAP Note 33135. If the RFC destination SAPSLDAPI does not exist, check the connection from SAP Solution Manager to the assigned SLD using the transaction SLDCHECK. More information: Access To SLD From ABAP Fails (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/78/20244134a56532e100000 00a1550b0/frameset.htm).

6.1.10. RFC connection is defined with a wrong connection type

Diagnosis The landscape verification tool checks include checking the RFC connections from the SAP Solution Manager system to the SAP support system OSS and the assigned System Landscape Directory (SLD). The relevant RFC destinations have the following naming convention: Connection to the SAP support system OSS: SAPOSS This RFC connection is used, among other things, to transfer information about existing SAP products, product versions, associated product instances, and software components to your SAP Solution Manager. You can use this information to check your system landscape. Connection to the System landscape Directory (SLD): SAPSLDAPI July 2010 22

Landscape Verification 1.0 for SAP Solution Manager This RFC connection is used to provide the system landscape of the Solution Manager (transaction SMSY) with information about the systems in your landscape that are registered with your SLD. In this case, although the RFC destination specified in the short text exists in the SAP Solution Manager system, the destination has the wrong connection type. The correct connection type depends on the RFC destination: SAPOSS Connection type 3 SAPSLDAPI Connection type T System Response Since the RFC connection SAPOSS or SAPSLDAPI forms one of the foundations for working with SAP Solution Manager, many important functions will not be available to you, if this destination is not working correctly. Procedure Correct the connection type in accordance with the details above, and repeat the check. You can find more information about the RFC destinations as follows: For more information about RFC connection SAPOSS, refer to SAP Note 33135. More information about checking the connection from the SAP Solution Manager to the assigned SLD using transaction SLDCHECK: Access To SLD From ABAP Fails (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/78/20244134a56532e100000 00a1550b0/frameset.htm).

6.1.11. System failure when calling RFC connection

Diagnosis The landscape verification tool checks include checking the RFC connections from the SAP Solution Manager system to the SAP support system OSS and the assigned System Landscape Directory (SLD). The relevant RFC destinations have the following naming convention: Connection to the SAP support system OSS: SAPOSS This RFC connection is used, among other things, to transfer information about existing SAP products, product versions, associated product instances, and software components to your SAP Solution Manager. You can use this information to check your system landscape. Connection to the System landscape Directory (SLD): SAPSLDAPI This RFC connection is used to provide the system landscape of the Solution Manager (transaction SMSY) with information about the systems in your landscape that are registered with your SLD. In this case, a system error was detected in the SAP Solution Manager system for the RFC destination specified in the short text. A runtime error occurred during the execution of the function module called in the target system. System Response July 2010 23

Landscape Verification 1.0 for SAP Solution Manager Since the RFC connection SAPOSS or SAPSLDAPI forms one of the foundations for working with SAP Solution Manager, many important functions will not be available to you, if this destination is not working correctly. Procedure Follow the appropriate procedure below for the RFC destination for which the error occurred: If the error occurred for the destination SAPOSS, check the destination using transaction SM59. If you cannot solve your problem using the information there, it is possible that the RFC destination is incorrectly configured. Use transaction OSS1 to recreate the RFC destination. For more information about RFC connection SAPOSS, refer to SAP Note 33135. For general information about your service connection to SAP, refer to the following link: http://service.sap.com/access-support If the error occurred for the destination SAPSLDAPI, check the connection from SAP Solution Manager to the assigned SLD using the transaction SLDCHECK. More information: Access To SLD From ABAP Fails (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/78/20244134a56532e100000 00a1550b0/frameset.htm).

6.1.12. Communication failure when calling RFC connection

Diagnosis The landscape verification tool checks include checking the RFC connections from the SAP Solution Manager system to the SAP support system OSS and the assigned System Landscape Directory (SLD). The relevant RFC destinations have the following naming convention: Connection to the SAP support system OSS: SAPOSS This RFC connection is used, among other things, to transfer information about existing SAP products, product versions, associated product instances, and software components to your SAP Solution Manager. You can use this information to check your system landscape. Connection to the System landscape Directory (SLD): SAPSLDAPI This RFC connection is used to provide the system landscape of the Solution Manager (transaction SMSY) with information about the systems in your landscape that are registered with your SLD. In this case, a communication error was detected in the SAP Solution Manager system for the RFC destination specified in the short text, that is, it was not possible to create the connection to the target system, or the connection was interrupted during communication. System Response Since the RFC connection SAPOSS or SAPSLDAPI forms one of the foundations for working with SAP Solution Manager, many important functions will not be available to you, if this destination is not working correctly. July 2010 24

Landscape Verification 1.0 for SAP Solution Manager Procedure Follow the appropriate procedure below for the RFC destination for which the error occurred: If the error occurred for the destination SAPOSS, check the destination using transaction SM59. If you cannot solve your problem using the information there, it is possible that the RFC destination is incorrectly configured. Use transaction OSS1 to recreate the RFC destination. For more information about RFC connection SAPOSS, refer to SAP Note 33135. For general information about your service connection to SAP, refer to the following link: http://service.sap.com/access-support If the error occurred for the destination SAPSLDAPI, check the connection from SAP Solution Manager to the assigned SLD using the transaction SLDCHECK. More information: Access To SLD From ABAP Fails (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/78/20244134a56532e100000 00a1550b0/frameset.htm).

6.1.13. Automatic data transfer to SMSY is not configured via SLD

Diagnosis One of the checks that the landscape verification tool performs is to check the RFC connection SAPSLDAPI to the assigned System Landscape Directory (SLD) and the associated configuration settings. This RFC connection is used to provide the system landscape of the Solution Manager (transaction SMSY) with information about the systems in your landscape that are registered with your SLD. To ensure that that the information in the SLD is regularly transferred to the system landscape of the Solution Manager, when setting up transaction SMSY, you normally create a job called LANDSCAPE FETCH to be regularly executed. In this case, this job was not found. System Response Since the provision of current data about your system landscape to the system landscape of the SAP Solution Manager forms one of the foundations for working with SAP Solution Manager, it is possible that no current data is available to you for important functions. Procedure To schedule this job, start transaction SMSY_SETUP. More information: Set-Up Automatic Data Capture for System Landscape (http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/31/b175362b9e4c329ef4b0e46 0a1ea5c/frameset.htm).

6.1.14. Internal error when checking job schedule for periodic landscape fetch
Diagnosis July 2010 25

Lan ndscape Ve erification 1 for SAP Solution Manager 1.0 P M One of the chec that the landscape v e cks verification tool perfor is to che the RFC n rms eck C conn nection SAP PSLDAPI to the assign System Landscape Directory (S o ned L SLD) and th he asso ociated conf figuration settings. Thi RFC conn is nection is us to provi the syste sed ide em land dscape of th Solution M he Manager (tr ransaction SMSY) with informatio about the S h on e syst tems in you landscape that are reg ur e gistered wit your SLD th D. To e ensure that that the info ormation in the SLD is regularly transferred t the system n s to m land dscape of th Solution M he Manager, w when setting up transaction SMSY you norma g Y, ally crea a job cal LANDS ate lled SCAPE FET TCH to be re egularly exe ecuted. In th case, an internal his erro meant tha it was not possible to check whe or at t o ether the job is scheduled. It was not b n poss sible to dete ermine the a actual cause of this erro e or. Pro ocedure Con ntact SAP S Support by c creating a cu ustomer me essage under application componen SVr n nt SMG-LV.

6.1.15. No periodic la andscape fetch job planned e b d

Dia agnosis One of the chec that the landscape v e cks verification tool perfor is to che the RFC n rms eck C conn nection SAP PSLDAPI to the assign System Landscape Directory (S o ned L SLD) and th he asso ociated conf figuration settings. Thi RFC conn is nection is us to provi the syste sed ide em land dscape of th Solution M he Manager (tr ransaction SMSY) with informatio about the S h on e syst tems in you landscape that are reg ur e gistered wit your SLD th D. To e ensure that that the info ormation in the SLD is regularly transferred t the system n s to m land dscape of th Solution M he Manager, w when setting up transaction SMSY you norma g Y, ally crea a job cal LANDS ate lled SCAPE FET TCH to be re egularly exe ecuted. In th case, alt his though the j was fou job und, it is not periodically schedule t ed. System Response ce ision of curr data ab rent bout your sy ystem landsc cape to the system land dscape Sinc the provi of th SAP Sol he lution Mana ager forms o of the fo one oundations for working with SAP g Solu ution Manager, it is possible that n current data is availa to you for importa no d able ant func ctions. Pro ocedure To s schedule thi job, start transaction SMSY_SE is n ETUP, and e ensure that t indicato the or Peri iodic is set. For more in nformation about this, see Set-Up Automatic Data Captu for ure Syst Landsc tem cape (http p://help.sap p.com/saphe elp_sm70eh hp1_sp23/he elpdata/en/3 31/b175362b b9e4c329ef f4b0e46 0a1ea5c/frames set.htm). If I you have scheduled the job LAN e NDSCAPE F FETCH using an extern job nal control tool you will r c l, receive this message ev though t ven there is not a problem in this case. p

6.1.16. No O OSS connection de efined in the syste em

Dia agnosis July 2010 y 26

Landscape Verification 1.0 for SAP Solution Manager The landscape verification tool checks include checking the RFC connection from the SAP Solution Manager system to the SAP support system OSS. This RFC connection is used, among other things, to transfer information about existing SAP products, product versions, associated product instances, and software components to your SAP Solution Manager. You can use this information to check your system landscape. You can also use the BAdI BADI_SMBI_DESTINATION_SET to set this RFC connection. In this case, you have changed the standard implementation for this BAdI in a way that means there is no longer a connection available to the OSS system. System Response Since the RFC connection to the SAP Support system OSS forms one of the foundations for working with SAP Solution Manager, many important functions will not be available to you, if this destination is not working correctly. Procedure Use transaction SE18 to check and correct your implementation of the BAdI BADI_SMBI_DESTINATION_SET. For more information about registering ABAP systems, see Configuring the SLD Data Supplier: Default Settings (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/b7ba48e2c0356be10000000a421 937/frameset.htm).

6.1.17. Some software components not covered by configured product instances

Diagnosis Versions of software components were found for the technical system for which no associated product instance was found in the system landscape of the Solution Manager (transaction SMSY). The following information is therefore displayed in the tables specified below: A list of the software component versions that are installed on this system, but for which no associated product instance was found in the system landscape of the Solution Manager. A list of the product instances that can be technically assigned to the system based on its software component versions. System Response Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your system is incorrectly registered, many important functions are not available to you, or are only available on a restricted basis. Procedure To assign one of the suggested product instances to the technical system, proceed as follows: 1. Start the system landscape of the Solution Manager (transaction SMSY) and navigate to the relevant product system.

July 2010

27

Landscape Verification 1.0 for SAP Solution Manager The product systems are grouped according to products; make sure that you choose the product system in the correct product sub tree. You can also use the search function by choosing the Other Object button and enter the system ID of the designated product system. Make sure that the correct product version is assigned as active to the product system. You can change the assignment on the Header Data tab page by choosing the Change Product Assignment button. On the Product Instance Selection tab page, there is a list of all possible product instances for the product version of the relevant product system; the Relevant indicator shows the installed product instances. Check if product instances that are listed in the table below as those that can be technically assigned are actually installed, and set the Relevant indicator for these product instances. Keep in mind, that you can only mark one product instance as Relevant if the product instance is running on an ABAP system. If you want to assign more product instances, choose the Also installed indicator. Save your changes, and repeat the check.

2.

3.

4.

5.

6.1.18. Product system contains technically inappropriate product instances

Diagnosis The product instances of technical system that are assigned to this system in the system landscape of the Solution Manager do not match the product instances that can be technically assigned to the technical system based on its software component versions. The table specified below therefore lists the product instances that are assigned to the system in the system landscape of the Solution Manager, but which technically cannot be assigned on the basis of the existing software component versions. System Response Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your system is incorrectly registered, many important functions are not available to you, or are only available on a restricted basis. Procedure To delete the assignment of the incorrect product instances for the technical system, proceed as follows: 1. Start the system landscape of the Solution Manager (transaction SMSY) and navigate to the relevant product system. 2. On the Product Instance Selection tab page, there is a list of all possible product instances for the product version of the relevant product system; the Relevant indicator shows the installed product instances. 3. Switch to change mode and delete the Relevant indicator for the product instances that were displayed in the table below as incorrect. 4. Save your changes, and repeat the check. July 2010 28

Landscape Verification 1.0 for SAP Solution Manager

6.1.19. Java Stack of Technical system &1 (dual stack) is not available in SMSY
Diagnosis The Java stack of the dual-stack system does not exist in the system landscape of the Solution Manager (transaction SMSY). System Response Since the system landscape forms the basis for working with SAP Solution Manager, many important functions are not available to you for this system, or are only available on a restricted basis. Procedure To include the system in the system landscape of the Solution Manager, register it in the System Landscape Directory (SLD); the system data is then automatically transferred to the system landscape of the Solution Manager. The procedure for registering the Java system in the SLD depends on the release of the Java system: For Java systems with a release before SAP NetWeaver 7.1, use the Visual Administrator to register the system in the SLD. More information: Setting Up the SLD Data Supplier for Java-Based Systems (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/b6847d96655295e100000 00a42189b/frameset.htm). For Java systems with a release of SAP NetWeaver 7.1, use the NetWeaver Administrator to register the system in the SLD. More information: Setting Up the SLD Data Supplier for AS Java Based Systems (http://help.sap.com/saphelp_nwpi711/helpdata/en/48/b6847d96655295e1000000 0a42189b/frameset.htm).

6.1.20. Technical system (system type ABAP) is not available in SMSY

Diagnosis The ABAP system or ABAP stack of the dual-stack system does not exist in the system landscape of the Solution Manager (transaction SMSY). System Response Since the system landscape forms the basis for working with SAP Solution Manager, many important functions are not available to you for this system, or are only available on a restricted basis. Procedure To include the system in the system landscape of the Solution Manager, register it in the System Landscape Directory (SLD); the system data is then automatically transferred to the system landscape of the Solution Manager. More information: Configuring the SLD Data Supplier: Default Settings (http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/b7ba48e2c0356be10000000a421 937/frameset.htm). July 2010 29

Landscape Verification 1.0 for SAP Solution Manager

6.1.21. Product system configured with non-existent product SAP ECC

Diagnosis The landscape verification tool checks, among other things, the assignment of product systems to product versions in the system landscape of the Solution Manager (transaction SMSY). In this case, an assignment to the SAP product SAP ECC was determined for the product system. However, this is not a valid assignment, since SAP ECC is not a valid standalone product, but is rather operated in the context of the SAP product SAP ERP. System Response Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your product systems are incorrectly registered, many important functions are not available to you, or are only available on a restricted basis. This is especially true for the use of the Maintenance Optimizer, if you want to perform an upgrade for a product system. Procedure Make the correct assignment in transaction SMSY. More information about the assignment of products and product versions to product systems: Change the Assignment of a Product System to a Product/Product Version (http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/45/5913de5d851ee3e10000000 a155369/frameset.htm).

6.2. Glossary
Landscape Pattern Describes how systems are used in a landscape. Examples: Hub: technical System used by two or more product systems (for example, a SAP NetWeaver Enterprise Portal (EP) used by the HR and SCM product systems) Sidecar: Any technical system that is used in a product system but not running on the ABAP stack. Product Used in SAP solutions. Generally speaking, a product fulfills business requirements. A maintenance period is defined for a product. Examples: SAP NetWeaver, SAP ERP. SAP ERP has several usages such as HR or FI. Product Instance (formerly Main Instance in SMSY, Instance or Software Unit in SLD): Part of a Product Version and the smallest element for designing system landscapes. It groups technically-dependent Software Component Versions, which have to be installed and operated on a single Technical System. July 2010 30

Landscape Verification 1.0 for SAP Solution Manager The different product instances of a product version could be installed on different technical systems or on the same technical system One product instance is always installed on one technical system (it cannot span more than one technical system). Examples: AS ABAP, AS Java, SAP ECC Server, TREX.

Product System (formerly System) Group of Technical Systems, on which one Product Version is installed. In one Product System there can be only one ABAP-based Technical System and zero or more non-ABAP Technical Systems Example: SAP CRM 7.0 Product Version Actual release of a given product. It bundles together Software Component Versions made available at the same time for implementing a well-defined scope of functionality. A product has versions (releases) consisting of Software Components. Examples: SAP ERP 6.0, SAP NetWeaver 7.0 Software Component (SC) Reusable component of the product from a production view: Unit of product upgrade or update / Support Package (one or more SCs). An SC may require other SCs. Examples: SAP_BASIS, SAP_HR Technical System (formerly named System Component for non-ABAP systems) Runtime environment in which SAP applications are executed. It is identified with a system identifier (SID). It must be manually and explicitly assigned to a Product System. A technical system could be running on one or more hardware boxes and has one database instance that is shared between the parts of the systems running on different boxes. The corresponding SMSY entity is copied automatically from a connected System Landscape Directory (SLD). However, it can be created manually, too.

July 2010

31