Show TOC

Background documentationPrerequisites Locate this document in the navigation structure

 

The Maintenance Optimizer contains a lot of maintenence transaction scenarios. The scenarios have various prerequisites.

Basic Prerequisites

  1. You have performed the basic configuration of the SAP Solution Manager (transaction SOLMAN_SETUP).

    For more information, see Basic Configuration of the SAP Solution Manager.

  2. You specify S-Users for the SAP Support Portal functions.

    You assign S-Users (SAP Service Marketplace users) to the SAP Solution Manager users (see S-Users in Maintenance Optimizer).

  3. You have satisfied the following prerequisites in the Landscape Management Database (LMDB):

    • The information about the technical systems involved is correct and complete in the LMDB.

    • The relevant product systems are maintained.

    • You have classified your technical systems by landscape pattern. For more information, see Landscape Patterns.

  4. You have installed the Download Manager locally in your workplace. The Download Manager is in the SAP Software Distribution Center in the SAP Support Portal.

    Note Note

    You can use the Software Lifecycle Manager instead of the Download Manager. For more information, see below.

    End of the note.
Prerequisites for Automatic Calculation of Maintenance Files

To calculate the maintenance files automatically, the following prerequisites must be satisfied in the Landscape Management Database (LMDB):

  1. You have assigned active product versions to the product systems to be maintained, in the system landscape.

  2. You have specified the required product instances for each product system to be maintained, on the Product Instance Selection tab in the system landscape.

    Flag the following product instances as follows, because the Maintenance Optimizer only considers such product instances when determining the maintenance files:

    • Flag the leading business ABAP product instances of a product system as Relevant.

    • Flag all other business ABAP product instances which are also installed in the relevant ABAP product instance.

      Note Note

      This flag is still required, if you no longer use the also-installed ABAP product instance.

      End of the note.

    • Flag all installed non-ABAP product instances (e.g. Java) as Relevant.

  3. You have assigned a message server and database host to each product system for which a maintenance transaction is to be performed, in the system landscape. Only so can the Maintenance Optimizer identify the product system uniquely.

  4. You can use the Software Lifecycle Manager instead of the Download Manager. To configure it:

    • Set up an RFC connection

      You need an HTTPS connection for communication between Maintenance Optimizer and Software Lifecycle Manager. More information: SAP Note 1138061.

    • Set up a logical port

    • Set up the Software Lifecycle Manager

      You call the Software Lifecycle Manager configuration assistant with the transaction /TMWFLOW/MOPZCFG. You go to the Central Download Directory Assistant with Central Download Directory.

    For further in information, see Customizing for SAP Solution Manager, under   SAP Solution Manager   Capabilities   Maintenance Management  .