Agent installation strategy

Solution Manager 7.1 and 7.0 EhP1(SP20 and higher)

July 2011 September 2013 Public

Agenda 1/2
Introduction
What is needed and where ?
Choose Diagnostics Agent or Agents On-the-fly Diagnostics Agents Agents On-the-fly

Landscape Examples
SAP Host Agent

Diagnostics Agent Characteristics

Diagnostics Agents are SAP Systems

Diagnostics Agent File Structure

Diagnostics Agent Releases information

Latest Diagnostics Agent Releases Diagnostics Agent Release Constraints / PAM Diagnostics Agent Release Characteristics

2012 SAP AG. All rights reserved.

Agenda 2/2
Diagnostics Agent and SLD Registration
Diagnostics Agent Mass Installation Diagnostics Agent Maintenance
Diagnostics Agent Upgrade Diagnostics Agent Replacement Diagnostics Agent Removal

2012 SAP AG. All rights reserved.

Introduction

Scope The following rules apply to both Solution Manager 7.0 EhP1 and 7.1, unless they are tagged [7.0 EhP1 only] or [7.1 only] Terminology The term host in this slide set does not designate network alias. Hosts must have their own IP addresses.

A Virtual host designates a simulated host running for example on top of a VMware.
A Logical host designates a network/host configuration which associates a physical host with one or more additional host names and dedicated IP addresses. This is used, for example, to move systems from one physical host to another. N.B.: To find the host name of an ABAP system, use transaction sm51, and for Java systems refer to the System Info Web page.

2012 SAP AG. All rights reserved.

What is needed and where? (Diagnostics Agent or Agents On-the-fly)

New feature available

Solution Manager 7.1 SP05 provides a new feature named Agents On-the-fly Agents On-the-fly concept introduces automatic Agent instantiations to address specifically the following use cases:
Managed systems in High Availability environments Physical or Virtual hosts running a high number of Logical hosts (outside High Availability environments)

Further details on Agents On-the-fly available in online documentation : Click here

Existing installations
Previous Diagnostics Agent installation process is still valid. Operate either classic Diagnostics Agents or Agents On-the-fly, depending on each Managed system environment. Diagnostics Agent installations already in place are still valid and do not necessarily need to be replaced by the Agent On-the-fly feature. Nevertheless in High Availability environments it could be of interest to put Agent On-the-fly in place.

2012 SAP AG. All rights reserved.

What is needed and where? (Diagnostics Agents)

Rule #1: Install the required number of Diagnostics Agents

In the context of each Solution Manager System use only one Diagnostics Agent or Agent On-the-fly per Managed host. Managed hosts are primarily logical hosts, or if not applicable physical/virtual hosts (as shown on the next slides)
Each Diagnostics Agent or Agent On-the-fly manages, on behalf of one Solution Manager, the systems/components running on the host on which it is running (and represents that host)
following slides explain what is a supported systems/components repeat the Managed System configuration (solman_setup) on each Solution Manager for each Technical System running on these hosts (logical host, or if not applicable physical/virtual host). Activities Byte Code Adapter Installation and Introscope Host Adapter have to be performed only in one leading Solution Manager system (see page 10)

For landscapes with logical host names and in case Agents On-the-fly are not used, specify, during the Diagnostics Agent installation, each time the logical host name
When installing an (additional) Agent for a logical host, using the Diagnostics Agent installation package, provide the short hostname, in the SAPInst step requesting a Virtual host name.

2012 SAP AG. All rights reserved.

What is needed and where? (Diagnostics Agents)

Rule #1 (details): Install required number of Diagnostics Agents
LogicalHost3 C1 C2 C7 C8

(not applicable in context of Agents On-the-fly)

LogicalHost2 C4 C5 C6

LogicalHost1 C3

Diagnostics Agent 1

Diagnostics Agent 2

Diagnostics Agent 3

Diagnostics Agent 4

SAP Host Agent

PhyHost2 or VMware

PhyHost3 or VMware

SAP Host Agent

. .

Only one Diagnostics Agent for each Solution Manager must exist per physical, virtual or logical host running a managed component A Diagnostics Agent will support the managed components installed/operated with that hostname Each Diagnostics Agent is uniquely identifiable in Solution Manager via that (short) hostname Own one SAP Host Agent per physical or virtual host
2012 SAP AG. All rights reserved.

DA

Diagnostics Agent SAP Host Agent

Managed Component (see following slides)

SAP Solution Manager

Diagnostics Agent 5

HA

SAP Host Agent

PhyHost1 or VMware

What is needed and where? (Agents On-the-fly)

Rule #1 (continued): How to use Agents On-the-fly (available with Solution Manager 7.1 SP05)
Mandatory context:
Managed systems in High Availability environments Physical or Virtual hosts running a high number of Logical hosts (outside High Availability environments)

Use case:

2012 SAP AG. All rights reserved.

What is needed and where? (Agents On-the-fly)

Rule #1 (continued): How to use Agents On-the-fly (available with Solution Manager 7.1 SP05)
Preparation

Diagnostics Agent landscape preparation:

Remove existing Diagnostics Agents at Physical, Virtual and Logical host level (in concerned landscape) Pay attention to recommendations for Diagnostics Agents Removal, to avoid potential Java Managed System startup failures (see page 29) Install Diagnostics Agents only at Physical or Virtual host level, without specifying any Logical hostname, using latest Diagnostics Agent installation package. See SAP note 1833501.

2012 SAP AG. All rights reserved.

What is needed and where? (Agents On-the-fly)

Rule #1 (continued): How to use Agents On-the-fly (available with Solution Manager 7.1 SP05)
Configuration Diagnostics Agent Configuration:
Start the Host configuration for each Physical or Virtual host Available under solman_setup / Managed System Configuration / Hosts Especially enable the Agents On-the-fly feature within step Enter System Parameters Adjust exclusion filters to have only relevant logical hosts, before saving press button. Logical host filtering-impact simulation is available via Display resulting host list button. Defining appropriate filters will avoid having irrelevant Agents On-the-fly instantiated. Agents On-the-fly get instantiated by the Diagnostics Agent running on the Physical or Virtual Host, as soon as the Enter System Parameters step is saved.

Using Agents On-the-fly:

Simply run as usual solman_setup / Managed System Configuration for implied Managed Systems In case no Agent On-the-fly for the Managed System logical hosts is visible within the step Assign Diagnostics Agents (similar to Diagnostics Agents), double check above pre-requisite items.

Online documentation available: Click here

2012 SAP AG. All rights reserved. 10

What is needed and where? (Diagnostics Agent/Agents On-the-fly)

Number of Diagnostics Agents depends on managed component distribution

Example where all components run with one hostname (physical, virtual or logical)
Solution Manager Enterprise Portal ERP / ECC Server

Java stack on 1 Host

Dual stack on 1 Host

ABAP Central Instance

+ ABAP Central Services

ABAP stack on 1 Host

Central Instance

Central Instance
+ ABAP Central Services

Java Central Instance

Dialog Instance

Dialog Instance

Java Central Services

Central Services

DB

DB

DB

Diagnostics Agent

Diagnostics Agent

Diagnostics Agent

2012 SAP AG. All rights reserved.

11

What is needed and where? (Diagnostics Agent/Agents On-the-fly)

Number of Diagnostics Agents depends on managed component distribution

Example where each component runs with different hostnames (physical, virtual or logical)
Solution Manager Enterprise Portal ERP / ECC Server

ABAP Central Instance

+ ABAP Central Services

Central Instance Diagnostics Agent Dialog Instance Diagnostics Agent

Distributed ABAP stack

Distributed Java stack

Distributed Dual stack

Central Instance Diagnostics Agent Dialog Instance Diagnostics Agent

Java Central Instance Diagnostics Agent Java Central Services

Java Central Services Diagnostics Agent

Possible since Solution Manager 7.1 SP08

ABAP Central Services Diagnostics Agent

Possible since Solution Manager 7.1 SP08

DB Diagnostics Agent

DB

DB

Diagnostics Agent
(1) Agent required in the scope of Solution Manager 7.1

Diagnostics Agent
(1) Agent required in the scope of Solution Manager 7.1

(1) Agent required in the scope of Solution Manager 7.1

(1)

In the context of High Availability environments consider to use the Agents On-the-fly feature available since Solution Manager 7.1 SP05
12

2012 SAP AG. All rights reserved.

What is needed and where? (Diagnostics Agent/Agents On-the-fly)

Covering 3-system landscape: Enable full RCA of QA Portal Managed System on both SolMans, by installing an additional Diagnostics Agent Solution Manager and extracting QA Portal perf. data from Prod. IS Enterprise Manager IMPORTANT Collected config. of
On the Dev. SolMan, when running solman_setup / Managed system configuration for the QA Portal Managed system, mark the activities Byte Code Adapter Installation and Introscope Host Adapter as Postponed.

Dev SolMan

managed systems Dev & QA

Comparison possible Dev Introscope Enterprise Manager Dev Enterprise Portal Introscope
Adapters

Diagnostics Agent

(Otherwise the Introscope Adapters of the QA Portal would report their data to the Dev. IS EM, what is not expected here.)

Prod SolMan

Solution Manager Collected config. of managed systems QA & Prod Comparison possible Prod Introscope Enterprise Manager

QA Enterprise Portal Introscope

Adapters

Diagnostics Agent Diagnostics Agent

Introscope Adapter

Use Prod IS EM to retrieve perf. data of QA Managed systems

Prod Enterprise Portal Introscope

Adapters

Diagnostics Agent

2012 SAP AG. All rights reserved.

13

3-System landscape

What is needed and where? (Diagnostics Agent/Agents On-the-fly)

[7.1 only] 3-system landscape requires a 2nd Diagnostics Agent (Prod. IS EM)

Dev SolMan

Solution Manager Collected config. of managed systems Dev & QA

Dev Enterprise Portal

Dev Introscope Enterprise Manager Diagnostics Agent QA Enterprise Portal

Prod SolMan

IMPORTANT On the Prod. IS EM host, install a second Diagnostics Agent instance, re-using the System ID (SID) of the Diagnostics Agent installed initially.
(Otherwise two Diagnostics Agent OS users would access the Prod. IS EM files. In case one Agent OS user updates via solman_setup some files, the other Agent OS user would else encounter access denied errors, especially if the umask is not set to 007.)

Solution Manager Collected config. of managed systems QA & Prod Prod Enterprise Portal

Prod. Introscope Enterprise Manager Diagnostics Agent Diagnostics Agent

2012 SAP AG. All rights reserved.

14

3-System landscape

What is needed and where? (Diagnostics Agent/Agents On-the-fly) Dev System landscape
Dev Enterprise Portal Introscope
Adapters

3-system landscape (continued)

Managed systems in a given E2E solution (Per Dev, QA or Prod type) must be connected to the same Solution Manager system

Dev ECC Server

Diagnostics Agent

Diagnostics Introscope Adapter Agent

QA System landscape
QA Enterprise Portal Introscope
Adapters

QA ECC Server

Diagnostics Agent

Diagnostics Introscope Adapter Agent

Prod SolMan

Solution Manager Prod Managed Systems data EP & ECC E2E Trace Analysis Prod Introscope Enterprise Manager

Prod System landscape

Prod Enterprise Portal Introscope
Adapters

Prod ECC Server Diagnostics Introscope Adapter Agent

Diagnostics Agent

2012 SAP AG. All rights reserved.

15

What is needed and where? (SAP Host Agent)

Rule #2: Have up-to-date SAP Host Agents

See SAP note 1365123 for the current minimum version
This note also confirms whether the installation/upgrade of the SAP Host Agent, performed by the installation of a Diagnostics Agent (installer 7.30 SPxx) covers currently known defects.

Install a SAP Host Agent if none has yet been installed (one per physical host)
Check whether there is a SAP Host Agent using the following path: o For Windows look under: "%ProgramFiles%"\SAP\hostctrl o For Unix, under: /usr/sap/hostctrl/

Update the SAP Host Agent according to SAP note 1031096, if the version is not sufficient
Check version at OS level (looking in the output at SAPHOSTAGENT Information): o For Windows: "%ProgramFiles%"\SAP\hostctrl\exe\saphostctrl -function ExecuteOperation -name versioninfo o For Unix: /usr/sap/hostctrl/exe/saphostctrl -function ExecuteOperation -name versioninfo [7.1 only] Currently installed Host Agent version is also visible in the host browsing, if Managed System Configuration has been performed with solman_setup o Navigate to Solution Manager Administration work center -> Select Landscape + Technical System selection type -> System Details -> System Details -> Hosts -> <search for your host> -> Host Status
2012 SAP AG. All rights reserved. 16

What is needed and where? (SAP Host Agent)

Rule #2 (continued): Have up-to-date SAP Host Agents

Implement automatic upgrade process (especially if you plan an update)
SAP note 1473974 describes ways to upgrade centrally and automatically, running SAP Host Agents.

2012 SAP AG. All rights reserved.

17

Diagnostics Agents are SAP Systems

Rule #3: The Diagnostics Agent is a standard SAP system

The same rules apply as for any standard SAP system
Do not install an Agent in the directory structure of another SAP system (or copy or move the files)
Agents must be independent of any other system installation

Several Diagnostics Agents can be installed using the same SID, but different instance numbers, in case they use the same kernel.
The agent SID must contain only Diagnostics Agent instances

Diagnostics Agents typically have different System/Instance ID patterns, depending on the release (see following slides)

2012 SAP AG. All rights reserved.

18

Diagnostics Agents are SAP Systems

Rule #3 (details): Alternatives for installing multiple Diagnostics Agents on the same host
These Agents have to be connected to different Solution Manager systems
Use the same dedicated System ID (and different instance numbers)
Exception: Do not use a same SID for Diagnostics Agents with different kernel releases (this is prevented by the latest installers).

Using different System IDs (and different instance numbers)

Allows independent installations, but requires internal distinct SID allocation rules in case the file system is mounted. It is indeed strictly forbidden to share the same Agent binaries/configuration files for multiple Agent instances. In particular, a same Diagnostics Agent file system installation must NOT be mounted and executed on several hosts at the same time.

2012 SAP AG. All rights reserved.

19

Diagnostics Agent File Structure

Description
Global exe SAPJVM global directory profile directory Instance directory script directory work directory Local exe Local SAPJVM Agent software and properties files Agent logs
(1)

7.0 / 7.01 SR1

/usr/sap/<SMDSID>/exe No SAPJVM (using separately installed JDK) /usr/sap/<SMDSID>/SYS/global /usr/sap/<SMDSID>/SYS/profile /usr/sap/<SMDSID>/J<XX> /usr/sap/<SMDSID>/J<XX>/script /usr/sap/<SMDSID>/J<XX>/work No local exe directory No SAPJVM /usr/sap/<SMDSID>/J<XX>/SMDAgent /usr/sap/<SMDSID>/J<XX>/SMDAgent/log

7.11 / 7.20 / 7.30 SP03 / SWPM 1.0 SP03 and higher

/usr/sap/<DASID>/SYS/exe /usr/sap/<DASID>/SYS/exe/jvm /usr/sap/<DASID>/SYS/global /usr/sap/<DASID>/SYS/profile /usr/sap/<DASID>/SMDA<XX> /usr/sap/<DASID>/SMDA<XX>/script /usr/sap/<DASID>/SMDA<XX>/work /usr/sap/<DASID>/SMDA<XX>/exe
(1)

/usr/sap/<DASID>/SMDA<XX>/exe/sapjvm_xx (1) /usr/sap/<DASID>/SMDA<XX>/SMDAgent /usr/sap/<DASID>/SMDA<XX>/SMDAgent/log

Contains executable kernel programs that are replicated (files moved for the SAPJVM) from SYS/exe every time the agent instance is started.
20

2012 SAP AG. All rights reserved.

Latest Diagnostics Agent Release

Rule #4: Use the latest SWPM 1.0 (SP03 or higher), when installing a Diagnostics Agent to comply with rule #3. See SAP note 1858920.
In case download bandwidth would not allow getting the associated DVDs (SWPM installer & Kernel) from SMP, alternatively download a smaller standalone Diagnostics Agent installation package 7.30 SP03. IMPORTANT: This standalone installer is outdated and not supported any longer. In case of problems please perform the installation using the latest SWPM version. A summary of Diagnostics Agents releases and characteristics is available on the next slide With Solution Manager release lower than 7.0 EhP1 SP20 only use older Diagnostics Agent release 7.01 SR1. This Diagnostics Agent release is installable with the help of the SAP EhP1 for SAP NetWeaver 7.0 Installation Master, Kernel & Java DVDs. A separately installed JDK 1.4.2 is also required.

2012 SAP AG. All rights reserved.

21

Diagnostics Agent Release Constraints / PAM

Agent releases
Compatible with Solution Manager Supported NW Managed system releases

7.0 / 7.01 SR1

Solution Manager lower than 7.0 EhP1 SP20 (1)

7.20
Solution Manager since 7.0 EHP1 SP20 (included) (1)(2)

7.30 SP03
Solution Manager since 7.0 EHP1 SP20 (included) (1)(2)

SWPM 1.0 SP03 and higher

Solution Manager since 7.0 EHP1 SP20 (included) (1)(2)

6.40, 7.00 and higher

6.40, 7.00 and higher

6.40, 7.00 and higher

See SAP note 1680045 1858920 PAM documentation: https://service.sap.com/sltoolset / Software Logistics Toolset 1.0 / PAM In PAM document, navigate to Software Provisioning Manager 1.0 / SAP Solution Manager Diagnostics Agent

Installation SAP note

1357812

1368413

1833501

Installer recommended when new installation required (See OS platform support on next slide)
(1)

When a Solution Manager system is upgraded, the Diagnostics Agents do not generally need to be upgraded manually. See next slide and rule #5. IMPORTANT: Rule #2 must be followed.

(2)

N.B.: This Diagnostics Agent release is also applicable to Solution Manager 7.1.
22

2012 SAP AG. All rights reserved.

Diagnostics Agent Release Characteristics

Agent releases 7.11 7.20
Old SAPInst based CE 7.20 & NW 7.0 EhP2 NW Java, ABAP or dual stacks 7.20 / patch 36 SAPJVM 6 DAA / SMDA<97 to 00> Yes

7.30 SP03 Standalone (2)

Old SAPinst based installers (3)

Latest Agent release (2)

SWPM 1.0 SP03 and higher based NW installers (3) 7.20 & 7.20 EXT SAPJVM 6 DAA / SMDA<97 to 00> Yes
(support offline mode)

Already silently installed with products based on Kernel Release (SAP products)
/ patch level with standalone installer

Old SAPInst based PI & CE 7.1 EhP1

7.11 SAPJVM 5 DAA / SMDA<97 to 00> No

7.20 / patch 401 SAPJVM 6 DAA / SMDA<97 to 00> Yes

(support offline mode)

JVM Default System ID / Instance Number Support both direct connection to SolMan & SLD registration @ installation SSL & SAPRouter Support @ installation SAP Host Agent installation Installation SAP Note

No Install manually 1234387

Yes (1) Auto-installed 1368413

Yes
(via installer option)

Yes
(via installer option)

Auto-installed/updated (2) 1829024

Auto-installed/updated (2) 1858920

Agent start/stop/control
(1) (2) (3)

Standard

Standard

Standard

Standard

IAIK libraries need to be provided manually. Also allows to configure the trusted connection @ SAP Host Agent level, automatically. For more information refer to SAP Note 1833501.
23

2012 SAP AG. All rights reserved.

Diagnostics Agent and SLD Registration

Available Diagnostics Agent connectivity options per installation scenario:

1. Diagnostics Agent is already installed silently with a managed system

The agent is registered in the System Landscape Directory specified during the managed system installation o The agent could be connected to Solution Manager using, for example, solman_setup -> Managed System Configuration. This will configure the agent remotely, to connect to Solution Manager via the Message Server. No System Landscape Directory is specified during the managed system installation o Connect the agent to Solution Manager via the Message Server using the smdsetup script, as documented in the Diagnostics Agent troubleshooting guide (http://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+Troubleshooting).

2012 SAP AG. All rights reserved.

24

Diagnostics Agent and SLD Registration

2. Agent is installed using a Diagnostics Agent standalone installation package

During the agent installation, choose to connect it to Solution Manager (via the Message Server) instead of only registering it in a System Landscape Directory. This will reduce the number of activities to be performed in solman_setup. Solution Manager connectivity data can be re-pushed to running Diagnostics Agents (useful in case of operational issues), in case the agent was also registered in a central System Landscape Directory. NEW: Operational issues concerning Diagnostics Agents to Solution Manager connectivity can be easily resolved via the Non-authenticated Agents list, available with Solution Manager 7.1 SP05. Prerequisite: Diagnostics Agent was connected to a Solution Manager 7.1 SP05 system at least once.

2012 SAP AG. All rights reserved.

25

Diagnostics Agent Mass Installation

Use the unattended mode to silently install Diagnostics Agents for large consistent landscapes
For Diagnostics Agent releases specific details see SAP note 1833501 / Mass Deployment Notes

2012 SAP AG. All rights reserved.

26

Diagnostics Agent Upgrade

Rule #5: No need to upgrade Diagnostics Agents (in contrast to SAP Host Agent)
Diagnostics Agents take their business logic (software) from the Solution Manager system to which they are connected
All Diagnostics Agents running and connected in the landscape are centrally patched by applying an LMSERVICE Java Software Component Archive on the Solution Manager system

Diagnostics Agent Installation SAP notes include a guide and simple manual procedures needed to resolve known punctual issues (support of cryptography, ). Alternatively, use the later described Agent replacement procedure. Some OS platform constraints might require a Diagnostics Agent Kernel upgrade. See SAP note 1707141.

2012 SAP AG. All rights reserved.

27

Diagnostics Agent Replacement

Rule #5 (continued): To replace a Diagnostics Agent uninstall the previous Agent and install the new required release:
Reset server name
Login to the Solution Manager system to which the agent to be upgraded is connected Navigate to the Agent Administration and note the server name of the old agent Reset server name using the context menu of the agent, and stop the agent

Install new Diagnostics Agent release using a different SID (no upgrade tool available) Assign the same Server Name to the new Agent using the smdsetup script (see details in the Diagnostics Agent troubleshooting guide). Java based Managed systems require to take some specific IMPORTANT actions (see next slides) Uninstall the previous Diagnostics Agent using SAPInst
2012 SAP AG. All rights reserved. 28

Diagnostics Agent Replacement

Rule #5 (In context of Java Managed System): In case the Ensure HA virtualization compatibility option was not used in the past:
Configure again the Wily Introscope Agent (Byte Code Adapter Installation) using transaction solman_setup -> Managed System Configuration -> Configure Automatically Pre-requisite since Solution Manager 7.1 SP05: Mark additionally the option "Ensure HA virtualization compatibility" within step "Enter System Parameters". Also ideally provide only a relative path name like ByteCodeAdapter for the "Introscope BC Adapter deployment path" field, in order to locate the Byte Code Adapter binaries and configuration files inside the Managed system directory structure (/usr/sap/<ManagedSID>/<InstanceID>). The Diagnostics Agent OS user (members of the SAPSYS OS group) must therefore also have write permissions at this Managed System path location. See SAP note 1163751 Restart the Java managed system This procedure updates the Managed System JVM parameters so that the Introscope Byte Code Adapter binaries are no longer taken from the previous old Diagnostics Agent directory structure.
2012 SAP AG. All rights reserved. 29

Diagnostics Agent Removal

Rule #6: To remove a Diagnostics Agent instance installed for a specific hostname:
In case the solman_setup Ensure HA virtualization compatibility option was used in the past to setup the Byte Code Adapter of the Java Managed System(s) running on that host
Optionally: Uninstall also the Byte Code Adapter by removing the JVM parameters listed in SAP note 797147

Else, take the following actions (in case the Ensure HA virtualization compatibility option was not used in the past during the solman_setup Managed System Configurations):
IMPORTANT: Remove JVM parameters listed in SAP note 797147 on the Java Managed System used to start/run the Introscope Byte Code Adapter. Finally restart the Java Managed system to no longer run the Introscope Byte Code Agent The Managed System JVM parameters (to be removed) show that the Introscope Byte Code Adapter executed inside the Managed System uses files from Diagnostics Agent directory structure:
Xbootclasspath/p:D:/usr/sap/DAA/SMDA77/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-0114/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA77/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2. 3.5-2011-01-14/wily/Agent.jar

Run the Diagnostics Agent installer SAPInst, to uninstall the Diagnostics Agent
2012 SAP AG. All rights reserved. 30