Agenda

1. Tivoli Business Service Manager v4.1.0Clayton ChingMarket Management, Business Service Managementcching@us.ibm.com

2. Agenda • What is Business Service Management? • What is TBSM 4.1? • Why Sell? • Who to sell to? • The value of BSM and TBSM • Competitors • More Information

3. Service Management requires a closed-loop approach • Event Management • Business ServiceVisualization • ProcessAutomation How does this relate to the business service? What’s happening with theinfrastructure? What actions do we take to correct the problems?

4. Service Dashboard Tivoli Integrated Portal • Common Portal • Linked Integration • Reporting • Historical Reporting TSLA TBSM Netview z/OS ERP systems Operating Systems Performance Analytics SLA for TEP CCMDB Process Managers TADDM Business Service Management Change and Process Management Impact – Advanced Event & Data Correlation Omnibus – Event Consolidation & Correlation Additional KPI & Business Support Data Analytics SubSystem Service Assure Server, Systems, & Application Availability & Performance Management Network Availability and Performance Management TSOM. TIM, TAM,ISS Distributed Mainframe Topology RCA Wireless Perf. Wired Perf. Probes OMEGAMON ITCAM ITM Proviso Network Assure Precision Resource Metrics & Enterprise Warehousing Service Provider Network Warehousing Wire-line Networks Applications Middleware Wireless Networks

5. What is BSM? IT in Business Terms Aligning IT with Business BSM is not a Product Prioritize IT according to Business Impacts Managing by Service - Not by IT Infrastructure Run your IT like a Business

6. Key Thought BSM is a journey and must incorporate the people, process and technology and information that support the business.

7. Business Service Management

8. What is a Business Service? Traditional understanding: • A customer, partner or user facing business application. • Examples: SAP, Seibel, Oracle, Microsoft Exchange Business Service defined: • A business service is any customer, partner or user facing group of applications, middleware, security, storage, networks and other supporting infrastructure that come together to enable a comprehensive, end-to-end business process, transaction, or exchange of information. Examples: Online banking, e-commerce, credit card processing

9. Single Effective Management Interface: Business Dashboard Realtime Business Indicators Service Status Indicators Domain Status Indicators Third Party Data Realtime & Historical Reports

10. Business Metrics vs. IT Metrics

11. What are KPIs? KPIs (Key Performance Indicators) are Operational, Line of Business, and financial metricsthat reflect the strategic performance of an organization Sample KPIs: Banking Transactions, Medical Record Lookups, processed orders, failed transactions, transaction response time

12. KPIs by Industry (sample) • Retail Financial Services • - Teller, ATM, Retail Banking Transactions completed • - Avg. Response Time by Transaction Type • - Failed Transactions • - Revenue from transactions • Operational Penalty for application downtime and severe performance degradation • Equities Trading • Transactions completed online • Transactions passed to trading floor • Online trading application performance • Online trading application availability • Auto Manufacturing Sales • Dealer Application Availability • Orders processed • Failed & reprocessed orders • Order processing time when circuit utilization high. • Video Publishing • - Number of videos purchased by retailers • - ‘Order processing’ application availability • - Partner network circuit availability • - Failed & reprocessed orders ASPs (service hosting) - Active Users per application instance by Customer SLA Type - Failed queries per application instance - Average logged-in time by customer - Average transaction completion time, and comparison to historic metrics under identical loads Great location on industry specific KPIs: http://w3-03.ibm.com/sales/compass/industry/lc/custbusvalqv.nsf/Content/85257067%3A00573A45

13. IT Centric KPIs Email Environment • MB of email processed by server and region • Internal and external Messages transferred • Average internal & external email transfer times • Failed transfers 3 Tier Web Applications - Breakdown of response times by tier and network - Response time by tier as percentage of historic averages - Active Users per application - Load Balancer sessions

14. Delivering BSM

15. TBSM facilitates the linking IT to the Business Experience Dependencies Real-time Transaction Performance, Service Status, and End-User & Service Experience - (ITCAM portfolio, 3rd Party) Relationship and Discovery Data – TADDM, CCMDB, MRO Asset, Inventory, Network Mgmt, BPEL, 3rd Party CMDB How does this relate to the business service? Infrastructure Events Business Metrics Service Management Any Event or Fault from Any Source - ITM, Omnibus, TEC, ITCAM, OMEGAMON XE, NMS, EMS, Devices, 3rd Party Business Support Data – Incidents, Call Records, Billing Data, Process dependencies, Revenue, and Risk Analysis data Actions Views What’s happening with theinfrastructure? What actions do we take to correct the problems? Impact Analysis, Task Automation, Config, Provisioning, Activation, and Orchestration – TPM, TCM, TIO, Impact Business Views: SLM/SLA, Rev$$, Health, Customer Operational Views: RCA, Compliance, Impact Analysis, Incident Mgmt.

16. Tivoli Business Service Manager

17. ITM v6 Netcool Impact: for 3rd party CMDB, XML WebServices & others OMNIbus Gateway For Trouble Ticket Tivoli Data Warehouse v2.1 IDML TBSM Agent Netcool Reporter Discovery Integration Legend = TBSM V4 installed TBSM v4.1 Architecture TBSM V4 Web-Console MOSWOS TBSM Server Integration Service Model Choice of 9 Server Platforms Reporting TADDM OMNIbus Server Discovery Flow Historical Reports Status Event Flow Out-of-box Status Event Mapping Probe Library now covers 500+ Event Sources – Largest Available • IMS • CICS • DB2 • TWS • SA/390 • ASG • BMC • CA • HP OpenView NNM • CA Unicenter TNG • BMC Patrol • NetIQ • TEC • ITM v5 • ITM v6 • OMEGAMON • ITCAM • Syslog • SNMP v1,2,3 • All 3rd Party • EMS/NMS Distributed and z/OS Monitoring

18. Business Service ManagementDiscovery Library Adapters z/OS

19. z/OS Mainframe resources, (OMEGAMON, 3rd Party applications) BSM Solution – High Level Architecture Customer Resource Data (Inventory, CMDB, Provisioning Data) Expand to 500+ Data Feeds visualization structure status permissions TADDM TBSM rules Dependencies Events Resource, Application, Network Discovery RAD Event Engine drives component status/health (OMNIBus – TEC, ITM, Probe feeds) Business Data CMDB MYSQL MSSQL DB2 structure status Customer Resource Data (Inventory, CMDB, Provisioning Data) Leverage Customer Data: (used to define services, drive health & compliance, & align IT resources to business service context) ORACLE Postgres Any RDBMS Incidents, Transactions, Billing, Performance, Process, Compliance Relationships & Health

20. BSM Solution for z/OS – Out-of-Box support TBSM v4.1 will provide support for the following z/OS Data Sources: • OMEGAMON XE v3.1, v4.1 Agents • OMEGAMON XE Distributed Agents and monitored resources will be discovered by the TMS Discovery Library Adapter • OMEGAMON XE status event integration will be supported by the OMNIbus EIF Probe. This support is not agent specific. • TBSM out-of-box configuration provided for discovery and status event flows • General z/OS Resources • The z/OS Discovery Library Adapter will discover the following z/OS resources and relationships: • zSeries hardware and z/OS details • Address Space details and relationships • DB2 Subsystem details and relationships • IMS Subsystem details and relationships • MQ Subsystem details and relationships • CICS Region details and relationships • WebSphere Application Server details and relationships • Status event integration for z/OS discovered resources will be supported by the OMNIbus EIF Probe. • Customers may send their own EIF status events to discovered resources • Options include NetView for z/OS Event Automation Service and EIF in USS

21. BSM Solution for z/OS – Alignment with OMEGAMON • Business Component Views • Executives • Business Managers • End Users •  TBSM • Operational Component Views • Application Support staff • Help Desk staff • Operations staff •  TBSM • Infrastructure Views • Operations staff • Technical Support staff •  ITM & OMEGAMON XE • TBSM provides value-add to an OMEGAMON XE / DE solution • Visualize business services and supporting infrastructure from the top down • Integrate IT infrastructure monitoring with the Business service monitoring • Integrate business metrics and status with infrastructure metrics and status from OMEGAMON • Manager of managers – supports a wide variety of data sources for alerts and metrics • Multi-path status propagation for alerts as well as aggregation of business metrics • Integrate with Tivoli Service Level Advisor – combines real-time SLA evaluation with historical trending and analysis • Low level Diagnostics • Technical Support staff • Systems Programmers •  OMEGAMON Classic

22. BSM Solution for z/OS – Alignment with OMEGAMON

23. Agenda • IBM Tivoli Business Service Manager V4.1 with z/OS Deep Dive • Key Features • z/OS Discovery • z/OS Service Modeling using Component Registry • z/OS Status Event Flows

24. What is the IBM Discovery Library? … IDML? … Common Data Model? • An XML schema specification, called IDentity Markup Language (IDML*), that includes the definition of the IBM Common Data Model. • It is a set of specifications, components, and best practices for communicating the discovery of resources and the relationships between resources within the enterprise. • The IBM Discovery Library facilitates a lightweight, common way to share information about discovered resources and relationships through the implementation of IDML • Discovery Library Adapters (DLAs) are written by IBM and others The discovery library is a specification for communicating the existence of resources and relationships between authors and readers.

25. z/OS Discovery Library Adapter • The z/OS DLA runs as a batch job • Manually as required, or via a job scheduler, or via an automation product. • Discovers resources and relationships on z/OS, including: • z/OS, zSeries Hardware, IMS, CICS, DB2, MQ and WebSphere • Produces XML files that comply with the IBM Common Data Model • 39 different classes • 91 different relationship pairs • 228 different class attributes • Possibly thousands of class instances depending on the environment • The XML files are transferred to the Discovery Library File Store, and loaded by various products: • CCMDB loads the XML files to detect configuration changes • TBSM loads the XML files for dependency relationships and event correlation • Others in future….

26. z/OS DLA Books • The z/OS DLA generates multiple XML files as members in a PDSE: • A member called “ZOSBASE” containing Hardware and z/OS details • A member called “ZOSTASK” containing Address Space details • A member per subsystem (DB2, IMS, MQ, CICS, WAS) • The DLA will also generate a “FTP statement deck” that is used in a subsequent FTP step to transfer the XML members to the Discovery Library File Store (DLFS) with the appropriate file name e.g. PUT IMP1CTL ZOSIMS210.IMP1CTL@pthomo1.au.ibm.com.2006-09-04T02.07.17Z.xml • To improve performance the DLA will checksum the books, ignoring the IDML timestamp that is within the book. • When a new discovery is performed the checksum will be compared and if it is identical to the previous discovery, the book will NOT be replaced or transferred to the DLFS.

27. ZOSBASE – zSeries hardware & z/OS details Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction IMS IMSProgram Sysplex ZVM IMSDatabase MQ SystemSpecificCollection ZVMGuest MQSenderChannel MQReceiverChannel CICS ZOS ComputerSystem CICSTransaction IPInterface CICSProgram WAS IPV4Address CICSFile Attributes include: • Parmlib active member contents • IODF dataset, time, edt • LNKLST, APF datasets BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

28. ZOSTASK – Address Space details & relationships Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction IMS IMSProgram Sysplex ZVM IMSDatabase Used by TADDM to stitch relationships from Distributed to z/OS Subsystems MQ SystemSpecificCollection ZVMGuest MQSenderChannel MQReceiverChannel CICS ZOS ComputerSystem CICSTransaction IPInterface CICSProgram WAS IPV4Address CICSFile BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell Attributes include: • Pgm, pgm parms • JobFunction • Allocations UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

29. DB2 Subsystem details & relationships – No Data Sharing Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction IMS Attributes include: • Version • Command Prefix • Sysdatabase Max Alteredts • Systablespace Max Alteredts • Systables Max Alteredts • Sysindexes Max Alteredts • Syscolumns Max Alteredts IMSProgram Sysplex ZVM IMSDatabase MQ SystemSpecificCollection ZVMGuest MQSenderChannel MQReceiverChannel CICS ZOS ComputerSystem CICSTransaction IPInterface CICSProgram WAS IPV4Address CICSFile BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

30. DB2 Subsystem details & relationships – Data Sharing Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction Attributes include: • Version • Command Prefix IMS IMSProgram Sysplex ZVM IMSDatabase MQ SystemSpecificCollection ZVMGuest Attributes include: • Version • Command Prefix • Sysdatabase Max Alteredts • Systablespace Max Alteredts • Systables Max Alteredts • Sysindexes Max Alteredts • Syscolumns Max Alteredts MQSenderChannel MQReceiverChannel CICS ZOS ComputerSystem CICSTransaction IPInterface CICSProgram WAS IPV4Address CICSFile BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

31. IMS Subsystem details & relationships Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction IMS IMSProgram Sysplex ZVM IMSDatabase MQ SystemSpecificCollection ZVMGuest MQSenderChannel MQReceiverChannel Attributes include: • Version • Command Prefix • IMSSubsysType • TransactionsChecksum • ProgramsChecksum • DatabasesChecksum CICS ZOS ComputerSystem CICSTransaction IPInterface CICSProgram WAS IPV4Address CICSFile BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

32. MQ Subsystem details & relationships Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction IMS IMSProgram Sysplex ZVM IMSDatabase MQ SystemSpecificCollection ZVMGuest MQSenderChannel MQReceiverChannel CICS ZOS ComputerSystem CICSTransaction Attributes include: • Version • Command Prefix IPInterface CICSProgram WAS IPV4Address CICSFile BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

33. CICS Region details & relationships Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction IMS IMSProgram Sysplex ZVM IMSDatabase MQ SystemSpecificCollection ZVMGuest MQSenderChannel MQReceiverChannel CICS ZOS ComputerSystem CICSTransaction IPInterface Attributes include: • Version • TransactionsChecksum • ProgramsChecksum • DatabasesChecksum • NetID, Applid • SYSIDNT, GRNAME • SIT, SITOverides CICSProgram WAS IPV4Address CICSFile BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

34. WebSphere Application Server details & relationships Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction IMS IMSProgram Sysplex ZVM IMSDatabase MQ SystemSpecificCollection ZVMGuest MQSenderChannel MQReceiverChannel CICS ZOS ComputerSystem CICSTransaction IPInterface CICSProgram WAS IPV4Address CICSFile BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

35. ZOSALL – Everything that is active in one book Db2Database DB2DataSharingGroup ZSeries CS DB2 Db2Tablespace Organization IMSSysplexGroup LPAR IMSTransaction IMS IMSProgram Sysplex ZVM IMSDatabase MQ SystemSpecificCollection ZVMGuest MQSenderChannel MQReceiverChannel CICS ZOS ComputerSystem CICSTransaction IPInterface CICSProgram WAS IPV4Address CICSFile BindAddress Fqdn WebSphere NamedEndPoint TcpPort StorageSubSystem WebSphereCell UDPPort WebSphereNode AddressSpace StorageVolume ConfigFile • Aqua – All attributes we know about the class are populated • Yellow – Stub instance for relationships only i.e. enough attributes to satisfy naming rules • Clear – Class is not populated in this book.

36. How the z/OS DLA works • Strong design focus to be SIMPLE, efficient and accurate • Anyone with basic access to the z/OS can perform the discovery • Does not require a live agent environment to be installed. • Does not require z/OS, IMS, CICS etc expertise. • Does not require site knowledge e.g. no naming conventions needed • Runs “out of the box”, but has also various configuration options for greater control. • Minimal prerequisites • The z/OS DLA uses various z/OS System Services and inspects memory control blocks. • The z/OS DLA does NOT issue z/OS commands in order to avoid possible performance overhead, syslog flooding and security prerequisites.

37. APF is a common installation requirement • Most users have OMVS segment authority e.g. FTP requires this • Systems programmers would normally have this authority • MQ and DB2 load module datasets are normally in the LNKLIST • DSNREXX Bind is a standard DB2 installation step Standard Prereqs Prerequisites • APF authorization of z/OS DLA load module dataset • User running the DLA job has OMVS segment authority • For FULL discovery (a lot is discovered without these):

38. Tivoli Monitoring Services Discovery Library Adapter • The TMS DLA comes with Tivoli Enterprise Portal Server (TEPS) and discovers: • All Managed Systems, including ITM and OMEGAMON XE agents • Logical View “collections” • Attributes to enable context sensitive launch into TEP • The z/OS DLA and TMS DLA can be used independently or in conjunction with each other. • Main strengths of z/OS DLA not covered by TMS DLA • Richer Subsystem Relationship & Attribute discovery • Z Hardware discovery • Main strengths of TMS DLA not covered by z/OS DLA • Enables context sensitive launch to TEP • Event correlation to ITM & OMEGAMON XE

39. Questions??