IBM Software GroupIBM Software Group
© 2009 IBM Corporation
Tivoli Dynamic Workload Console& TWS Bridge
Alexandra ThurelTWSz Development Manager
Paris, 12 Mai 2009
2© 2009 IBM Corporation
Tivoli Dynamic Workload Console 8.5 : L'interface Web de TWS
� Principaux concepts
� Les différents profilesd'utilisateurs
� Edition d'application TWS
� Suivi du déroulement du plan
� Fonction de reporting
http://www.flickr.com/photos/jahovil/542568413/
3© 2009 IBM Corporation
Browsers
Tivoli Dynamic Workload Console – Topology Example
TDWCISC
z/OSServer
8.38.3
8.5
TDWCISC
8.4
8.4, 8.5
Browsers
Browsers
Browsers
Browsers
z/OSConnector
TWSMDM
TWSFTA
TWSSA
4© 2009 IBM Corporation
ModelingReporting
EventManagment Submit
Monitoring
Workload ServiceAssurance
Tivoli Dynamic Workload Console: Macro Features
5© 2009 IBM Corporation
Function coverage in steps
8.3 Monitoring Jobstream, Job, Resources, Workstation…. + Submit (Predefined job/Jobstream…)
8.4 Event Management Reporting
8.4 FP1 Dynamic Critical Path
8.5Dynamic Critical Path, Variable Table +
Modeling Jobstream/Job, Resources, Workstation… + Runcycle
Calendar, VirtualWorkstation, Automationfiltering criteria …
Mass Update, Daily Planning, Service functions
12/08
03/08
Product futures are directional in nature and does not imply any product plan commitment in the part of IBM.Plans and designs are subject to change at any time without notice.
03/09
GraphicalView
SOX
zOS feature
Distributed feature
Both
8.5 FP1Conditional Logic
Print Jobstream prop., CopyPaste dependencies
6© 2009 IBM Corporation
2003
June
TWS 8.2 GA. New look and feel for the JSC GUI.
June
TWS 8.2.1 GA. Mature and
optimized JSC
December
TDWC 8.3 provides the new operational Web UI
April
TWS 8.3 GA. RDBMS modelingand WAS planning technology. JSC is published along.
(Next release)
Provide graphical views interfaces to
TWA familyOctober
TWS 8.4 and TDWC 8.4, graphical reporting and
improved usability
TWA Graphical Interfaces evolution
2004 2005 2006 2007 2008 2009
March, June
TDWC quarterly fixpacks for more
function and better user experience
December
TWS 8.5 and TDWC 8.5, completes Web Interface
with modelling part
May
TWSz 8.5 & TDWC introduce
Conditional Logic
7© 2009 IBM Corporation
Les différentsprofiles d'utilisateurs
8© 2009 IBM Corporation
TDWC’s Roles
Administrator
Operator
Analyst
Configurator
Designer
• Define TDWC users• Define and share TWS engine connections• Design Workload definitions• Design and Monitor Event rules• Design and Monitor Scheduling environment• Define and share TDWC'c tasks to Monitor TWS scheduling objects • Submit Jobs and JobStreams• Generate Trial and Forecast plan• Define and share TDWC'c tasks to Generate Historical and Production reports• View Dashboard• Modify User preferences
• Design Workload definitions• Modify User preferences
• Define and share TDWC'c tasks to Monitor TWS scheduling objects • Submit Jobs and JobStreams• Generate Trial and Forecast plan• Modify User preferences
• Define and share TDWC'c tasks to generate• Historical and Production reports• Modify User preferences
• Define and share TWS engine connections• Modify User preferences
IBM Software GroupIBM Software Group
© 2009 IBM Corporation
Edition d’applications
10© 2009 IBM Corporation
Workload Modelling, Planning and Forecasting
� Centralized modeling of heterogenous batchworkloads across the enterprise
– Centralized repository for all batch objects (e.g. calendars, jobs, job-streams, resources, etc..)
– Centralized security, authorization and auditing
� Centralized planning for calendar-driven and event-driven batch workload
– Viewing and documenting current and forecast plans
– Viewing and documenting dependencies among jobs, resources, calendars, etc…
11© 2009 IBM Corporation
Workload Modeling
Efficient and innovative way to prepare workloads, develop workflows to map Business Processes, and manipulate existing or new definitions.
© 2009 IBM Corporation
13© 2009 IBM Corporation
Conditional dependencies
14© 2009 IBM Corporation
Add a conditionto your
jobstream
Define yourcondition(s)
IBM Software GroupIBM Software Group
© 2009 IBM Corporation
Suivi du déroulement du plan
16© 2009 IBM Corporation
How do I monitor my own jobs?
� Single point of monitoring and control for batch workload and batch environments
– Monitor workload jobs events (e.g. job start/end) and alerts (i.e. job in error, late, long)
– Monitor events related to scheduling infrastructure health
– Monitoring of business Critical Jobs, critical path, critical predecessors, risk level
Jobs Monitor v
iewTDWCTDWC
Workload Das
hboardTDWCTDWC
Batch jobs view
sTEPTEP
© 2009 IBM Corporation
Sara, how do I understand and repair failure?
TDWC drill path provide
� Dashboard – to – single job log easy path
� One-click access to key information
� Drill stack to go back and forth between the steps
18© 2009 IBM Corporation
Monitoring and Modifying Conditions in CP
19© 2009 IBM Corporation
Business needs
� How to improve Service Level Agreements, automate operations and reduce costs?
� How to monitor and measure the impact of workloads against business service delivery?
� How can I filter and prioritize critical events from a flood of system-wide events?
� How can I ensure business priorities to get the right attention, and speed their implementation time?
� How can I enable proactive reaction?
TDWC SpecialWorkload Service Assurance
Available on TWS z/OS 8.3 SPE and
TWS 8.5
Administration
Automation
Automation
Operation
Solution
Allows identification of criticalworkload
Calculates critical path to criticalworkload and keep itdynamically updated
Takes autonomous remedialactions for lagging jobs inthe critical path
Gives a view of the critical end points and the possibilityto understand how well workload isprogressing to reachthat point to trigger proactivehuman reaction
20© 2009 IBM Corporation
1:00
21:00
Workload Service Assurance: Identifying critical workload
� Every production has some critical jobs that must be completed by a given time
5:00
6:00
� Critical jobs may be any distributed or mainframe jobs in the end-to-end network
21© 2009 IBM Corporation
1:00
21:00 5:00
6:00
Workload Service Assurance: Critical Path determination
� Automatic determination of critical path tocritical jobs
� Through the network of internal and externaldependencies
�Path with minimum slack time�Cannot be delayed without delaying the
critical job
� Dynamic adjustements: an alternate legmay become critical
�Unexpected anomalous condition in the critical jobs predecessors
�Unplanned workload
22© 2009 IBM Corporation
TWS z/OS - Workload Service Assurance
� User identification of critical jobs and their deadline
� New views (ISPF, JSC, WEB UI and TEP views) for Critical Jobs and Critical Paths
� Critical Path is dynamically recalculated when unexpected delays occur on jobs outside the original Critical Pathy or for jobs dynamically added to the plan
� Graphical and dashboard views of critical Jobs and their risk to miss deadline (High, Potential, no-risk), with drill-down navigation to predecessor jobs causing the risk.
� Automatic promotion of jobs on critical path for critical jobs in high or potential risk
IBM Software GroupIBM Software Group
© 2009 IBM Corporation
Reporting
24© 2009 IBM Corporation
� Historical data analysis and statistics, detecting jobs with exceptions: success rates, late starts, long durations, missing deadlines, etc …
� Tuning the workload of workstations: job runs, comp aring workload, etc…
Jobs statistics
view
TDWCTDWC
Jobs in error
reports
TDWCTDWC
Workstation
Workload
Summary
TDWCTDWC
Reporting feature
Workstation
Workload
Runtimes
TDWCTDWC
25© 2009 IBM Corporation
Report type : Job Run History example� Measure business compliance and SLAs
Report type
Filter criteria
26© 2009 IBM Corporation
Report type : Job Run Statistics� Workload schedule forecasting
Filter criteria
27© 2009 IBM Corporation
Report type : Workstation workload summary� Capacity planning adjustements
Filter criteria
28© 2009 IBM Corporation
Report type : Workstation workload runtimes� Monitor and tune workload capacity
Filter criteria
29© 2009 IBM Corporation
Tivoli Workload Automation value proposition
• Respond faster and make better decisions
• Single point of operational control
• End to end visibility
• Manage risk and compliance
• Predictable plans
• Event Driven Workload Automation
• Conditional logic
• Lower costs and build agility
• Workload Service Assurance
• Virtualization
See your business Manage your business Improve your business
Visualize Control Automate
30© 2009 IBM Corporation
TWS Bridge
Comment communiquer en peer-to-peer entre plusieurs contrôleurs TWS
31© 2009 IBM Corporation
TWSFault
Tolerant Agent
TWS XA
TWSDomain Manager
TWSMaster
TWSStandard
Agent
TDWBAgent
TDWBAgent
BrokerAgents
BrokerServer
TWSFault
Tolerant Agent
Open systemsOpen systems
Command Command Line Line
InterfaceInterface
c:\
TWSzAgent
z/OS z/OS SysplexSysplex
TWSzEngine
TWSzAgent
TWSzAgent
WebWebBrowserBrowser
Dynamic Console Server
----------ISPF
----------ISPF ISPF
InterfaceInterface
End to end solutionsEnd to end solutionsTWSz X-agent
End-to-end cross enterprise workloads aggregation
With TWA you can deploy flexible configurations to adhere to any organizational structure, and provide security, robustness, scalability and centralized control
32© 2009 IBM Corporation
End to End z Driven scenario
Master DomainManager
Def. Billing
33© 2009 IBM Corporation
Multimaster Bridge scenario
Master Master
Def. Billing
“call Def Billing”
MultiMaster proposal: two primitives
1: Submit and Track. I (requestor) want you (executor) to execute this workload and let me know about status, completion, results, etc.
2: Cross dependencies. I (successor) want to start workload after you (predecessor) have finish.
Def. Billing
34© 2009 IBM Corporation
Multimaster mechanism overview
TWS Dist
TWS z TWS z
TWS Dist
� Four cases to cover
– A: z/OS to z/OS
– B: z/OS to Dist
– C: Dist to z/OS
– D: Dist to Dist
CB
A
D
35© 2009 IBM Corporation
Case A: z/OS to z/OS
� Primitive 1: submit and track
– Several possibilities, ETT, PIF calls. To be examined further.
� Primitive 2: cross-dependencies
– Implementation through common tracker.
– Scenario steps
• TWSz B (predecessor) runs the workload. At the end of each application, a best practice instructs to run a dummy operation on the common tracker
• TWSz A (successor) has the workload defined with the same name. • When TWSz B job executes, TWSz A sees the jobs and tracks to completion.
• Workload on TWSz A that depends on the job can start right after completion.
36© 2009 IBM Corporation
For More InformationTivoli User GroupsYou can get even more out of Tivoli software by participating in independently run Tivoli User Groups around the world; learn about online and in-person opportunities near you at www.tivoli-ug.org
Tivoli TrainingIBM offers technical training and education services to help you acquire, maintain and optimize your IT skills. For a complete Tivoli Course Catalog and Certification Exams visit www.ibm.com/software/tivoli/education
Tivoli ServicesWith IBM Software Services for Tivoli, you get the most knowledgeable experts on Tivoli technology to accelerate your implementation. For a complete list of Services Offerings visit www.ibm.com/software/tivoli/services
Tivoli SupportIBM Software Premium Support provides an extra layer of proactive support, skills sharing and problem management, personalized to your environment.Visit www.ibm.com/software/support/premium/ps_enterprise.html
37© 2009 IBM Corporation
MERCI !