SMD Agent and Host Agent for z/os News, Best Practices and Demo Rainer Pfister, SAP SE Jochen Röhrig, IBM

Transcription

1 SMD Agent and Host Agent for z/os News, Best Practices and Demo Rainer Pfister, SAP SE Jochen Röhrig, IBM zsap Customer Conference Böblingen April 16, 2015 Public Use this title slide only with an image

2 2015 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. 2

3 2015 SAP SE oder ein SAP-Konzernunternehmen. Alle Rechte vorbehalten. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet. SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit. Weitere Hinweise und Informationen zum Markenrecht finden Sie unter Die von SAP SE oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Produkte können länderspezifische Unterschiede aufweisen. Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informationszwecken. Die SAP SE oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren. Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentation dargestellte Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation oder eine zugehörige Präsentation, die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP SE oder ihrer Konzernunternehmen können von der SAP SE oder ihren Konzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden. Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von den Erwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie getätigt wurden. Dem Leser wird empfohlen, diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen nicht auf sie zu stützen. 3

4 Agenda Introduction: SAP Host Agent & SAP Solution Manager Diagnostics Agent SAP Solution Manager DB Discovery & OS-Monitoring Best Practices: Setup Check (Demo) Related SAP Notes & Hints

6 Introduction SAP Host Agent Crucial component of any SAP system Must be installed on each operating system (physical or virtual host) on which a component of an SAP system is running (Directory: /usr/sap/hostctrl) Manages many aspects on the operating system level, such as: Starting / stopping of SAP instances Starting / stopping / status determination of databases Collecting operating system performance data Offering services to other SAP components (in particular: to SMD Agent) 6

7 Introduction SAP Solution Manager Diagnostics Agent Central component in SAP landscapes managed by SAP Solution Manager Must be installed on each system (logical host) managed by the SAP Solution Manager (Default Directory: /usr/sap/daa) Manages many aspects on the operating system level, such as: Discovery of components that should be managed by the SAP Solution Manager Collecting and reporting of monitoring data if managed systems to SAP Solution Manager 7

9 SAP Solution Manager Discovery and Monitoring Related Components Managed System SAP Solution Manager 7.1 SAP ABAP SAP JAVA SLD Data Supplier SLD Data Supplier Database Host Agent Diagnostics Agent DBA Cockpit EFWK (Pull / Push) ACE MEA BW Consumer Alerting Status Exceptions Database Changes Reporting LMDB SLD 9

10 SAP Solution Manager Database Registration 1st Method: SLD Registration and Replication Managed System SAP Solution Manager 7.1 SAP ABAP SLD Data Supplier SAP JAVA SLD Data Supplier Host Database Replication LMDB SLD 10

11 SAP Solution Manager Database Registration 2nd Method: Database Outside Discovery Managed System SAP Solution Manager 7.1 SAP ABAP SLD Data Supplier SAP JAVA SLD Data Supplier Host Database sapdbctrl Host Agent Diagnostics Agent Outside Discovery Mapping LMDB SLD 11

12 SAP Solution Manager Database Registration Database Outside Discovery on z/os Managed System SAP Solution Manager 7.1 SAP ABAP SLD Data Supplier SAP JAVA SLD Data Supplier sapdbctrl-support for Tivoli System Automation managed DB2 members New New z/os LPAR Commands via IFI DB2 for z/os New Detect DB2 subsystems via z/os subsystem control blocks DISPLAY GROUP DISPLAY DDF DB2-SS Detection up Host Agent sapdbctrl Diagnostics Agent Outside Discovery LMDB Mapping IFI: DB2 Instrumentation Facility Interface SLD 12

13 New Common Information Model SAP Solution Manager OS Monitoring with SAP Host Agent CIM Provider on z/os SAP ABAP SAP JAVA SLD Data Supplier SLD Data Supplier z/os LPAR DB2 for z/os Host Agent Diagnostics Agent ACE Consumer Alerting Status MEA Exceptions Database BW Changes Reporting sapcimb http SAP Solution Manager 7.1 EFWK (Pull / Push) Managed System XML z/os LPAR ca wily Introscope RMF Distributed Data Server 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 13

14 SAP Solution Manager CIM Provider Exploitation Workload Analysis (CA Wily Introscope ) New http[s]://<solman-host>:8081/webview/jsp/login.jsf 14

15 SAP Solution Manager CIM Provider Exploitation System Monitoring Alerting New Tx SOLMAN_WORKCENTER Technical Monitoring System Monitoring Hosts 15

16 SAP Solution Manager CIM Provider Exploitation Change Analysis Computer System New Tx SOLMAN_WORKCENTER Root Cause Analysis System Analysis Change Reporting 16

17 SAP Solution Manager CIM Provider Exploitation Change Analysis Operating System New Tx SOLMAN_WORKCENTER Root Cause Analysis System Analysis Change Reporting 17

18 SAP Solution Manager CIM Provider Exploitation Change Analysis Virtual Computer System New Tx SOLMAN_WORKCENTER Root Cause Analysis System Analysis Change Reporting 18

20 Setup-Check CIM Provider RMF Distributed Data Server Check whether the HTTP connection to RMF DDS works by pointing your browser to the RMF DDS-URL (Default port is 8803) Check whether data is collected by pointing your browser to this URL: <LPAR-Name> is the SMF-ID of one of your LPARs on which RMF data collection is enabled. 20

21 Setup-Check CIM Provider SAP Host Agent sapcimb Get OS monitoring metric values % /usr/sap/hostctrl/exe/sapcimb -e -c SAP_MetricValueg ********************************************************** CreationClassName, string, SAP_MetricValue MetricDefinitionId, string, OS.CPUCount MeasuredElementName, string, OperatingSystem TimeStamp, datetime, MetricValue, string, 4 ********************************************************** CreationClassName, string, SAP_MetricValue MetricDefinitionId, string, OS.UserTimePercentage MeasuredElementName, string, OperatingSystem TimeStamp, datetime, MetricValue, string, 30 **********************************************************... In case of failure raise the trace level /usr/sap/hostctrl/exe/sapcimb -e -c SAP_MetricValue T 3g and check for errors in the trace outputg Issue the command from a z/os USS shell on an LPAR on which the a SAP Host Agent is running 21

22 Setup-Check CIM Provider SAP Host Agent CIM Web Services Get OS monitoring metric values % /usr/sap/hostctrl/exe/saphostctrl -function GetCIMObject -enuminstances SAP_MetricValue This must output a list of metrics (see previous slide). In case of failure: Raise the SAP Host Agent trace level /usr/sap/hostctrl/exe/host_profile: service/trace = 3 hostexec/trace = 3 Restart the SAP Host Agent % /usr/sap/hostctrl/exe/saphostexec restartg Reissue the command described above Check for error messages in /usr/sap/hostctrl/work/sapstartsrv.log Issue the command from a z/os USS shell on an LPAR on which the a SAP Host Agent is running 22

23 Setup-Check Database Discovery SAP Host Agent sapdbctrl (1/2) List databases %/usr/sap/hostctrl/exe/sapdbctrl list Instance name: SGA1, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: SGA1, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: SGC1, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: SGC1, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: SGI1, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFSGI1, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: SGD1, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFSGD1, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: SGD2, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFSGD2, Status: Stopped Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Stopped (DB2 base is stopped) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Stopped (DB2 Distributed Data Facility is stopped) Instance name: D107, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFD107, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: D110, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFD110, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: D111, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFD111, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running)... Issue the command from a z/os USS shell on an LPAR on which the a SAP Host Agent is running 23

24 Setup-Check Database Discovery SAP Host Agent sapdbctrl (2/2) Get database status %/usr/sap/hostctrl/exe/sapdbctrl status DDFSGI t db2 Database Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Get database properties %/usr/sap/hostctrl/exe/sapdbctrl getproperties DDFSGI -t db2 Database/Distribution=shared Database/InstanceList=Name=SGI1;Host=ihsapde.wdf.sap.corp;Name=SGI2; Host=ihsapfe.wdf.sap.corp;Name=SGI3;Host=ihsapje.wdf.sap.corp Database/ConnectAddress=Protocol=tcp;Host=ihsapde.wdf.sap.corp;Port=8182;SSID=SGI1 Issue the command from a z/os USS shell on an LPAR on which the a SAP Host Agent is running 24

25 Setup-Check Database Discovery SAP Host Agent Database Control Web Services (1/2) List databases %/usr/sap/hostctrl/exe/saphostctrl -function ListDatabases Instance name: SGA1, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: SGA1, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: SGC1, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: SGC1, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: SGI1, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFSGI1, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: SGD1, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFSGD1, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: SGD2, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFSGD2, Status: Stopped Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Stopped (DB2 base is stopped) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Stopped (DB2 Distributed Data Facility is stopped) Instance name: D107, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFD107, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: D110, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFD110, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Instance name: D111, Hostname: ihsapde, Vendor: IBM, Type: db2, Release: Database name: DDFD111, Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running)... Issue the command from a z/os USS shell on an LPAR on which the a SAP Host Agent is running 25

26 Setup-Check Database Discovery SAP Host Agent Database Control Web Services (2/2) Get database status %/usr/sap/hostctrl/exe/saphostctrl -function GetDatabaseStatus -dbname DDFSGI dbtype db2 Database Status: Running Component name: DB2 base (DB2 base address spaces DBM1, MSTR, and IRLM), Status: Running (DB2 base is running) Component name: DB2 Distributed Data Facility (DB2 Distributed Data Facility (DDF) for DRDA), Status: Running (DB2 Distributed Data Facility is running) Get database properties %/usr/sap/hostctrl/exe/saphostctrl -function GetDatabaseProperties -dbname DDFSGI dbtype db2 Database/Distribution=shared Database/InstanceList=Name=SGI1;Host=ihsapde.wdf.sap.corp;Name=SGI2; Host=ihsapfe.wdf.sap.corp;Name=SGI3;Host=ihsapje.wdf.sap.corp Database/ConnectAddress=Protocol=tcp;Host=ihsapde.wdf.sap.corp;Port=8182;SSID=SGI1 Issue the command from a z/os USS shell on an LPAR on which the a SAP Host Agent is running 26

27 Setup-Check SAP Solution Manager SMD-Agent Connectivity http[s]://<solman-host>:<port>/webdynpro/dispatcher/sap.com/tc~smd~server~agent~admin/smdagentadminapplication?sap-language=en 27

28 Setup-Check SAP Solution Manager Detection of Hosts and Databases SAP Solution Manager Unified Landscape Browser http[s]://<solman-host>:<port>/sap/bc/webdynpro/sap/diagls_landscape_browser_app Databases Search 28

31 Setup-Check SAP Solution Manager Technical Monitoring Setup http[s]://<solman-host>:<port>/sap/bc/webdynpro/sap/wd_sise_main_app?sap-language=en Technical Monitoring Steps 4 Template Maintenance, 5 Define Scope, 6 Setup Monitoring and 7 Reporting 31

32 Setup-Check CA Wily Introscope R SAP SMD Agent Delivery of OS Metrics http[s]://<solman-host>:8081/webview/jsp/login.jsf 32

34 SAP Host Agent and SAP SMD Agent Setup on z/os SAP Host Agent Apply the following SAP Notes: Note Installing Package SAPHOSTAGENT Download and install SAP Host Agent on z/os on each LPAR on which an SMD Agent will be installed Note DB2-z/OS: SAP Host Agent problem on z/os Apply fixes to ensure correct SAP Host Agent behavior on z/os Note DB2-z/OS: sapdbctrl: Prerequisites and Configuration Setup z/os to enable automatic database detection by SAP Host Agent (sapdbctrl) Note DB2-z/OS:CCMS:HAG: CIM-Provider Enablement for z/os Setup z/os to enable OS monitoring by SAP Host Agent (sapcimb) In particular, this includes setting up RMF and RMF DDS on z/os 34

35 SAP Host Agent and SAP SMD Agent Setup on z/os SAP Solution Manager Diagnostics Agent (1/2) Install Java on target z/os LPAR Tested: Java 6 and Java 7 Recommended: Java 7 For more information, see 35

36 SAP Host Agent and SAP SMD Agent Setup on z/os SAP Solution Manager Diagnostics Agent (2/2) Apply the following SAP Notes: Note Installation of Diagnostics Agents SAP SMD Agent installation strategy Note Diagnostics Agent - Installer Versions Overview on SAP SMD Agent installer versions Note Diagnostics Agent installation with SWPM Download instructions for documentation, installer and kernel package Note ZSCSinst Installationtool for SAP Central services on z/os Documentation for zscsinst (used for installing SMD Agent on z/os instead of SAPINST) 36

37 SAP Host Agent and SAP SMD Agent Setup on z/os SAP Solution Manager Apply the following SAP Note: Note DB2-z/OS:CCMS: Database outside discovery enablement Enable Solution Manager (ABAP-part) for database outside discovery 37

38 SAP Host Agent and SAP SMD Agent Setup on z/os Post Agent Installation Configuration (1/2) SAP Host Agent If necessary, set environment variables as described in SAP Notes: Note DB2-z/OS: sapdbctrl: Prerequisites and Configuration Note DB2-z/OS:CCMS:HAG: CIM-Provider Enablement for z/os 38

39 SAP Host Agent and SAP SMD Agent Setup on z/os Post Agent Installation Configuration (2/2) SAP Solution Manager Diagnostics Agent Set up connectivity to SAP Solution Manager using the smdsetup-script as described in the SAP SMDAgent Installation Guide If necessary, correct the path to JVM in Diagnostics Agent profile: In /usr/sap/daa/sys/profile/daa_smda<instnum>_<host> change SETENV_04 = PATH=$(DIR_EXECUTABLE):%(PATH):/usr/lpp/java/<JavaVersion>/bing tog SETENV_04 = PATH=$(DIR_EXECUTABLE):/usr/lpp/java/<JavaVersion>/bin:%(PATH) 39