Show TOC

Background documentationPrerequisites Locate this document in the navigation structure

 

The Maintenance Optimizer contains a lot of scenarios for maintenence procedures. The scenarios have different prerequisites.

Basic Prerequisites

  1. You have configured the Maintenance Optimizer in the SAP Solution Manager customizing.

    You must perform the following customizing activities for the Maintenance Optimizer:

    • Assign S users for the SAP Support Portal.

      This activity specifies the S users (user ID for the SAP Service Marketplace) assigned to user IDs for the SAP Solution Manager.

      For more information see S Users in the Maintenance Optimizer.

    • Enter user for communication with SAP Service and Support systems

      This activity specifies the RFC connection SAP-OSS and the corresponding RFC user.

  2. You have assigned product versions to the system to be maintained, in the system landscape.

  3. You have assigned the systems to be maintained to a logical component.

    Note Note

    If you want to use a solution, you must assign the systems to be maintained, to the solution landscape. For more information, see Solution Manager System Landscape.

    End of the note.

  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

The following prerequisites must be satisfied in der SAP Solution Manager system landscape (transaction SMSY) for automatic calculation of the maintenance files:

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

  2. You have specified the relevant instances for each system to be maintained on the Selecting Main Instances tab in the system landscape.

    Flag the following instances as relevant because the Maintenance Optimizer only considers relevant instances when determining the maintenance files:

    • All business main instances in a system.

    • All ABAP business instances installed in addition to the ABAP main instance.

      Note Note

      These instances can be assigned to a subsystem. This subsystem is a system component. You ca create components for a system, in the transaction Solution Manager System Landscape (SMSY). For more information about managing the system landscape, see Solution Manager System Landscape.

      End of the note.

  3. You have assigned a host to each system for which a maintenance procedure is to be performed, in the system landscape.

    Note Note

    If no host is assigned to a system for which a maintenance procedure is to be performed, the Maintenance Optimizer cannot identify the system unambiguously.

    End of the note.

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

    • Set-up an RFC connection

      SAP recommends an HTTPS connection. For further information, see the security guide in the SAP Service Marketplace, under   http://service.sap.com/instguides   SAP Components   SAP Solution Manager   <current release>   SAP Solution Manager Security Guide  .

    • Set-up a logical port

      For further information, see the security guide in the SAP Service Marketplace, under   http://service.sap.com/instguides   SAP Components   SAP Solution Manager   <current release>   SAP Solution Manager Security Guide  .

    • Set-up the Download Directory Assistant

    • Set-up the Software Lifecycle Manager

    Note Note

    Call the Central Download Directory Assistant with transaction /TMWFLOW/MOPZCD. You can view or delete files in the Central Download Directory with the Central Download Directory Assistant.

    Call the Configuration Assistant for the Software Lifecycle Manager with transaction /TMWFLOW/MOPZCA in the SAP Solution Manager.

    End of the note.