Professional Documents
Culture Documents
Demystifying-Solution-Manager 7.1 PDF
Demystifying-Solution-Manager 7.1 PDF
Manager Stream
Demystifying Solution Manager 7.1
configuration focus on diagnostics
Roland Hoeller/SAP AGS Product Support
Movember 26, 2013 Public
Agenda
Prerequisites
System Preparation
(Highlights)
Basic Configuration
(Highlights)
Managed System
Configuration
Housekeeping tips
The SAP delivered client 001 can be used as productive client for SAP Solution Manager
It is also possible to use another productive client:
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client and as
the source client for users
Afterwards convert the Java UME to the new productive client
Restart the Java Stack
SAP Quick Sizer (for Small to Large Solution Manager installation)/SAP Solution Manager
sizing Toolkit (Large Solution Manager installation) provides information on infrastructure
requirements including SAPs, Memory, Databases and Disk Spaces needed to implement
selected ALM scenarios for a set of Managed Systems.
Navigation
Guided procedure with all steps for the
basic configuration
Activities
Lists all single activities during each
step along with the documentation
how to perform for the IMG activity
Log
Shows detailed logs per activity
Configures the basic scenarios in SAP Solution Manager (Service Delivery, Issue
Management, Early Watch Alerts, Maintenance Optimizer, Root Cause Analysis, )
Needs to be performed after new installations and after support packages to perform
Basic delta configuration
Configuration
Overview screen tells you which configuration needs update
In the first step dialog and system users are created which are needed later during the System
Preparation:
Select a user to create or
update
Create a new user or
update the authorizations
of an existing user
If the user creation is
performed manually,
check the respective
checkbox (4):
If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is
required:
The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the
Solution Manager ABAP stack, and the Solution Manager ABAP and Java stack
For more information about installing a SAP Web Dispatcher, and configuration
options, see SAP Help Portal at URL Generation in an AS-ABAP - Web Dispatcher
Configuration*
In this step you explicitly allow SAP Solution Manager to create web services using the
following authentication types:
Basic Authentication
X.509 Certificate Authentication
Ticket Authentication
Starting with Solution Manager 7.1 the diagnostics agents can be connected with certificate
based authentication to SAP Solution Manager. This has the following benefits:
Prevents agents locking the agent connection user because of a wrong password
The password of the connection user (SMD_ADMIN) does not expire
Diagnostics agents having authentication issues will show up on the tab
Non-authenticated agents in the Agent Administration UI*
Even if the password is not expiring anymore, please note that the
certificate itself only has a restricted validity. Make sure to recreate a
new certificate before the old one expires.
This step enables SAP Solution Manager to access to the System Landscape Directory (SLD):
If SLDs exist specify all of them, which are connected to either Managed Systems or Diagnostics agents, via the Add SLD
Server button
Register Solution Manager in one of the SLDs by choosing the Target of SAP Solution Manager DS radio button
If no SLD yet exists, you can set up a local one in the SAP Solution Manager system
In this step the synchronization between LMDB and one ore more SLDs is set up:
The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the
following information from the system landscape:
SAP Software Catalog (CR content)
CIM Model
Technical system
landscape descriptions
In this step, the System Landscape information can be migrated from the SMSY. The SMSY was
used in earlier releases and contains information that cannot be provided by an SLD:
It is strongly recommended to perform the Product System migration
SAP Solution Manager uses different agents for the monitoring of the landscape. In this step
the agents are installed:
Install the agents on all hosts on which one or more of the following is running:
A Managed System which should be connected to SAP Solution Manager
A CA Wily Introscope Enterprise Manager
A Standalone database
A third party product not registered to an SLD
Please refer to the agent installation strategy documentation attached to SAP Note 1365123
For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode. See
SAP Note 1486330 for details
Each Diagnostics Agent can report to exactly one SAP Solution Manager, in multi-tier landscapes several Diagnostics Agents per host are needed,
e.g. to connect development systems to the development/test Solution Manager and to the productive Solution Manager
In this step all necessary Diagnostics Agents are connected to the Solution Manager system:
Only agents using the SLD connection method, connected to an SLD known to Solution Manager are visible
Select the SLD* that contains your agents and click Get Agents to retrieve the agents
The Complete step gives an overview over all performed activities and their status
After the System Preparation the Basic Configuration needs to be performed
To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator
user (default: SOLMAN_ADMIN), which you have created in step 1
In this step it is defined witch BW system SAP Solution Manager will use:
Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis
SAP recommends setting up BW in the production SAP Solution Manager client
A separate BW system can be used for Solution Manager
Its not recommended to use the company's business BW system together with SAP Solution Manager
If you use a separate BW system, please make sure that the BI_CONT and the ST-BCO is always the level as required by
the Solution Manager (SAP Note 1483508)
In the first step the dialog and system users are created which are used later in the System
Preparation:
Select the user you want
to create or update
Create a new user or
update the authorizations
of an existing user
If user management is
performed manually,
check the respective
checkbox User creation
and role assignment
performed manually
Provide the manually created user
and a password for later use in
SOLMAN Setup
Solution Manager will then not check
the existence, password correctness
or the authorizations of the user in this
case, therefore, please make sure the
user is correct
Prerequisites:
A Diagnostics agents needs to be installed and connected to
Solution Manager on the Wily EM host
The operating system user of the Diagnostics agent (default:
daaadm for UNIX and SAPServiceDAA for Windows) needs read
and write access to the Wily EM installation directory (default:
/urs/sap/ccms/wilyintroscope)
In this step, IBase components and objects that represent systems are created:
The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM
All systems in LMDB and SMSY need to be maintained in IBase
The Complete step gives an overview over all performed activities and their status
After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration
Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself, because otherwise
monitoring functionalities might not work correctly
All technical systems known in LMDB are visible in the Managed Systems Configuration:
Single technical systems can be found under the tab Technical Systems
Also the single stacks of dual-stack systems are visible here, but the configuration is performed in scenario context
Dual-stack system are visible under the tab Technical Scenarios
The technical scenario Dual Stack is created by Solution Manager automatically, if it finds an ABAP stack with a matching Java stack in LMDB
during LMDB sync
To configure a dual-stack system, always start the configuration for the technical scenario
Standalone databases and system databases are visible under the tab Databases
System databases are set up together with the technical system or the technical scenario they belong to
Standalone hosts are visible under the tab Hosts
A host needs to be configured explicitly to activate Diagnostics agent nodes
If the system is not displayed in the technical system list, check if it is properly connected to SLD, for more information see:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape
The roadmap of the Managed System Setup depends on the type of the configured object and only
contains the steps necessary for this system:
Dual stack system
J2EE system
Database/Host only
To get more information about the selected configured object use the link for the technical system:
The first step is to maintain the Managed System information in LMDB, this includes:
Assigning the technical system(s) to a product system
Selecting the product instances that are diagnostics relevant
Assigning the technical system to a logical component
7. Click OK
* Up to SM 7.1 SP 08 Logical Components were related to the Product System. This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical
Component. This is not longer possible.
With SAP Solution Manager 7.1 SP 10 the maintenance of Logical Components moved to LMDB
You can access Logical Components via transaction LMDB under the tab Logical Components
You can:
1. Assign or delete technical systems to/from
a Logical Component
The check prerequisites step verifies that the Managed System and Solution Manager fulfill the
diagnostics prerequisites from a landscape definition and software component point of view:
Run the prerequisites check. If there is an error, check the log information for details and correct the errors
This step only exists for ABAP systems, because only ABAP needs to be connected via RFC:
For each ABAP system create at least one READ RFC destination (typically connect to the active client)
To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System, has the authorization S_RFCACL. To
use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System.
You also need to create a READ RFC destination for Solution Manager itself. The NONE RFC destination is currently not supported by
Diagnostics.
To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a
Diagnostics Agent to each instance of the system:
Select the instance from the list and click Assign
In the new window select the Diagnostics Agent from the list, that has the same host name as the managed instance
If the required agent is not in the list use the SLD Agent
Candidates, to connect the agent from SLD or the Agent Use Check Host Agents to check the connection status
Admin for agent trouble shooting. Preferred method: and the release of the SAP Hostagent
Connect the Diagnostics Agent via the smdsetupscript
It is recommended to install and connect all required agents before the managed system setup, see
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed_System_Checklist
In this step the connection parameters of the Managed System are configured.
Carefully read the context help of the input Use the Check URL link to check if the load
fields and provide the necessary input balancer host and the HTTP port are correct
(the port can be found in transaction SMICM
of the managed system and under Technical
Instances HTTP Ports in the LMDB
To make EWA alerts visible in alert inbox,
check Activate EWA Monitoring
In this step verify the Managed Systems default landscape parameters. Sometimes additional
input is required so that the step can be performed correctly:
Check every landscape parameter carefully
Use the Check existence of path when saving option, to make sure the entered paths are valid
To enable the Diagnostics Agent to gather data about the Managed System, connection users
for the ABAP and the Java stack are required:
Additionally, users can be created to be provided to SAP in case the support needs to log on to the system
In this step several manual activities can be performed, that cannot be carried out
automatically. These are:
Maintain SAPRouter data for the system in Service Market Place
Adjust HTTP log parameter to enable ICM logging
Restart the Java Stack (this is necessary for the Byte Code Adapter installation)
Set up the R/3 connection to enable remote supportability for the Managed System
This step verifies whether the system is configured correctly. Additionally, the status in the
overview of the Managed Systems Configuration is updated:
Select Execute All to perform all activities
If there are errors in the configuration check, please see the log area for details and fix the listed errors
The Complete step gives an overview over all performed activities and their status
If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and
other scenarios in SAP Solution Manager
Notes
706705 Solution Manager: Components
for Messages
1478974 - Diagnostics in SAP Solution
Manager 7.1 (Supported Products)
1483508 Solution
Manager 7.10: Root Cause Analysis pre-
requisites
Contact information:
Roland Hoeller
Senior Support Engineer
Roland.Hoeller@SAP.com
Appendix
Solution Manager Upgrade
SAP Solution Manager 7.1
Installation/upgrade roadmap
Preparation
Implement missing
Download software on managed Perform
Implement
software from systems Backup
Pre-requisites
SMP
Upgrade
Installation
Upgrade Install
SAPHostAgent Install SMDAgent
Solman_setup
on all managed Solution for All Solman_setup
hosts Manager managed
Upgrade Hosts
Solution
Manager
Including
Wili IS EM Install
Repeat Install
SMDAgent
managed SMDAgent Run managed
for DB host Systems Install wily
and Wily on Wily Systems
configuration IS EM configuration
Hosts for PI systems
Hosts
Post Processing
Restart Java
Run Self- Managed
Diagnosis systems
The upgrade program upgrades an ABAP system using a system cloning and switch procedure.
This procedure installs a copy of the system, the shadow system, in parallel with the original system. The
shadow system is used to update the affected software components and to install the additional
components, while the original system is still in production operation.
Space
Operating two instances in parallel places increased demands on free space in the file system, in the
database, and on the system resources.
Duration
No precise guidelines can be given for the duration of an upgrade. The duration of the system cloning
depends to a great extent on the amount of data, the database system, and the hardware and can take
several hours. Although the system can still be used in production operation, you have to take into
account a possible performance decrease during this cloning process.
To upgrade to SAP Solution Manager 7.1 on the JAVA Stack, the SAP Enhancement Package Installer uses
a deployment-based procedure. No shadow system is required for the JAVA Stack. The procedure is highly
automated with minimum user interaction.
S-Users are requested and maintained via SAP Service Market Place: http://service.sap.com/user-
admin
Ensure that all support package levels for the managing system (Solution Manager) and the
managed systems are up to date according to SAP Note 1483508
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS, check and maintain the connection settings in transaction OSS1,
the configuration changes will be adapted automatically
You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note
17285
2013 SAP AG. All rights reserved. Public 62
Check Prerequisites
SAP Solution Manager Profile Parameters
Make sure the following profile parameters are set in you SAP Solution Manager system
Check SAP note 1582842 - Profile parameters for Solution Manager 7.1 for latest recommendations
The Basic Configuration and the configuration of the managed systems build the basis for further
configuration and make sure the following basic functionalities is set up:
Early Watch Alerts
System recommendations SOLMAN_SETUP supports the standard customizing for
Service Engagement and Delivery the most Solution Manager scenarios. Further expert
Project Management customizing is possible using SAP Reference IMG
Issue Management
Solution Documentation
Maintenance Optimizer
Test Management
Send tickets to SAP End-User
SolMan
Job BI PI Interface Experienc
Self-
Monitoring Monitoring Monitoring Monitoring e
Monitoring
Monitoring
System Preparation
Basic Configuration (~ 3h)
(~ 2h*)
* Please add waiting time for initial LMDB sync (~4 12h))
During the basic configuration of SAP Solution Manager several users and roles are created, if you run a CUA
or another user management tool, you have two options to handle this user creation:
Option 1: Create and maintain users manually Option 2: Create users automatically via SOLMAN_SETUP
You can create all required users manually before or during in CUA
SOLMAN_SETUP To be able to create users automatically in the CUA via
The documentation in the user creation steps of SOLMAN_SETUP tell SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user,
you which users are needed and which roles need to assigned to this used in the RFC (2) from the managed system to CUA
users The picture below describes the dataflow during user creation in CUA
After the creation of the user you can provide this existing user to See the SAP Solution Manager Security Guide for details:
SOLMAN_SETUP http://service.sap.com/~form/sapnet?_SHORTKEY=011000358700
00735220&_OBJECT=011000358700000482312011E
This is the only option if you run a central user management tool other
than SAP CUA
In this step you download and implement the Central Correction Note for Solution Manager:
The CCN comprises all corrections for the configuration
scenarios of the basic configuration
It is recommended to implement the complete central
correction note, but if you want to implement only certain
corrections, the note contains the information about all
single notes and their source application
You must implement the central correction SAP Note
manually, with the SAP Note Assistant (SNOTE)
Some post-processing steps in the notes could be
automated, these can be performed by executing the Post-
Processing
In a multi-tier Solution Manager landscape the note
download is performed in the development system and the
note corrections are transported to the other systems
Nevertheless the post processing steps have to be
performed in each system
In the sub-steps of this step, you perform the initial part of the connectivity configuration, this
includes:
Web Dispatcher related configuration
Web services related configurations
Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system
SAP Gateway (required in the scope of the Sybase Unwired Platform integration)
Setup of SAP Connect for notification management
In this step, you enable the SAP Web Services communication between the ABAB and the Java
stack of SAP Solution Manager
Required logical ports are created in transaction SOAMANAGER, the creation is performed automatically
In this step you activate SAP NetWeaver Gateway Services for mobile devices:
To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via e.g. the Technical Monitoring
app
Prerequisite: To create a system alias a customizing request has to be created in Solution Manager first
Node: the name of the SMTP node which handles outgoing e-mail
Host: the name of your mail server
Port: the port number at which your mail server can be accessed
To enable SAP Solution Manager to send notification via e-mail,
select the SMTP Active field.
To enable SAP Solution Manager to send notification via SMS,
select the Fax/Pager Active field.
In the Domain field, you can, for example, enter the domain name
of your organization, if you want to restrict the scope of possible
recipients.
When you have completed this step, the system landscape description is stored in SAP
Solution Manager. This includes the following sub-steps:
The SAP Solution Manager system is registered in the SLD
The technical system descriptions, CIM model, and the SAP Software Catalog (CR content) from the System Landscape
Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager
The synchronization connection between LMDB and the relevant SLDs is setup and activated
For upgraded SAP Solution Manager systems, system information created in SMSY, previously, can be migrated into LMDB
Diagnostics agents and SAP Hostagents are installed
Diagnostics agents are connected to SAP Solution Manager
from SMSY
Establish Trusted Connection: The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the
physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default
daaadm) must be a trusted user to the SAP Hostagent
Physical Host
Windows
SAP Hostagent Diagnostics Agent
IS Host
SAPMSCT Adapter
Web Service
Web Service
P4 Client
RL
Outside
SAPDBCT
Discovery
RL
SAPOscol Other
OtherAgelets
Agelets
Unix
As a rule of thumb you can say, you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating
System.
With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios, where a logical host moves from one physical host to
another. See the RCA wiki under http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+and+HA+support for details.
The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for
the physical/virtual host
After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly
Which agents are started depends on the current logical hostname situation on the physical/virtual host requires it,
e.g. if an SAP instance moves from one physical host to another (taking it logical host name with it)
sapstartserv
Logical Host A Logical Host B Logical Host A
In the sub-steps of this step you make sure that SAP Solution Manager can be connected to
SAP and to other systems, this includes:
Maintaining the connection to SAP Service Market Place
Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring
Create users necessary for internal and external connectivity of Solution Manager
Set up the RFCs and web services for Root Cause Analysis and other scenarios
In this sub-step you set up the connection between Solution Manager and SAP Service Market
place:
Enter the S-user(s) that were created during the preparation steps
During this step two RFC destinations are created:
SAP-OSS
SAP-OSS-LIST-O01
The S-user for SAP Backend will be maintained in the
global settings of Solution Manager and it will be used
in the RFC connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication will be assigned to the
user SOLMAN_ADMIN and SOLMAN_BTC in
transaction AISUSER
For security reasons it is recommended to maintain two S-users for Solution Manager. The S-user for
SAP Backend should have no authorizations since it could be misused for direct logon.
The S-user for Communication is needed to perform tasks like synchronize service messages and system
data and to request licenses. This user needs more extensive authorizations.
In this step you provide the administrator users, used for further setup:
Recommendation: Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator. This ensures that the
administrator has the required authorizations.
If you set up the BW in a different client or system you have to create or update a BW administrator user
In this sub-step you set up RFCs and web service URLs for the communication between
Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics
Agents:
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents
Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution
Manager
In this step you perform several manual activities in Solution Manager, that cannot be carried
out automatically:
You configure the logical systems in SAP Solution Manager
You activate automatic service content updates
You can delete documents and sessions from Solution Manager
You activate extended authorization checks for Workcenter views
You can perform configuration for IT Task Management
You setup HTTP and R/3 connections in Service Market Place to enable remote supportabilty
Import all CA Wily Introscopes in your landscape, also You can also create own users
MoMs and Collectors Click the Refresh button when you are done
In this optional step you create configuration users for the other Solution Manager scenarios:
The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager
scenarios
You can use this users as templates for other users
Details about the users and roles can be found in the user documentation and
In the Managed System Configuration the configuration status of the system is displayed:
You can use the Show Details button to display status details below the overview table and to update the status via status
check
Use the filter functionality to find the system you are interested in
To start the configuration of a system/scenario/database/host select it from the list and press the respective Configure
button
5. Save
6. Save
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.
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.
SAP 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 other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.