sap solution manager 7.1 configuration

SAP Solution Manager

Maintenance Planning Guide

Using SAP Solution Manager 7.1 SP5-6

including Landscape Management Database (LMDB)

Target Audience:

■ Technology Consultants

■ System Administrators

■ Support Specialists

Version 2.01

August 2012

i

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or

transmitted in any form or for any purpose without the

express permission of SAP AG. The information contained

herein may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Outlook, and PowerPoint 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,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either trademarks or registered trademarks of Adobe

Systems Incorporated in the United States and/or other

countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered

trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,

WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

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

NetWeaver, and other SAP products and services

mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in

Germany and in several other countries all over the world.

All other product and service names mentioned are the

trademarks of their respective companies. Data contained

in this document serves informational purposes only.

National product specifications may vary.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided “as is” without a warranty of

any kind, either express or implied, including but not

limited to, the implied warranties of merchantability,

fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. SAP has no control over the

information that you may access through the use of hot

links contained in these materials and does not endorse

your use of third party web pages nor provide any warranty

whatsoever relating to third party web pages.

SAP NetWeaver “How-to” Guides are intended to simplify

the product implementation. While specific product

features and procedures typically are explained in a

practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable for

errors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

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

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

ii

Document History

Document Version Description

1.00

(SAP Solution

Manager 7.0 –

7.1SP4)

November 8, 2011

First version for use with SAP Solution Manager 7.0 – 7.1 SP4

1.01

(SAP Solution

Manager 7.0 –

7.1SP4)

November 29, 2011

Updated section User Maintenance for Maintenance Optimizer.

Updated section Technical and Product Systems.

1.1

(SAP Solution

Manager 7.0 –

7.1SP4)

May 2012

Complete text review

Deleted: references to Solution Manager System Landscape (SMSY)

Deleted: Table with usage types; not relevant for updates/upgrades

Included: List of notes for the usage of technical usages

2.0

(SAP Solution

Manager 7.1)

June 2012

New version for use with SAP Solution Manager 7.1 SP5

Complete text review

New: Product System Maintenance with Landscape Management Database

(LMDB)

Deleted: Install the Landscape Verification Add-On

Deleted: Forward Data from Central SLD to Local SLD in SAP Solution

Manager

New: landscape verification with the LMDB

Deleted: references to SAP Solution Manager System Landscape (SMSY)

Deleted: references to old Landscape Verification tool

2.01

(SAP Solution

Manager 7.1, SP5-6)

Oct. 2012

Improved description of chapter 4.4.1 Assign Landscape Patterns

This guide is regularly updated in SAP Service Marketplace at http://service.sap.com/mopz.

Make sure you have the latest version of the guide by checking SAP Service Marketplace.

Please enter questions and comments at http://scn.sap.com/docs/DOC-31192.

http://service.sap.com/mopz

http://scn.sap.com/docs/DOC-31192

iii

Typographic Conventions

Type Style Description

Example Text Words or characters quoted

from the screen. These

include field names, screen

titles, pushbuttons labels,

menu names, menu paths,

and menu options.

Cross-references to other

documentation

Example text Emphasized words or

phrases in body text, graphic

titles, and table titles

Example text File and directory names and

their paths, messages,

names of variables and

parameters, source text, and

names of installation,

upgrade and database tools.

Example text User entry texts. These are

words or characters that you

enter in the system exactly as

they appear in the

documentation.

<Example

text>

Variable user entry. Angle

brackets indicate that you

replace these words and

characters with appropriate

entries to make entries in the

system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Description

Caution

Important

Note

Recommendation or Tip

Example

iv

Table of Contents

1. About this Document .......................................................................................................... 1

2. Sources of Information ....................................................................................................... 1

3. SAP Solution Manager Prerequisites ................................................................................ 1

3.1 Update SAP Solution Manager ..................................................................................... 1

3.2 Install Implementation Content Add-On ....................................................................... 2

3.3 Complete SAP Solution Manager Basic Configuration ................................................ 2

3.4 Maintain Users for Maintenance Optimizer .................................................................. 2

4. System Landscape Data Maintenance .............................................................................. 3

4.1 Register Technical System Data in SLD ...................................................................... 4

4.2 Transfer Data from SLD to SAP Solution Manager Landscape Management

Database (LMDB) and Migrate SMSY Data ................................................................. 5

4.3 System Landscape Modeling in SAP Solution Manager .............................................. 5

4.3.1 System Landscape Modeling Rules ................................................................ 8

4.4 System Landscape Description in the Landscape Management Database (LMDB) ... 9

4.4.1 Assign Landscape Patterns ............................................................................. 9

4.4.2 Create and Verify Product Systems ............................................................... 16

5. Selecting and Downloading Software Packages ............................................................ 18

5.1 Starting a Maintenance Transaction ........................................................................... 18

5.1.1 Plan Maintenance .......................................................................................... 19

5.1.2 Select Files .................................................................................................... 20

5.1.3 Download Files .............................................................................................. 24

5.1.4 Implement ...................................................................................................... 24

5.1.5 End Maintenance ........................................................................................... 24

Maintenance Planning Guide – Using SAP Solution Manager 7.1 SP5

Page 1

1. About this Document

The guide is intended for technology consultants, system administrators, and support specialists.

The Maintenance Optimizer (MOpz) in SAP Solution Manager plays a central role in maintaining SAP systems and to successfully upgrade and update technical systems.

The Maintenance Optimizer calculates the required enhancement package files, support package stacks, and additional update packages and creates a stack configuration file (XML). This file can be read by update tools like the Software Update Manager (SUM) and is used as an input file for the installation.

This guide provides information on the following topics:

Required SAP Solution Manager version and add-ons for the upgrade and update process

Basic configuration of SAP Solution Manager and Maintenance Optimizer

Correct maintenance of your system landscape description in SAP Solution Manager:

o How to collect system landscape descriptions in SAP Solution Manager

o How to model technical systems and product systems in SAP Solution Manager for additional updates

o How to verify the correctness of your SAP system landscape description

o How to calculate the stack configuration files with the Maintenance Optimizer

2. Sources of Information

Managing System Landscape Information in the SAP Help Portal at http://help.sap.com/solutionmanager71 Application Help --> SP05 SAP Solution Manager Operations

Maintenance Optimizer in the SAP Help Portal at http://help.sap.com/solutionmanager71 Application Help SP05 Maintenance Management

Maintenance Optimizer in the SAP Support Portal at http://service.sap.com/mopz.

System Landscape Directory (especially the Planning Guide) in the SAP Community Network

3. SAP Solution Manager Prerequisites

3.1 Update SAP Solution Manager

For the installation of the SAP Business Suite EHP5, you require at least SAP Solution Manager 7.0 SP23.

Using the Maintenance Optimizer is mandatory as of SAP Business Suite EHP4.

Always update SAP Solution Manager to the latest support package. This guide refers to SAP Solution Manager 7.1 SP5.

To check your current version in the SAP Solution Manager system, choose System → Status →

Component information. For software component ST, the release must be 400, the SP level should be

at least SP23.

If you are not using the required SAP Solution Manager version, update the application. For more information, see SAP Note 1583348 and the Master Guide SAP Solution Manager 7.1 at http://service.sap.com/instguides → SAP Components → SAP Solution Manager → Release 7.1 → Planning.

https://help.sap.com/saphelp_sm71_sp05/helpdata/en/31/6f58dd0fdd4d208735c2b2e190de84/content.htm

http://help.sap.com/solutionmanager71

https://help.sap.com/saphelp_sm71_sp05/helpdata/en/46/418970cdb45fabe10000000a1553f7/frameset.htm




https://service.sap.com/sap/support/notes/1583348

http://service.sap.com/instguides


Page 2

3.2 Install Implementation Content Add-On

We recommend that you use the implementation content add-on.

The implementation content add-on (ST-ICO) provides information on how to implement and configure SAP business scenarios and processes in SAP Solution Manager. This includes scenario and process descriptions as well as integrated configuration information supported by SAP implementation, operations, and upgrade roadmaps.

To find out which ST-ICO version is deployed on your SAP Solution Manager system, log on to the SAP Solution Manager system with SAP GUI and choose System → Status → Component information

, and check the level information for the software component ST-ICO. For more information about

the implementation content, see SAP Note 631042 and SAP Solution Manager for the SAP Business Suite 7i2011 at http://service.sap.com/solutionmanager → Media Library → Presentations.

3.3 Complete SAP Solution Manager Basic Configuration

To use SAP Solution Manager for enhancement package installation or other maintenance processes,

ensure that the basic configuration was successfully done:

1. Log on to the SAP Solution Manager system.

2. Start transaction SOLMAN_SETUP.

3. In the Overview, check the statuses for System Preparation and Basic Configuration. Both should be completed. If there are warnings or errors, resolve the issues and complete all open tasks.

Diagnostics Prerequisites in the Installation Check step and Diagnostics Configuration in the Automatic Configuration step do not influence the selection and download of enhancement package files. You may therefore omit these activities at this point.

Ensure that the latest version of SAP Note 1590226 is implemented in your system. It ensures that the

latest Maintenance Optimizer version is available.

SAP Solution Manager Configuration from an initial state is described in the Solution Operations Guide for SAP Solution Manager, section Software Change Management for more information. You find this guide at http://service.sap.com/instguides → Installation & Upgrade Guides → SAP Components → SAP Solution Manager → Release 7.1 → Operations. After the configuration, all statuses must be Confirmed (green icon).

3.4 Maintain Users for Maintenance Optimizer

The Maintenance Optimizer client of SAP Solution Manager communicates with the SAP Service Marketplace to calculate the required download stack for your SAP system landscape maintenance.

Make sure that your user in SAP Solution Manager and your s-user for the SAP Service Marketplace have the required authorizations to use the Maintenance Optimizer functions and that the two users match.

Your user in the SAP Solution Manager system requires the following roles:

SAP_MAINT_OPT_ADMIN: full authorization for the Maintenance Optimizer

SAP_MAINT_OPT_ADD: authorization to write the XML into the EPS inbox directory

SAP_SMWORK_BASIC: authorization for the work center frame, navigation and table control

SAP_SMWORK_CHANGE_MAN: access to Change Request Management work center

Copy the standard roles to your own (customer) namespace, maintain the authorizations, generate the profiles and perform a user comparison to ensure that the authorizations were assigned to the users.

For more information, see:

SAP Note 1032322 for details about additional authorization checks for Maintenance Optimizer, for example, how to restrict specific transactions or functions


http://service.sap.com/solutionmanager





Page 3

Security Guide for SAP Solution Manager for additional information about standard roles at http://service.sap.com/instguides → SAP Components → SAP Solution Manager → Release 7.1 → Operations

You need an s-user for the SAP Service Marketplace (SMP). If you do not have one, request it at http://service.sap.com/user-admin → Request New Users.

Your s-user needs the SWCATALOG authorization to execute Maintenance Optimizer and to order

software from the SAP Software Catalog. To check authorizations, goto http://service.sap.com/user-admin, log on with your user, and choose Search and Maintain Users. The authorization for the Execute Maintenance Optimizer activity must be assigned.

Assign your s-user to the SAP Solution Manager user that works with the Maintenance Optimizer:

1. In your SAP Solution Manager system, start transaction AISUSER.

There is only a value help for the Contact Person field if the background job

REFRESH_ADMIN_DATA_FROM_SUPPORT has already been run. If this is not the case,

manual entries cause a warning message because the s-user is not found. Assign the contact person for the system administrator user first and maintain the contact persons for all other project members when the administrator has run the background job.

2. Choose New Entries. Under User, enter an SAP Solution Manager system user and under Contact Person assign a contact person of the SAP Service Marketplace (= SAP Support Portal), which is an s-user ID without the „s‟.

If three instead of two columns are visible in transaction AISUSER, you are running the

BAdi Business Add-In to Manage Several SAP Customer Numbers, which is applicable if you manage several SAP customer numbers in your SAP Solution Manager system. If you do not manage several SAP customer numbers, deactivate this BAdI:

a. Start transaction SPRO in the SAP Solution Manager system.

You find the BAdI in the SAP Reference IMG under SAP Solution Manager → Basic Settings → Connection to SAP → Several SAP Customer Numbers -> Business Add-In to Manage Several SAP Customer Numbers.

b. The dialog will ask you whether you want to deactivate the BAdI implementation

AI_SDK_SP_RFC_RP AI_SDK_SP_RFC_RP. Choose Yes.

c. Check transaction AISUSER. It now shows only two columns.

For more information on Maintenance Optimizer, see http://service.sap.com/mopz.

4. System Landscape Data Maintenance

The SAP NetWeaver System Landscape Directory (SLD) is the central directory of system information required to manage your application life-cycle. It contains a description of the technical systems of your landscape (hosts and software currently installed) and a catalog of all software (CR content, SAP Software Catalog) delivered by SAP that can theoretically be installed in your landscape (such as the software components available from SAP). As the system information is updated automatically, the SLD provides reliable and up-to-date information as the central information provider for the SAP Solution Manager.

The Maintenance Optimizer relies on up-to-date information about your system landscape. Therefore, it is crucial that landscape information is correctly synchronized and maintained in the SAP Solution

Manager Landscape Management Database (LMDB, transaction LMDB). The landscape verification

function in LMDB helps you to detect and correct errors in the system landscape description of the SAP Solution Manager.


http://service.sap.com/user-admin





Page 4

The graphic shows the central steps how system landscape data is maintained and used:

1. Register technical systems of your system landscape in central SLD. The preferred way to do this is by automatic data suppliers that are set up in the technical systems. Technical systems periodically send data to the SLD.

2. Synchronize SLD technical system descriptions with SAP Solution Manager Landscape Management Database (LMDB).

3. Create product system descriptions in LMDB, manually, and run verifications.

4. Use verified landscape descriptions with other SAP Solution Manager applications, such as the Maintenance Optimizer.

For more information about the SLD, see:

System Landscape Directory at http://scn.sap.com/docs/DOC-8042.

Planning Guide - System Landscape Directory at http://scn.sap.com/docs/DOC-14151.

4.1 Register Technical System Data in SLD

Depending on your system landscape setup, data can be sent automatically to the SLD from the

following systems:

Application Server (AS) ABAP systems are registered using transaction RZ70.

AS Java systems are registered with the Visual Administrator or, as of SAP NetWeaver 7.1, the NetWeaver Administrator.




Page 5

Dual-stack system is registered automatically when the related AS ABAP and the AS Java have been registered.

TREX systems are registered by generating SLD configuration files and copying them to the Global SLD Directory

Selected technical systems used by SAP, for example ATC Server, Unspecific Cluster System, MS IIS Instance, use predefined data suppliers.

For third-party systems, you can setup generic data suppliers like sldreg.

How exactly the technical systems can be registered in the SLD is described in the following

documents:

Planning Guide - System Landscape Directory in the SAP Community Network at http://scn.sap.com/docs/DOC-14151.

List of data suppliers: Register Technical Systems Automatically by Data Suppliers in the SAP

Help Portal.

4.2 Transfer Data from SLD to SAP Solution Manager

Landscape Management Database (LMDB) and

Migrate SMSY Data

After setting up system registration in the SLD, you can synchronize this system information from the

SLD with the Landscape Management Database (LMDB) in SAP Solution Manager. The SLD

synchronization connection is set up during the initial configuration of the SAP Solution Manager:

1. In the SAP Solution Manager system, start transaction SOLMAN_SETUP.

2. Choose System Preparation Prepare Landscape Description Set Up LMDB Under Synchronization Connections between SLD and LMDB you can see whether there already is a connected SLD.

3. If no SLD is connected yet, choose Add and define a new connection.

4. Ensure that the connection is active (green status icon) and that the first full automatic synchronization ran successfully.

For more information, see Managing System Landscape Information in the SAP Help Portal at

http://help.sap.com/solutionmanager71 Application Help SAP Solution Manager Operations.

4.3 System Landscape Modeling in SAP Solution

Manager

With the technical system information as a basis, you can now start to model the product system

descriptions for the logical system landscape in SAP Solution Manager.

This section explains how to model your system landscape in SAP Solution Manager. First of all, it is

very helpful to understand the basic terminology used in this context:


http://help.sap.com/saphelp_sm71_sp05/helpdata/en/88/55bbf626a542ea86d7f9be9e3fecad/frameset.htm

https://help.sap.com/saphelp_sm71_sp05/helpdata/en/31/6f58dd0fdd4d208735c2b2e190de84/content.htm



Page 6

Product SAP Products are the applications SAP ships and group sets of functions to solve

business requirements. The complete product model is shipped as SAP Software

Catalog (or “CR Content” in the SLD). The availability of products is published in the

Product Availability Matrix (PAM. Under http://service.sap.com/pam). The product

model defines the product structure with its product instances, software components,

version, and technical dependencies between product and its components. Products

typically have a name starting with 'SAP...' and are characterized by a version period

and a maintenance cycle.

A product can be installed on one or more technical systems. All technical systems

that are involved in the installation of one product form the product system.

Examples: SAP ERP, SAP NetWeaver, and SAP Solution Manager.

One product consists of one or more product versions.

Product

version

Each SAP product is installed in a product version, which is a concrete release of a product, available at a particular time for a specific scope of functionality. It bundles product instances and the included software component versions.

Like products, information on product versions is shipped in the SAP Software Catalog. They are the basis for the compatibility of closely coupled systems and the maintenance of product systems. For each product version, a maintenance period is defined.

Example: SAP ERP 6.0, which is a product version of the product SAP ERP.

There are standalone product versions (for example, SAP ERP 6.0) and add-on product versions that require another product version as foundation for their installation and operation (for example, EHP5 for SAP ERP 6.0). For more information about add-on product versions, see Assign Technical Systems, Product Versions, and Product Instances.

Technical

system

Installing a product version on hardware, on one or several physical or virtual hosts, creates one or more technical systems. Technical systems can either be distributed on one or more application servers or on a database system on the same or a different host, web dispatcher, etc. or can run everything on one host.

A technical system is installed and administered as a whole. Often, e.g. in AS ABAP

http://service.sap.com/pam


Page 7

and AS Java, it is identified by a system ID (SID) or extended SID, a host, and an installation number. There are different technical system types, for example Application Server (AS) ABAP, AS Java, or TREX. Technical systems are central elements when it comes to maintenance and operational activities, such as monitoring and alerting.

Product

system

A group of technical systems on which a product version is installed. Product systems are used to maintain and plan products in the system landscape. Most product versions can be installed in different ways on one or more technical systems, therefore knowing only the product version is not enough for maintenance. You also need to define the associated product systems to maintain SAP products.

On the technical systems of a product system, one standalone product version and either zero, one, or several add-on product versions are installed. As of SAP Solution Manager 7.1 SP5, you can assign more than one AS ABAP to a product system and zero, one, or several non-ABAP technical systems.

Software

component

version

Product versions bundle software component versions that are made available at the same time for implementing a specific scope of functionality. A software component is the smallest entity that can be installed on a technical system. It is a reusable component of the product. A software component version can be part of several product instances. It can require other software component versions to be installed as

well.

Examples: SRM Server 7.01, SAP BASIS 7.20, and Portal 7.0.

Product

instance

Technically dependent software component versions are grouped in product instances

(formerly known as main instances, instance or software units in transaction SMSY)

which are the smallest elements in a system landscape described in SAP Solution Manager. One product instance must be installed and updated as a whole on a single technical system. (ABAP-Java dual-stack systems are considered one technical system.) Patches can still be installed for individual software components.

The various product instances of a product version can be installed on one or several technical systems.

There are some exceptions to this rule. Some product instances (for example in SAP NetWeaver PI) are installed on both the AS ABAP and AS Java technical systems. In such cases you have a mandatory dual-stack, and both stacks are treated as one technical system, even though for a dual-stack system technical systems of the types AS ABAP and AS Java need to be registered separately in the System Landscape Directory (SLD).

Examples: SAP ECC Server, SAP XSS (Self-Services), TREX.

Synonyms: main instance (in SAP Solution Manager transaction SMSY), software unit (in System Landscape Directory [SLD])

Dual-stack SAP system that contains installations of both AS ABAP and AS Java. A dual-stack has the following characteristics:

o Common SID for all application servers and the database

o Common startup framework

o Common database (with different schemas for ABAP and Java)

All parts (technical systems and installed product instances) of a dual stack must completely be assigned to one product system.

Technical

usage

Technical usage is a further qualification describing a specific configuration of a product version. It bundles product instances for a distinct usage. It can be spread over multiple technical systems and technology types. Not all product versions have this additional grouping. There is a mapping between business functions and technical usages for ERP enhancement packages.


Page 8

For more information about products and their elements, see Understanding Landscape Descriptions - Part I: the Simple Approach to Explaining Products, Product Instances, and Software Components in the SAP Community Network.

For more information about technical usages and business functions, see the Master Guide for SAP ERP 6.0 Enhancement Package 6 at http://service.sap.com/erp-ehp6-inst, section Enhancement Packages and Software Components: Architecture Overview.

4.3.1 System Landscape Modeling Rules

This section explains the rules to model a landscape description in SAP Solution Manager:

1. A product system has one active standalone product version. The standalone product version must be installed on all technical systems belonging to the product system.

(The dual-stack upgrade to SAP NetWeaver 7.30 with SEM-BW is an exception to this rule. In this case, see SAP Note 1539356 for a description of the correct product system configuration.)

2. If additional add-ons or enhancement packages (EHPs) are deployed on the system, these also must be assigned to the product system as product versions. There are two kinds of EHP product versions: add-on EHPs and standalone EHPs. For example, SAP ERP 6.0 EHP 6 is an add-on product version that requires its standalone SAP ERP 6.0 product version; SAP EHP3 FOR SAP NETWEAVER 7.0 is a standalone product version.

3. All installed product instances of a product version must be assigned to the product system.

Some product instances contain both ABAP and Java components (for example, SAP NetWeaver Mobile Infrastructure or SAP NetWeaver Process Integration). If such a product instance is installed, you have to link it to the relevant Java technical system.

4. Landscape patterns must be assigned to technical systems.

A landscape pattern defines whether a technical system is assigned to one (sidecar) or more (hub) product systems. For more information, see Assign Landscape Patterns.

If you model a product system for an SAP CRM, SAP SRM, or SAP SCM product with an SAP NetWeaver Java component (for example, SAP Enterprise Portal), create a separate product system for the SAP NetWeaver product. All installed SAP NetWeaver product instances have to be assigned to this product system. This note is relevant for the following product versions:

SAP CRM 7.0

SAP CRM 7.0 / NW7.01

SAP SRM 7.0

SAP SRM 7.0 / NW7.01

SAP SCM 7.0

SAP NetWeaver ERECRUIT, LSOFE, SEM-BW, and FINBASIS are stand-alone Add-Ons installable on SAP NetWeaver systems, but in SAP PPMS they are modeled within the ERP product. Therefore, the system must be configured as ERP system and the corresponding instance must be marked as installed. For more information, see SAP Note 1326576 and SAP Note 1531022.

The Product System Editor of the LMDB helps you to create consistent landscape descriptions: When you assign technical systems to a product system, the LMDB automatically suggests product instances and the related product versions that are installed on the selected technical system. You only need to select the instances relevant for the selected product

http://scn.sap.com/people/wolf.hengevoss/blog/2011/07/21/understanding-landscape-descriptions--part-i-the-simple-approach-to-explaining-products-product-instances-and-software-components

http://scn.sap.com/people/wolf.hengevoss/blog/2011/07/21/understanding-landscape-descriptions--part-i-the-simple-approach-to-explaining-products-product-instances-and-software-components

http://service.sap.com/erp-ehp6-inst





Page 9

system. This, of course, requires that the SAP Solution Manager is provided with reliable technical system information by SLDs. For more information, see Assign Technical Systems, Product Versions, and Product Instances. The landscape verification function checks whether a landscape description complies with the rules for product systems. It detects incorrect assignment of product versions, instances, or landscape patterns. For more information, see Verify Your Product System Information.

4.4 System Landscape Description in the Landscape

Management Database (LMDB)

As of Solution Manager 7.1 SP5, technical systems and product systems are maintained in LMDB, but

no longer with transaction SMSY.

SAP Solution Manager 7.0 SAP Solution Manager 7.1

SP01-04

SAP Solution Manager 7.1

SP05

Product and technical system

information is maintained in

SMSY.

Product system information is

maintained in transaction SMSY.

Technical system information is

maintained in the new

Landscape Management

Database (transaction LMDB).

Product and technical system

information is maintained in the

LMDB.

Prerequisite: You have completed the activities described under Transfer Data from SLD to SAP

Solution Manager Landscape Management Database (LMDB) and Migrate SMSY Data.

It is strongly recommended, that technical system information is provided automatically by SLD data

suppliers. Manual entries must be avoided since they can lead to inconsistencies and hinder later

automatic updates by SLD.

Some information cannot be delivered by SLD, you need to maintain it manually, for example the

landscape pattern, custom attributes, and the complete product system information.

To view and edit system descriptions, start SAP Solution Manager: Work Centers (transaction

SOLMAN_WORKCENTER) SAP Solution Manager Administration Landscape and choose

Technical Systems or Product Systems, for example.

(Alternatively, you can access the LMDB data directly with transaction LMDB.)

For more information, see the following LMDB documents:

SP1-4: Setup Guide LMDB under http://service.sap.com/solutionmanager Media Library

Technical Information

SP5: Managing System Landscape Information in the SAP Help Portal at

http://help.sap.com/solutionmanager71 (available as of June 2012).

4.4.1 Assign Landscape Patterns

In the LMDB, you need to set the landscape pattern for a technical system to define whether a technical system is used by one or several product system:

http://service.sap.com/solutionmanager



Page 10

A sidecar technical system is connected to exactly one ABAP-based backend system via a product

system. During an upgrade, the Maintenance Optimizer handles the sidecar technical system strongly

coupled with the corresponding ABAP-based backend system and keeps the application and the

underlying SAP NetWeaver of both systems in sync.

However, there are a few exceptions when a sidecar technical system is not updated synchronously

with the assigned superordinate product system but completely independent, e.g. for a technology-

driven upgrade to SAP NetWeaver 7.3. For this reason, it is required to additionally create an own

product system for the SAP NetWeaver product version, as you would do for a hub system.

A hub technical system is connected to more than one ABAP-based backend system via a product

system. During upgrades, the Maintenance Optimizer handles the system as a shared system and

only updates of the selected application are installed, while the underlying SAP NetWeaver and other

applications are upgraded to the minimally required version, see the example below.

Only Create Hubs in Case of Close Maintenance Dependencies

A hub technical system should not be created for mere functional dependencies (e.g. Adobe Document Services or TREX) but rather for technical and upgrade-related dependencies (e.g. for XSS, XECO). Hub modeling is only recommended if there is a tight connection between product versions when it comes to maintenance activities; this dependency can be defined by common technical usages, for example.

AS ABAP Cannot Be a Hub

Product system definition does not support using one AS ABAP technical system for more than one product system; therefore you cannot assign a Hub landscape pattern to an AS ABAP technical system. (This also applies to an AS ABAP part of an SAP NetWeaver Gateway, which technically works as a hub system but must not be defined as such in the technical system editor of the LMDB.)


Page 11

Landscape Pattern Unknown

You have to define the landscape pattern Hub or Sidecar manually. Initially, all technical systems that are registered in the LMDB by an SLD get the landscape pattern Unknown. With this status, the Maintenance Optimizer will handle them like a hub system and calculate updates with minimal impact.

Example A: SAP ERP 6.0 EHP 5 with a Hub Deployment

In this example, an HCM application of SAP ERP (EHP5 FOR SAP ERP 6.0) is running on an AS ABAP-based backend system (product system F6W) and on a separate SAP NetWeaver Portal system (SAP EHP2 FOR SAP NETWEAVER 7.0) that provides the Employee Self-Services (product system F6X). Additionally, the Portal system is used by an SAP SRM 7.0 system (product system F7A).

The following list from the LMDB Product System Editor shows the involved product systems, product

versions, product instances, and technical systems. The three product systems shown are related by

the commonly used technical system:


Page 12

The following product systems have to be maintained in SAP Solution Manager LMDB:

Create product system F6W manually in LMDB to describe the HCM application. It contains the technical systems F6W and F6X. The product version EHP5 FOR SAP ERP 6.0 is installed on both technical systems.

EHP5 FOR SAP ERP 6.0 is an add-on product version that requires the standalone product version SAP ERP 6.0. Therefore one standalone product version (SAP ERP 6.0) and one add-on product version (EHP5) have to be assigned to product system F6W.

The following product instances are assigned product system F6W: Central Applications (SAP ECC Server), Portal Content, Portal Content Self Services, and SAP XSS (Self-Services).

Here you see the product instances for product system F6W:

Create product systems F7A and F6X manually in LMDB to describe the SRM application.


Page 13

Product system F7A contains the technical systems F7A and F6X. Product version SAP SRM 7.0 is installed on both technical systems.

For product version SAP SRM 7.0 you also need to create a separate product system for the SAP NetWeaver Portal.

EHP1 FOR SAP SRM 7.0 is an add-on product version that requires a standalone product version SAP SRM 7.0. The product instances SRM Server and Portal Content Supplier are assigned to the product system. In the LMDB product system editor, you can see all product instances for product system F7A if you choose the Technical System Assignment node:

Product system F6X: For product version SAP SRM 7.0, you also need to create a separate product system for the SAP NetWeaver Portal (SAP EHP2 FOR SAP NETWEAVER 7.0).

You can use the same Portal product system to implement new SAP NetWeaver Portal functionality available with a new enhancement package version for SAP NetWeaver 7.0 with the SAP ERP product system. The SAP SRM product system remains unchanged.

SAP EHP2 FOR SAP NETWEAVER 7.0 is a standalone product version. Therefore, do not assign the product version SAP NETWEAVER 7.0, in addition. The product instance Enterprise Portal is assigned to the product system F6X:

Technical system F6X with the Portal product instance is assigned to product system F6X (SAP Enterprise Portal) as well as to product system F7A (SAP SRM). Therefore, product system F6X (SAP Enterprise Portal) must be considered during the update of product system F7A (SAP SRM).

The technical system F6X is used by multiple product systems, therefore it needs to be maintained as a hub in the LMDB technical system editor:


Page 14

When you choose Related Product Systems in the LMDB product system editor, you can see all involved product systems, technical systems, product versions, and product instances at a glance:

Example B: SAP CRM with a Sidecar Deployment

This section shows an example of a sidecar deployment: An SAP Customer Relationship

Management (SAP CRM 7.0) application uses SAP Interactive Forms by Adobe.

The SAP CRM 7.0 application with Adobe Document Services (SAP NetWeaver 7.3) requires one

product system for SAP CRM (in this example, product system LGD). It uses the CRM AS Java

product instance from the technical system for SAP NetWeaver (in this example: A96).


Page 15

This is what the product system looks like in the product system editor of the LMDB:

Example product system LGD with its product instances:

As the AS Java technical system A96 in this example is only used by product system LGD in the landscape, the landscape pattern sidecar is assigned to the AS Java technical system. This has the effect that the SAP NetWeaver layer of technical system A96 is kept as consistent with the technical system LGD as possible: During updates of LGD, the SAP NetWeaver stack and the product stack of CRM 7.0 are both updated synchronously. As a result, both systems have the same technology level and SP stack level.

In the technical system editor of the LMDB, you can define the landscape pattern:


Page 16

4.4.2 Create and Verify Product Systems

4.4.2.1 Assign Technical Systems, Product Versions, and Product

Instances

When you create product systems – which must be done manually – in the LMDB of SAP Solution

Manager, assigning product instances (including their relation to technical systems and product

versions) is the central task.

Prerequisite: The SLD connection is active and the full automatic synchronization and thereby the

technical system information is complete.

Migrate product system information from SMSY to LMDB:

When you are updating to SAP Solution Manager 7.1, you can migrate selected information

about technical systems and complete product system descriptions – which cannot be

provided by the SLD – from the previous storage (Solution Manager System Landscape,

SMSY) to the new LMDB storage. This avoids manual recreation.

Goto transaction SOLMAN_SETUP under System Preparation Prepare Landscape

Description Migrate Data into LMDB.

Manually create product system information:

1. Start transaction LMDB, choose the Product Systems tab, enter the ID for the product

system and choose Create New Product System.

2. Select the Technical System Assignment step from the navigation tree.

3. Initially, the list is empty. To add product instances that belong to the product system,

choose Add.

4. Assign product instances relevant for the product system. For help, expand the help tray.

For more information, see Migrate System Information from SMSY to LMDB and Manage Logical

Landscape Information in the SAP Help Portal at http://help.sap.com/solutionmanager71.

https://help.sap.com/saphelp_sm71_sp05/helpdata/en/e7/101fc81c0642df8c75b0e15111b2a4/frameset.htm

https://ldcidp7.wdf.sap.corp:44370/sap/bc/webdynpro/sap/wd_sise_main_app?sap-language=ENhttps://help.sap.com/saphelp_sm71_sp05/helpdata/en/2f/f0a5a230e54d62921a282622536916/frameset.htm

https://ldcidp7.wdf.sap.corp:44370/sap/bc/webdynpro/sap/wd_sise_main_app?sap-language=ENhttps://help.sap.com/saphelp_sm71_sp05/helpdata/en/2f/f0a5a230e54d62921a282622536916/frameset.htm



Page 17

4.4.2.2 Verify Your Product System Information

When the product system information in LMDB is complete, you must make sure that the system

landscape in SAP Solution Manager Landscape Management Database (transaction LMDB) complies

with the rules described under System Landscape Modeling Rules. Only then, the Maintenance

Optimizer can work correctly.

The landscape verification function can detect incorrect assignments of product versions, instances, or

landscape patterns.

For known exceptions regarding the landscape verification function in LMDB, see SAP Note

1721112. It lists the cases for which there are error messages that can be ignored.

Proceed as follows:

1. Start transaction LMDB Product Systems choose a system choose Maintain choose

the Verification step at the bottom of the navigation tree.

2. To start the verification, choose Execute Verification Check. In the list with verification results, you see which corrections you need to make.

An error (red icon) means that your action is required. A warning (yellow traffic light) informs you that there are descriptions that are missing or incorrect but that do not influence the Maintenance Optimizer functionality.

Read the Message Text, which briefly explains the issue.

3. Choose the links in the Action column or the system name links to navigate to the area where a correction is required. You can also choose the system name in the Check Object column to navigate to the affected system.

4. After each correction, repeat the verification until all issues are solved.

For more information, see Verify Product Systems in the SAP Help Portal at

http://help.sap.com/solutionmanager71 Application Help SAP Solution Manager Operations

Managing System Landscape Information Manage Logical Landscape Information.


https://help.sap.com/saphelp_sm71_sp05/helpdata/en/22/ff7fecb79d40bea1960c8a6b837ba5/frameset.htm



Page 18

5. Selecting and Downloading Software Packages

The Maintenance Optimizer tool in SAP Solution Manager calculates the required enhancement

package files and creates the stack configuration file. The following sections describe the procedure in

detail.

Prerequisite: You have maintained the relevant product systems and verified them in the product

system editor of the LMDB. For more information, see Create and Verify Product Systems.

Detailed documentation: Maintenance Optimizer in the SAP Help Portal at http://help.sap.com/solutionmanager71 Application Help SP05 Maintenance Management.

5.1 Starting a Maintenance Transaction

Start a maintenance transaction for a selected product version in a product system directly from the

product system editor of the LMDB (transaction LMDB Product Systems Product System

Overview):

Here, you can also see and proceed with existing maintenance transactions, if there are some.

Alternatively, you can start transaction SOLMAN_WORKCENTER and choose the Change Management

Common Tasks New Maintenance Transaction.

In case of authorization issues, see Maintain Users for Maintenance Optimizer.

For the selected product version, a Maintenance Optimizer transaction with a unique identifier is created. The process consists of five steps, which are described in the following sections.




Page 19

5.1.1 Plan Maintenance

In the following, the typical work steps of the Maintenance Optimizer Transaction are described. For a detailed documentation, see http://help.sap.com/solutionmanager71 Application Help Change Request Management and Change Control Maintenance Optimizer.

To complete this work step of the Maintenance Optimizer transaction, proceed as follows:

1. Select the solution for which you want to download the software packages.

Select a product version for the selected solution.

For any enhancement packages for SAP ERP, select product version SAP ERP.

2. The related product systems are displayed. Select one or several product systems to be updated.

We recommend that you create a single stack configuration file for all product systems of a track (development system, quality assurance system, and production system). In addition, run your Maintenance Optimizer transactions for every affected system at the same time, in the same maintenance transaction. This way you ensure that all systems are upgraded with exactly the same software. If you run the same Maintenance Optimizer transaction at different points in time, it can include slightly different software because SAP changes support package stacks whenever a fix is available for a critical issue in the software. If you get the system message „There is already a transaction for the systems of this product version‟, check SAP Note 1296589.

3. Choose Continue.

The system checks the instances installed in your product system and determines the update options. This check is based on the product system settings that you made in the Landscape Management Database (LMDB).




Page 20

5.1.2 Select Files

To complete this work step of the Maintenance Optimizer Transaction, proceed as follows:

1. Choose Calculate Files Automatically as the file selection mode.

Check the Log tab regularly, to see if any issues have occurred. In addition, the Systems tab provides helpful information about the systems to be updated or upgraded.

2. Choose Continue. Decide which update option you want to pursue.

Select the Enhancement Package Installation update option if you want to install a new enhancement package. If you want to upgrade to an enhancement package, select the upgrade option Upgrade Enhancement Package Installation.

3. Choose Continue to proceed with the Choose Stack sub-step.

4. Select the Target enhancement package product version and Target enhancement package stack level.

Choose Stack Details to display a summary of the contents of the selected target stack.


Page 21

5. Select the technical usages.

A technical usage provides a set of business functions. Therefore, the decision which technical usages are to be installed depends on the business requirements. From a technical point of view, a technical usage consists of product instances that consist of software components. If you need help with the decision about technical usages, see the Business Function Prediction for SAP ERP on the SAP Service Marketplace at http://service.sap.com/bfp.

Technical usages already installed in the system are automatically selected. You can select additional technical usages.

The technical usages are grouped by instance. For example, the instance group Portal Content comprises all technical usages which contain the instance Portal Content. So a technical usage can be part of several instance groups.

You can display detailed information about technical usages by clicking on the link with the name of the technical usage. This shows you product instances of the selected enhancement package release, required product instances, product versions, and product systems.

You can only select technical usages for which required product instances are flagged as installed in the LMDB. Product instances for unavailable technical usages are highlighted in red.

You cannot select a technical usage if it includes software components that must run on an SAP NetWeaver Portal that is not installed in your system. For details about the mappings between technical usages, business functions, product instances and the software components check following SAP Notes: - SAP Note 1642789 Enhancement Package 2 for SAP CRM 7.0: Required SWC - SAP Note 1473026 Enhancement package 1 for SAP SCM: Required SWC - SAP Note 1585806 Enhancement package 2 for SAP SCM 7.0: Required SWC - SAP Note 1083576 SAP enhancement package 3 for SAP ERP 6.0 - required SWC - SAP Note 1324838 Enhancement package 5 for SAP ERP 6.0: Required SWC - SAP Note 1165438 Enhancement package 4 for SAP ERP: Required SWC - SAP Note 1566412 Enhancement package 6 for SAP ERP 6.0: Required SWC - SAP Note 1359215 Technical prerequisites for using enterprise services - SAP Note 1595753 Enhancement packages for SAP CRM 7.0: Required SWC - SAP Note 1052470 SAP ERP 6.0 EhP 2 - Business functions and SW components












Page 22

6. If you have assigned Java technical systems to your maintenance transaction, the Maintenance Optimizer also shows all installable Java instances in the section Additionally Installable Java Instances. Java instances that are relevant for the selected version of the target stack are pre-selected.

If you select additional Java instances, you can choose from a bigger selection of technical usages in the upper section Technical Usages.

7. Choose Continue to proceed with the Confirm Target sub-step.

8. Check and confirm the major target constellation of your system.

If at this step a connected SAP NetWeaver system (for example an SAP NetWeaver Portal, or an SAP Business Warehouse system) is supposed to be updated to a release that you did not expect, check if you have correctly maintained the landscape pattern of the technical system. See Assign Landscape Patterns.

9. Choose Continue to proceed with the Choose Add-on Products.

10. The Maintenance Optimizer lists the following selection options if add-ons are affected by the installation, upgrade, or update:

Add-ons already installed that you can update with the update, upgrade, or installation of the enhancement package

Add-ons that you can install with the update, upgrade, or installation of the enhancement package

Select the add-ons and the stack level hat you want to install. Previously installed add-ons are preselected.

Choose the add-on links to display the add-on instances and installable alternative (that is, the compatible software component versions).


Page 23

The Maintenance Optimizer provides the option to include add-ons directly into your maintenance operation, so that you use the same downtime window instead of installing the add-ons separately afterwards.

Add-ons are part of the stack XML file for target releases based on NW 7.0 EHP2 or higher, that is, add-ons are included as of SAP ERP 6.05 or higher.

11. Choose Continue to proceed with the Select OS/DB-dependent files sub-step.

12. Select the files that correspond with the combination of your operating system and database.

Also select the files for SAP IGS and SAP HOST AGENT and for the Software Update Manager (SUM) if they are provided for selection. For more information about the SUM option, see SAP Note 1626435.

If you run application servers on different operating systems, make sure that you also include their kernels files. Sliding the mouse pointer on the kernel files displays a quick info that explains for which system the kernel files were calculated.

13. Choose Continue to proceed with the Select Stack-Independent files sub-step.

14. Select the stack-independent files and files for the add-on upgrade or add-on installation. In most cases, the stack-independent files include a SPAM/SAINT update for the target release. If you decided to install new add-ons, the corresponding files are displayed.

A red asterisk indicates that there is no delivery package on the SAP Service Marketplace for a support package.

You can also select files from the download basket for this maintenance transaction manually by choosing Include/Exclude Files in Download Basket.

The Maintenance Optimizer downloads these files, but does not automatically import them. You have to import them manually.

15. Choose Continue to proceed with the Select Stack-Dependent files sub-step.

16. Decide how to deal with the stack-dependent files.

These files directly correspond to the technical usages that you have selected.

The support packages for the basis release are also displayed, the Maintenance Optimizer calculated them for the software components that you do not want to update with the enhancement package.

We recommend that you keep the selection. However, you can deselect any support package that you do not want to apply to your system. Components of an SP stack that are not in productive use do not need to be patched during the implementation of the SP stack, unless there is a technical or logical dependency to the productive components.

If deselection of support packages of a software component is disabled, the previously selected technical usages and the target support package level indirectly determine that these support packages are required.

Do not deselect the files for the software components SAP_BS_FND and WEBCUIF as

they are required for the enhancement package.



Page 24

17. To include current patches for Java support packages in your maintenance transaction, choose Add Java Patches.

The Maintenance Optimizer downloads these files, but does not automatically import them. You have to import them manually.

18. To add HR Support Packages or Country Legal Change Packages (CLC Packages) for an HR system selected as a product system to your maintenance transaction, choose Add HR Packages.

19. Choose Continue to proceed with the Confirm Selection sub-step.

20. To download the files, choose whether you want to download them with the Download Basket or with the Software Lifecycle Manager (only available if configured).

21. Choose Continue.

5.1.3 Download Files


1. A package configuration file containing your selections, based on your entries, is generated. Once you confirm the selection in the step Confirm Selection, this file is stored in the database in the SAP Solution Manager and at operating system level in the Electronic Parcel Service Inbox of the transport directory.

Download the XML stack file. The text file is only needed for an upgrade with source release SAP R/3 4.6C (see SAP Note 1022704).

2. Download the files as soon as you have completed the Maintenance Optimizer Transaction.

If you get a system message “Adjustment of stack delta XML done with error: check application log” at this step, either your SAP Solution Manager system does not have the latest SPAM level, or you have insufficient user authorizations to write the XML in the EPS/IN directory (see Maintain Users for Maintenance Optimizer).

3. Choose Continue.

5.1.4 Implement

To complete this work step of the Maintenance Optimizer transaction, proceed as follows:

1. Download the files according to the Maintenance Optimizer calculation.

2. Use the appropriate update tool, like the Software Update Manager (SUM), SAP Enhancement Package Installer (SAPehpi), SAP upgrade tools (SAPup and SAPJup) to implement the downloaded items. For more information, see www.service.sap.com/sltoolset.

3. After you have implemented the changes for the product system(s), change the Status of Implementation for Product System(s) to Completed.

4. Choose Continue.

5.1.5 End Maintenance


1. Choose Complete Transaction.

After you have completed this maintenance transaction you can no longer make any changes to it.

2. Choose Close.

For detailed information about the steps, see Maintenance Optimizer in the SAP Help Portal at http://help.sap.com/solutionmanager71 Application Help SP05 Maintenance Management.


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



Documents

sap solution manager 7.1 configuration