Generating Stack(XML file) in Solution manager for EHP Upgrade

 If you are upgrading ECC System using Enhancement Package Installer ( EHPI ) tool. While upgrading you need to genarate stack.xml, which contains all support patches list and EHP tool uses it as a reference of patch list. It contains list of all patches which are required during the installation.

Prerequisites:

Maintenance Optimizer is configured in solution manager.
Configured Technical System in SMSY.
User ID is maintained in AISUSER
Authorizations described in SAP Note # 1032322

 Generating Stack File:

Patches required for upgrade can be downloaded from Solution Manager. To download patches use transaction DSWP and create  a New Maintenance Transaction.

Select your solution, product version and product system to which you want to upgrade

Once you select Click Continue

If you are generating stack for

Select the components which you want to include in your upgrade depending upon your usage type.

After selecting components you need to confirm major target, which will give you a synopsis of change of upgrade components.

Select the add-on required for installation.

Select kernel depending on your product version.

In next step you will have the option of excluding or including the patches/components. It is recommended that you do not un-check any components, which will lead to miss the dependent components. Download stack.xml file and this need to be uploaded into download directory of your upgrade.

All patches present in stack files are confirmed automatically and can be downloaded using SAP Download Manager.

Landscape Management Database (LMDB)

The Landscape Management Database (LMDB) is a directory of elements of a system landscape. The core task of the LMDB is to provide information about the entire system landscape at a central location. The Solution Manager System Landscape (SMSY) and the System Landscape Directory (SLD) already provide this function with different technologies for different applications. The aim of the LMDB is to unify the SLD and SMSY in SAP Solution Manager. The LMDB is supplied with data automatically, in as far as this is possible.

                               

Integration with the System Landscape Directory
Data suppliers exist for most technical systems and automatically register these systems in the System Landscape Directory (SLD). The SLD, therefore, is the central data source for the LMDB. Changes to technical systems should be carried out in the SLD where possible.
Integration with the Solution Manager System Landscape


For information on the advantages of the LMDB with regards to the previous SMSY storage, see the SCN blog Evolution of landscape data management - What's better with LMDB?
SAP Note 1679673 explains the most important differences between LMDB and SMSY.

There is a clear separation of tasks in System Landscape Directory (SLD) and LMDB:

The SLD is the target for self-registration of technical systems in the IP landscape. This technical systems information is provided for applications in non-productive and productive applications such as SAP NetWeaver Process Integration and WebDynpro (Java) based applications that need this information. Because of the productive use of the data it provides, often many SLD systems are used in customer landscapes (see SLD Topology: How-To Gather and Distribute SLD-Data in Your IT-Landscape).

The LMDB retrieves technical system information from the SLD as a basis for landscape data, to manage technical systems in monitoring and maintenance processes. It acts as a single source of truth in SAP Solution Manager. It provides a centralized UI approach to landscape verification functions and transaction SMSY.

As of SAP Solution Manager 7.1 SP0-4, the LMDB manages information about technical systems, hosts.

As of SP5, the LMDB also manages product system information.

Transaction SMSY is the "old" system information storage, being replaced by the LMDB bit by bit.

Up to SAP Solution Manager 7.1 SP4, SMSY is still used to manage product system information, but gets all technical systems information from the LMDB.

As of SP5, SMSY is only used to manage project-related data (logical components and solutions); the required data (technical systems and product systems) ar edited and provided by the LMDB (see New in SP05: Product System Editor in the Landscape Management Database of SAP Solution Manager 7.1).

                               

As of SAP Solution Manager 7.2, SMSY does not exist any longer. See Deactivation of Transaction SMSY.

The separation of roles is reflected in the architecture: Technical systems can register only in the SLD. All data changes in the SLD are retrieved immediately by the LMDB, as well as the CIM model and the CR content (SAP software catalog). Because both SLD and LMDB are needed in one landscape; without an SLD connected, LMDB cannot work AND data in SLD and LMDB must be consistent and must not overlap.

SAP Solution Manager 7.1 installation

Home

Installation of SAP Solution Manager in Windows platform compatible with Amazon / Azure Cloud / Hyper-V / Standalone server
The SAP Solution Manager 7.1 installation steps below suitable on all Windows server environment including Amazon Web Services (AWS), Microsoft Azure, Microsoft Hyper-V or standalone server installation.

These configurations including:

A) Prerequisite
B) Oracle Database Installation
C) SAP Solution Manager 7.1 Installation with SWPM
D) SAP GUI Installation and login the SAP Solution Manager for the first time
E) Others


A) Prerequisite:
1) Windows server 2008 be ready

2) Minimum SAP Solution Manager 7.1 installation files

Download Object	Title
50118243_6	NW 7.0 Presentation - 7.30 Compilation 2 Present. ½
51041940	ORACLE Client 11.2.0.3
51042334_1 – 6	ORACLE RDBMS 11.2.0.3 Windows x64
51042607_1 - 12	SAP SOLMAN 7.1 SR1 Inst. Export (2)
51042609_1 – 5	SAP SOLMAN 7.1 SR1 Java Comp
51042616_9	SL CONTROLLER 700
51046511_6	720 UC Kernel for SWPM SP03 - Windows Server on x64 64bit
70SWPM10SP02_4-20009707.sar	Software Provisioning Manager 1.0 SP2 for NW 7.0x

3) Recommended server specifications:

Type	Descriptions
OS	Windows Server 2012 Data Center
RAM	12GB
Hard disk	400GB (c:\ 100GB d:\300GB)

4) Reference for OS environment setup on AWS Cloud and Microsoft Hyper-V 

- AWS Cloud:  Section: AWS AMI Setup and Configurations (SAP IDES Installation)

- Microsoft Hyper-V: Section: A) Creating new VM in Hyper-V (setup Red Hat Enterprise Linux Server in Microsoft Hyper-V Server 2012)

5) Assumption:

     - The Windows OS will be configure as workgroup instead of joining a domain / active directory.

     - All the installation are mostly with default settings and further configurations or fine tune will be perform

        after the installation.

     - Windows OS been patched to latest update and some prerequisite steps as in SAP IDES Installation

     - The installation time estimation was based on a installation on Microsoft Hyper-V 2012 environment

        with the above mentioned hardware. In fact, the actual installation time might vary.

B) Oracle Database Installation:

1) Run the Oracle setup batch file "sapserver,cmd" to begin the database installation

 2) Enter the installation drive and SID

 3) Installation splash screen

 4) Click "Next"

 5) Click "Next" ignore the warning

 6) Select "Skip the software updates"

 7) Select " Install database software only"

 8) Select "single instance database installation"

 9) Click "Next"

 10) Select "Enterprise Edition"

 11) Choose the installation drive

 12) Wait for the verification process

 13) The verification process

 14) Click "Install" to begin the installation

 15) Click "Details" button to shown the installation progress

 16) The additional installation progress screen

 17) Wait until the installation complete and the click "Close" button

 18) Confirm the database been installed

B) SAP Solution Manager 7.1 Installation with SWPM

The installation process estimate will take about ~5 hours to complete with the above mentioned hardware specifications

1) Double click the "sapinst" extracted from SWPM - Section E) Others below shown how to extract the installation file with sapcar program

 2) Select "SAP Solution Manager 7.1 Support Release 1"

 3) Select "typical"

 4) The installation splash screen

 5) Select the SWPM kernel

 6) Enter the SAPSID and installation drive

 7) Configure the FQDN or it can be configure after the installation

 8) Enter the master password

 9) Enter the Oracle database ID created during the database installation

 10) Select the installation export package

 11) Select the other installation export package

 12) Click  "Next" with all the default settings

 13) Select the Java component package

 14) Ensure the installation drive are correct

 15) Click "Next" to accept the default listener configuration or change the port according to existing firewall

        policy

 16) Select the kernel package

 17) Select the Oracle client package

 18) Select "Configure a local SLD" in this example

 19) Enter the computer name in "Object Server Name"

 20) Click the "Next" button

 21) Click "Yes" button

 22) Click "No SLD destination" in this example

 23) Verify the selected options and click "Next" to accept all the settings

 24) The installation begin

 25) Example of the installation process

 26) Example of the installation process

 27) Example of the installation process

 28) Around ~5 hours for the installation to complete

 29) SAP management console and listener status command showing the SAP services are up and running

D) SAP GUI Installation and login the SAP Solution Manager for the first time

1) Perform the SAP GUI installation from the media kit: 50118243_6

2) The settings for the SAP logon

3) Login with user: "sap*"

4) The information screen

5) The relevant SAP system information

6) Login to the portal (http: port: 5<SID>00, https: port: 5<SID>01)

7) Main Menu of the portal

8) Use the default login: "j2ee_admin" and master password entered during installation

9) Sample of information screen

10) Again using the "j2ee_admin" for access

11) Sample of information screen

12) That's all on the basic steps to perform a new SAP Solution Manager installation.

13) Please refer to the common troubleshooting on SOLMAN_WORKCENTER post for further configurations or common errors troubleshooting

E) Others

How to extract the SWPM installation file with SAPCAR

1) Download the "Software Provisioning Manager 1.0 SP2 for NW 7.0x" from SAP marketplace

 2) Extract the sar file with SAPCAR -xvf <swpm filename.sar>

 3) The "sapinst" program use for the SAP Solution Manager installation

How to clear SWPM cache or resolve the SAP Solution Manager 7.1 selection node was not available for installation

After running the "sapinst", the "SAP Solution Manager 7.1 Support Release 1" option was not available and it seem appearing with different option ex: SAP Solution Manager 7.1 for HANA.

This happen due to the other SWPM was executed before and the files were cache and causing the other SWPM relevant selection node not updated.

1) Locate to "c:\users\Administrator\AppData\Local\Temp\2", delete all the files and folders contains in it

 2) Re-run the correct SWPM "sapinst" and the correct node would appear