IBM Tivoli Workload Scheduler Automation - Nordic TWS conference

IBM Software Group 

® 

Tivoli Workload Automation 

Overview of latest updates 

Flora Tramontano – Flora.Tramontano@it.ibm.com 

TWA Product Manager 


© 2007 IBM Corporation

IBM Software Group | Tivoli software 

The Workload Management is leading the change 

Automate calendar-based 

production batch – workload 

planning 

Orchestration of work flows 

Centralized management 

Optimize use of existing 

resources 

Provide increased 

availability, reduce errors 

Constant productivity 

increase on batch window 

Governance across 

scheduling points through a 

consolidated view 

Event-based scheduling, on 

demand 

Provide proactive alerts on 

workload risks and improve 

SLA 

Transform complexity in 

platform/application flexibility 

Integration across Tivoli 

Follow the ERP evolution 

SAP progresses 

Use of virtualization 

technology 

Service Mgmt automation 

(best practices) 

Align to Business 

Processes 

Runbook template flow 

definitions 

Flexible implementation 

Pluggable product 

Solution-based offering 

Adapters based on 

standards - web services 

Dynamic topology 

Traditional scheduling New scheduling needs Service based scheduling 

2


Tivoli Workload Automation - last updates timeline 

Current versions 2Q07 

3Q07 

4Q07 

1H08 

Tivoli Workload 

Scheduler 

V8.3 

V8.4 

V8.4 FP1 

Event based scheduling 

TEP integration 

IPv6 support 

LDAP support 

Consumability improvements 

CCMDB Integr. 

Events for business logic 

Eclipse-based TWS 

Workbench 

Tivoli 

Workload 


for z/OS 




for 

Applications 


Dynamic 


Broker 


Dynamic 


Console 

V8.3 

V8.3 

V1.1 

V8.3 

V8.3 SPEs 

NT password 

encryption in E2E 

TCP/IP 

communication 

support 

V1.2 

Auditing 

Extended platform coverage 

(Solarix, HP-UX) 

Oracle RDBMS support 

V8.3 SPEs 

Reporting feature 

Virtual Workstation 

V8.4 



LDAP and IPv6 support 

SAP job submission (alignment to JSC) 

z/OS 8.3 features alignment 

V8.3 SPEs V8.3 SPEs 

IPv6 

NOERROR enhancements 

V8.4 

SAP load balancing 

SAP events in EDWA 

Import SAP calandars 

Dynamic Critical Path 

V8.4 FP1 

BDC session management 

IDOCs management 

Process chains 

V8.4 FP1 


3


TWS (dist) 8.4 

Event-Driven Workload Automation 

Extends the current TWS calendar-based capabilities to orchestrate unplanned, eventdriven 

workload 

 

Trigger the execution of TWS jobs and jobstreams on unplanned asynchronous events (eventrules) 

Provides real-time user notification 

 

Notify users when anomalous conditions happen in the TWS scheduling infrastructure or in the 

TWS batch scheduling activity 

Extends TWS integrability with third party products 

 

Allow to call an external product from TWS when a particular event condition happens in TWS 

Improve TWS self-monitoring and self-healing capabilities 

 

Automate recovery actions for TWS infrastructure or scheduling problems 

4




The “Event Rule” object is fundamental in the new Event-Driven architecture 

Event Rule is made up of: 

Event 

Correlation rule 

Action 

Event 

Action 

Event 

Events 

Correlation 

Actions 

•File created, modified, deleted 

•Message logged to a file 

•TWS events 

Job/Jobstream status change 

Return code condition 

TWS agent status (linked/unlinked) 

TWS message box status (threshold 

%, box full, etc) 

•Email received on an email server 

•SAP •Filtering batch rule related event 

• Generic •Combination event of events (ordered or 

random) in a specific time window 

•Submit a TWS Job/Jobstream 

•Answer a TWS prompt 

•Send an email 

•Send a TEC event 

•Write a message in the message log 

•Send an SNMP trap 

5



Event-driven scheduling/notification 

Scenario #1 – Trigger TWS on TWS Event Rule 

If file /abc/file1 is FTP’ed on machine-x and TWS job* is successful, start TWS 

jobstream-y 

If msg “EGS0243 Tr A terminated” issued in file /var/log1 on machine-x, start TWS 

job_tr1 

If event “job_exec_tr1=succesfull” is received in 1 hour send an Informational email 

to joe.smith@company.com otherwise send an Error email to the same user 

Scenario #2 – Integration with external tools 

When any job named “SAP*#USA-*” terminates in error, TWS executes the 

command “/usr/apps/helpDesk –openTicket –text ‘job $jobname abended on SAP 

system $wsname’” to open a service desk ticket 

TWS also sends an event to Tivoli Enterprise Console 

Scenario #3 – TWS autorecovery in case of problems on agent 

When the TWS mailbox utilization on the TWS master machine pass the 90% 

threshold, write a warning message into a log record and run the TWS utility to 

increase the size of the TWS message box 

6




TWS WebUI –Define Triggering Rule 

Rule Builder 

Rule Builder 

Rule Builder 

General Information 

Correlation rule 

Trigger Name 

New Trigger 

Events 

TWS Events 

Job status change 

JS status change 

Workstation status change 

TWS process status change 

O/S Events 

External Events 

Custom Events 

Actions 

TWS Actions 

Notifications 

Send e-mail 

Log message 

Send to TEC 

Description 

A 

A B C 

Actions when rule is matched 

… perform all the following actions. 

A 

B 

C 

When all these events occur in this order… 

1) AB* 

Job 

status 

change 

jsmith@a.. 

Send 

e-mail 

2) WSAG1 

WS 

status 

change 

Server Connection 

MASTERDM 

Actions when rule times out 

Draft 

Valid from: Fri 01/12/2007 

Starts: 

00:00 AM 

Valid to: Indefinitely Ends: 11:59 PM 

Correlate events 

based on 

Workstation Name 

Send e-mail – Action Properties 

To: 

jsmith@acme.com 

Cc: 

Subject: 

7


TWS (dist) 8.4 - TEP integration 

TEP 

Desktop 

Client 

TEP Browser 

Client 

HTTP / IIOP 

HTTP / IIOP 

TEMS 

TEPS 

Job events 

Job submitted, failed, launched, done 

Job suspend until expired 

Job ready, hold, cancelled, restarted 

Job in intro, stuck, wait, wait deferred, 

scheduled status 

Job late 

Job until time expired 

Jobstream events 

Jobstream submitted, abend, stuck, 

started, done 

Jobstream suspend until expired 

Jobstream in ready, hold, cancel 

pending status 

Jobstream late 

Jobstream until expired 

Socket Data 

provider 


Universal 

Agent 

File Data 

provider 

TWS distributed 

Engine 

8



Current versions 

2Q07 

3Q07 

4Q07 

1H08 



V8.3 

V8.4 

V8.4 FP1 



IPv6 support 

LDAP support 


CCMDB Integr. 



Workbench 




for z/OS 




for 

Applications 


Dynamic 


Broker 


Dynamic 


Console 

V8.3 

V8.3 

V1.1 

V8.3 

V8.3 SPEs 

NT password 


TCP/IP 

communication 

support 

V1.2 

Auditing 




V8.3 SPEs 



V8.4 







IPv6 


V8.4 





V8.4 FP1 




V8.4 FP1 


9


NT password encryption in E2E 

TWS z/OS 

Controller 

Events 

Events 

Mainframe centralized encryption 

Time and calendaring 

rules 

Same Windows user to run jobs on all 

Windows machines 

Password encryption on mainframe 


Trackers 

TWS Dist 

Agents 

Local agent encryption 

USRREC 

USRCPU(cpu) 

USRNAM(nam) 

USRPSW(pwd) 

I 

Different Windows users for each local 

machine 

Password encryption on local 

... 

... 

TOPOLOGY 

USERMEM 

... 

10

Monitoring ALL SYST EMS 

CITY1 

CITY3 

CITY2 


TCP/IP connection 

API 

TWS for 

z/OS/ESA 

Info Mgmt 

ISPF 

TCP/IP 

APPC/VTAM 

TWS for z/OS 

Engine 

Sysplex 

TCP/IP 

APPC/VTAM, 

XCF 


Data Store 


Hot standby Engine 

Scheduling 

DataBase 

APPC/VTAM, 

XCF, DASD 

z/OS Domain 

TWS z/OS Controller 

and z/OS Trackers 

Remote ISPF Dialogs 

and PIF 

Tivoli Dynamic 


Console 

TCP/IP 

APPC/VTAM, 

XCF 

TWS z/OS Controller 

and Data Store 

eWas 


Agents 

Job 

Scheduling 

Console 

TCP/IP 

z/OS Domain 

11



Report types 

IBM Tivoli 

Dynamic 

Workload Console 

Master 

(z/OS or Dist) 

JDBC 

Events 

Events 

DB2 LUW 

Job Run History 

Late jobs, missed deadlines, rerun 

indicators 

Job Run Statistics 

success/error rates, 

min/max/average duration, late and 

long duration statistics 

Workstation workload summary 

Workload by workstation, 

aggregated by hour, day, etc. 

Workstation workload runtime 

Job run times and durations on the 

workstation 

Custom SQL reports 


Trackers 


rules 

Data for reporting is extracted from a 

DB2 LUW 


Agents 

12




Report type 

Filter criteria 

13




Report type 


14




Report type 


15



Workstation workload runtimes 

Report type 


16


Customer value 



Measure business compliance and SLAs 

IBM Tivoli 

Dynamic 


JDBC 

DB2 LUW 


Workload schedule forecasting 


Capacity planning adjustements 

Master 

(z/OS or Dist) 

Events 

Events 

Workstation workload runtime 

Monitor and tune workload capacity 


Trackers 


rules 

Custom SQL reports 


Agents 

17



Before Virtual Workstations 

One to one relationship with Workstation and Destination 

If we wanted to exploit the SYSPLEX we still forced everything down one pipe 

We only had ONE alternate Workstation at any one time 

Virtual Workstations 

Allows a Single Workstation to submit to multiple destinations 

Each destination has 

Its own status 

Its own intervals 

Its own values for PS, R1 and R2 

TWS will submit work in sequence around eligible destinations 

This means you can make a workstation follow resource movements either planned or unplanned 

18



Example 

TRK1 

TRK2 

Workstation VIWS is submitting 

jobs, each lasting 40 minutes. 

Destination TRK1 will close at 

21:00 and reopen at 21:30 

VIWS 

TRK4 

TRK3 

19


NOERROR enhancement 

NOERROR LIST (error code entry, … , error code entry) 

General entry: nnnn, Sxxx, Uxxx 

Specific entry: jobname.stepname.procstepname.errorcode 

NOERROR enhanced 

Relational operators in NOERROR statements 

New specific entry: jobname.stepname.procstepname.errorcode.operator 

Easy way to specify a range (ex. twsjob.step01.proc01.0004.GT, 

tws.step01.proc01.0032.LT) 

New FLSH error code 

New extended status 

20


Workload Service Assurance: The solution 

Administration 

Identifies critical workload 

Automation 

Calculates critical path to critical workload and keep it 

dynamically updated 

Automation 

Takes autonomous remedial actions for lagging jobs in 

the critical path (leveraging WLM integration) 

Operation 

Gives a view of how well workload is progressing to 

reach critical end points (risk level of end points), 

to trigger proactive human reaction 

21


Workload Service Assurance: The ultimate scenario 

1. The WEB UI critical jobs dashboard gives at a 

first glance the view of how well the critical 

workload is proceeding 

Dean: the operator 

2. Pies of color-coded high risk, potential risk 

and no risk jobs are provided 

3. Likely Dean explores high risk job first and 

checks whether automatic remedial actions 

are enough to take the workload back on 

course or human intervention is needed 

4. Then goes to potential risk jobs (critical jobs 

that are not at risk, nevertheless they have 

delays or errors in the network of 

predecessors) 

5. Dean fixes the potential problem with a 

potential risk job (i.e. a predecessor was in 

error) and he realizes that all critical jobs are 

now on track! 

22


Workload Service Assurance: Customer value 

Alignment of workload to business priorities 

Service Level management, automate operations and reduce costs 

Forecasting expected completion of jobs, taking in account 

historical metrics and indicators 

Monitoring the most current critical path 

Automating remedial actions as first reaction to risk 

Proactive alerting of users about potentially risk conditions 

Forwarding information to TEP and TBSM 

23




2Q07 

3Q07 

4Q07 

1H08 



V8.3 

V8.4 

V8.4 FP1 



IPv6 support 

LDAP support 


CCMDB Integr. 



Workbench 




for z/OS 




for 

Applications 


Dynamic 


Broker 


Dynamic 


Console 

V8.3 

V8.3 

V1.1 

V8.3 

V8.3 SPEs 

NT password 


TCP/IP 

communication 

support 

V1.2 

Auditing 




V8.3 SPEs 



V8.4 







IPv6 


V8.4 





V8.4 FP1 




V8.4 FP1 


24


SAP Load Balancing 

The TWS definition of an SAP 

job has the new property: 

Server Group 

25


SAP Load Balancing 

The TWS definition of an SAP 

job has the new property: 

Server Group 

The user will choose the desired 

value from the pick list of all the 

server groups. 

26


SAP Load Balancing – Use Case (cont.d) 

The execution of critical jobs 

cannot be affected by system 

maintenance. 

A 

B 

C 

R/3job 

27


SAP Load Balancing – Use Case (cont.d) 

The execution of critical jobs 

cannot be affected by system 

maintenance. 

A 

B 

If critical jobs are assigned to 

server groups, maintenance 

of a member won’t disrupt the 

scheduling activities. 

R/3job 

C 

28


SAP Event Management 

TWS for Applications 8.4 allows including SAP events into 

the TWS scheduling activities in two ways: 

• In the scheduling plan (XBP 2.0 and 3.0 supported): 

a TWS job or job stream is scheduled to start once an SAP 

event is raised; 

• In a pure event driven approach (XBP 3.0 only): 

whenever an SAP event is raised (it might be never or 

many times), a specific action is performed (TWS job 

submitted, e-mail sent, ...). 

29


SAP Event Management 

TDWC will allow defining an event rule. That is a rule that associates 

an action to the occurrence of a predefined set of events. 

30


Features 8.4 FP1 

BDC sessions management 

SAP Event Management (IDOCs) 

SAP Process Chains 

31




2Q07 

3Q07 

4Q07 

1H08 



V8.3 

V8.4 

V8.4 FP1 



IPv6 support 

LDAP support 


CCMDB Integr. 



Workbench 




for z/OS 




for 

Applications 


Dynamic 


Broker 


Dynamic 


Console 

V8.3 

V8.3 

V1.1 

V8.3 

V8.3 SPEs 

NT password 


TCP/IP 

communication 

support 

V1.2 

Auditing 




V8.3 SPEs 



V8.4 







IPv6 


V8.4 





V8.4 FP1 




V8.4 FP1 


32


Tivoli Dynamic Workload Broker 

 


Environment: UNIX, Windows, Linux 

Tivoli Workload Scheduler 

 

Stand-alone product 

Job 

Scheduling 

Console 

Dynamic 


Console 

Java, 

Web Services 

& other APIs 

Add-on product to Tivoli Workload 


Users, applications and application servers 

can also submit workloads directly 

Planning 

Database 

Scheduling 

Engine 

 

Policy-based dispatching 


Matches workload requirements, priorities 

and attributes to IT resource attributes, 

performance and availability 

Policy-based IT resource utilization 

Automatic discovery of configuration 

changes 

TDWB Server 

Resource 

Advisor 


Dispatcher 

Planning 

Database 

 

Advanced automation 

Integrated with Tivoli Provisioning Manager 

to provision resources on demand 

TDWB 

Agent 

TDWB 

Agent 

TDWB 

Agent 

Integration with Tivoli CCMDB to map 

Workload Automation into formal IT 

management processes 

33


Tivoli Dynamic Workload Broker in the TWS Family 

TDWB is a Standard Agent for 

TWS and TWS for z/OS 

TDWB 1.1 supports AIX, 

LINUX and Win platforms. 

TDWB 1.2 supports Solaris 

and HP-UX 

TDWB 1.2 supports Oracle 

JSC 

TDWB is integrated with TWS 

8.4-8.3-8.2.1-8.2 distributed and 

with TWS for z/OS 8.3-8.2 

TWS 

MDM 

TWS Z/OS 

Controller 


DM 

TDWB 

Server 


Agent 


SA 

TWS Z/OS 

Trackers 


FTA 


FTA 

TDWB 

Agent 

TDWB 

Agent 

34




2Q07 

3Q07 

4Q07 

1H08 



V8.3 

V8.4 

V8.4 FP1 



IPv6 support 

LDAP support 


CCMDB Integr. 



Workbench 




for z/OS 




for 

Applications 


Dynamic 


Broker 


Dynamic 


Console 

V8.3 

V8.3 

V1.1 

V8.3 

V8.3 SPEs 

NT password 


TCP/IP 

communication 

support 

V1.2 

Auditing 




V8.3 SPEs 



V8.4 







IPv6 


V8.4 





V8.4 FP1 




V8.4 FP1 


35


Tivoli Dynamic Workload Console at a Glance 

Web portal application 

A component of TWS z/OS and TWS (dist) 

Included and fully supported at no extra charge 

IBM Tivoli Dynamic 


Establishes a single, easy-to-use, Web-based 

virtualized control point for the entire 

enterprise workload automation network 

Client node 

(Browser) 

Client node 

(Browser) 

Client node 

(Browser) 

Low Total Cost of Ownership 

Portal 

Node 

(ISC) 

No need to deploy software on any monitoring 

machine 

Leverage Integrated Solution Console 

technology 


TWS for 

z/OS 


Workloa 

d Borker 

Improved productivity and efficiency 

36


Tivoli Dynamic Workload Console architecture 

ISC Runtime 

Portal 

node 


Views 

TWS Model 

Objects 


Portlets 

HTTP/HTTPS 

Application services 

Access Plan Interface 

Connector client 

z/OS connector 

client 

TDWC Web Console Client 

RMI/IIOP over SSL 

RMI/IIOP over SSL 

z/OS Server 

z/OS Engine 

TWS MDM 

Bobca 

t 

J2EE 

Cconnector 

z/OS Connector 

Bobca 

t 

J2EE z/OS 

Cconnector 

TCP/IP 

TCP/IP 

Server 

APPC 

Server 

E2E 

Server 

Planner 

Choreographer 

Job Executor 

Event 

Manager 

37


Tivoli Dynamic Workload Console – Task Oriented 

A “task” hides the details of query filters and configuration data 

definition 

The “task” concept promotes (but does not force) an effective 

separation of roles 

The administrator is in charge to prepare and share tasks to others users 

The task owner can edit his/her tasks 

“Tasks” prevent the operators from dealing with the complexity of 

filtering definition and configuration data management 

“Tasks” allow the operator to focus just on the essential steps to 

monitor and control the execution of jobs, or other operations 

38


Tivoli Dynamic Workload Console – Drill Down 

1 

A “multi tabbed pane” approach to 

easily navigate back and forward the 

outputs coming from the drill down 

activity 

1 

2 

3 

Starting from a job list 

click on the workstation 

hyperlink related to a 

specific job to view the 

workstation properties 

Click on the “limit” 

property hyperlink to edit 

the property value 

Click on the browse job 

tab to go back to the 

starting job list panel 

2 

Previous panels 

can be redisplayed 

clicking on the 

corresponding tab 

3 

Hyperlinks offering 

different ways for a 

user to find 

information or drill 

down to more 

detailed data 

39 

39


Summary 

We have doubled our investment in the scheduling market 

Our development team is tied directly to solving business pains 

for our customers 

Tivoli Workload Scheduling is tied directly to IBM’s on demand 

strategy and is a foundational component for Tivoli’s IT process 

automation solution focus 

Nobody gets left behind moving to new version and products 

We are hitting all development targets in 2007, and have a 

committed roadmap through 2008-2009 

Our End Game is Well Defined, We are 

Aligned to Our Customer Needs, and We 

are Investing to Lead the Market 

40

IBM Tivoli Workload Scheduler Automation - Nordic TWS conference

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?