Maintenance Planning Guide For Sap Solution Manager 7.1 Sp05 And Higher 5w1d4d

PUBLIC

For SAP Solution Manager 7.1 SPS 5 and Higher Document Version: 3.0 – 2016-02-18

Maintenance Planning Guide Including Maintenance Optimizer

Content

1

About This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2

Prerequisites in SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.1

Updating SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.2

Installing Implementation Content Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.3

Completing SAP Solution Manager Basic Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.4

Maintaining s for SAP Solution Manager and SAP Portal. . . . . . . . . . . . . . . . . . . . . . . . . . 6

3

Synchronizing System Landscape Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3.1

ing Technical System Data in SLD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2

Synchronizing SAP Solution Manager with SLD and Other Repositories. . . . . . . . . . . . . . . . . . . . . . . . 10

4

Modeling System Landscapes in SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

4.1

Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

4.2

System Landscape Modeling Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.3

Landscape Patterns (Upgrade Strategy for AS Java). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.4

Maintaining System Tracks with Maintenance Optimizer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.5

Creating Product Systems in SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Creating Product Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 ing Product System Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Creating a Product System for a Dual-Stack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5

Executing a Maintenance Optimizer Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

5.1

Step 1: Plan Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5.2

Step 2: Select Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.3

Step 3: Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.4

Step 4: Implement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5.5

Step 5: End Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

6

Correcting Installed Software Information (CISI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

7

Copying Stack Configuration Files for Identical Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

8

Special Cases in Installation and Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

2

PUBLIC © 2016 SAP SE or an SAP company. All rights reserved.

Maintenance Planning Guide Content

1

About This Document

The Maintenance Planning Guide describes the steps to maintain system landscape description in SAP Solution Manager 7.1 (SP05 and higher) in order to carry out consistent updates and upgrades of software. The guide is intended for technology consultants, system s, and specialists. The guide describes how to create consistent installed software information (ISI) for the involved technical systems. The information must be consistent in all places: ● in the technical systems ● in the System landscape Directories (SLDs) ● in SAP Solution Manager ● in SAP Portal The Maintenance Optimizer in SAP Solution Manager plays a central role to successfully upgrade and update the technical systems on that an SAP product is installed. It uses the system descriptions managed in SAP Solution Manager to calculate the required enhancement package files, package stacks, and additional update packages. For this calculation, the system information must match the information in the SAP Portal. Maintenance Optimizer 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.

Sources of Information ● Documentation for System Landscape Management (LMDB) in the SAP Community Network at http:// scn.sap.com/docs/DOC-29495 ● Maintenance Optimizer documentation in the SAP Help Portal at http://help.sap.com/solutionmanager71 under

Application Help

select SP and language

Maintenance Management

Maintenance Optimizer

● Maintenance Optimizer information in SAP Service Marketplace at http://.sap.com/mopz ● System Landscape Directory (SLD), especially the Planning Guide, in the SAP Community Network at http:// scn.sap.com/docs/DOC-8042 ● Specifics in Installation and Upgrade ● Maintenance of Products in the System Landscape ● Planning Landscape Changes - A Best Practice Guide

Maintenance Planning Guide About This Document


3

2

Prerequisites in SAP Solution Manager

Before you can manage system landscape information in SAP Solution Manager, install the latest version with the required add-ons, complete the setup, and maintain the authorizations.

2.1

Updating SAP Solution Manager

As of SAP Business Suite EHP4, Maintenance Optimizer is mandatory to update and upgrade software. Always update SAP Solution Manager to the latest package.

Procedure To check the current version of your SAP Solution Manager system, logon to the system in SAP GUI. Choose System Status Component Information . For software component ST, the release must be at least 400, the SP level at least SP23. If you are not using the required SAP Solution Manager version, update the application. As of SAP Solution Manager 7.1, the Landscape Management Database (LMDB) replaces transaction SMSY as the new repository for system information and landscape descriptions. You can migrate all system landscape information from the old to the new repository. Update Maintenance Optimizer according to SAP Note 1940845

.

More information: ○ SAP Note 1583348 ○ Master Guide SAP Solution Manager 7.1 at http://service.sap.com/instguides SAP Solution Manager

Release 7.1

under

SAP Components

Planning .

○ Migrate System Information from SMSY to LMDB in the SAP Help Portal at http://help.sap.com/ solutionmanager71 under Information

2.2

Application Help


Managing System Landscape

Set Up the Landscape Management Infrastructure

Installing Implementation Content Add-On

We recommend that you install the implementation content add-on (ST-ICO) for SAP Solution Manager. It provides information on how to implement and configure business scenarios and processes. This includes

4


Maintenance Planning Guide Prerequisites in SAP Solution Manager

scenario and process descriptions, integrated configuration information ed by SAP implementation, operations, and upgrade roaps.

Procedure 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 information for the software component ST-ICO.

Status

Component Information

and check the level

More information: ○ SAP Note 631042 ○ SAP Solution Manager for the SAP Business Suite 7i2011 at https://service.sap.com/~sapidb/ 011000358700000363412010E .

2.3

Completing SAP Solution Manager Basic Configuration

To use SAP Solution Manager for maintenance processes, complete the basic configuration.

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

Note Diagnostics Prerequisites in the Installation Check step and Diagnostics Configuration in the Automatic Configuration step do not influence the selection and of enhancement package files. You may therefore omit these activities at this point. 4. Check if the latest version of SAP Note 1590226 Maintenance Optimizer version is available.

is implemented in your system. It ensures that the latest

Next Steps Initial SAP Solution Manager Configuration is described in the Solution Operations Guide for SAP Solution Manager, section Software Change Management, at http://service.sap.com/instguides Components

SAP Solution Manager


Release 7.1

under

SAP

Operations .


5

2.4

Maintaining s for SAP Solution Manager and SAP Portal

To perform maintenance transactions in SAP Solution Manager, the needs several roles and authorizations in SAP Solution Manager and in SAP Portal.

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

Procedure 1. Your in the SAP Solution Manager system requires the following roles: ○ SAP_MAINT_OPT_: 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 comparison to ensure that the authorizations were assigned to the s. More information: ○ SAP Note 1032322 for details about additional authorization checks for Maintenance Optimizer, for example, how to restrict specific transactions or functions ○ Security Guide for SAP Solution Manager for additional information about standard roles at http:// service.sap.com/instguides

under

SAP Components


Release 7.1

Operations . 2. Check if you have an s- for SAP Portal. If you do not have one, request it at http:// .sap.com/- under Request a new . To use Maintenance Optimizer and to order software from the SAP Software Catalog, your s- needs the SWCATALOG authorization. Check your authorizations under http://.sap.com/- . Log on with your s-, and choose Search and Maintain s. The authorization for the Execute Maintenance Optimizer activity must be assigned; the permission name is SWCATALOG: Order Software in Software Catalog. 3. Your in SAP Solution Manager must be assigned to your s- for the SAP Portal. Proceed as follows: ○ In your SAP Solution Manager system, start transaction AIS. There is only a value help for the Person field if the background job REFRESH__DATA_FROM_ has already been run. If this is not the case, manual entries cause a warning message because the s- is not found. First, assign the for the system

6



. When the has run the background job, maintain the s for all other project . ○ Choose New Entries. Under , enter an SAP Solution Manager system ; under Person, assign a for the SAP Portal, which is an s- ID without the ‘s’.

Note If three instead of two columns are visible in transaction AIS , 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 as follows: 1. Start transaction SPRO in the SAP Solution Manager system. You find the BAdI in the SAP Reference IMG under


SAP Customer Numbers

Basic Settings

Connection to SAP

Several

Business Add-In to Manage Several SAP Customer Numbers .

2. The dialog asks you whether you want to deactivate the BAdI implementation AI_SDK_SP_RFC_RP AI_SDK_SP_RFC_RP. Choose Yes. 3. Check transaction AIS. It now shows only two columns. For more information on Maintenance Optimizer, see http://.sap.com/mopz


.


7

3

Synchronizing System Landscape Data

Information about installed software and hardware of a technical system is used by several consumers in the system landscape. So, it is regularly updated and synchronized in the landscape. 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 (products, product versions, their software components etc.). As the system information is updated automatically, the SLD provides reliable and up-to-date information as the central information provider for SAP Solution Manager. 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 Landscape Management Database of SAP Solution Manager (LMDB, transaction LMDB). The verification function for product systems in the LMDB helps you to detect and correct errors in the system landscape description of SAP Solution Manager.

Figure 1: Flow of information about a system landscape

The graphic shows the central steps how system landscape data is maintained and used: 1. technical systems in your system landscape in the central SLD with automatic data suppliers that are set up on the technical systems. Technical systems periodically send information to the SLD. 2. To send technical system information from the SLD to SAP Solution Manager, setup the synchronization connection in SAP Solution Manager. Updated system information is synchronized at least every ten minutes and stored in the Landscape Management Database (LMDB).

8


Maintenance Planning Guide Synchronizing System Landscape Data

To complete landscape descriptions, create product system descriptions in LMDB, manually, and run verifications. 3. Use verified landscape descriptions with other SAP Solution Manager applications, such as the Maintenance Optimizer. In maintenance transactions, you can create stack XML files with which the SAP Global Backbone (SAP Portal) can calculate the basket for updates and upgrades. 4. With the correct system information, applications can monitor and maintain systems in the landscape. More information: ● System Landscape Directory at http://scn.sap.com/docs/DOC-8042 ● Planning Guide - System Landscape Directory at http://scn.sap.com/docs/DOC-14151

3.1

ing Technical System Data in SLD

Use automatic data suppliers to regularly technical systems in the central System Landscape Directory (SLD). Thereby, information about current hardware and installed software is sent to the SLD and can be forwarded to SAP Solution Manager.

Context Depending on your system landscape setup, data can be sent automatically to the SLD from the following systems: ● Application Server ABAP systems are ed using transaction RZ70. ● Application Server Java systems are ed with the Visual or, as of SAP NetWeaver 7.1, the NetWeaver . ● A dual-stack is ed automatically when the related AS ABAP and the AS Java have been ed. ● TREX systems are ed 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.

Procedure Set up the data suppliers for technical systems und them in the SLD, which is described in SAP Note 1869701 . For more information, see the Planning Guide - System Landscape Directory at http://scn.sap.com/docs/ DOC-14151



9

3.2

Synchronizing SAP Solution Manager with SLD and Other Repositories

SAP Solution Manager receives most of the technical system information from a System Landscape Directory (SLD), which receives the information from SLD data suppliers on the technical systems. SAP Solution Manager uses system information in internal and external applications, like the SAP Portal.

Context The SLD synchronization connections are set up during SAP Solution Manager Configuration (transaction solman_setup). For information on the setup, see the following documents at http://help.sap.com/solutionmanager71 under Application Help Information


SAP Solution Manager Operations

Managing System Landscape

Set Up the Landscape Management Infrastructure :

Procedure 1. Connecting LMDB to System Landscape Directory (SLD) 2. Synchronizing with SAP Portal 3. Synchronizing with Transport Management System (TMS)

Next Steps To check if the data that SLD data suppliers send is consistent for LMDB requirements, see SAP Note 1842956 (Check Data Supplier Consistency for Technical System in LMDB).

10



4

Modeling System Landscapes in SAP Solution Manager

With the automatically provided technical system information as a basis, you can model the logical landscape in SAP Solution Manager. Define, for example, which product instances on which technical systems belong together to form a product system. This information is crucial for the maintenance process. For very basic considerations, see Landscape Recommendations

4.1

in the SAP Community Network.

Terminology

When we are talking about system maintenance, it is very helpful to understand the basic SAP terminology used in this context. From a maintenance view, the focus is on product systems which are modeled in SAP Solution Manager. The following graphics illustrate, where product systems are embedded in the SAP solution landscape and of which important elements a product system consists.

Maintenance Planning Guide Modeling System Landscapes in SAP Solution Manager


11

Table 1: Modeling Product Systems - Terminology Term

Description

product

SAP Products are the applications SAP ships and group sets of functions to solve busi ness 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) at https://.sap.com/pam

). The product model de

fines the product structure with its product instances, software component versions, 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 main tenance 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.

12



Term

Description

product version

Each SAP product is installed in a product version, which is a concrete release of a prod uct, 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 mainte nance of product systems. For each product version, a maintenance period is defined. One product system must have one standalone product version. Example: SAP ERP 6.0, which is a product version of the product SAP ERP.

Note There are standalone product versions (for example, SAP ERP 6.0) and add-on prod uct versions, which require another product version as foundation for their installa tion and operation (for example, EHP5 for SAP ERP 6.0). For more information about add-on product versions, see Asg Technical Systems, Product Versions, and Product Instances [page 24]. technical system

Installing a product version on hardware, on one or several physical or virtual hosts, cre ates 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 istered as a whole. Often, e.g. in AS ABAP 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. Automatic data suppliers on the technical system send information about hardware and software to the SLD, for further distribution in the landscape. Virtual hosts themselves by diagnostics agents. For more information.

product system

●

SAP Note 1365123

●

Agent Data in the SAP Solution Manager LMDB

●

How to create a virtual system in Solution Manager 7.1

(especially the attached demonstration)

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 as sociated product systems to maintain SAP products. On the technical systems of a product system, one standalone product version and ei ther 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.



13

Term

Description

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 compo nent of the product. A software component version can be part of several product in stances. 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 Man ager. One product instance must be installed and updated as a whole on a single techni cal 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.

Note There are some exceptions to this rule. Some product instances (for example in SAP Process Integration) are installed on both the AS ABAP and AS Java technical sys tems. 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 ed separately in the System Landscape Directory (SLD). Examples: SAP ECC Server, SAP XSS (Self-Services), and TREX. Synonyms: main instance (in SAP Solution Manager transaction SMSY), software unit (in System Landscape Directory) dual-stack

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

Common SID for all application servers and the database

●

Common startup framework

●

Common database (with different schemas for ABAP and Java)

All parts (technical systems and installed product instances) of a dual-stack must com pletely be assigned to one product system. It is no longer recommended to install dual-stacks. Existing dual-stacks are recom mended to be split into individual technical systems. For more information, see the Dual-Stack Split – How to Ensure Correct Technical System Data in SLD and LMDB af ter the Split

14

.



Term

Description

technical usage

Technical usage is a further qualification describing a specific configuration of a product version. It describes a set of business functions by bundling product instances, consist ing of software components, for a distinct usage. It can be spread over multiple techni cal systems and technology types. Not all product versions have this additional group ing. There is a mapping between business functions and technical usages for ERP en hancement packages.

More information: ● White Paper: The SAP Solution Landsape ● SCN: Understanding Landscape Descriptions - Part I: the Simple Approach to Explaining Products, Product Instances, and Software Components ● Master Guide for SAP ERP 6.0 Enhancement Package 7 Components: Architecture Overview

4.2

, section Enhancement Packages and Software

System Landscape Modeling Rules

This section explains the basic rules to model a landscape description in SAP Solution Manager. 1. A standalone product version is installed on one or more technical systems, which are all described in one product system. Only one active standalone product version and its technical systems can be described in one product system. This ensures a consistent update of a complete product version. (The dual-stack 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 and Special Cases in Installation and Upgrade .) 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 add-on EHPs (such as SAP ERP 6.0 EHP 6) and standalone EHPs (such as SAP EHP3 FOR SAP NETWEAVER 7.0. 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 Process Integration). If such a product instance is installed, you have to link it to the relevant Java technical system. 4. A landscape pattern must be assigned to an AS Java system. A landscape pattern defines the upgrade strategy for an Application Server Java in SAP Solution Manager. When the technical system is assigned to one product system, the landscape pattern sidecar is assigned, when it is reused in several product systems, hub is assiged. For more information, see Landscape Patterns (Upgrade Strategy for AS Java) [page 16].

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



15

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 For more information, see SAP Note 1326576

, 1531022

, and Special Cases in Installation and Upgrade

.

SAP NetWeaver ERECRUIT, LSOFE, 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 product system and the corresponding instance must be marked as installed. For more information, see SAP Note 1326576

, 1531022

, and Special Cases in Installation and Upgrade

.

SAP SEM-BW now can be installed independently of the SAP ERP product system. For more information, see Special Cases in Installation and Upgrade . The LMDB s you in creating consistent product systems: When you create a product system in SAP Solution Manager, 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 a product system. This, of course, requires that the SAP Solution Manager is provided with reliable technical system information by SLDs. For more information, see Creating Product Systems in SAP Solution Manager [page 22]. 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 ing Product System Information [page 26].

4.3

Landscape Patterns (Upgrade Strategy for AS Java)

In the Landscape Management Database (LMDB), you need to set the upgrade strategy for a technical system of type Application Server (AS) Java, so that the correct upgrade strategy can be defined in maintenance transactions.

Context The assignment of landscape patterns is required for AS Java technical systems in a product system/ maintenance dependency (= landscape pattern 'sidecar') or several product systems(maintenance dependencies (=landscape pattern 'hub') in which also ABAP technical systems are assigned. The landscape pattern decides

16



which maintenance strategy will be used. In the LMDB, you can change the assignment on the overview screen of the technical system:

A sidecar AS Java is connected to exactly one ABAP-based backend system. During an upgrade, Maintenance Planner handles the technical system innovation-driven, 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 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 AS Java is connected to more than one ABAP-based backend system via a product system. During upgrades, Maintenance Optimizer updates the shared system with minimal impact: Only updates of the selected application are installed, while the underlying SAP NetWeaver and other applications are upgraded to the minimally required version. 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 (for example, 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. Landscape Pattern Unknown You have to define the landscape pattern Hub or Sidecar manually. Initially, all technical systems that are ed 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: Two Independent Product Systems



17

In the simplest case, only one technical system with all its product instances is used in one product system:

Example B: SAP CRM with a Sidecar Deployment This is an example of a sidecar deployment: An SAP Customer Relationship Management (SAP CRM 7.0) application uses SAP Interactive Forms by Adobe:

In the LMDB, the product system looks like this:

18



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). 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. Example C: 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 Portal system (SAP EHP2 FOR SAP NETWEAVER



19

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 most convenient way to display all relationships in the LMDB is selecting one of the involved product systems and to choose Related Product Systems:

In this example, the following product systems have to be maintained in the LMDB:

20



● Product system F6W describes the ERP application, which consists of the standalone product version (SAP ERP 6.0) and the add-on product version EHP5 FOR SAP ERP 6.0, which cannot be installed without the standalone version. Product system F6W refers to two technical systems: ○ F6W (ABAP), on which the ECC Server and the Central Applications are isntalled ○ F6X (Java), on which the ERP Portal content is installed So the following product instances are assigned product system F6W: Central Applications, SAP ECC Server, 2x Portal Content, Portal Content Self Services, and 2x SAP XSS (Self-Services). ● Product system F7A describes the SRM application. It contains the standalone product version SAP SRM 7.0 and the add-on product version EHP1 FOR SAP SRM 7.0, which cannot be installed without the standalone version. Product system F7A refers to two technical systems: ○ F7A (ABAP), on which the SRM Server is installed ○ F6X (Java), on which the SRM Portal content is installed So the following product instances are assigned product system FA7: 2x SRM Server, Portal Content, and Portal Content Supplier. ● Product system F6X only describes the SAP EHP2 FOR SAP NETWEAVER 7.0 product version. (It is a standalone product version, so do not assign the product version SAP NETWEAVER 7.0, in addition.) The Enterprise Portal product instance, which is installed on the technical system F6X (JAVA) is assigned to this product system. Having all the SAP NetWeaver Portal instances on a separate technical system, which is described by an own product system, enables you to maintain the SAP NetWeaver parts independently from the ERP or SRM product systems. You can use the same Portal product system to implement new SAP 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. Because the technical system F6X is used by several product systems, it needs to be maintained as a hub in the LMDB technical system editor.

4.4

Maintaining System Tracks with Maintenance Optimizer

There are specific requirements for the update of a system track that consists of development, test, production, and other systems.

Context To update a single system, Maintenance Optimizer provides all files and the stack configuration file, which can be handed over to the installation tool to apply the files. This works for a single system. But a system track can consist of many individual systems for development, quality assurance, production etc. Thereby, the following issues arise: ● Different stack levels of the systems in a track The productive system probably is on the lowest stack level because it is not updated that often. The quality assurance system could be the same or higher as the productive system, and the development system most likely has the highest stack level of the track because it is regularly patched and updated. Therefore the stack configuration files generated by Maintenance Optimizer can be different if they are generated separately from each other.



21

● Different number of activated business functions on systems in a track Most likely, the smallest number of activated business functions can be found on the productive system, a higher number on the quality assurance system, and an even higher number on the development system. Therefore, the generated stack configuration file for the development system is not necessarily relevant for the other systems.

Procedure To maintain a system track consistently, include all systems of one track in one Maintenance Optimizer transaction. Produce a single stack configuration file for the whole track. Do not generate a separate stack configuration file for every single system of a system track. This ensures the consistency of the patch or upgrade throughout all systems and prevents extra work. You can assign technical usages separately for each system of the track during the maintenance transaction.

Note We recommend that you do not implement Legal Change Packages during the patch phase of a system track. This can cause inconsistencies between the different systems of a track and invalidate the generated stack configuration file for the whole system track. Information about Legal Change Packages is provided using SAP Notes (“planned legal changes”).

Next Steps Software changes must be tested in every configuration, by all involved s and parties. Implementing new software in the production system must be the last step. For more information, see SCN: Maintenance of system tracks with Maintenance Optimizer

4.5

.

Creating Product Systems in SAP Solution Manager

With the technical system information, you can now start to model the product system descriptions for the logical system landscape in SAP Solution Manager. As of SAP Solution Manager 7.1 SP05, technical systems and product systems are maintained in the LMDB, but no longer with transaction SMSY.

Context The following table shows the steps in which transaction SMSY was replaced by the LMDB over the last SAP Solution Manager versions:

22



Table 2: Introduction of the New System Repository for Landscape Data - Landscape Management Database (LMDB) SAP Solution Manager 7.0

SAP Solution Manager 7.1 SP01-04

SAP Solution Manager 7.1 SP05 and higher

Product and technical system informa tion is maintained in SMSY.

Product system information is maintained in transaction SMSY. Technical system in formation is maintained in the new Land scape Management Database (transaction LMDB).

Product and technical system infor mation is maintained in the LMDB. Landscape verification is integrated ito the LMDB editor for product systems.

Note Prerequisite: You have completed the activities described under Synchronizing SAP Solution Manager with SLD and Other Repositories [page 10]. It is strongly recommended, that technical system information is provided automatically by SLD data suppliers. Manual entries in the LMDB must be avoided since they can lead to inconsistencies and hinder later automatic updates by the SLD. If no product versions and product instances are reported, the following Wiki shows how to manually model different products in the LMDB: http://wiki.scn.sap.com/wiki/x/4I-uDQ . Some information cannot be delivered by the SLD, you need to maintain it manually in the LMDB, for example the landscape pattern, custom attributes, and the complete product system information. To view system descriptions, start SAP Solution Manager: Work Centers (transaction SOLMAN_WORKCENTER and choose

Solution Manager istration

Landscape

Technical Systems

or Product Systems, for example.

Alternatively, you can access the LMDB data directly with transaction LMDB. For more information, see the SAP Help Portal at http://help.sap.com/solutionmanager71 under Help

select language and SP


Application

Managing System Landscape Information

Managing Product Systems If a product system must be defined depends on the type of the technical system that is to be updated. For the following technical system types must be updated with Maintenance Optimizer and require a product system: ● Application Server ABAP ● Application Server Java ● SAP HANA Database ● TREX System For the following technical system types, no product system is required, because maintenance with Maintenance Optimizer is not ed or not required: ● SAP BusinessObjects Cluster ● Sybase Unwired Platform ● SAP NetWeaver Master Data Management Server (MDM) ● SAP Identity Management (IDM)



23

4.5.1 Creating Product Systems In contrast to technical system information, which is automatically provided by data suppliers, you need to create product system information manually in the LMDB of SAP Solution Manager. It defines, which technical systems and product instances need to be updated and upgraded together in maintenance processes.

Prerequisites The SLD connection is active and the full automatic synchronization and thereby the technical system information is complete.

Tip Migrate existing 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 re-creation. To do so, start transaction SOLMAN_SETUP and choose Landscape Description

Migrate Data into LMDB

System Preparation

Prepare

.

To configure a product system that consists of more than one technical system, a rough sequence should be followed: 1. Assign the primary (most important) AS ABAP technical system. Create the product system from the primary AS ABAP technical system first, using the extended system ID as product system name. If no AS ABAP is part of the product system, start with the primary technical system of a different type and use the extended SID of this system as product system name. To do so, start transaction LMDB, select the technical system in edit mode, and choose Assign to Product System under Software. Check the product instances that are marked as installed for any technical system before you add it to a product system. The product instances for which the Installed indicator is set in the technical system serve as starting point for the product instance assignment in the product system editor. If no such indicator is set, assign the relevant product instances only in the product system editor. 2. Assign secondary AS ABAP technical systems. 3. Assign non-AS-ABAP technical systems.

Context When you create product systems, asg product instances (including their relation to technical systems and product versions) is the central task. Regular verification checks help you to make a product system consistent so that it can be used in maintenance transactions. If no product versions and product instances can be reported by automatic data suppliers, the following Wiki shows how to manually model different products in the LMDB: http://wiki.scn.sap.com/wiki/x/4I-uDQ .

24



To create new product systems, proceed as follows:

Procedure 1. You can use the following starting points: ○ Start from the existing technical system: ○ Start transaction SOLMAN_SETUP and choose Managed Systems Configuration. Select the related technical system, choose Configure and create a product system in the first step of the guided procedure. ○ Start transaction LMDB and select the related technical system for editing. Choose

Software

Edit

Product System Assignment . ○ Start directly with the product system: Start transaction LMDB and select Product Systems, enter the product system name, and choose Create. Under Assigned Technical Systems, choose Add to add the involved technical systems and product instances. 2. Assign technical systems and their product instances: In each case, a dialog box opens, ing you with proposals on which product instances to assign. For more information, read the help text in the dialog. As of SAP Solution Manager 7.1 SP10, you can also create product systems automatically in the Managed System Configuration and in the LMDB editor for product systems. Also, if not all product instances are provided by data suppliers, the improved search for more proposals simplifies the product system creation: It suggests product instances based on software component information from the system and the SAP Portal. For more information, see Evolution of Landscape Data Management – Part II: What’s better with LMDB in SAP Solution Manager 7.1, SPS10? . 3. the product system description. The verification function in the editor for product systems checks the consistency of the product system definition. To do so, functionality from the SAP Portal is accessed with a remote service. Perform a new verification check whenever you make changes to a product system and always before you start a maintenance transaction. 4. Updating product system information Until SAP Solution Manager 7.1 SP08, you must manually create and update product system information. As of SP10, product system information is updated automatically as soon as the information for related technical systems is updated with the next SLD synchronization; the LMDB updates the assigned product instances and the indicator for diagnostics-relevance. For more information, see SAP Note 1832868 .

Next Steps For more information, see Managing Product System Information in the SAP Help Portal at http://help.sap.com/ solutionmanager71 under

Application Help





Managing Product System Information .


25

4.5.2 ing Product System Information When the product system information in LMDB is complete, that the system landscape in SAP Solution Manager complies with the modeling rules. Only then, Maintenance Optimizer can work correctly. As of SAP Solution Manager 7.1 SP05, the verification feature is included into the editor for product systems in the LMDB.

Context The most important check criteria are described described under System Landscape Modeling Rules [page 15]. The landscape verification function can detect incorrect assignments of product versions, instances, or landscape patterns.

Procedure 1. You can see the verification status of all your product systems in the Solution Manager istartion work center (transaction sm_workcenter) under

Landscape

Product Systems . From here, you can also edit

and the product systems. In the product system editor of the LMDB, choose the Verification step at the bottom of the navigation tree. 2. To start the verification, choose Execute Verification Check. In the result list, you see the required corrections. An error (red icon) means a mandatory correction. A warning (yellow traffic light) informs you that there are missing or incorrect product system descriptions that, however, do not influence Maintenance Optimizer.

Caution For known exceptions regarding the landscape verification function in LMDB, see SAP Note 1721112 . It describes the cases for which error messages appear that can be ignored or must be handled in a different way. 3. To read the error description, choose the info button. 4. Many errors can be directly corrected by choosing the link in the Action column. 5. After each correction, choose Execute Verification Check, again, and take care of the remaining errors.

26



Next Steps For more information, see in the SAP Help Portal http://help.sap.com/solutionmanager71 under Help



Managing Product System Information

Application


ing Product Systems .

4.5.3 Creating a Product System for a Dual-Stack Dual-stacks are systems where an Application Server ABAP and an Application Server Java are installed on the same technical system. In SAP Solution Manager, they are represented by two technical systems and maintained in one product system.

Context Both technical systems representing the dual-stack parts have the same system ID and the same message server.

Note The installation of dual-stacks is only recommended for selected scenarios where this is mandatory: for example, for SAP Solution Manager 7.0 and 7.1, and for SAP Process Integration 7.11. Apart from that, it is no longer recommended to install dual-stacks. Split existing dual-stacks into individual technical systems. For more information, see Dual-Stack Split – How to Ensure Correct Technical System Data in SLD and LMDB after the Split .

Procedure A dual-stack can be created in SAP Solution Manager automatically or manually: ○ Automatic activity: The two dual stack parts are ed as two technical systems and as one technical scenario in SAP Solution Manager. By default, the two parts of a dual-stack are automatically ed as a technical scenario consisting of an AS ABAP and a AS Java technical system. When you display one of the technical systems in the LMDB, you can see the dual-stack partner in the Overview screen. ○ Manual activity: For dual-stacks, create one product system and assign both stacks, this is, the technical systems. To assign the right dual-stack partners, it is recommended that you select the technical scenario under

SAP Solution Manager Configuration (transaction solman_setup)

Technical Scenarios

Managed Systems Configuration

Configure Scenario .

Switch to edit mode, select a dual-stack part, choose for the second dual-stack part as well.


Edit

Assign to Product System

and save. Do this


27

It is important to assign both technical systems and all their installed product instances to the same product system. Thereby, one product system represents the complete dual-stack. Otherwise, you could damage the installation during an upgrade or update.

Next Steps The next transaction with Maintenance Optimizer will calculate a stack XML file for the complete dual-stack.

28



5

Executing a Maintenance Optimizer Transaction

Maintenance Optimizer in SAP Solution Manager calculates the required enhancement package files and creates the stack configuration file. In the following, the typical work steps of a Maintenance Optimizer transaction are described. For a detailed documentation, see http://help.sap.com/solutionmanager71 under language


Application Help

select release and

Maintenance Optimizer .

Prerequisite: You have maintained the relevant product systems and verified them, as described under ing Product System Information [page 26]. The following sections describe the maintenance transaction in detail. Detailed documentation: ● In the SAP Help Portal at http://help.sap.com/solutionmanager71 under

Application Help

select release

and language ○ Change Control Management ○


Maintenance Optimizer

● Maintenance Optimizer at http://.sap.com/mopz To start a maintenance transaction in Maintenance Optimizer. you have the following option: ● Start transaction LMDB. Choose the Product Systems tab and select the product system that you want to update. In the Overview, for a selected product version, choose the link under Maintenance Transactions. You can either proceed with an existing maintenance transactions, or create a new one:

Maintenance Planning Guide Executing a Maintenance Optimizer Transaction


29

● Alternatively, you can start transaction SOLMAN_WORKCENTER and choose Common Tasks

Change Management

New Maintenance Transaction .

In case of authorization issues, see Maintaining s for SAP Solution Manager and SAP Service Marketplace [page 6].

5.1

Step 1: Plan Maintenance

You are in the Plan Maintenance work step of Maintenance Optimizer. Here, you select the solution, product version, and product systems that you want to update or upgrade.

Context

30



Procedure 1. Select the solution for which you want to the software packages. Select a product version for the selected solution.

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

Note 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 Maintenance Optimizer transaction several times for a product, the calculated stack XML files can include different software because SAP changes package stacks whenever a fix is available for a critical issue in the software. Always apply the latest, stack XML file that you produced. 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).

5.2

Step 2: Select Files

You are in the Select Files work step of Maintenance Optimizer. Here, you decide about the content of the stack configuration file that you need for the upgrade or update.

Context

Note 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. Choose Calculate Files Automatically as the file selection mode.



31

Procedure 1. Sub-Step: Choose Stack 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.

Select the technical usages. See also: Defintion of 'technical usage' under Terminology [page 11] and Innovation Discovery for SAP Products . Technical usages that are already installed on the system are automatically selected. You can select additional technical usages.

The technical usages are grouped by instance. For example, the Portal Content instance group comprises all technical usages which contain the Portal Content instance. 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.

32



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.

Note You cannot select a technical usage if it includes software components that must run on an SAP 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

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



33

If you select additional Java instances, you can choose from a bigger selection of technical usages in the upper Technical Usages section . Choose Continue 2. Sub-Step: Confirm Target Check and confirm the major target constellation of your system.

Note If at this step a connected SAP NetWeaver system (for example an SAP 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 Landscape Patterns (Upgrade Strategy for AS Java) [page 16]. 3. Sub-Step: Choose Add-On Products (if available) Now choose the add-on products. 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 SP stack level hat you want to install. Previously installed add-ons are preselected.

34



Note Choose the add-on links to display the add-on instances and installable alternative (that is, the compatible software component versions). 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.

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

Choose Continue. 4. Sub-Step: Select OS/DB-Dependent files Select the files that correspond with the combination of your operating system and database. Also select the files for SAP IGS, SAP HOST AGENT, SAPJVM, 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. Choose Continue. 5. Sub-Step: Select Stack-Independent Files 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.

Note A red asterisk indicates that there is no delivery package on the SAP Service Marketplace for a package. You can also select files from the basket for this maintenance transaction manually by choosing Include/Exclude Files in Basket.



35

Note The Maintenance Optimizer s these files, but does not automatically import them. You have to import them manually. Choose Continue. 6. Sub-Step: Select Stack-Dependent Files In this step, Maintenance Optimizer offers installation files for optional, alternative software component versions. These files directly correspond to the technical usages that you have selected. Alternative software component versions are, for example, SAP JAVA DATA DICTIONARY 7.0, 7.01 and 7.02 for the SAP XECO product instance, and SAP SHARED JAVA APPLIC. 7.30, 7.31, and 7.32 for SAP XECO NW 7.3. Maintenance Optimizer only offers alternative software component versions for which the following conditions apply: ○ It is still in maintenance. ○ It is newer than the installed one. ○ It is consistent with other selected alternative software component versions of the product instance. By default, Maintenance Optimizer pre-selects the existing software component versions. We recommend that you keep the selection. But if required, you can select a higher, alternative version to add it for the installation, and you can deselect versions 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 is disabled, the previously selected technical usages and the target package level require these packages. Note the messages (including long texts) in the log for recommendations. Examples: ○ If BI_CONT 736 is installed in the system and BI_CONT 735, 736 and 737 are defined in the SP stack, then 735 will not be provided for selection, 736 will be pre-selected as recommendation (because 736 is the currently installed version), and 737 will also be provided for selection. ○ If no BI_CONT is installed and BI_CONT 736 and 737 are defined in the SP stack, then 737 will be preselected as recommendation (because it is the latest version) and 736 will also be provided for selection.

Note Do not deselect the files for the software components SAP_BS_FND and WEBCUIF. They are required for the enhancement package. To include current patches for Java packages in your maintenance transaction, choose Add Java Patches. To add HR 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.

Note Maintenance Optimizer s the selected files, but does not automatically import them. You have to import them manually.

36



Choose Continue. 7. Sub-Step: Confirm Selection To the files, select whether you want to them with the Basket or with the Software Lifecycle Manager (only available if configured). Once you confirm the selection, this file is stored in the database of SAP Solution Manager and at operating system level in the Electronic Parcel Service Inbox (EPS/IN) of the transport directory. Choose Continue to get to the Files [page 37] work step.

5.3

Step 3: Files

You are in the Files work step of Maintenance Optimizer. Here, you can the stack configuration file, which includes your previously defined update or upgrade information.

Context Note the files as soon as you have completed the Maintenance Optimizer transaction.

Procedure 1. the XML stack file. A package configuration file containing your selections, based on your entries, is generated. The text file is only needed for an upgrade with source release SAP R/3 4.6C (see SAP Note 1022704

).

If you get a system message “Adjustment of stack delta XML done with error: check application log”, either your SAP Solution Manager system does not have the latest SPAM level, or you have insufficient authorizations to write the XML in the EPS/IN directory. For more information, see Maintaining s for SAP Solution Manager and SAP Service Marketplace [page 6]. 2. Choose Continue to get to the Implement [page 38] work step.



37

5.4

Step 4: Implement

You are in the Implement work step of Maintenance Optimizer. Here, you are instructed to implement the update or update with other tools.

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

.

2. After you have implemented the changes for the product systems, change the Status of Implementation for Product System(s) to Completed. 3. Choose Continue to get to the End Maintenance [page 38] work step.

5.5

Step 5: End Maintenance

You are in the End Maintenance work step of Maintenance Optimizer. Here, you close the maintenance transaction.

Context When you complete a maintenance transaction, you can no longer make any changes to it. It remains for later reference.

Procedure 1. Choose Complete Transaction. 2. Choose Close.

38



6

Correcting Installed Software Information (CISI)

If the installed software information (ISI) is wrong or missing on the technical system itself, it cannot be correctly forwarded in the system landscape. You can correct ISI on the system by a corrective XML file.

Context Installed software information is the set of data associated with a technical system. It stored in different tables and files on the system itself and propagated to the System Landscape Directory (SLD) to be used, for example, in system landscape maintenance. This is the most important information that is included: ● System ID ● Hosts ● Product and product version ● Product instances ● Software components During the installation or upgrade of a technical system, information about the installed product version and product instances is stored on the system itself. This information is forwarded to the SLD and SAP Solution Manager. It can happen that the information stored on the technical system is not correct or missing or not forwarded at all. For example, installed product instances can be reported as being installed on the technical system in the LMDB but they do not match the installed software components. This creates errors in the landscape verification or in the Maintenance Optimizer transaction. In this case, you can correct ISI and create a corrective xml file in SAP Solution Manager and use Software Update Manager (SUM) to correct the information on the system. Prerequisites: You need at least SAP Solution Manager 7.1 SP06 and Software Update Manager SP08 from SL Toolset 1.0. For background information regarding installed software information (ISI), see SAP Note 1877731

.

Procedure Follow the procedure that is described in SAP Note 1816146

Maintenance Planning Guide Correcting Installed Software Information (CISI)

.


39

7

Copying Stack Configuration Files for Identical Systems

To reuse a previously calculated target constellation for another system, you can copy the stack configuration file.

Procedure To reuse a calculated target constellation on another system, use a copy report. It only works if both systems have the same Service Pack level. Otherwise, create an individual maintenance transaction for the second system. For more information, see SAP Note 1600302

.

Note To maintain systems belonging to one system track (development, test, production system etc.), see Maintaining System Tracks with Maintenance Optimizer [page 21].

40


Maintenance Planning Guide Copying Stack Configuration Files for Identical Systems

8

Special Cases in Installation and Upgrade

Regarding installation and upgrade, for some SAP products certain exceptions apply. The guide Special Cases in Installation and Upgrade SAP products, such as the following:

comprises recommendations on how to manage specific

● Additional installation of SAP ERP Portal Content on top of an existing SAP Portal ● Additional installation of SAP CRM or SAP SRM Portal Content on top of an existing SAP Portal ● Modeling of SAP SEM-BW, SAP ERECRUIT, LSOFE, and FINBASIS ● Updating to SAP NetWeaver 7.3 Hub ● Products that are not or only partially relevant for Maintenance Optimizer The focus is on new installation, product system modeling in the Landscape Management Database (LMDB), and updates or upgrades with Maintenance Optimizer and Software Update Manager (SUM).

Maintenance Planning Guide Special Cases in Installation and Upgrade


41

Important Disclaimers and Legal Information

Coding Samples 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 to 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, unless damages were caused by SAP intentionally or by SAP's gross negligence.

Accessibility The information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet Hyperlinks The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).

42


Maintenance Planning Guide Important Disclaimers and Legal Information

Maintenance Planning Guide Important Disclaimers and Legal Information


43

go.sap.com/registration/ .html

© 2016 SAP SE or an SAP company. 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 SE or an SAP company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP company for informational purposes only, without representation or warranty of any kind, and SAP or its d companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP company 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. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or ed trademarks of SAP SE (or an SAP company) in and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx for additional trademark information and notices.

Maintenance Planning Guide For Sap Solution Manager 7.1 Sp05 And Higher 5w1d4d

Overview 3z723u

More details 2i4a6q

Related Documents g842

Maintenance Planning Guide For Sap Solution Manager 7.1 Sp05 And Higher 5w1d4d

Funcionalidades Sap Solution Manager 5ck1a

Sap Solution Manager Overview 19642m

Sap Solution Manager 5q4lm

Sap Solution Manager 5q4lm

Sm001 Intro Sap Solution Manager 40643m

More Documents from "Karthik Seetharaman" 6g398

Maintenance Planning Guide For Sap Solution Manager 7.1 Sp05 And Higher 5w1d4d

1mrk508016-ben D En Bistable Relays Rxmvb 2 And Rxmvb 4 c5c66

Lost And Found Spell 9z6s

Tamil Films Of 1950 - 2010 1r4a41

Sqr.pdf 3c4726