sapsolutionmanager7.1_sizingguide
DESCRIPTION
SAPSolutionManager7.1_SizingGuide.pdfTRANSCRIPT
SAP Solution Manager 7.1
Sizing Guide
SAP Solution Manager
Sizing Guide
Document Version 2.1 – October 2012
Valid for SAP Solution Manager 7.1 SP5
© Copyright 2007 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.
Microsoft, Windows, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, and Informix are trademarks
or registered trademarks of IBM Corporation in the United
States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks
of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or
registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems,
Inc., used under license for technology invented and
implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, 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 in several
other countries all over the world. All other product and
service names mentioned are the trademarks of their
respective companies. Data contained in this document
serves informational purposes only. National product
specifications may vary.
These materials are subject to change without notice. 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.
Disclaimer
Some components of this product are based on Java™. Any
code change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is only
to be used by SAP’s Support Services and may not be
modified or altered in any way.
Documentation on SAP Service Marketplace
You can find this documentation at
service.sap.com/instguidesNW04
SAP AG
Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20
www.sap.com
T yp o g r a p h i c C o n ve n t i o n s
Type Style Represents
Example Text
Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT
Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.
Example
text
Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.
Example
text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example
text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.
EXAMPLE
TEXT
Keys on the keyboard, for example, F2 or ENTER.
I c o ns
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
October 2012
Sizing Guide
Contents
1 SUMMARY .......................................................................................................................... 2
2 SAP SOLUTION MANAGER ARCHITECTURE ................................................................. 2
3 FACTORS THAT INFLUENCE PERFORMANCE .............................................................. 6
4 SIZING METHODOLOGY ................................................................................................... 9
4.1 Approach ................................................................................................................... 9 4.2 Managed Systems characteristics .......................................................................... 9
4.2.1 Size of the managed landscape ..................................................................... 9 4.2.2 Solution type of the managed landscape ........................................................ 9 4.2.3 Assumptions.................................................................................................. 11 4.2.4 SAP Solution Manager Scenario .................................................................. 11 4.2.5 Number of Business Processes .................................................................... 11 4.2.6 Number of Concurrent active users .............................................................. 12 4.2.7 Number of EEM Robots ................................................................................ 12 4.2.8 Number of Service Desk documents ............................................................ 12
4.3 Solution Manager Sizing KPIs ............................................................................... 13 4.4 SAP Solution Manager's sizing ............................................................................. 15
4.4.1 Introscope SmartStor .................................................................................... 15 4.4.2 Solution Manager Database ......................................................................... 15 4.4.3 Database Monthly growth ............................................................................. 21 4.4.4 Cluster Consideration ................................................................................... 22 4.4.5 CPU and Memory ......................................................................................... 23 4.4.6 Network ......................................................................................................... 27 4.4.7 Impact on Managed systems ........................................................................ 27
5 PERFORMANCE SETTINGS ............................................................................................ 28
5.1 Solution Manager Settings .................................................................................... 28 5.2 Wily IS EM setup and tuning ................................................................................. 29
October 2012
Sizing Guide 2
1 Summary This document describes how to estimate hardware resources that are necessary to implement different scenario on SAP Solution Manager7.1 System.
It provides rules, guidelines, and best practices for the definition of hardware requirements like mainmemory, disk space and CPU.
It will also identify the required cluster configuration for Solution Manager and for Introscope infrastructureto implement SAP Solution Manager.
This document should be used with the SAP Solution Manager Sizing spreadsheet which implements the formulas described in this document.
2 SAP Solution Manager Architecture The SAP Solution Manager runs in a separate central system, to which all other SAP systems areconnected.
Systems that are administered using the SAP Solution Manager are referred to as"managed systems". These managed systems can be bundled within a solution.
Sizing of SAP Solution Manager does not include the sizing of the managed systems, but it is strongly dependent on the size of the managed systems, and on the number of managed systems connected to the Solution Manager.
The architecture of SAP Solution Manager relies on the following elements
Agents technology
SAP Solution Manager
Introscope Enterprise Manager (EM)
Agents technology
Two agents are installed on the managed systems:
SAP Host agents
SMD agents running at the Host level of the managed systems.
Introscope Agents running at the SAP J2EE instances of the managed systems.
Those agents send data on regular pre-defined time interval from the managed systems to Solution Manager. The amount of data (size and frequency) sent by those agents will be the main factor influencing the performance of the system.
Solution Manager
SAP Solution Manager runs on top a SAP NetWeaver dual stack. It collects and aggregates data sent by the SMD agents.
In a simple environment, this SAP NetWeaver 04s double stack manages all data collection and aggregation. In a more complex environment, a NetWeaver cluster must be implemented to manage multiple agents.
Introscope Enterprise Manager
Introscope EM is a server running on a central place that collects, performs calculations on, and stores metricsreported by multiple agents. In a simple Introscope environment, one single standalone Enterprise Manager collects, persists, and processes all theagent metrics, then supplies the resultant data for viewing in the Introscope Workstation orWebView browser instances.
October 2012
Sizing Guide 3
In a more complex environment, two cluster scenarios are recommended by SAP, depending on the nature of the managed systems landscape.
MOM Collector: Enterprise Managers in the role of Collectors can beclustered so that their collected metrics data is compiled in a single Manager of Managers(MOM) EM, which provides a unified view of all the metrics to the connected Workstationand WebView instances. Each Collector will be associated to a Smart Data Store. In this configuration, all EMs in a MOM / Collector setup should be located in the same LAN.
This document will consider:
The sizing for the ABAP stack requirements, the J2EE stack requirements and the Introscope EM requirements.
The impact of the Agents on the managed systems.
This document will not consider the performance tuning of SAP Solution Manager.
October 2012
Sizing Guide 4
The picture below describes an example of simple Solution Manager Architecture.
SMD agents installed in the managed systems landscape are used to collect Extractor Framework records and Introscope Metrics. Those data are then aggregated into the Solution Manager BI Database and the IntroscopeSmartStor.
The Introscope Metrics data are reported every 15 seconds.
The Extractor Framework records are extracted every hour.
The following picture gives an overview of the different clustering capabilities of Solution Manager to implement E2E RCA in a complex environment:
Solution
Diagnostics Agents
Managing System
Solution Manager Introscope EM
Managed Landscape
Solution
Diagnostics Agents
Solution
Diagnostics Agents
BI Database Introscope Smart Store
Introscope metrics Extractor Framework Records
October 2012
Sizing Guide 5
Managing System
Solution
Diagnostics Agents
Managed Landscape
Solution
Diagnostics Agents
Solution
Diagnostics Agents
Solution Manager
BI Database
Introscope metrics
BI Extractor Framework
Records
Introscope EM MOM
ABAP
instance
JavaServer
Introscope EM
Collector
Introscope Smart Store
Introscope EM
Introscope Smart Store
Solution
Diagnostics Agents
Managed Landscape
Solution
Diagnostics Agents
Solution
Diagnostics Agents
Introscope metrics
October 2012
Sizing Guide 6
3 Factors that influence performance The sizing of SAP Solution Manager depends on the following factors:
Type of Scenario implemented in SAP Solution Manager
Number and roleof concurrent Users accessing Solution Manager
Solution Landscape:
Hardware configuration of the managed Landscapes
Software infrastructure of the managed landscapes
Product instances
Load of the Solution
SAP Solution Manager Scenario
The factors influencing the performance depend on the different scenarios that will be implemented on Solution Manager.
The following scenarios are considered in this document:
Root Cause Analysis/Basic Configuration Root Cause Analysis provides standardized tools to enable a systematic and targeted end-to-end component localization of the root cause of IT problems. As Root Cause Analysis is a mandatory scenario in order to implement SAP Solution Manager, it also includes the Basic Configuration of Solution Manager.
Collaboration The Collaboration section of the SAP Solution Manager is the point of access to SAP support services, including remote services, on-site services, self services, and Best Practicedocuments.
Service Desk The Service Desk of the SAP Solution Manager offers a complete infrastructure for organizing andoperating solution-wide support.
Change Request Management Theobjective of Change Management is to carry out changes economically and in a timely manner withminimal risk. Change Request Management includes processes for managing change requests,project management, and change logistics.
Implementation and Upgrade The Implementation and Upgrade scenarios support the implementation of customer projects andthe definition of template projects and upgrade projects. It includes roadmaps, editor for creating and maintaining business blueprints, access to theImplementation Guides (IMG), and tools for testing, monitoring and distributing Customizing.
Technical Monitoring
The technical monitoring scenario monitors systems performance, availability, configuration and exception. It includes also specific product monitoring such as BI, PI and connection Monitoring.
End User Experience Monitoring
The EEM scenario controls the availability and the performance of the solution from user point of view
October 2012
Sizing Guide 7
Concurrent active Users
Concurrent users are working simultaneously or concurrently in the system. They consume system resources at the same time.
Active users are defined as running a given number of business processes in a given time period.
We distinguish between three categories of active users, because these categories represent typical activity patterns of users
- ALow User or occasional user processes on average ten interaction steps an hour or one every six minutes.
- A Medium User processes in average 120 interaction steps an hour or one every 30 seconds. Most users will have a comparable profile
- A High User processes an average of 360 interaction steps an hour or one every 10 seconds. This is typical for power users working in call centers or doing data entry.
In addition to those three categories, during the sizing process of Solution Manager, we will distinguish later in this document between different types of User depending on their role on Solution Manager.
For example, a Service Desk User will not consume the same level of resources than a Administrator using only Solution Monitoring and Root Cause Analysis.
Solution Landscape
The following elements of the solution landscape of the managed systems connected to SAP Solution Manager will influence the sizing
Number of Systems.
Number of hosts (or virtual hosts) per system.
An SMD Agent is installed on each host (physical or virtual).
Number of server nodes or instances per host.
The combination of systems/hosts/nodes will determine the number of agents reporting data to Solution Manager.
The combination of systems/hosts will give the number of alerts reported for the monitoring of the solution.
October 2012
Sizing Guide 8
Product instances
The volume of data reported by the managed systems is highly dependent on the software components running on the managed systems.
The type of products (Portal, XI, ECC…) running in the solution, will indicate the nature of those components and thus will indicate the volume of data sent by the agents running on the managed systems.
Load of the Solution
The products of the solution gives already a good indication on the data sent by the agents, but to get the correct amount of data, a user sizing or a throughput sizing on the managed systems is needed.
To simplify the process, we assume that the size of the managed system goes into one of the following category:
M
L
XL
XXL
The load of the solution will influence the number of data collected in SAP Solution Manager.
Standard Sizing for SAP Solution Manager
The standard sizing recommendations for End-to-End Root Cause Analysis including Basic Configuration in SAP Solution Manager are the following:
Data Base Disk Space
installation
SAPs Memory
SAP Solution Manager 80 GB (DB) 20 GB 2000 8 GB
Introscope EM 40 GB (SmartStor)
250 MB 2000 4 GB
Remarks on standard settings
This sizing should always be checked against your landscape configuration with the guidelines described in the rest of the document.
The following rules in this document are used to validate that the standard configuration will be enough to support the operation of E2E RCA in your landscape.
Solution Manager and Introscope EM can be installed on two different servers or on the same server.
In general, those sizing recommendations correspond to the implementation of the E2E RCA scenario for a maximum of 5 large Solutions (including different roles: Dev, QA, Prod) for different product types.
October 2012
Sizing Guide 9
4 Sizing methodology
4.1 Approach
The sizing methodology for RCA in SAP Solution Manager follows the steps described below:
Characteristics of the managed systems landscape
a. Size of the managed landscape.
b. Product instances of the managed Landscape.
c. System Load of the managed Landscape.
d. Solution Manager's scenario.
e. Number of concurrent users.
Computation of the sizing KPIs corresponding to the characteristics of the managed systems.
Calculation of SAP Solution Manager's resources.
a. Disk Size.
b. Cluster configuration.
c. Hardware Sizing (CPU and Memory).
d. Impact on managed systems.
4.2 Managed Systems characteristics
4.2.1 Size of the managed landscape
The first questions to answer when considering the solution manager environment are:
How many systems do I have to connect to my Solution Manager?
How many server nodes and hosts are supporting those systems?
Parameters Description
Number of systems
#Systems
For each system, the minimal DB size for SAP Solution Manager and Introscope EM is computedlater in this document.
Number of hosts per system
#Servers
One SMD agent will be installed per host.
The number of SMD agents will be used later in the sizing process.
Number of Java Server nodes per systems
#Java Server nodes
One Introscope agent will be installed per Java Server node.
The number of Introscope agents will be used later in the sizing process.
4.2.2 Solution type of the managed landscape
The next question to answer is about the amount of data that will be collected on solution Manager. It depends on the products running in the solution and the expected load on the solution.
The load can to be either measured on existing systems or estimated with a T-shirt Sizing project. Please refer to SAP Quick-Sizer reference: http://service.sap.com/QuickSizer for more information.
October 2012
Sizing Guide 10
Parameters Description
Type of the solution The amount of data collected by the RCA Solution Operation tool depends on the type of the solution.
A portal solution will generate iViews metrics that are not reported in an XI solution. On the contrary, an XI solution will produce, queue information metrics.
Expected Load per system
The load on the system depends on the number of users and the transactional throughput on the system.
This measure depends in general on the role assigned to the system. For example, a 'production' system will most likely produce L or XL load of data.
In the same way, a sand-box, or QA system will be of type S or M.
The expected loadshould be classified in one of the following category.
Load per system Description / Guidelines
M Dev system
L Production system with medium volume of users or transactions
XL Production system for large volume of users or transactions
XXL Production system for extra large volume of users or transactions
October 2012
Sizing Guide 11
4.2.3 Assumptions
Inorder to simplify the process, we assume that the number of data reported per usage type could be classified into two categories:
High
Low
So for each product supported byRCA in SAP Solution Manager, the following approximation is performed regarding the number of metrics reported to IntroscopeEM (#metrics) and the number of Extractor Framework recordscollected by Solution Manager (#Ext Fmk Records).
Usage type #metrics #Ext Fmk Records
WebAS6.40/7.00 (ABAP) Low High
WebAS6.40/7.00 (J2EE) High Low
ECC5.0 / 6.0 High High
Portal incl. KMC based on NW04/NW04S High Low
TRex7.0x/7.1X Low Low
BI 3.1/3.5/7.0x/7.1x Low High
XI 3.x/7.0x/7.1x High High
CRM4.0 Low High
CRM5.0 / 5.2 /2007 High High
SRM 6.0 Low Low
Duet 1.0 Low Low
MDM5.5 SP6 P1 / 7.1 Low Low
xMII 11.5 Low Low
SAP Business byDesign High High
Mobile Infrastructure Low Low
WEB Dispatcher 7.10 Low Low
SAP Solution Manager 7.0x Low High
SAP HANA Low High
SAP Data Service 4.0 Low High
4.2.4 SAP Solution Manager Scenario
The next KPI to find is the list of Solution Manager's scenarios that will be implemented. By default, the Root Cause Analysis/Basic configuration has to be implemented. The rest of the scenarios are optional as they depend on your Solution Manager's requirements.
4.2.5 Number of Business Processes
For the Business Process monitoring and Solution Documentation scenario, you need to find out how many business processes will be involved in those scenarios.
October 2012
Sizing Guide 12
For BP Monitoring. The follows KPIs are used in the Solution Manager Sizing
#Alerts = 10 Number of alerts produced per connected host
#Servers = 3 Number of hosts per system
#Systems = 5 Number of manager systems included in BP Monitoring scenario
4.2.6 Number of Concurrent active users
The last point to determine is the number of concurrent active users per Solution Manager's scenarios. Depending on the type of scenario implemented on your Solution Manager, the behavior of the Solution Manager's Users will not be the same. For this reason, we consider two Roles of Users when performing a sizing of SAP Solution Manager.
Role 1:
Users running the following scenarios
Service Desk,
CharM,
Collaboration.
Role 2:
Users running the following scenario
Implementation
Upgrade
Root Cause Analysis and Solution Monitoring are not taken into account due to the fact that they are not user's centric application. The main factors influencing the performance for those scenarios are the load of data produced by the managed systems.
4.2.7 Number of EEM Robots
In End User Experience Monitoring scenario, we need to consider the number of robots that will be implemented.
4.2.8 Number of Service Desk documents
In Service Desk scenario, the KPI to consider is the number of tickets created per day.
October 2012
Sizing Guide 13
4.3 Solution Manager Sizing KPIs
Based on the characteristics of the managed systems landscape, the two tables below are used as input to estimate the KPIs of the Solution Manager's sizing.
This table below is used to identify the relevant sizing KPIs for one System instance of a specific product, based on the Load (observed or estimated) and the type of product.
System Load M
L XL
XXL
Low High Low High Low High Low High
Sizing Units Introscope Agents
Number of Introscope metrics per IS agents
#metrics per Introscope Agents
500 1500 750 4000 1000 7500 4000 30000
Sizing Units SMD agents
Number of Introscope metrics per SMD agents
#metrics per SMD Agents
250 1000 500 1500 750 2000 3000 8000
Sizing Units Managed Systems
Number of Extractor Framework records per day per Managed Systems
#Ext Fmk Records
5000 25000 10000 50000 15000 100000
60000 400000
Sizing Units Number of Hosts
Number of Alerts produced per connected Hosts
#Alerts
40 40 80 320
By repeating this step for all systems of the solution landscape attached to your Solution Manager, you will find the total number of data collected and aggregated in SAP Solution Manager.
October 2012
Sizing Guide 14
The table below is used to classify the concurrent active users depending on their roles and categories.
As described earlier in this document, two roles are relevant for the Sizing's project. For each roles, we consider three families of Users: Low, Medium and High as described in the table below:
User Description
#Role 1 Low Activity User 10 dialog steps per hour or less for Service Desk, CharM or Collaboration scenario.
#Role 1 Medium Activity User 2 dialog steps per minute or less for Service Desk, CharM or Collaboration scenario.
#Role 1 High Activity User 6 dialog steps or more per minute or less for Service Desk, CharM or Collaboration scenario.
#Role 2 Low Activity User 10 dialog steps per hour or less for Implementation and Upgrade scenario.
#Role 2 Medium Activity User 2 dialog steps per minute or less for Implementation and Upgrade scenario.
#Role 2 High Activity User 6 dialog steps or more per minute or less for Implementation and Upgrade scenario.
The KPIs corresponding to your solution landscape will be used in the rest of the document to calculate the hardware resources and the cluster configuration for a correct sizing of RCA in SAP Solution Manager:
#metrics per IS Agents
#metrics per SMD Agents
#Ext Fmk Records
#MAI Ext Fmk Records
#BPNumber
#Role <RoleID><Category> Activity User
#Java Server nodes
#Alerts
#Servers
#Systems
October 2012
Sizing Guide 15
4.4 SAP Solution Manager's sizing
4.4.1 IntroscopeSmartStor
Root Cause Analysis
Thesize of the IntroscopeSmartStor is given by adding the size for all systems as described in the formulas below. This size is a fixed size as the data are aggregated by the IS EM.
IntroscopeSmartStorSize (MB) (#Java Server nodes * #metrics per IS Agents + #Servers * #metrics per SMD agents)* 0,09
4.4.2 Solution Manager Database
The size of the Solution Manager Database can be identified by using the formulas corresponding to the scenarios implemented for your Solution Manager.
Basic + Root Cause Analysis
BI Database Size (MB) INITIAL + (#Systems * #Ext Fmk Records) * 0.12
End-User Experience Monitoring (Technical Operations)
BI Database Size (MB) (#nb of Robots *1000) * 0.12
CharM + Implementation
DB SIZE (MB) #Role 1 Low Activity User / 300 + #Role 1 Medium Activity User / 30 + #Role 1 High Activity User / 10 ) * 3600 * Number of work hour per day * Workdays per year * 5,12 / 1000 / 1000
#Role 2 Low Activity User / 300 + #Role 2 Medium Activity User / 30 + #Role 2 High Activity User / 10 ) * Workdays per year * 531738 / 10000 / 1000
Service Desk
DB SIZE (MB) #number of tickets per day * Workdays per year *5.12 / 5 / 1000
Solution documentation
DB SIZE (MB) #BPNumber*200
October 2012
Sizing Guide 16
Technical Monitoring
Input table
Input table #product
#number of metrics
#percentage of BI records
#alerts #host dependant metrics
#metric type
Adobe DS 7.0 200000 60 % 30 60 % 20
BW 3.1/3.5/7.0x/7.1x
200000 60 % 30 60 % 20
Business byDesign
200000 60 % 30 60 % 20
CRM 4.0 200000 60 % 30 60 % 20
CRM 5.0/5.2/2007
200000 60 % 30 60 % 20
CRM 7.0/7.01 200000 60 % 30 60 % 20
Duet 1.0 200000 60 % 30 60 % 20
ECC 5.0/6.0 ECC 5.0/6.0
200000 60 % 30 60 % 20
MDM 5.5 SP6 P1/7.1 P2
200000 60 % 30 60 % 20
Mobile Infrastructure
200000 60 % 30 60 % 20
Portal incl. TREX and KMC based on NW04/NW04S
200000 60 % 30 60 % 20
SAP Business Object Strategy Management 7.0/7.5
200000 60 % 30 60 % 20
SAP CPS 7.0 by Redwood
200000 60 % 30 60 % 20
SAP Data Service 4.0
200000
60 %
30
60 %
20
SAP eSourcing 4.2/5.0
200000 60% 30 60% 20
SAP GRC AC 5.2/5.3
200000
60 %
30
60 %
20
SAP HANA
200000
60%
30
60%
20
October 2012
Sizing Guide 17
SAP ME 5.1 200000 60 % 30 60 % 20
SAP Netweaver CE 7.1
200000 60 % 30 60 % 20
SAP Solution Manager 7.0x
200000 60 % 30 60 % 20
SAP xMII 11.5/12
200000 60 % 30 60 % 20
SCM 4.1/5.0/2007/7.0
200000 60 % 30 60 % 20
SRM 5.0/6.0/7.0 200000 60 % 30 60 % 20
TREX 7.0x/7.1x 200000 60 % 30 60 % 20
WEB Dispatcher 7.10
200000 60 % 30 60 % 20
WebAS 6.40/7.0x/7.1x (ABAP)
200000 60 % 30 60 % 20
WebAS 6.40/7.0x/7.1x (J2EE)
200000 60 % 30 60 % 20
PI 3.x/7.0x/7.1x 200000 60 % 30 60 % 20
October 2012
Sizing Guide 19
Granularity
#granu Granu Type Explanation Value
#granu1 Minute (one day has 1440 minutes)
1440
#granu2 Hour 24 hours per day 24
#granu3 Day 1
#granu4 Weekly 1/7 0.143
#granu5 weekly with hour
profile
1/7 * 24 3.429
#granu6 Monthly 1/30 0.033
#granu7 Monthly with hourly profile
(1 / 30) * 24 0.8
Lifetime
#lifetime LifeTime Type Explanation Value
#lifetime 1 Minute 8 days history 8
#lifetime2 Hour 1 month history 31
#lifetime3 Day 100 days 100
#lifetime4 Weekly One year history
52
#lifetime5 weekly with hourly profile
1 month history 31
#lifetime6 Monthly 4 years history 47
#lifetime7 Monthly with hourly profile
1 month history 31
October 2012
Sizing Guide 20
KPIs
#number_of_metric_types = 800 + #product_metric_type * #product
#number_BI_metrics =
#systems * #number_of_metrics * #percentage_of_BI_records*
#host_dependant_metrics * #number_of_vhosts
+
#systems * #number_of_metrics * #percentage_of_BI_records *
(1-#host_dependant_metrics)
Alert
Alert tables size (KB) = #system * #alerts * 20
Aggregates
Aggregates table size (KB) = #number_of_metric_types * 220
DSO
Data growth per day (bytes) =
#granu1 * (#number_BI_metrics) +
#granu2 * (#number_BI_metrics) +
….+
#granu7 * (#number_BI_metrics)
Assumption:
The DSO size is included in the BI table size.
BI
#number_of_BI_record =
#granu1 * #lifetime1 *(#number_BI_metrics)+
#granu2 * #lifetime1 *(#number_BI_metrics)+
….+
#granu7 * #lifetime7 * (#number_BI_metrics)
Data Volume (Bytes stored in BI) =
#number_of_BI_records * 160 Byte
+ #number_BI_metrics *(8(dimtable)+ 76(SID table))
+ #number_of_metric_types * (8 + 132 )
+ #number_of_metric_types * (12 + 32 + 132) ( Metric name)
+ #number_of_systems*(44 + 72 + 52 + 72 + 52 + 52 + 72 + 52+
+ #number_of_vhosts * (16 + 132 + 132 + 132)
+ #number_of_vhosts * (12 + 132 + 132) (Object)
+ #number_of_java_nodes * (16 + 24 + 132 + 132)
October 2012
Sizing Guide 21
Assumptions:
- The "object" dimension is equal to the "host" dimension.
- The metric name dimension is equal to the metric type dimension.
DB SIZE (GB) BI Data Volume + Aggregates + Alert tables size
4.4.3 Database Monthly growth
Basic
The BI Aggregation mechanism will add an additional monthly growth of 1% of the total size of the BI Database. Please refer to the BI archiving documentation to manage this growth.
Technical Monitoring
No monthly data base growth in this scenario is expected.
CharM, Implementation and Service Desk
The data base growth for those scenarios corresponds to the same valus computed by formulas mentioned above.
October 2012
Sizing Guide 22
4.4.4 Cluster Consideration
The following formulas have to be taken into consideration when clustering Solution Manager and Introscope EM to support E2E RCA for complex and large Solution landscape.
You should consider clustering when the number of SMD agents is greater than 400 or/and the number of IS agents is greater than 50.
Root Cause Analysis
Rules Description
One Server Node can handle 500 SMD agents.
Add one additional Server node every 100 connected SMD agents.
A IS Collector can handle 500 000 metrics.
Add one additional IS Collector every 500 000 metrics.
For example, for a XL/High system it represents 70IntroscopeAgents.
1 dialog work process can handle 100000Extractor Framework Records per day.
This rule allows respecting the1 hour extractor framework processing time window.
Add one dialog work process for every system producing 100000 Extractor Framework Records per day.
Add one dialog work process for every group of systems producing 100000 Extractor Framework Records per day.
Depending on the number of dialog work processes derived from this formula, you may consider to add additional ABAP instances to your Solution Manager.
October 2012
Sizing Guide 23
4.4.5 CPU and Memory
The CPU and memory configuration can be identified by using the formulas corresponding to the scenarios implemented for your Solution Manager.
Basic configuration
Each cluster element added in Solution Manager to support the managed landscape has to follow the rules below:
Memory (GB) CPU (SAPS)
Solution Manager main instance 8 2000
Additional Solution Manager server node 4 2000
Introscope EM 4 2000
Additional IS Collector 4 2000
#SAPS_per_system #SAPS_per_server
0,03 0,04
#mem_per_system #mem_per_server
4 5
Size #factor
M 0,5
L 1
XL 2
XXL 5
October 2012
Sizing Guide 24
Memory (GB) CPU (SAPS)
Application Server LF * (#system * #factor * #mem_per_system + #server * #factor * #mem_per_server) * 3/5
LF * (#system * #factor * #saps_per_system + #server * #factor * #saps_per_server) * 3/5
Database Server LF * (#system * #factor * #mem_per_system + #server * #factor * #mem_per_server) * 2/5
LF * (#system * #factor * #saps_per_system + #server * #factor * #saps_per_server) * 2/5
Note LF: Load Factor = 65%
Solution Documentation
Memory (GB) CPU (SAPS)
Database Server (#BPNumber *0,6)/ 500 (#BPNumber * 2.5)
Service Desk
Memory (GB) CPU (SAPS)
Application Server #number_of_users * 62 / 1000 (#number_of_tickets_per_day *10 /24 / 3600) * 730
Database Server #number_of_users * 6,2 / 1000 (#number_of_tickets_per_day *10 / 24 /3600) *730 * 1/5
Assumptions:
- The number of dialog steps to complete a tickets is : 10.
Role 1 User (CharM)
Memory (GB) CPU (SAPS)
Application Server (#Role 1 Low Activity User +#Role 1 Medium Activity User + #Role 1 High Activity User ) * 62 / 1000
(#Role 1 Low Activity User / 300+ #Role 1 Medium Activity User /30+ #Role 1 High Activity User / 10 ) * 730 * 4/5
Database Server (#Role 1 Low Activity User + #Role 1 Medium Activity User + #Role 1 High Activity User ) * 6.2 / 1000
(#Role 1 Low Activity User / 300+ #Role 1 Medium Activity User / 30+ #Role 1 High Activity User / 10 ) * 730 * 1/5
October 2012
Sizing Guide 25
Role 2 User (Implementation)
Memory (GB) CPU (SAPS)
Application Server (#Role 2 Low Activity User +#Role 2Medium Activity User+#Role 2High Activity User )*18,75/1000
(#Role 2 Low Activity User / 300+ #Role 2 Medium Activity User / 30+ #Role 2 High Activity User / 10 ) * (200000/100/20)*3)4/5
Database Server (#Role 2 Low Activity User +#Role 2Medium Activity User+#Role 2High Activity User )*2,55/1000
(#Role 2 Low Activity User /300+ #Role 2 Medium Activity User /30+ #Role 2 High Activity User / 10 ) * (20000/100/20)*3)1/5
Note For Service Desk and CharM scenarios users are concurrent Users.
End User Experience Monitoring
Memory and CPU depends in number of robots which are considered as Virtual Hosts. One Java Server node can manage 500 Virtual Host.
Technical Monitoring
#SAPS_per_system #SAPS_per_server
0,02 0,03
#mem_per_system #mem_per_server
4 5
Size #factor
M 0,75
L 1
XL 2
XXL 5
Memory (GB) CPU (SAPS)
Application Server #system * #factor * #mem_per_system + #server
(#system * #factor * #saps_per_system + #server
October 2012
Sizing Guide 26
* #factor * mem_per_server * 3/5
* #factor * #saps_per_server) * 3/5
Database Server #system * #factor * #mem_per_system + #server * #factor * mem_per_server * 2/5
(#system * #factor * #saps_per_system + #server * #factor * #saps_per_server)*2/5
Shared Mem (KB) = #number_of_metric_types * 18
October 2012
Sizing Guide 27
4.4.6 Network
For best usage, network responses times should be adapted to the different needs of communication used between the different elements of the RCA architecture in Solution Manager.
Network Requirement
Collector to MOM When a MOM requests data from a Collector, theroundtrip response must be less than 500 ms.
Diagnostics agents (Introscope Agents, SMD Agents) to Solution Manager systems
The network transfer rate between Solution Manager and the Managed systems must be greater or equal than 100Mbit/s.
4.4.7 Impact on Managed systems
SMD agents, IS agents and Extractor tasks have a very limited impact on the managed systems
The table below summarizes the resources required by RCA in SAP Solution Manager's activities (Introscope Agents, SMD Agents, Extractor jobs) on the managed systems:
The numbers below are given for a XL/High system.
Impact on managed systems
Disk (MB) SMD Agent 7.0x: 200 MB per Host (or Virtual Host) where an SMD Agent is installed.
SMD Agent 7.1X: 500 MB per Host (or Virtual Host) where an SMD Agent is installed.
Memory (MB) 256 MB in AIX environment or 128 MB for other environments per Host (or Virtual Host) where an SMD Agent is installed.
Network 3% usage for a 100Mbit/s Network bandwidth.
CPU 5 % CPU average increase per Host (or Virtual Host) belonging to the Managed Systems.
October 2012
Sizing Guide 28
5 Performance Settings
5.1 Solution Manager Settings
Number of Java dispatcher threads.
Java dispatcher threads are used for the p4 communication between the SMD Agents and Solution Manager.
The number of Java dispatcher threads depends on the number of SMD agents connected to the Solution Manager Instance.
This number should be set according to the following formula:
number_of_Dispatcher_Thread (ThreadManager->MaxThreadCount)
= number_of_SMD_agents * 1.75
Default value of MaxThreadCount After an installation of Solution Manager, the default value of the parameter MaxThreadCount in the Java Dispatcher configuration is set to 70. This setting allows by default to connect maximum 40 agents.
Maximum Heap Size for Dispatcher.
The java heap size of the Dispatcher should be set to the following value in order to avoid timeout connection issues:
Java Max Heap Size (-Xmx) = Number of SMD agents * 1.28
Number of RFC listener
RFC listeners are used for the JCO/RFC communication between the ABAP and Java stacks of Solution Manager.
The number of RFC listeners is given by the following formula:
number_of_RFC_listener = number_of_Background_process + 1 / number_of_Java_Server_Node
October 2012
Sizing Guide 29
5.2 Wily IS EM setup and tuning
Collector to MoM clock drift limit.
MoM and Collector clocks need to be synchronized to within AT MOST three seconds.
JVM setttings
The JVM Heap Size (-Xmx) must be large enough to handle all active metrics. The newSize parameter must be adapted accordingly and the Xms should be equal to the Xmx parameter.
You will find below a typical java command line parameters used to start a Collector:
Xms4096m -Xmx4096m -Xmn800m -verbose:gc -Dswing.volatileImageBufferEnabled=false -Djava.awt.headless=true
Disk Requirement
EM Storage
File system used for Enterprise Manager files storage baselines.db, and traces.db should be a local disk and not a network file system (NFS).
Using NFS for EM storage could result in performance degradation that can be covered to some extent by having enough RAM available as FS cache, or by adding another EM.
Cluster Consideration
In a Wily IS MoM/Collector environment, every Collector must have a dedicated disk I/O subsystem for SmartStor with no other processes competing for it.
This needs to be set appropriately in the IntroscopeEntrepriseManager.propertiesfile for every Collector and EM like described in the example below:
# The directory that the EM will use for data storage
introscope.enterprisemanager.smartstor.directory=data
introscope.enterprisemanager.smartstor.directory.archive=data/archive
introscope.enterprisemanager.smartstor.dedicatedcontroller=true
Only the Collector requires a dedicated SmartStor database and dedicated controller. MOM machines also have a SmartStor instance, but due to the vastly smaller metrics load, are able to house the SmartStor instance on the same disk as other MOM components.
Providing a separate disk for each SmartStor AND setting the dedicated controller property to true affects the total number of metrics an Enterprise Manager can handle because these allow for better sharing of disk resources.
To determine if a machine being considered for use as SmartStor is a single dedicated disk or drive, you may need to determine if the machine has multiple controllers (same as multiple hard drives). It's important to understand that multiple partitions on the same drive share a controller, which is not an appropriate environment for the SmartStor instance.
October 2012
Sizing Guide 30
You can use commands like du (for disk usage) on Unix/Linux or Windows Device Manager to determine whether two drives are logically different or physically different. It's critical that the drives are physically different.
Additional parameters
Disable application heuristics (baselining) introscope.enterprisemanager.application.overview.baselines=false
Reduce number of incoming events from agents:
Switch off TT sampling (agent and/or EM) introscope.agent.transactiontracer.sampling.enabled=false introscope.agent.transactiontracer.sampling.perinterval.count=0
Switch off/reduce error snapshots introscope.agent.errorsnapshots.enable=false in agent profile
Remove management modules in the collector:
Only Management modules of the MoM are used. Management modules in the Collector must be removed.