BMC Transaction Management - PowerPoint PPT Presentation

Loading...

PPT – BMC Transaction Management PowerPoint presentation | free to view - id: f6364-ZDc1Z



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

BMC Transaction Management

Description:

9/6/09. BMC Transaction Management. John Barnard. MAINVIEW Development Director. 9/6/09 ... Ensures applications meet their business needs ... – PowerPoint PPT presentation

Number of Views:55
Avg rating:3.0/5.0
Slides: 52
Provided by: johnba76
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: BMC Transaction Management


1
BMC Transaction Management
  • John Barnard
  • MAINVIEW Development Director

2
BMC Transaction Management Value
BMC Transaction Management helps IT improve
business service delivery by detecting, isolating
and resolving business transaction performance
problems across the enterprise.
  • Understand there is a problem before the phone
    rings
  • Ensures applications meet their business needs
  • Increased revenue and improved customer
    satisfaction

3
What do customers do without Transaction
Management
  • End users flood the service desk with complaints
    aboutpoor service (performance, availability, or
    accuracy)
  • Monitor components (databases, servers,
    operatingsystems, etc) without considering the
    end user orquality of service delivered
  • Point fingers when there is a problem and say My
    piece (db, server, OS) was working great
  • Waste time and money researching and replicating
    problems
  • IT is viewed as an inhibitor of business rather
    than an enabler
  • Business is lost due to failed and poor
    performing transactions

4
Moving Beyond Silos
80
BMC Transaction Management moves beyond
technology monitoring to provide the end users
point of view of application performance
5
Business Applications and Software Silos
Business Application Support
Application Architecture
Disparate Information Different Semantics
Mainframe
Distributed
Sftwe Tech 1
Sftwe Tech 2
Sftwe Tech 3
Sftwe Tech 4
Sftwe Tech 5

Sftwe Tech n
Business Application 1
Business Application 2
Business Application n
Network and Server Hardware
6
Business Application/Service Management
Business Application Support
Application Architecture
Integrated Information Common Semantics
Help Desk
Business Service and Transaction Management
ESM
Application Topology
Mainframe
Distributed
Sftwe Tech 1
Sftwe Tech 2
Sftwe Tech 3
Sftwe Tech 4
Sftwe Tech 5

Sftwe Tech n
Business Application 1
Business Application 2
Business Application n
IT Operations Support
Help Desk Support
Network and Server Hardware
Network Systems Management Support
7
Business Application/Service Management
Business Service and Transaction Management
Mainframe
Distributed
Sftwe Tech 1
Sftwe Tech 2
Sftwe Tech 3
Sftwe Tech 4
Sftwe Tech 5

Sftwe Tech n
Business Application 1
Business Application 2
Business Application n
Network and Server Hardware
8
Spanning Distributed and Mainframe Applications
MAINVIEW Transaction Analyzer
Q Nami! by MQSoftware
WEB
Business Service and Transaction Management
Distributed
Mainframe
Web Server
Data Base
CICS
App Server
App Server
App Server J2EE
Websphere
Business Application 1
Business Application 2
Business Application n
End Devices
9
An Integral Part of BMCs BSM Strategy, ITIL Best
Practices Existing Infrastructure Investments
  • Provides understanding of the performance of
    Business Services
  • Delivering value on its own
  • Adding value to BMC Business Service Management
    products and strategy
  • Adding value to Infrastructure Monitoring
  • Increases the ROI of application and
    infrastructure management by aligning IT
    performance with business objectives

10
The Mainframe World
  • MVTA Introduction
  • MVTA Technical Description
  • MVTA Next Steps

11
How many ways are there to interoperate in z/OS?
  • IBM Software and System groups have created a
    nightmare over time!
  • The nightmare is bad for customers
  • The multiplicity of interoperation facilities has
    grown over many years
  • As with freeway systems.create one and people
    drive on it!
  • Applications that are tried and true do not
    change unless there is a compelling business
    reason for it.
  • Critical business logic that works today may
    suddenly stop if a developer opts to use the
    latest gee whiz technology
  • Emerging facilities are adopted and glued on to
    the old methods
  • Companies buy companies and wire systems together
  • Its a mess!

12
A day in the life of a transaction
CICS
DB2
IMS
MQ
WAS
13
MAINVIEW Transaction Analyzer (MVTA)
  • MVTA is part of the MAINVIEW family
  • Benefits from common infrastructure and
    communication
  • Utilizes data from existing BMC monitoring
    solutions
  • Correlates transaction information
  • Consolidates transaction information from
    different subsystems across the mainframe
    environment
  • Tracks transaction through and across z/OS
    environments
  • User sees the path taken for each unit of work in
    the logical order in which they were invoked
  • Near real time
  • Improves debugging capabilities
  • Provides information about transactions as they
    flow
  • Makes it easier to pinpoint problems (problem
    isolation)
  • Application-level units of work summarize what
    happened during the transaction
  • No need to hunt through several products to see
    where breakdown occurred

14
Architectural Overview of MVTA
IP?
Qnami!
eWLM
WAS
CTG
15
Example transaction flow
  • CICS-DB2 Transaction
  • 1. Transaction TRN1 in Region CICS1 on image
    MVS1
  • 2. TRN1 Invokes DB2 system DB21using Plan PLAN1
  • 3. TRN1 Uses Distributed Program Link (DPL) to
    program PROG2 in CICS2 on image MVS2. This runs
    under the standard mirror task CSMI
  • 4. CSMI invokes DB2 system DB22 using Plan
    PLAN2
  • 5. CSMI returns
  • 6. Transaction TRN1 returns
  • 7. UOR created
  • TRN1 has a UOR UOR1
  • DB21 using PLAN1 has a UOR UOR2
  • CSMI has a UOR UOR3
  • DB22 using PLAN2 has a UOR UOR4

16
Sample Flow for illustration
CICS1
CICS2
DB21
DB22
SQL PLAN1
SQL PLAN2
TRN1
CSMI
UOR1
UOR3
DPL to PROG2
UOR4
UOR2
SYNCPOINT And End
MVCICS PAS
MVDB2 PAS
MVCICS PAS
MVDB2 PAS
MVTA PAS
MVLOG STC
MVLOG STC
MVTA PAS
MVI CAS
MVI CAS
MVTA Log
MVTA Log
17
On Demand Correlation
  • MVTA Correlates Transaction data On Demand
  • End user request for a VIEW
  • Request via View Based API
  • Any Timer driven process requesting it
  • Observes the adage Keep the data local!
  • Reduced overhead. The price is paid when a user
    requests correlation
  • Increased flexibility by not storing all data in
    the same location

18
Correlation View
19
Drill down from Problem Isolation to Diagnosis
  • MAINVIEW Transaction Analyzer provides problem
    isolation based on information provided by
    underlying MAINVIEW monitors
  • MAINVIEW monitors provide diagnosis via drill
    down from MVTA
  • Using standard MAINVIEW architecture, MVTA
    hiperlinks to UOW/UOR information in
  • MAINVIEW for CICS
  • MAINVIEW for IMS
  • MIANVIEW for DB2
  • MAINVIEW WEBSPHERE for MQ

20
CICS Drill Down to MAINVIEW for CICS
21
CICS Direct Link to MAINVIEW for CICS
22
CICS Drill Down on File to see delay reason
23
IMS Drill down to MAINVIEW for IMS
  • Requires MVIMS 4.2 with PTFs
  • BPI9796, BPI9802, BPI9797, BPK1153

24
IMS Hyperlink into MAINVIEW for IMS
25
DB2 Drill down to MAINVIEW for DB2
  • Hiperlink on the Count to expand rows
  • Hiperlink on the DB2 ID field to get thread
    information.

26
DB2 DOMEQRPN Thread Accounting Report
27
DB2 DOMEQRPN Thread Accounting Report (cont.)
28
MQ Search Result
29
MQ MVTA with CICS, MQ, and IMS
30
MQ Hyperlink to MQ from GET latency page1, page2
31
Next Steps for MVTA
  • Additional z/OS support
  • Integration with MAINVIEW Websphere for
    Application Server (MVWAS)
  • Tracking transaction flows at the enterprise
    level.
  • MVTA captures MQ related transaction flows when
    they enter z/OS
  • For MQ applications following best practices
    where MQ MSGIDs are unique, MVTA answer important
    questions
  • A CICS task executes MQPUT to a Queue for which
    an IMS trigger is defined
  • Question What IMS transaction ran and how well
    did it perform?
  • MVTA does not capture MQ related flows before
    they enter z/OS
  • From where did the initial MQ request originate
    in the distributed environment and how well did
    application processes associated with it perform

32
Qnami! By MQSoftware
33
People, Process and Information Delivers Business
Application Value
Efficiency Depends on People, Process and
Information
  • Information
  • The management tools that address the visibility
    of the business application and expose
    information in the appropriate semantics
  • People
  • The virtual and/or dedicated application support
    team (and others)
  • Process
  • The organization's way of providing business
    application support and the interaction of the
    support team with other members of the enterprise

34
Business Application Management
The Information
Aggregate Business Metrics
Quality of Business
Business Intelligence
Process Analysis
Real-time Business Content
MVTA
Business Perf
Business KPI
Inf Mgmt
Business Proc Stats
Business Notification
Q Nami! BTM
MAINVIEW
Business Application Management
ITIL
SOA
SLA
Problem Mgmt
IT Notification
Service Delivery
Business Agility
Service Quality
Problem Identification
Real-time IT Events
35
Q Nami! Value Proposition
  • Benefits
  • Real-time monitoring of each business transaction
  • Event on transaction payload value for
    business-level information exposure
  • Supports many regulatory requirements for
    business operations
  • Monitor revenue and business risk of each
    transaction in real-time
  • Isolate transaction and business process
    inefficiencies resulting in less downtime,
    efficient use of IT resources, reduced
    operational risk and accurate process
    optimization
  • Increased efficiency in demonstrating compliance
    and service level agreements
  • Assures data integrity for business intelligence
    reporting requirements
  • Aligns IT with the business

36
Q Nami! Value Proposition
  • Features
  • Transaction Monitoring
  • Business Performance Monitoring
  • Quantitative
  • Qualitative
  • Business Process Measurements
  • SLA Monitoring and Reporting
  • Business Payload Monitoring and Reporting
  • Business Service Monitoring
  • Performance and Availability Monitoring
  • Event Correlation and Management based on Payload
    Contents and Transaction Timeouts or Failures

37
Q Nami! Transaction Monitoring Support
Java API
C API
CICS API
COM/.NET API
Q Nami! provides a robust transaction monitoring
solution regardless of technologies used or
architectural styles employed.
38
Business Performance Information
Business Performance Information through the
Payload Monitoring Engine
39
Business Notification
Payload monitoring provides the ability to set
business thresholds for out of range payload data
and take appropriate automated action
40
Technical User Perspective
Business service views from performance and
availability data provides immediate status of
business application with respect to
infrastructure performance
41
Technical User Perspective
IT operations and application support teams can
observe the real-time transaction status of
transactions flowing through the business
application
42
Technical Notification
Notification of a transaction that has failed
leads IT Operations and application support teams
to view the location of where the transaction has
failed
43
Problem Determination in Multi-Tier,
Heterogeneous Technology Business Applications
  • Focus of discussion is on problem determination
    and management functionality of Q Nami!
  • Q Nami! understands the status of a transaction
    at any distributed location with some Mainframe
    presence
  • MVTA understands the status of a transaction at
    any location on the mainframe
  • .. but, there are other virtual team members who
    gain value from knowing the overall transaction
    status and pinpointing causes of problems
  • Result Work more efficiently, lower business
    application support costs, decrease dramatically
    the time to resolve a problem

44
Business ApplicationInsurance Policy Purchase
MVTA
Architectural view of data flow for Insurance
Policy Purchase business application
CICS
WAS
WMB
DB2
WMQ
WMQ
IMS
Linux
AIX
z/OS
MV
Business Application Support Virtual Team
45
Business ApplicationInsurance Policy Purchase
Everything is running with no problems. Virtual
team members can concentrate on other value
producing activities
MVTA
Life is good!
CICS
Txn 1 Start
WAS
WMB
DB2
WMQ
WMQ
IMS
Linux
AIX
Txn 1 End
z/OS
MV
Business Application Support Virtual Team
46
Business ApplicationInsurance Policy Purchase
Q Nami! operations console showing the status of
individual transactions
MVTA
Q Nami! drill-down to performance and
availability metrics for WAS
CICS
Txn 1 Start
WAS
WMB
DB2
WMQ
IMS
Linux
AIX
z/OS
MV
BMC RCA deep-dive JEE analysis finding root cause
of problem
Business Application Support Virtual Team
47
Business ApplicationInsurance Policy Purchase
Q Nami! operations console showing the status of
individual transactions
MVTA
Q Nami! drill-down to performance and
availability metrics for WMB
CICS
Txn 1 Start
WAS
WMB
DB2
WMQ
WMQ
Analyze specific node in WMB execution group to
optimize response times
IMS
Linux
AIX
z/OS
MV
Business Application Support Virtual Team
48
Business ApplicationInsurance Policy Purchase
MVTA
Q Nami! drill-down to business service views for
insurance policy purchase business application
Q Nami! operations console showing the status of
individual transactions
CICS
Txn 1 Start
WAS
WMB
DB2
WMQ
WMQ
Analyze specific interactions of mainframe
components through MVTA
IMS
Linux
AIX
z/OS
MV
Business Application Support Virtual Team
49
Q Nami! Integration With MVTA
  • Product Integration Phase 0
  • Jointly written white paper on Q Nami! and MVTA
    integration foundations
  • Product Integration Phase 1
  • Simple launch in context from Q Nami! to MVE/MVTA
  • Product Integration Phase 2
  • Q Nami! pull of MVTA data and displayed in Q
    Nami! dashboard
  • Potential integration to MAINVIEW monitors
  • MAINVIEW monitors launched when QNami! detects
    transaction hang or slow down in real time
    transaction environments
  • MAINVIEW monitor information pulled for inclusion
    into QNami dashboard
  • Futures
  • Possible integration with BMC Atrium CMDB and BMC
    Discovery
  • Possible integration with BMC Capacity Management
    Data Base (CDB)

50
Summary
  • The enterprise focus needs to be on the business
    application and not the technology
  • IT to business alignment is attained through
    people, process and information synchronization
  • Information source for business application
    management is the transaction flow
  • Information measurement is attained from having
    focus on the business transaction in a business
    application
  • Q Nami! provides end-to-end business transaction
    monitoring and supports various levels of
    functionality for both business and technical
    users
  • Q Nami! and MVTA make a powerful combination to
    monitor and manage business applications that
    span distributed and mainframe systems

51
Thank You!
About PowerShow.com