Wily Enterprise ManagerCluster Setupfor E2E RCA Scenario

SAP Solution Manager 7.0 EhP1

SAP Active Global Support

January 2009

SAP Introscope Architecture

Real-time,Historical, &Performance Alerting

IntroscopeEnterpriseManager

Persistentstore

JVM

Application Server

J2EE Application

IntroscopeBytecode

Agent

.Net CLR

.Net Application

IntroscopeWebView

SAP DiagnosticsAgent

IntroscopeWorkstation

Port6001

Port6001

Port8081

IntroscopeBytecode

Agent

IntroscopeHost

Adapter

Scaling beyond a Single EM

EMAgent

AgentAgentAgent

Solution Manager

Workstation

EM1Agent

AgentAgentAgent

Solution Manager

Workstation

EM2Agent

AgentAgentAgentWorkstation

EMCollector

AgentAgent

AgentAgent

Solution Manager

Workstation

EMCollector

AgentAgent

AgentAgent

EMMoM

Single EM

Multipleisolated EMs

EM Cluster /MoM

Combination of both

EM1Agent

AgentAgentAgentWorkstation

EM2Agent

AgentAgentAgentWorkstation

EMCollector

AgentAgent

AgentAgent

Solution Manager

Workstation

EMCollector

AgentAgent

AgentAgent

EMMoM

EM Cluster / MoMRequirements and Properties

LicensingNo additional license cost for MoM

TechnicalAll Enterprise Managers must be located in a low-latency LANClock synchronization: System clocks of all EMs must be synchronized with a differenceof at most 3 seconds.– NTP recommendedAgents can only be connected to collectors.Workstation connections only to MoMManagement Modules should only be put on the MoM.Agent fail-over – not supported by automated SAP installation of agent

SizingCollector ~ isolated EM sizingMoM: CPU intensiveIf multiple EMs on same host: Each collector should have a dedicated disk

MoM vs. Isolated EM

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

Pro Isolated EMIsolation: performance problems on a single Collector remain local to that collector and donot affect overall performance (whereas a single „bad“ collector may impact the completeEM cluster) – easier to support in case of problemsAllows for EMs in different locations, each with different permissions, managementmodules, EM releaseVirtually no scalability limitRelease independency of EM versions (MoM: all EMs in the cluster must have samerelease)

Solution Manager Integration - Overview

- Solution Manager supports all EM configuration variants:One or more isolated EMsOne or more EM clustersAny 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.

Roadmapfor EM Cluster implementation

Select ClusterConfiguration

Cluster setupCluster

VerificationDeclare

EMsSetup Solution

ManagerConnect IS agents

1 2 3 4 5 6

EM ClusterMoMs, EMs, Collectors

are installed andConfigured

Solution ManagerMoMs, EMs, are

declared inSolution Manager

Managed SystemsEMs and Collectors areattached to Server Nodes

and SMD Agents

© SAP 2007 / Page 9

1. Select Cluster configuration

The choice between a Single EM, a MoMs or a Multi-EMsscenario is given by the SMD Sizing Toolkit.

2. Enterprise Manager Cluster Setup

PrerequisitesAll Enterprise Managers must be located in a low-latency LANClock synchronization: System clocks of all EMs must be synchronized with a difference of at most 3seconds.– NTP recommendedAgents 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=wdfd00202885aintroscope.enterprisemanager.clustering.login.em1.port=6001introscope.enterprisemanager.clustering.login.em1.publickey=internal/server/EM.publicintroscope.enterprisemanager.clustering.login.em2.host=wdfd00202886aintroscope.enterprisemanager.clustering.login.em2.port=6001introscope.enterprisemanager.clustering.login.em2.publickey=internal/server/EM.public

3. EM Cluster Verification

The custom metric host containsone custom metric agent per collector

(with collector name as suffix)and one for the MoM.

The MoM custom metric agentcontains a subtree MOM,

listing all connected collectors.

4. Declare the IS EMs into Solution Manager(transaction solman_setup)

5. Setup Solution ManagerConfigure Diagnostics (solman_setup)

Run the managed system setup inSMD

5. Solution Manager SetupConfigure Diagnostics (solman_setup)

Select an EM from the EMs list.

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

Start the IntroscopeAgent setupapplication.

6. Associate EMs to IS byte Code Agents

Select the ServerNode you want to

setup

Press SetupIntroscope Agent

Select EM chosenduring managed

system setup

Select technical systemchosen during the setup

6. Associate EMs to IS byte Code AgentsSelect correct Collectors

List of collectors will bedisplayedSelect the correctCollector for theselected Server node

Capacity may helpyou to decide onwhich Collector youwant to connect.

Press Apply tostart the setup

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

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

6. Associate EMs to IS byte Code AgentsSpecific settings

SP19 : The AIX settingsbutton disappears andJ9 settings are solved

automatically

SP18 : Special optionsin case of J9 jvm needs

to be set manually

Wily IS EM compatibility support:EM version to IS byte Code Agents

By default it is not possible to setup an IS agent 7.Xto an EM 8.X, if you want to do so, set the propertyIS7XtoEM8X.allowed to true at the wily agentapplication properties level

NOTE : IS agent 8.X are NOT compatible withEM 7.X !

Wily IS EM compatibility support:Agent to Collector connectivity

By default it is not possible to setup an IS agent 7.Xto an EM 8.X, if you want to do so, set the propertyIS7XtoEM8X.allowed to true.

By default the selection of collectors is not possible incase of an EM8X, if for any reason you want to do socollectors.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 switchbetween these two setups with a few steps.In particular, if you keep the existing collector EMs as isolated EMs, the agents on managedsystems 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 MoMEnter all collectors as EMs

Shut down MoMDelete 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 EMDelete the isolated EMs which you converted to collectors in step 1 (they are detected viathe MoM)