Vous êtes sur la page 1sur 22

Wily Enterprise Manager

Cluster Setup
for E2E RCA Scenario

SAP Solution Manager 7.0 EhP1

SAP Active Global Support

January 2009
SAP Introscope Architecture

Port
8081 Introscope
Host
Introscope Adapter
WebView
SAP Diagnostics
Real-time, Introscope Agent
Historical, & Enterprise
Performanc
e Alerting Manager
Introscope J2EE Application
Workstation Port
6001 Port
6001 Application Server
Introscope JVM
Bytecode
Agent

.Net Application

Persistent
Introscope
store
Bytecode .Net CLR
Agent
Scaling beyond a Single EM

Agent
Solution Manager Agent
EM Agent
Agent
Single EM
Workstation

Agent
Agent
Workstation EM1 Agent
Agent

Multiple
Solution Manager
isolated EMs
Agent
Agent
Workstation EM2 Agent
Agent

Agent
EM Agent
Agent
Collector Agent
Workstation
EM Cluster / EM
MoM Solution Manager
MoM Agent
EM Agent
Agent
Collector Agent
Combination of both

Agent
Agent
Workstation EM1 Agent
Agent

Agent
Agent
Workstation EM2 Agent
Agent

Solution Manager Agent


EM Agent
Agent
Collector Agent

EM
Workstation
MoM Agent
EM Agent
Agent
Collector Agent
EM Cluster / MoM
Requirements and Properties

Licensing
No additional license cost for MoM
Technical
All Enterprise Managers must be located in a low-latency LAN
Clock synchronization: System clocks of all EMs must be synchronized with a difference
of at most 3 seconds.
– NTP recommended
Agents can only be connected to collectors.
Workstation connections only to MoM
Management Modules should only be put on the MoM.
Agent fail-over – not supported by automated SAP installation of agent
Sizing
Collector ~ isolated EM sizing
MoM: CPU intensive
If multiple EMs on same host: Each collector should have a dedicated disk
MoM vs. Isolated EM

Pro EM Cluster / MoM


Unified view on all agents: The users do not have to know which agent is connected to
which MoM, MoM is transparent – looks like a single EM from Workstation point of view
Customizing of management modules etc. is central – no need for manual propagation to
Ems
Official Wily solution for scalability and high availability

Pro Isolated EM
Isolation: performance problems on a single Collector remain local to that collector and do
not affect overall performance (whereas a single „bad“ collector may impact the complete
EM cluster) – easier to support in case of problems
Allows for EMs in different locations, each with different permissions, management
modules, EM release
Virtually no scalability limit
Release independency of EM versions (MoM: all EMs in the cluster must have same
release)
Solution Manager Integration - Overview

- Solution Manager supports all EM configuration variants:


One or more isolated EMs
One or more EM clusters
Any combination of those
- By default, SMD is installed to support the Single EM scenario.
- In SMD, only MoM and EM are declared: Collectors are discovered.
- In order to support the Multi-Ems or MoMs scenario, the following steps should be
performed:
1. Install corresponding Wily Infrastructure.
2. Declare the EMs (standalone EMs or MoMs) into Solution Manager.
3. Configure solution Manager for Multi-Ems and MoMs scenario.
4. Associate EMs (standalone EMs or MoMs) to IS byte Code Agents and SMD Agents.
Roadmap
for EM Cluster implementation

1 2 3 4 5 6

Cluster Declare Setup Solution Connect IS agents


Select Cluster Cluster setup Verification EMs Manager
Configuration

EM Cluster Solution Manager Managed Systems


MoMs, EMs, Collectors MoMs, EMs, are EMs and Collectors are
are installed and declared in attached to Server Nodes
Configured Solution Manager and SMD Agents
1. Select Cluster configuration

The choice between a Single EM, a MoMs or a Multi-EMs


scenario is given by the SMD Sizing Toolkit.

© SAP 2007 / Page 9


2. Enterprise Manager Cluster Setup

Prerequisites
All Enterprise Managers must be located in a low-latency LAN
Clock synchronization: System clocks of all EMs must be synchronized with a difference of at most 3
seconds.
– NTP recommended
Agents can only be connected to collectors.
Management Modules should only be put on the MoM.
Collector settings
(IntroscopeEnterpriseManager.properties):
– introscope.enterprisemanager.clustering.collector.enable=true

MoM settings
(IntroscopeEnterpriseManager.properties):
– introscope.enterprisemanager.clustering.manager.enable=true
– List connection data for all collector Ems, e.g.
introscope.enterprisemanager.clustering.login.em1.host=wdfd00202885a
introscope.enterprisemanager.clustering.login.em1.port=6001
introscope.enterprisemanager.clustering.login.em1.publickey=internal/server/EM.public
introscope.enterprisemanager.clustering.login.em2.host=wdfd00202886a
introscope.enterprisemanager.clustering.login.em2.port=6001
introscope.enterprisemanager.clustering.login.em2.publickey=internal/server/EM.public
3. EM Cluster Verification

The custom metric host contains


one custom metric agent per collector
(with collector name as suffix)
and one for the MoM.

The MoM custom metric agent


contains a subtree MOM,
listing all connected collectors.
4. Declare the IS EMs into Solution Manager
(transaction solman_setup)
5. Setup Solution Manager
Configure Diagnostics (solman_setup)

Run the managed system setup in


SMD
5. Solution Manager Setup
Configure Diagnostics (solman_setup)

Select an EM from the EMs list.


6. Associate EMs to IS byte Code Agents
(solman_setup)

Start the Introscope


Agent setup
application.
6. Associate EMs to IS byte Code Agents

Select EM chosen
during managed
system setup
Select technical system
chosen during the setup

Select the Server


Node you want to
setup

Press Setup
Introscope Agent
6. Associate EMs to IS byte Code Agents
Select correct Collectors

EM 8.0:
This is not possible by default to select a specific collector for the connection. This is fully
managed by Wily IS EM 8.0.

EM 7.2:
A specific collector must be selected. The LoadBalancing in not supported by Wily IS EM
7.2

Capacity may help


you to decide on
List of collectors will be which Collector you
displayed want to connect.
Select the correct
Collector for the
selected Server node

Press Apply to
start the setup
6. Associate EMs to IS byte Code Agents
Specific settings

SP18 : Special options


in case of J9 jvm needs
to be set manually

SP19 : The AIX settings


button disappears and
J9 settings are solved
automatically
Wily IS EM compatibility support:
EM version to IS byte Code Agents

NOTE : IS agent 8.X are NOT compatible with


EM 7.X !

By default it is not possible to setup an IS agent 7.X


to an EM 8.X, if you want to do so, set the property
IS7XtoEM8X.allowed to true at the wily agent
application properties level
Wily IS EM compatibility support:
Agent to Collector connectivity

By default it is not possible to setup an IS agent 7.X


to an EM 8.X, if you want to do so, set the property
IS7XtoEM8X.allowed to true.

By default the selection of collectors is not possible in


case of an EM8X, if for any reason you want to do so
collectors.selection.EM8X.allowed to true.

Please refer to sap note 1272620 for more details.


Converting EM Cluster Isolated Ems (1)

The decision EM Cluster vs. Isolated EM is not a one-way decision. It is possible to switch
between these two setups with a few steps.
In particular, if you keep the existing collector EMs as isolated EMs, the agents on managed
systems must not be changed / reconfigured:
Convert EM Cluster Isolated EMs:
Copy management modules (or new content from SAPISMM.SAR) to collector Ems.
In SMD / Advanced Setup / Wily & NWA – list of Enterprise Managers:
Delete the MoM
Enter all collectors as EMs
Shut down MoM
Delete the property in introscopeEnterpriseManager.properties:
introscope.enterprisemanager.clustering.collector.enable=true
Restart collector Ems
Converting EM Cluster Isolated Ems (2)

Convert Isolated EMs EM Cluster:


Perform the MoM setup as described on slide “Enterprise Manager Cluster Setup”
In SMD / Advanced Setup / Wily & NWA – list of Enterprise Managers:
Enter the MoM as EM
Delete the isolated EMs which you converted to collectors in step 1 (they are detected via
the MoM)