Demystifying Solution Manager 7.1 - Configuration Focus On Diagnostics Roland Hoeller SAP PDF

Welcome to the Solution
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
2013 SAP AG. All rights reserved. Public 3

Prerequisites
Check Prerequisites Roadmap
Before starting with the configuration of SAP

Solution Manager please prepare the following:
Solution Manager S-users in SAP Service Market Place
Ensure correct support package level of SAP Solution
Manager
Check SLD CR content and model version
Check RFC destination SAPOSS
Verify Solution Manager profile parameters
Download software for Diagnostics Agent and SAP
Hostagent
Download CA Introscope Enterprise Manager
Optional: Perform a client copy

Check Prerequisites
Optional: Client Copy
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
Please ensure that you entered 001 as

Source Client User Masters for your client
copy

Hardware pre-requisites
quick sizer/Sizing Tool kit
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.

SAP Solution Manager Configuration
UI components
Navigation
Guided procedure with all steps for the
basic configuration
Step Help Section

Provides detailed information to each
step, such as what needs to be done
and what will happen in the
background
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

Configuration Roadmap
Prepares the Solution Manager system for the basic configuration

Needs to be performed fully after a new installation or upgrade
Partially after patches and upgrades to update dialog and system users, and assign the
System
appropriate default roles
Preparation During this step the Central Correction Note (CCN) that contains the latest corrections is
implemented
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
Connection and configuration of managed systems

Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP
Solution Manager
Managed
Systems Creation of Logical Components for managed systems
Configuration Setup of the Exception Management Dashboard for the managed systems

System Preparation
System Preparation Roadmap
The scenario System Preparation consists of

the following steps
Create Users
Check Installation
Implement SAP Note
Configure Connectivity
Prepare Landscape Description
Complete

System Preparation
Create Users
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):
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, therfore make sure the user is
correct

System Preparation
Configure Web Dispatcher
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
Enter the URL and the port for the

Web Dispatcher
Save the entries
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*

System Preparation
Set Authentication Types for Web Services
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
Read the documentation provided

for the activity
Start transaction SOAMANAGER
or click on the provided navigation
link
Activate all authentication
methods and save your changes
The explicit setup is necessary

for security compliance reasons

System Preparation
Set Authentication Policy for Agents
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*
New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent
connection
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.

System Preparation
Select SLD
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

System Preparation
Set Up LMDB
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

System Preparation
Migrate Data into LMDB
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
This migration is necessary after an

update or upgrade from SAP Solution
Manager below 7.1 SP04 to avoid
manual recreation.

System Preparation
Prepare Outside Discovery - Overview
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
For more detailed information please refer

to the agent installation strategy document
attached to SAP note 1365123.

System Preparation
Prepare Outside Discovery Diagnostics Agents Installation
For Diagnostics Agents the following activities have to be performed:

On each Logical Host on which a managed object is running:
Provide a Diagnostics Agent: Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality
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
It is highly recommended to install all agents and

plug-ins for a system before starting with the managed
systems configuration.
Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites
checklist:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Manag
ed_System_Checklist

System Preparation
Connect Diagnostics Agents
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 agents of the following systems

need to be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-
Monitoring)
Only agents using the direct connection

method, are visible in the SMD Agent
Administration (http://<SolMan-
Host>:5XX00/smd/AgentAdmin). You can later
push the SLD settings to all agents via
Advanced Settings Agent Candidates
Management
*The list of SLDs is maintained in step 5.1

System Preparation
Complete
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

Basic Configuration
Basic Configuration Roadmap
The scenario Basic Configuration consists of

the following steps
Specify Solution
Specify User and Connectivity Data
Configure CA Introscope
Configure Manually
Configure Automatically
Configure Engagement Reports
Create Configuration Users
Maintain Systems in IBase
Complete

Basic Configuration
Specify Solution
In this step the first Solution is created in Solution Manager:

A logical component is created for SAP Solution Manager
Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the
SAP Solution, this makes sure that:
You can perform Service Delivery for all production systems
SAP EarlyWatch Alert is scheduled for all production systems

Basic Configuration
Specify SAP BW System
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)
By default the BW client is always set to client 001.

The BW environment setting can be changed using
function module RS_MANDT_UNIQUE_SET if:
Another client than 001 is used as production
Solution Manager client BW should be set up in
this client
BW should be set up in a separate Solution
Manager client and this client is not 001
BW should be set up on a separate system but the
client is not 001

Basic Configuration
Create Users
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

Basic Configuration
Configure CA Wily Introscope
In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager:

It is possible to connect already existing Introscope Enterprise Managers
The recommended version to be used is Wily Introscope Enterprise Manager 9.1
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)
* Dependencies on IS Bytecode agents:

IS BC Agent 9 support only Java 5 and higher
IS BC Agent 8 is needed to manage older managed systems running with
Java 4
Deploy both SCAs on Solution Manager Java Stack, automatic
deployment of the appropriate BC Agent depending on the JVM of the
managed system

Basic Configuration
Maintain Systems in IBase
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
1. Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 make
sure there are no errors in the report output
2. Run the automatic activities by choosing

Execute All

Basic Configuration
Complete
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

Managed System
Configuration
Managed Systems Configuration Roadmap
The Managed Systems Configuration consists

of the following steps
Assign Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Create Users
Configure Manually
Check Configuration
Complete

Managed Systems Configuration
Overview
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

Roadmap Overview
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:

Assign Product
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

Assign Product Set Diagnostics Relevant Flag
Set Diagnostics Relevant Flag:

There are three ways to set the Diagnostics
Relevant flag:
A. Set the Diagnostics Relevant flag

automatically
Or edit the assignment manually. To do this

choose Edit Assignment
B. Set the Diagnostics Relevant flag on the

Product Instances tab. Here the flag is
also set for all assigned product instances
for which a Diagnostics template exist
C. Set the Diagnostics Relevant flag for

selected product instances on the
Product Instances (Details) tab
Make sure to select the product

version listed in SAP note
1478974 as diagnostics relevant.

Assign Product Assign Logical Components
Assign Logical Components:

As of Solution Manager 7.1 SP 10 Logical
Components are related to Technical
Systems*: You need to create one Logical
Component for each Technical System
1. Choose Assign Logical Component
2. Select the correct client (ABAP only)
3. Select the system role
4. Select the correct Product Instance
5. Select an existing Logical Component or

create a new one
6. Click the Check button to verify your

entries
7. Click OK
8. Save your changes
* 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.

Logical Components in LMDB
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
2. Maintain the available system roles

(changes made here apply to all logical
components system wide)
3. Change the system role of a Technical

System
4. Delete a Logical Component

Check Prerequisites
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

Connect Managed System
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.

Connect Managed System Further functionality
Create ABAP administration user: Clean up existing RFCs:

For the creation of RFCs and further configuration a quite powerful If necessary clean up existing RFCs for the managed system
user is needed
Create this user here
Create the user as user type System to prevent dialog log on with this
user!

Assign Diagnostics Agent
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

Enter System Parameter
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
Provide an administrative user for

The database parameters the managed system. Use the Test
depend on the database type. Logon links to verify the provided
logon data

Enter Landscape Parameter
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
The following statuses are possible:

No Parameter: No input required.
Default used: Verify the parameter
Input missing: Enter the parameter.
Agent offline: This is for your information
only. The agent on the system is only
needed to verify the entered values on
the system (e.g. the instance path). You
can continue even when the agent is
offline.

Create Users
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
Select the user that

should be created or
updated
Either create a new user
or update the
authorizations of an
existing user
If your user management
manually is performed
manually, check the
respective checkbox (4):
Provide the manually created user and a
password
Solution Manager will then not check the
users existence, its password nor if the user
has the correct authorizations

In this step several automatic activities are performed:

Connect the managed system to Root Cause Analysis
Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)
Set up of the alerting for Early Watch Alerts
1. Choose Execute All to execute all activities

2. A progress bar shows you the current execution
status
3. If an activity fails check the log area for details

Configure Manually
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

Check Configuration
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

Complete
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

Housekeeping
Housekeeping tips
To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job. This job deletes data from the cubes in BW, compresses the cubes and deletes
requests. SAP Note 1480588
When using MS SQL or Oracle please 1178655
Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note
Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71
By default Solution Manager is configured to support about 40 SMDAgents. Adjust the number of threads SAP Note
1916137

Further information
Documentation (Master Guide, Sizing,

Upgrade)
http://service.sap.com/instguides -> SAP
Components -> SAP Solution Manager
Expert Guided Applications (EGI)

https://websmp107.sap-
ag.de/sap/bc/bsp/spn/esa_redirect/index.
htm?gotocal=X&deliverymethod=0401
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

Thank you
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

Installation & Upgrade
upgrader
The complete upgrade process is divided into eight roadmap steps.

Installation & Upgrade
upgrader
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.

Appendix
Prerequisites
Check Prerequisites
S-Users in SAP Service Market Place
S-Users are requested and maintained via SAP Service Market Place: http://service.sap.com/user-
admin

Check Prerequisites
SAP Solution Manager Support Package Level
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
Main Component Version
Solution Manager SAP_BASIS 702 SP13

ABAP Stack ST 710 SP10
Solution Manager LM-SERVICE 7.10 SP10

Java Stack
BI Component BI_CONT 706 SP06
SAP_BW 702 SP13
ST_BCO 710 SP07
CRM BBPCRM 701 SP10

Check Prerequisites
Update SLD CR Content & Model
Check SLD Prerequisites

Landscape data in Solution Manager 7.1 is stored in the Landscape Management Database which is synchronized
with SLD. This synchronization requires some minimum version of the CR Content and the model deployed in the
connected SLD:
SLD Netweaver Stack: NW 7.02 SP 06 Patch 5*
CR Content: minimum 9.1, better latest available Check SAP note 669669 for further
Model Version: minimum 1.6.36, better latest available information on CR Content & Model
update
To check the content version go to http://sldhost:sldport/sld

Check Prerequisites
RFC Destination SAPOSS
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
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
Parameters Description Recommended value
abap/buffersize Program buffer size 500000
abap/shared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdb/ntab/entrycount Number of nametab entries administrated 30000
rsdb/ntab/ftabsize Data area size for field description buffer 60000
rsdb/ntab/irbdsize Data area size for initial records buffer 15000
rtbb/buffer_length Size of single record table buffers 60000
rsdb/cua/buffersize CUA Buffer Size 10000
zcsa/table_buffer_area Size of generic table buffer 100000000
zcsa/db_max_buftab Directory entries in generic table buffer 10000
zcsa/presentation_buffer_area Size of the buffer allocated for screens 20000000

Maximum number of entries in the
sap/bufdir_entries 10000
presentation buffer
rsdb/obj/buffersize Size of export/import buffer 50000
rsdb/obj/max_objects Max. no. of exporting/importing objects 20000

Appendix
System Preparation
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 7.1 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP
Allows an easy, fast and step-by-step configuration of SAP Solution Manager
Single, easy to use wizard for system

preparation & basic configuration
Highly automated configuration
Integrated documentation for each step
Easy access to open tasks and postponed
activities
Configuration of all managed systems from
one central entry point
Configuration of other scenarios like Technical
Monitoring, Data Volume Management,
Exception Management

Configuration Dependencies
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
Service Custom Data Business Change

Job Business IT Service EWA Alert
Avail.
Managem
Code Volume Measureme Process
Process
Request
Managem Managem
Technical Monitoring (~ 1h for Infrastructure Configuration & ~1h per
Managem Managem Managem nt Platform Change Managem system type for Template Maintenance if custom templates are used)
ent Monitoring ent ent
ent ent ent Analyzer ent
Managed System Configuration (~ 1h per system + agent installation)
System Preparation
Basic Configuration (~ 3h)
(~ 2h*)
* Please add waiting time for initial LMDB sync (~4 12h))

Check Prerequisites
Optional: User management with Central User Administration
(CUA)
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

System Preparation
Check Installation
This is an automatic installation check for configuration-relevant parts of the installation:

If a check status turns red, check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual

System Preparation
Implement SAP Note
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
Check for notes which require manual activities before the

implementation and for notes that require manual post-
You will be notified by SOLMAN_SETUP if a new version of the note a
processing activities
released.

System Preparation
Configure Connectivity
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

System Preparation
Enable Web Services
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
To check the logical ports

and end points work
correctly, check them via
transaction SOAMANAGER
as described in the activity
documentation
The user SM_INTERN_WS is used for the web service communication.

The activity has to be re-performed if the user password is changed.
Make sure you change the password only in SOLMAN_SETUP System
Preparation Step 1.

System Preparation
Configure Gateway
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

System Preparation
Configure SAPconnect
In this sub-step you enable Solution Manager to send notifications:

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)
To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the
Notification Management
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.
To set up a more complex mail

configuration or change the send job
frequency, call transaction SCOT.

System Preparation
Prepare Landscape Description
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

System Preparation
Set Up LMDB - Details
Configure Object Server Add new Synchronization Connection

The Object Server Name differentiate equal objects in Select the SLD with which you want to synchronize from
different CIM servers (SLD or LMDB) the Source URL drop-down list
Choose a name that is different from all other SLD or Save & Activate your connection
LMDB object server names in you landscape
The very first activation starts an initial, full
synchronization to import all SLD system information to
the LMDB, which can take several hours.

System Preparation
Activate/Deactivate Advanced: Change Source/Target Rank

You can activate and deactivate a connection A rank is the quantifier in case of conflicting changes
After the first full synchronization and incremental The LMDB rank must be higher than the SLD rank to
synchronization imports new changes every 10 minutes protect manual changes in the LMDB from being
The job for the LMDB synchronization is called overwritten
SAP_LMDB_LDB_0000000001

System Preparation
Advanced: Add Notification Advanced: Set CR Source

For connected SLDs as of SAP Netweaver 7.1 SP 12 (SAP One of the SLD systems must be selected as the CR
note 1546079) you can configure an additional SLD Source
change notification to actively propagate SLD content This SLD must have the latest SAP Software Catalog,
changes including SAP CR Content updates and own product
definitions
If you set up notification, additional batch jobs, which actively
request SLD changes, are started at notification time. To The first synchronization connection is automatically
avoid high system load due to notifications, SLD and LMDB selected as CR source
limit notifications and notification processing if the change
rate is too high.
System landscape descriptions are always

imported from all connected SLDs. Therefore,
they must not overlap.

System Preparation
Data Migration from SMSY to LMDB

To migrate information that cannot be provided by an SLD,
After the first full LMDB synchronization you can migrate such as product system information and custom attributes,
the complete description of selected technical systems you will use the next step Migrate Data into LMDB!
from SMSY
This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no
SLD data suppliers for an automatic data transfer are available.
Never use this for systems registered in an SLD connected to
Solution Manager, otherwise there is a risk of system duplicates in
LMDB, with one system that was migrated from SMSY and the other
one synchronized from the SLD.

System Preparation
In this step, different basic ABAP configuration steps are performed:

Choose Execute All to perform all activities
In case of errors check the log area and correct the error
If the security regulations of your organization require it, you can perform the activities manually, as described in the activities
documentation

System Preparation
Prepare Outside Discovery SAP Hostagents
For SAP Hostagents the following activities have to be performed:

On each physical or virtual host:
Install/Update SAP Hostagent: The installation procedure is described in the installation guide attached to SAP note 1031096
It is recommended to enable the automatic update feature of the SAP Hostagent, so that you can update the Hostagent centrally. This is described in SAP
Note 1473974.
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.

System Preparation
Prepare Outside Discovery Diagnostics Agents On-the-fly
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.
An agent on-the-fly is similar to a standard Diagnostics Agent regarding:

Runtime behavior
Configuration
Deployment layout
Each agent node still has its own configuration and its own dedicated logical host name
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)
Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts
See the Appendix of this slide show for

installation and setup information

System Preparation
Prepare Outside Discovery Diagnostics Agents new functionality
with SP 05
Up to Solution Manager 7.1 SP 04 As of Solution Manager 7.1 SP 05

One diagnostics agent instance needed to be installed for each Introduction of the agent on-the-fly concept, that enables a diagnostics
managed host agent to start up agent instances on-the-fly as required by the current
High installation effort especially in highly virtualized environments hostname situation
Agent on-the-fly are running under the same SID and instance
Higher resource consumption by the diagnostics agents
number but in isolated processes
Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of
the parent diagnostics agent
Physical Host SAP Physical Host SAP

Hostagent Hostagent
Agent SID/SMDA98 Agent SID/SMDA97 Agent SID/SMDA98

Jstart
Logical Host A Jstart Jstart
Logical Host A
sapstartserv
sapstartserv
sapstartserv
Logical Host A Logical Host B Logical Host A
Jstart Logical Host B

Logical Host B Logical Host B

Appendix
Basic Configuration
Basic Configuration
Specify User and Connectivity Data
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

Basic Configuration
Specify Connectivity Data
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.

Basic Configuration
Set Up Credentials
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

Basic Configuration
Solution Manager Internal Connectivity
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

Basic Configuration
Configure CA Wily Introscope Extended Configuration
Expert Mode Delete References

The expert mode give you more detailed information on If you want to delete CA Wily Introscope from Solution
the connected CA Wily Introscope Manager you have to delete all references of managed
Gives you access to the Delete References functionality systems to this CA Wily Introscope first
to clean up references between managed systems and CA Please note that the Introscope agents assigned to this
Wily Introscope systems will continue to report to the old CA Wily
Introscope until you re-run the relevant activities in the
managed systems setup for these systems

Basic Configuration
Configure Manually
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

Basic Configuration
Configure CA Wily Introscope Connect existing CA Wily Introscope
Step 1: Discover Installation Step 2: Assign a User

Click Import Existing Installation Assign a connection user and a password for each CA Wily
Enter the installation path under which CA Wily Introscope Introscope Enterprise Manager
is installed on the host (default: By default, the administration user of the CA Wily
/usr/sap/ccms/wilyintroscope) Introscope Enterprise Manager is assigned as the
Select the Diagnostics agent which is installed on the host connection user
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
If the system denies

access, ensure that
the diagnostics
agent user has
read/write access
to the folder in
which CA Wily
Introscope is
installed.

Basic Configuration
Configure Manually
Maintain Logical Systems Service Content Update Configuration

The logical system name identifies the SAP system client uniquely in a Instead of applying ST-SER Support Packages you can activate the
distributed SAP landscape, this is necessary for ALE and RFC Service Content Update to keep your EarlyWatch Alert up-to-date
communication The SAP Solution Manager will then always retrieve the latest
The following functions use logical systems: corrections for the EarlyWatch Alert from SAP Service Marketplace
Customizing Distribution, Business Process Monitoring, BI Analysis,
Service Desk and Change Request Management
The SAP recommendation for the logical system name is
<SID>CLNT<client>
1. Maintain the logical

systems names in view
V_TBDLS using
transaction SM30
2. Assign the logical

system name to a
client in transaction
SCC4

Basic Configuration
Configure Manually
Enable Work Center Authorization Check

With Solution Manager 7.1 a new check on authorization object
SM_WC_VIEW is provided, with this check you control the views and
tasks (navigation panel entries) in a work center
By default this authorization check is not active, you need to activate
the authorization check by activating a BAdi
The authorization object is contained in the new
SAP_SMWORK_BASIC_* roles
Caution: Refer to the activity help for more

detailed information on the activation of the
BAdi

Basic Configuration
Configure Manually
Enable remote HTTP and R/3 Connection

With this activity you set up the HTTP and R/3 connection for the system from SAP Service Market Place to enable SAP support to access the system for
remote support
Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R/3) for details
1. Make sure SAP Router data is maintained 2. Go to 4. Click on the connection type and maintain
for your system in the system data in SAP www.service.sap.com/remoteconnection the contact person
Service Market Place and click Maintain Connections 5. Dont forget to maintain the URLs for the
3. Click on your systems and scroll to the area HTTP connection
Set up Connection types 6. In the section Open/Close Connection you
can then select your connection to open it

Basic Configuration
Configure Manually
Delete Session Documents and Download Import Calendar Entries

With this activity you can delete sessions and their documents and IT Calendar, Work Mode Management and central Notification
delete download data and reporting documents of a solution or Management use factory and holiday calendars
landscape With this activity you extend the validity date of the SAP calendars if
When deleting, a check is made for inconsistencies within the sessions necessary
and documents to be deleted
This activity helps you to reduce data volume in Solution Manager
1. Call transaction SCAL and
display the Factory Calendars
2. Make sure they are valid until
2050 In case the calendars are only
valid until 2010 you can
import the calendars valid
until 2050 from SAP Note
1426524
If SAP Calendar was
changed you can manually
maintain the calendars as
described in SAP note
1426524

Basic Configuration
Configure Manually
Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 7.1 and hence some configuration has to be done before it can
be used
1. Copy transaction type SMOT to transaction type ZMOT
2. Maintain your custom transaction type if you chose another name than ZMOT
3. Create Business Partners for Solution Manager users
4. Create an Organizational Model
5. Schedule task scheduler batch job
Please refer for SAP Note 1825634 for more details

Basic Configuration
In this step you schedule automatic activities in Solution Manager:

Solution Manager BW system related setup and customizing is performed
Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer, Issue Management
and Service Desk
Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager
Scheduling of SAP basis and Solution Manager specific house-keeping jobs
Setup of Solution Manager Diagnostics and the extractor framework
Setup of the monitoring and alerting infrastructure
1. Choose Execute All to execute all activities

2. A progress bar shows you the current execution
status
3. If an activity fails check the log area for details

Basic Configuration
Configure Engagement Reporting
In this step you perform further manual configuration:

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP
Service and Support Backbone to generate landscape data and engagement reports
The activities in this step have some automatic activities from the previous step as prerequisite, check the activity
documentation and make sure all necessary activities from the previous step were performed successfully
Start the activities via the link in the navigation column, the setup is done as soon as the transactions are launched

Basic Configuration
Create Configuration Users
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

Appendix
Managed System Configuration
Status Overview
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

Assign Product Assign Product System
Assign Product System:

1. Click the Assign Product System link
2. Select the product system, if it doesnt

exist, use the Create button to create it
3. Use the Proposal option to find the

correct product version and product
instances for your system
4. Select the correct product instances
5. Save

Assign Product Assign Product System
Assign Product System (option):

If the correct product version is not in the list,
close the pop-up
1. Switch to the tab Product Instance

(Detail) and use the Add button to
assign the product instances manually
2. Use Proposal For All Software

Components
3. Select the correct product instance
4. Now assign the product system on the tab

Product Instances with the button Edit
Product System Assignment
5. Select Assign All Unassigned
6. Save

Connect Managed System Create RFC Destinations
Create RFC Destinations:

1. Select the client for which you want to
create RFC destinations on the table
above
2. Add additional information to the RFC

(e.g. if you want to use load balancing)
3. Select the RFCs you want to create and

how you want to create the users used in
the RFC destination
4. Fill in the administrator credentials (if you

create BACK RFCs you also need to
provide credentials for Solution Manager)
you can only add credentials after
selecting RFCs to create or update
5. Click the Execute button

Configure Manually
Maintain SAP Router data Adjust HTTP Log Parameter

By maintaining SAP router data for the managed system in the SAP To be able to analyze logs written by the Internet Communication
Service Market place you make sure the system can be opened for Manager (ICM) with Root Cause Analysis you need to maintain the
remote service connections additional parameter icm/HTTP/logging_0
Navigate to: http://service.sap.com/system-data and select the This activity is only needed for ABAP-based systems and for J2EE
managed system systems based on SAP Netweaver 7.10 or higher
Maintain the system data for the SAP Router that you wish to use on See the activity help for details on how to perform the activity
the System tab, in the SAP Router area,
Click on Multiple Links to open the sub-activities

Configure Manually
Restart JAVA Stack Enable remote R/3 Connection

Some activities during the automatic configuration require the restart of To enable remote supportability for the managed system you need to
the Java Stack: maintain the remote R/3 connection for the system in Service Market
The adjustment of the JVM parameters Place
Go to http://service.sap.com/remoteconnection and click Maintain
The deployment of the Wily Byte Code Agent
Connections
The restart can be scheduled during maintenance, but until the restart
Select the managed system and the R/3 Support connection type
no JVM specific metrics (like Garbage Collection and Heap Size) are
reported to CA Introscope Enterprise Manager

2013 SAP AG. 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 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.
National product specifications may vary.
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.

Demystifying Solution Manager 7.1 - Configuration Focus On Diagnostics Roland Hoeller SAP PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Demystifying Solution Manager 7.1 - Configuration Focus On Diagnostics Roland Hoeller SAP PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

Welcome to the Solution

2013 SAP AG. All rights reserved. Public 3

Before starting with the configuration of SAP

2013 SAP AG. All rights reserved. Public 5

Please ensure that you entered 001 as

2013 SAP AG. All rights reserved. Public 6

2013 SAP AG. All rights reserved. Public 7

Step Help Section

2013 SAP AG. All rights reserved. Public 8

Prepares the Solution Manager system for the basic configuration

Connection and configuration of managed systems

2013 SAP AG. All rights reserved. Public 9

The scenario System Preparation consists of

2013 SAP AG. All rights reserved. Public 11

Provide the manually created user

2013 SAP AG. All rights reserved. Public 12

Enter the URL and the port for the

2013 SAP AG. All rights reserved. Public 13

Read the documentation provided

The explicit setup is necessary

2013 SAP AG. All rights reserved. Public 14

New agents and agents (re)connecting to Solution Manager will

2013 SAP AG. All rights reserved. Public 15

2013 SAP AG. All rights reserved. Public 16

2013 SAP AG. All rights reserved. Public 17

This migration is necessary after an

2013 SAP AG. All rights reserved. Public 18

For more detailed information please refer

2013 SAP AG. All rights reserved. Public 19

For Diagnostics Agents the following activities have to be performed:

It is highly recommended to install all agents and

Please visit the SOLMAN_SETUP Wiki in SDN to

2013 SAP AG. All rights reserved. Public 20

The agents of the following systems

Only agents using the direct connection

*The list of SLDs is maintained in step 5.1

2013 SAP AG. All rights reserved. Public 21

2013 SAP AG. All rights reserved. Public 22

The scenario Basic Configuration consists of

2013 SAP AG. All rights reserved. Public 24

In this step the first Solution is created in Solution Manager:

2013 SAP AG. All rights reserved. Public 25

By default the BW client is always set to client 001.

2013 SAP AG. All rights reserved. Public 26

2013 SAP AG. All rights reserved. Public 27

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager:

* Dependencies on IS Bytecode agents:

2013 SAP AG. All rights reserved. Public 28

1. Run the report COM_PRODUCT_UPDATE

2. Run the automatic activities by choosing

2013 SAP AG. All rights reserved. Public 29

2013 SAP AG. All rights reserved. Public 30

The Managed Systems Configuration consists

2013 SAP AG. All rights reserved. Public 32

2013 SAP AG. All rights reserved. Public 33

2013 SAP AG. All rights reserved. Public 34

2013 SAP AG. All rights reserved. Public 35

Set Diagnostics Relevant Flag:

A. Set the Diagnostics Relevant flag

Or edit the assignment manually. To do this

B. Set the Diagnostics Relevant flag on the

C. Set the Diagnostics Relevant flag for

Make sure to select the product