IBM Software Group

Tivoli Workload Scheduler 8.4
Event-Driven Workload Automation (EDWA)

July 2008

© 2008 IBM Corporation

IBM Software Group | Tivoli software

Event-Driven Workload Automation objectives
 Extend the current TWS capabilities to orchestrate planned calendar-based workload to the unplanned world, by allowing user to define event-driven rules for batch jobs scheduling
 Trigger the execution of TWS batch jobs and job streams based on the reception or combination of real-time “events”

 Provide real-time user notification feature
 Notify users when anomalous conditions happens in the TWS scheduling infrastructure or in the TWS batch scheduling activity
Portal node

 Extend 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
Distributed System  Allow to automate recovery actions for TWS infrastructure or scheduling problems

2

© 2008 IBM Corporation

IBM Software Group | Tivoli software

Event-Driven Workload Automation basic concepts
An Event-Driven Workload Automation Rule is a composition of:
 Events
 E.g. “file x is created”, “message xyz issued in a log-file“, “Job x abended with RC=12” , “TWS agent unlinked”, “An email is received”, “Event xyz issued on SAP systemx ” Event Event Event

 Events Correlation Conditions
 E.g. Filter, Events Sequence, Events Set

 Actions
 E.g. “Submit a TWS jobStream” “Send an e-mail”, “Send An event to T/EC”, Write a message in

the

message log

Correlation rule

Sample scenarios
 Submit a Job Stream when a defined set of events is received
 When file /abc/file1 is FTP’ed on machine-x and at least one of the TWS job* running on the Workstation machine-x is in successful status, then start the TWS jobstream-y
Action Action

 Scenario #2 – Trigger a credit transfer transaction and notify result
 If msg “EGS0243 Transaction A terminated” is issued in logfile /var/log1 on machine-x, start TWS job_exec_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

3

© 2008 IBM Corporation

IBM Software Group | Tivoli software

New concepts: the Event Rule
 The main concept of the event-driven scheduling/notification architecture is the Event Rule  The Event Rule object is a composition of:
 Events
e.g. “The file x on machine y is created”

Event

Event

Event

 Events Correlation Conditions
e.g. “event_x and event_y are received in a specific or random order”,

 Actions
e.g “submit job_x on machine_y”, “send an email to joe_smith@abc.com”,

Correlation rule

 The Event Rule can be associated to a:
 Validity time interval
 Status: draft or complete Action Action

4

© 2008 IBM Corporation

IBM Software Group | Tivoli software

Event-Rules: the Life Cycle big picture
Create

Rule Editor

Event Rule (not built yet)
Events, Correlation Rule, Actions

Deploy (Manual/ Scheduled)

Rules Builder

Builds Event Rule (built) Ah-Hoc Job submission Perform Actions

Deploys Events

Event-Rules Engine Listen & Correlate

Jobs status notification  send Email  send T/EC event

EDWA life cycle

Monitors

 Modeling  Activation & Deploy

 Create, Modify, Delete, List  Starts the monitoring activity  Activates the events receiving  Activates the correlation and actions triggering

 Monitoring & Management

 Query and browse event rule instances  Drill down on actions executed for a specific event rule

5

© 2008 IBM Corporation

4: Main flows Calendar-based scheduling Scheduling Database Extract Job Stream Calendar Job Job Job  Cal rules  Jobs Generate Production Plan Job Stream Instance Time Execute Execute Planner Engine Job Event Rule  Events  Corr.IBM Software Group | Tivoli software TWS 8. Rule  TWS Actions Generate Event Rules Ah-Hoc submission Event-Rules Jobs status notification  send Email  send TEC event Rules Builder Event Rule Instance Listen & Correlate Engine Events Monitors Event-Driven workload 6 © 2008 IBM Corporation .

IBM Software Group | Tivoli software User Interfaces Modeling  Can be done using the Tivoli Dynamic Workload Console (aka TWS Web UI) and the TWS Command Line Interface (composer)  Documented APIs are provided Activation & Deploy  It can be automated using the option manager (optman)  A new customization of the planman CLI is provided for manual or scheduled activation Monitoring & Management  Can be done both using the Tivoli Dynamic Workload Console (aka TWS WebUI) and the TWS Command Line Interface (aka TWS composer CLI)  Documented APIs are provided 7 © 2008 IBM Corporation .

4 for Applications) Action Action  8 © 2008 IBM Corporation . file modification completed. May also be an event generated via a Command Line Interface that will be provided by TWS and that can be used by customer to generate custom events SAP batch related events (using TWS 8.IBM Software Group | Tivoli software Event Rule modeling The supported Events are:        File created. may be an application log file) TWS specific monitors Job/jobstream status changed and return code condition Status of TWS agents (linked/unlinked. log message written Event A message is issued on a log-file (e.g. file deleted. started/stopped) Application server status changed Prompt status changed Event Event Correlation rule  Generic event.

IBM Software Group | Tivoli software Event Rule modeling The supported Correlation Conditions are:   Event filter Event Rule is activated when a single event matches a user specified filtering condition based on the Event properties Event Event Event   Events Sequence Event Rule is activated when the ordered sequence of events is detected within a specified time window Correlation rule   Events Collection Event Rule is activated when the un-ordered sequence of events is detected within a specified time window   Event timeout Event Rule is activated when one or more events arrive but the complete sequence does not arrive within the specified time window Action Action 9 © 2008 IBM Corporation .

ITM or NetCool Write a message in the message log Action Action Correlation rule 10 © 2008 IBM Corporation .IBM Software Group | Tivoli software Event Rule modeling The supported Actions are:  Submit a TWS Job. submit a TWS Job Stream. submit ad-hoc TWS Job Event Event Event     Answer a TWS Prompt Send an e-mail Send an EIF event to T/EC.

unlock  modify  new  rename eventRule definition is completely written in XML unlike other TWS objects written in Scheduling Language 11 © 2008 IBM Corporation .print  lock .  For example: -composer new eventRule  Composer is able to manage eventRule objects with commands:  create – extract  delete  display Local encoding is used by default  encoding For XML list .IBM Software Group | Tivoli software Composer new features  Is possible to specify in “composer new” command which kind of object you want to add.

 where: 12 © 2008 IBM Corporation . This is an example of the output running “planman deploy”.IBM Software Group | Tivoli software Planman command line: event rule activation  Is possible to perform the build and deployment of the event rules using directly the planman CLI:    planman deploy [-scratch] -scratch option builds again all rules defined in the database.

13 © 2008 IBM Corporation .IBM Software Group | Tivoli software Planman command line : event rule activation  planman command line activates all valid event rules and deploys the monitoring configuration to the specific agents.  The event rules that are not in draft status and are in the valid time interval are periodically (the frequency interval can be customized) checked for changes by TWS that automatically builds or refreshes the internal correlation and monitoring information for those rules. To get this result a new optman keyword has been created: deploymentFrequency / df = 5 Note: The default value is 5 minutes.

IBM Software Group | Tivoli software Conman new features (1/2)  The enhancements are provided by new commands that you can use to:  Download the latest monitoring configuration for the event monitoring engine on the workstation.wait] [.noask] stopmon [domain!]workstation [.noask] 14 © 2008 IBM Corporation . using deployconf command (permission to “start” action on the specified workstation is required in the security file):  deployconf [domain!]workstation  Manage the monitoring process using startmon and stopmon commands (permissions to “start” and “stop” actions on the specified workstation are required in the security file):   startmon [domain!]workstation [.

IBM Software Group | Tivoli software Conman new features (2/2)  Start and stop the WebSphere Application Server process using startappserver and stopappserver commands (permissions to “start” and “stop” actions on the specified workstation are required in the security file):  startappserver [domain!]workstation [.wait]  stopappserver [domain!]workstation [. stopeventprocessor and switcheventprocessor commands (permissions to “start” and “stop” actions on the specified workstation are required in the security file):  startevtproc [domain!]workstation  stopevtproc [domain!]workstation  switchevtproc [domain!]workstation 15 © 2008 IBM Corporation .wait]  Manage the new event processing server used in event-driven workload automation using starteventprocessor.

® IBM Software Group EDWA Architectural overview © 2008 IBM Corporation .

TBSM.Reference Architecture WEB-UI http(s) ISC TWS WEB-UI Rules Modeling Portlets Rules Monitoring Portlets CLI C:\> http(s)  Monitoring agent  Responsible to monitor for events condition on TWS agents  Embeds NetCool Monitoring technology  EIF based technology  Rules Correlation Server  Responsible to receive/correlate events and to execute actions  Integrates with ITM. it embeds a very advanced correlation engine component  Web-UI  Provides portlets for event rules modeling.IBM Software Group | Tivoli software Event-driven scheduling . TEP. TSM. monitoring and mgmt  Use SOAP/HTTP and XML technology © 2008 IBM Corporation eWAS TWS Master Planner Model Connector RMI Stub Java Based UI DB Rules Correlation Server JDBC JSC RMI Plan Connector Scheduling Model TWS Engine Production Plan JDBC TWS DM eWAS plan EAR TWS Backup Master eWAS Planner Model Connector Plan Connector TWS Engine Production Plan Triggering Engine TWS FTA TWS FTA Monitoring TWS Engine Production TWS Engine Plan Production Plan Agent TWS FTA Monitoring Agent TWS Engine Production Plan TWS Engine Production Plan 17 .0 concepts. NetView  J2EE application. uses Ajax/Dojo technology  Command line Interface  Provides CLI for event rules modeling. monitoring and mgmt  Portal application on Integrated Solution Console technology  Implements WEB 2. T/EC.

IBM Software Group | Tivoli software Event-driven scheduling-Reference Architecture WEB-UI http(s) 1. TWS Engine Production Plan 4 Triggering Engine 7. TWS Engine Production Plan TWS FTA TWS FTA Monitoring TWS Engine Production TWS Engine Plan Production Plan Agent TWS FTA Monitoring Agent TWS Engine Production Plan 8. eWAS TWS Master Planner 2 Rules Correlation Server Model Connector 7 7 Plan Connector 1 RMI Stub Java Based UI DB JDBC JSC RMI Scheduling Model 4. ISC TWS WEB-UI Rules Monitoring Portlets Rules Modeling Portlets User queries. Production Plan JDBC 3 TWS Engine TWS DM eWAS plan EAR TWS Backup Master eWAS Planner Model Connector Plan Connector 6. 5 6 5. 18 . Correlation and monitoring rules are updated. Events-Correlation Server starts its events listening and processing activity Monitoring configurations are downloaded and activated to the TWS agents The monitoring agent starts to monitor and to send events Rules Correlation Server receives the events and check if they match any defined rule If an event rule is matched. to query the status of TWS event-rule instances and actions © 2008 IBM Corporation 2. creates or modifies eventrules in the TWS database. the correlation server calls an actions helper to execute the actions The action helper creates a event-rule instance and logs the action result into the database User uses the monitoring interface. CLI C:\> http(s) 8 1 3.

actions and jobs submission based on events. NetCool. 19 © 2008 IBM Corporation .  Base monitoring and events correlation functionalities are embedded into the product  Is simple and lightweight  Low footprint  Easy to install and configure  Easy to use  Is Extensible  EDWA allow to plug-in new event types. new event monitors and actions without requiring changes to TWS code  Support of generic. user defined and generated events  Integrated with Tivoli availability mgmt products  Able to integrate and leverage advanced monitoring capabilities from existing T/EC.IBM Software Group | Tivoli software TWS 8. ITM and TEP environments  Is Scalable  EDWA Is able to support a big number of events.4 Event-Driven Architecture Benefits  Do not prerequisite external Monitoring/Event products  The solution is self-contained in TWS.

it contains all the plugins that implement events and actions for event management.  The steps to implement new events or actions are the following:  create a new event/action plugin  put it inside the directory “eventPlugIn”  restart Websphere Application Server  Every plugin is composed by three main components:  TWSPlugIn.xml = a file containing plugin’s configuration  One or more java class file containing the implementation of the plugin 20 © 2008 IBM Corporation .properties = a file containing main plugin’s informations  TWSPluginConfiguration.IBM Software Group | Tivoli software Pluggable architecture  Under TWS installation directory. there is the folder “eventPlugIn”.

 Examples regarding how to interface with TWS WebServices  (JobService.IBM Software Group | Tivoli software SDK  We developed a Workbench eclipse based that will help customers to create new plugins for event management and to use APIs.label=1TW10WS01  This workbench will allow to:  Create Event plugins  Create Action plugins  Create applications that will use TWS public APIs  This workbench will contain:  Sample event plugins  Sample action plugins  Examples regarding how to make connections to TWS and how to work with objects in the database and in the plan using TWS public APIs. http://www-01.com/software/brandcatalog/portal/opal/details?catalog.ibm. JobStreamService and SchedulingFactory) 21 © 2008 IBM Corporation .

® IBM Software Group EDWA Using the TDWC Web Console Creating or editing an Event Rule © 2008 IBM Corporation .

Workload Definition .IBM Software Group | Tivoli software Event Rule Editor: Overview The Event Rule Editor is the tool you use to create and edit Event Rules You open the Rule Editor directly from the TDWC portfolio: .New Event Rule Or you open it by selecting an Event Rule from a query table and click “Edit” Engine on which the Rule is created/edited Draft/Complete status Validity interval Event correlation types Timeout conditions Common attributes correlation Events Timeout actions Actions 23 © 2008 IBM Corporation .Event Management .

the Editor opens in its entirety. As soon as you select an engine. the Editor connects to the engine and loads the list of event and action plug-ins available on it. whether existing or a new one. 24 Select an Engine Connection and click Go © 2008 IBM Corporation . The Rule will be kept locked all the time. You can then save the progresses on the Rule multiple times while you are working on it. The Event Rule.IBM Software Group | Tivoli software Event Rule Editor: Overview The Event Rule Editor connects to a specific engine to store or retrieve the Event Rule. is locked on the TWS database and is kept locked until the Editor is “Closed”. When the connection is successful.

© 2008 IBM Corporation . A “Draft” Rule will not be activated or deployed. 25 Dates and times expressed here will be referred to the TWS engine Time zone unless otherwise specified here The Rule will be valid every day between the specified dates. but only within the hours specified here. The Rule will be valid between the specified dates. An empty value for one or both extremes means midnight.IBM Software Group | Tivoli software Event Rule Editor: General Information This section contains general information about the Event Rule and its validity period. In this case refer to the manuals for what are the effects on the first and last validity day. An empty value for one or both extremes means indefinite. A “Non Draft”. A Daily end prior to Daily start is a valid range and represents a range that crosses midnight. so it will not generate events and will not run actions. The changes you make to a Rule (including changing the “Draft” flag) will be effective only after the next deploying of the Rule. or “Complete” Rule will be activated and deployed at next “Planman –deploy” (either scheduled or manual) and will be active within its Validity Period.

 Ordered Sequence of events Click here to change Complete Information available clicking here Remove an Event by clicking here To expand/collapse a section click the title bar 26 © 2008 IBM Corporation .  Unordered Set of events.IBM Software Group | Tivoli software Event Rule Editor: Events Add an Event by clicking here Select the type of correlation:  Single event.

IBM Software Group | Tivoli software Event Rule Editor: Timeout and Correlation Enable Timeout and specify a value here Select properties common to all events here. They must all match for the rule to be satisfied 27 © 2008 IBM Corporation .

The specify its properties assigned to each Event values are in OR automatically. not allowed Wildcards are allowed for this Filtering on some properties may be mandatory. values not be allowed. change it here Wildcards may or Multiple. You can add optional properties from the drop-down list. 28 property Remove Optional properties clicking here A non-empty value is required Specify a comparison operator Add optional properties from this list © 2008 IBM Corporation . You can condition. semi-colon-separated. These are in AND condition.IBM Software Group | Tivoli software Event Rule Editor: Event Properties Event Properties specify a filtering condition for events. A condition on a property is specified with a The Properties are displayed below comparison operator and one or Select an Event by clicking it to A name is generated and more values. A property can be added multiple times.

because they are actually parameters for the Action Some properties are mandatory. etc… A variable chooser helps inserting variables. and then one of its Properties. A Variable pointing to the selected property will be inserted at the end of the current input field Use Machine-readable format to use variables as input to scripts. Variables are used to take values from Event properties to use into Action properties You can use Variables for any Action Property 29 © 2008 IBM Corporation . programs. A property can be specified only once.IBM Software Group | Tivoli software Event Rule Editor: Actions and Variables Actions Properties do not specify a comparison operator. You can add optional properties from the drop-down list. Select an Event from the list of events currently added to the rule.

Press the Lookup button here 30 © 2008 IBM Corporation . a Lookup facility helps selecting an existing object in the TWS database. Lookup is available for Jobs. Job Streams and Workstations. Specify search criteria and press Search. Click on an item to select it.IBM Software Group | Tivoli software Event Rule Editor: Lookup of TWS objects When specifying properties related to TWS objects. The list of results appears below. Looking-up an object will fill-in all the object properties in the Action. not only the property next to which the button appears. or change the criteria and search again.

switch to the Timeout Actions tab to work with these 31 © 2008 IBM Corporation .IBM Software Group | Tivoli software Event Rule Editor: Timeout Actions Switch by clicking here If you enabled Timeout.

Click the box to resolve them in the Properties section Errors are detected while you are typing and are shown below the corresponding field 32 © 2008 IBM Corporation .IBM Software Group | Tivoli software Event Rule Editor: User Input Validation An Event or Action box turns RED if there are outstanding errors with it.

IBM Software Group | Tivoli software Event Rule Editor: User Input Validation Errors related to invalid ranges are outlined with a box around the corresponding fields 33 © 2008 IBM Corporation .

IBM Software Group | Tivoli software Event Rule lifecycle management  Event Rules    Associate Event filters with response and timeout Actions Can be listed using a query task On the resulting table. you can drill-down to see a rule’s properties in read-only. and perform administrative actions on it 34 © 2008 IBM Corporation .

® IBM Software Group Event Monitoring using the TDWC Web Console © 2008 IBM Corporation .

IBM Software Group | Tivoli software Event Rule monitoring  Event Rule Instances   Represent event rules that have been matched An Event Rule Instance includes information like event rule name. whether the rule was satisfied or timed-out and other An Event-Rule Instance is created each time the event conditions contained in the an event-rule are matched or you have defined timeout actions and the rule times-out  36 © 2008 IBM Corporation . date/time when it was matched and the list of actions that were triggered.

IBM Software Group | Tivoli software Event Rule monitoring  Triggered Actions  Represent actions that have been run as result of an event rule being matched  A triggered action instance includes information like action type. action name. date/time when it was executed and if it was executed successfully or not  A triggered action instance is created for each action that is executed when an event rule is matched 37 © 2008 IBM Corporation .

specific for actions of the “Log Message” type  This view shows each message that was logged as result of a Log Message action with a more event console-like look&feel  You will be able to see for each Operator Message a corresponding record also in the Triggered Actions view 38 © 2008 IBM Corporation .IBM Software Group | Tivoli software Event Rule monitoring  Operator Messages  An Operator Message is a particular type of action instance that includes a textual field containing the message text  Operator Messages represent another view on the Triggered Actions list.

IBM Software Group | Tivoli software Event Rule monitoring  Workstations      The “workstations in plan” view has been enhanced to show event monitoring information You can see whether a workstation is the Event Processor Server You can see whether the SSM Monitoring Agent is running You can see whether the workstation has received the latest monitoring configuration You can perform administrative actions on the selected workstation(s) 39 © 2008 IBM Corporation .

action runs and logged messages are kept in the TWS database default = 10  logCleanupFrequency (lc) specifies how often to look for history data older than logHistory days. which must be deleted default = 5 (minutes)  Options used by TECEventForwarder action plugin:  TECServerName (th) hostname or IP address of the TEC server to which events are forwarded default = localhost  TECServerPort (tp) port of the TEC server to which events are forwarded default = 5529 40 © 2008 IBM Corporation .IBM Software Group | Tivoli software Global Options  General options for EDWA:  enEventDrivenWorkloadAutomation (ed) enables or disables the event driven workload automation feature default = YES (EDWA is enabled)  deploymentFrequency (df) specifies how often event rule updates are applied on the event processor and deployed to the TWS agents default = 5 (minutes)  enEventProcessorHttpsProtocol (eh) enables or disables use of the HTTPS protocol to connect to the event processor server default = YES (HTTPS is enabled)  eventProcessorEIFPort (ee) port of the Tivoli Event Integration Facility (EIF) for communication with the event processor server default = 31131  logHistory (lh) number of days for which history of triggered rule instances.

IBM Software Group | Tivoli software Global Options  Options used by MailSender action plugin:  smtpServerName (sn) hostname or IP address of the SMTP server through which outgoing e-mails are delivered default = localhost  smtpServerPort (sp) port of the SMTP server through which outgoing e-mails are delivered default = 25  smtpUseSSL (us) enables or disables use of Secure Sockets Layer (SSL) to secure the connection to the SMTP server default = NO (SSL is disabled)  smtpUseTLS (tl) enables or disables use of Transport Layer Security (TLS) to secure the connection to the SMTP server default = NO (TLS is disabled)  smtpUseAuthentication (ua) enables or disables user/password authentication against the SMTP server default = NO (authentication is disabled)  smtpUserName (un) name of the user to be used to authenticate with the SMTP server (if authetication is enabled) default = name of the tws_user  smtpUserPassword (up) password of the user to be used to authenticate with the SMTP server (if authetication is enabled) default = not set  mailSenderName (ms) name of the mail sender to be used for e-mails sent by TWS default = TWS 41 © 2008 IBM Corporation .

as a result of a “conman switcheventprocessor” command)  processors only the master domain manager and the backup master can be event default is YES for master DM and backup master DM.IBM Software Group | Tivoli software Local Options  Options added to the localopts file for EDWA: AUTOSTART MONMAN    Tells whether or not the monman process for monitoring of generated events should be automatically started at the startup of this CPU  the monman process can be also controlled manually by using the “conman startmon” and “conman stopmon” commands  default is YES CAN BE EVENT PROCESSOR    Tells whether or not this CPU can take responsibility of being an event processor (e. NO for other CPUs  42 © 2008 IBM Corporation .g.

® IBM Software Group TWS & ITM Integration Overview © 2008 IBM Corporation .

Agents monitor systems and applications passing the collected data to the monitoring server. and analysis of it (it needs an RDBMS installed on the same physical system).1 provides also a customizable agent called Universal Agent (UA).IBM Software Group | Tivoli software ITM Architecture  The TEMS (Enterprise Monitoring Server) is the key component on which all other architecture components depend directly and collects and control data received from agents.  The TEPS (Enterprise Portal Server) is the repository for all monitoring data which allows for retrieval. manipulation.  ITM v6.  The Tivoli Enterprise Monitoring Agents are data collectors. RDBMS Tivoli Enterprise Monitoring Server (Hub) Tivoli Enterprise Portal Server  The TEPC (Tivoli Enterprise Portal Client) is a Javabased user interface that connects to the TEPS to view all monitoring data collections. The UA is a full-featured intelligent remote agent with dynamic application capabilities that allows monitoring only the data you are interested in. 44 Tivoli Enterprise Portal Client (Browser/Desktop) Systems being monitored and data collected using Tivoli Enterprise Monitoring Agents © 2008 IBM Corporation .  The TEPS keeps a persistent connection to the Hub Tivoli Enterprise Monitoring Server and can be considered a logical gateway between it and the TEPC.

which use data definitions files (metafiles) to describe the source and structure of the data supplied by the data providers.4 the TWS provides an integration with ITM 6.  The Tivoli Universal Agent obtains its data from interfaces called data providers.  There are different data providers but TWS uses two of them: • File Data Provider to have a logical view inside TEP to monitor the jobs/jobstreams status changes • Script Data Provider to have a logical views inside TEP to monitor the TWS resources and processes 45 © 2008 IBM Corporation .IBM Software Group | Tivoli software TWS-ITM Integration via Universal Agent Starting from 8.  The Tivoli Universal Agent is a generic agent of ITM and can be configured to monitor any data you collect. The obtained data can be seen via TEP with specific monitoring situations.1 FP05 and highest using data providers that represent the interfaces of the ITM Universal Agent.

Launch the ITMConfig script to configure the UA to monitor TWS Launch the ITMCreateSituations script to configure the TEP to create and display TWS situations  The following TWS resources and processes can be monitored via TEP:            netman batchman jobman Mailman Appserver Host availability Page out Swap space availability TWS disk free TWS Message files TWS space used by:  stdlist  schedlog 46 © 2008 IBM Corporation .IBM Software Group | Tivoli software Script Data Provider Integration  For each FTA you want to monitor an ITM Universal Agent should be installed on it  Configuration steps required: 1. 2.

47 © 2008 IBM Corporation .4 with IBM Tivoli Monitoring ( and in general with third party monitoring applications) in order to receive EIF events from them. with the EDWA is possible to integrate Tivoli Workload Scheduler 8. This significantly extends the scenario of triggering the workload submission.IBM Software Group | Tivoli software Extend TWS integrability with third party products: ITM  In addition to the Universal Agent integration.

IBM Software Group | Tivoli software Backup 48 48 © 2008 IBM Corporation .

and as soon as one of the specified jobs ends in error. in the time-window 18:00-22:00 EST  You save the Event Rule that is automatically activated by the TWS  TWS starts monitoring all the specified jobs.  The Event Rule is valid from Dec 1st to Dec 31th.com. 49 © 2008 IBM Corporation .IBM Software Group | Tivoli software Possible customer scenarios  Scenario #1 – Simple notification  You define the following Event Rule  When jobs ABC*#* terminates in error. then send an e-mail to the john.smith@mycorp. In the subject and the body of the e-mail the text includes the key of the job ended in error. it send the notification e-mail  You receive the e-mail and check the status of the jobs.

com  You save the Event Rule that is automatically activated by the TWS  TWS starts monitoring the status of the Workstation CPU1  As soon as the Workstation status is unlinked and the TWS starts the 10 minutes timeout  If the event “CPU1 linked” is not received in 10 minutes. queries the actions/rules that was triggered in the last 10 minutes and from there navigates to the CPU1 instance where can perform a first problem analysis 50 © 2008 IBM Corporation .jones@company. send an Error email to ricky.IBM Software Group | Tivoli software Possible customer scenarios  Scenario #2 – Trigger TWS Agents status  You define the following Event Rule  When any the Workstation CPU1 is unlinked and the Workstation CPU1 is not linked back within 10 minutes. goes to the TWS Event Rule management interface. TWS sends the Error email  Ricky Jones receives the Error email.

it submits the jobstream-y  You check if the Event Rule was triggered in the last two hours and see its status 51 © 2008 IBM Corporation . in the time-window 18:00-22:00 EST  You save the Event Rule that is automatically activated by the TWS  TWS starts monitoring file /abc/file1 on machine_1. then start the TWS jobstream-y  The Event Rule is valid from Dec 1st to Dec 31th. and as soon as the file is created and it is not anymore in use.IBM Software Group | Tivoli software Possible customer scenarios  Scenario #3 – Submit a Job Stream when FTP completed  You define the following Event Rule  When a file is created in directory /abc on machine_1 and the same file is no more modified.

IBM Software Group | Tivoli software Possible customer scenarios  Scenario #4 – Trigger a shopping online transaction  You define the following Event Rule  When the custom events “shopping request” is received and the custom event “shopping transaction permission” is not received in 1 minute. otherwise it logs an Information message with the transaction status and submits the TWS Ad Hoc job_order_dealt_with 52 © 2008 IBM Corporation . TWS should send an Error email to the user@company.com otherwise an Information message should be logged and the TWS Ad Hoc job_order_dealt_with should be submitted  You save the Event Rule that is automatically activated by the TWS  The Event Rule is automatically activated  Once the event “shopping request” is received. TWS sends an Error email to the user. TWS starts the 1 minute timeout  If the event “shopping transaction permission” is not received in 1 minute.

com alerting for a Job in late  You save the Event Rule in draft status. TWS starts the 5 minutes timeout  If the event “job-y successful or abend” is not received in 5 minutes.IBM Software Group | Tivoli software Possible customer scenarios  Scenario #5 – Trigger long duration Jobs based on timeout  You define the following Event Rule  When the event “job-x=exec” and the event “job-x=succ/abend” are received in 5 minutes TWS should reply Yes to prompt-1 and starts the jobstream-z otherwise it should send an Informational email to the tws-oper@company. TWS sends the Informational email otherwise it replies Yes to prompt-1 and submits the jobstream-z 53 © 2008 IBM Corporation . After few days the user reedits the rule. changes the email recipient and save it as not-draft  The Event Rule is automatically activated  Once the job-x status is exec.

 As soon as a couple events for the same flight are received. 54 © 2008 IBM Corporation . a job is run sending an event “seat available” for each person that has not checked-in  Each time a person is added to the queue for the flight a event “person in queue” is generated  The following Event Rule is defined  When the event “seat available” and the event “person in queue” are received for the same flight than submit a job to assign the seat to the person.  The rule is saved and automatically activated.IBM Software Group | Tivoli software Possible customer scenarios  Scenario #6 – Airport queue for a flight  The following custom events are generated  30 minutes before a flight departure. the job to assign the seat is submitted.

 You can reactivate the Event Rule in a later time. 55 © 2008 IBM Corporation . TWS executes the specified help desk command and sends an event to T/EC  After some period. you set the above Event Rule in draft status.IBM Software Group | Tivoli software Possible customer scenarios  Scenario #7 – Integration with SAP (and external tools)  You define the following Event Rule  When an event called ID3965 is generated on SAP server Billing.  As soon as the specified event is triggered on SAP. The Event Rule is automatically deactivated by TWS. TWS must execute the command “/usr/apps/helpDesk –openTicket –text „Processing error $parameter on SAP system $wsname’” to open a service desk ticket  TWS should also send an event to Tivoli Enterprise Console  You save the Event Rule that is automatically activated by the TWS  TWS starts monitoring the status of SAP events activated on the Billing system.

943.0398 .7488082/39 398. .10//.19 47 425090 #:0-0 ./9/.039#:0. -0900390850..7074:5%.10/070 %0#:0-0.9438  437.0/:0/47 2.943.943 .039#:0/9470307../9!074/ %0.#:0 3.0 94.3/..70 900110....9./0.9843901789.89.:/3 .:014743047-49 097020820.900.8147.908. .90/.798.19 1.48419.70 .30.908 -:9 4393904:78850..9.31472./7.9..3//0540/ .382/39 .3:.043.9.07/.3/-0 .3/98 ../95074/  7.3 /054  09078..9..7.439.3:.31472.80 7010794902./-0900390 850.3390 7..38 0307.1907 90309/05434190 #:0  .30 9.-4:9 90.$419.10//.  -00110.:014743047-49 097020820.908 30259.9309 !.10/ 070 30259.3/92080570880/070 -07010770/9490%$0330 %20430:3088490780 850..89 .03/574794.32.9.3/7057080398.943 %880.19 #:0349-0 .90/47/0540/ 84 93490307.09398 '..383/01390  47547.3084:2.. %0#:0-0..3/3497:3.

99095041.0398  7/070/$06:03.7074:5%.3.3070 $00..3/.039#:0/947.70 .30 42509031472.039  &347/070/$09410.3070 #024.3070 %405..3.0398 //.943 $300..0410.-0.4770.07094...943 .039 -.0.$419.039-..0398 ..48419.

943 .4..580. 80.943.90990-.7   47547..

9574507908 ..039#:0/947%204:9.147 907:094-08.9.1.48419.9810/   47547.943 .4224394.3/850..943 3.:0070 $00.-0%204:9.3/4770.$419.2.7074:5%.0398 070 %02:89.70 .0.

0/-04 4507.40/ /..47 :950 802 .574507908 17429889  47547.:08.78434507..039!74507908 850.43/943147 0.1.43/943 .039#:0/947.7074:5%..//45943.947.:08 349-0...9.//0/2:950 9208 %080.309070 /.3 .703 .3/43047 $00.43/94343. 5745079082.70.70/85. 574507908174290 /745 /4389 5745079.703 # .3/ 2470.425.2080307.039 .3070 2.3 .1. 57450798 850.947 4:.-0 574507908.3994 3.:942.039-..3/..0398 .7843 %0!74507908...3.0 5943.443 805.$419.40/14798 5745079 9073438420 #024. .48419.7.90/ .:08 %0 850.9.43/943  343 0259.943 ..039!74507908 . 4:..:08706:70/ $50.198574507908 ..3-0 .947 //45943..425...7/8.70 ..8830/940.10/9.90/.7/82.40/ 349.19073 .

.3..-08.9438!74507908 /4349850..70 .7598  5747..039 57450790894:80394.0.7.-01472.7074:5%.3/'.48419.7.943 $420574507908 .425.99003/4190.3/.7..994 :80.3.947 -0.//0/9490 7:0 .1.30 70.9438.947 4: .70.44807058380793.:77039..3. .7. .943574507908 4:.943 .28 09.943!745079   47547..7.3-0 850..7.9:..90/5745079-0380790/ .0398.9.70:80/949.3:80'.:7703935:9 10/ &80.-08 .$419.10/4343.7.039#:0/947.20907814790 .:081742.702..0391742908941 0. 5.835:9948.-0543939490 800./.-08 '.-0. 574507908174290 /745 /4389 5745079.-08.7.0 $00.7843 4507.3/9034304198 !74507908 '.-08147.//45943.:80 90.

99 47. 904-0..98 .90/ 94%$4-0.9 058800. 44:51..30 90.7.039#:0/94744:541%$4-0.-0 1474-8 4- $970.3/57088 $0.43.28...48419.180.78 $50.7074:5%.7907.943 3494390 574507930994 .3 4-0.78-04 ..90-:9943 .93.3 08934-0.91 3.9 574507908390 .390294800.98 03850.-.7907.3/80.9..7.13 57450790870.3/ 4789..7.. %08941708:98.550.550.3 !70889044:5-:9943070   47547.80 44:58...$419.943 .70 .93 90%$/.9438 443 :5.

943 .9438 9.7074:5%.48419.9438 $9.94 90%204:9.-0/ %204:9 89.-94479 9080   47547.70 .039#:0/947%204:9.$419..-.3070 14:03.

03947.3/307747899 .70843-0490 .7074:5%.943 3./.70/090.943 .70 953.70 .90-4947084.47708543/310/   47547.$419.943 77478.704:989.90/04:.0902390 !7450790880.48419.039#:0/947&80735:9'.3/.943-49:738#19070 .

/7.943 .039#:0/947&80735:9'..70 4:930/9.74:3/90 .47708543/310/8   47547.943 7747870.48419.-4./.$419.7074:5%.90/943.308.70 .

0.039#:0 10.039#:08    884.$419.7:0 8574507908370.70 .9.03919078970854380.02..3.6:079.90.9438 .7074:5%./ 43 .3-0890/:83.48419.3/7 /4394800.943 ../23897.-0 4:..3/9204:9.3/ 5071472.8 390708:939.02039 ..9438439   47547.

039439473:8390%0-43840  47547.943 .7074:5 . $419.

0397:03.9.48419.20 /.7074:5%.9.3.70 .90.039#:0 2439473 .3.$419.:/0831472.039#:0389..0397:089.039#:0389.0/ 3.0-0032.94300.08   #057080390.03.

702.94389..039 #:0389.0/474:.039 7:0.9.0/0130/9204:9.8 2..43/9438.920039.3 0.9810/47 920/ 4:9.88.907097070/ 0907907:0..920900.0/.30/390.439.90/0.3.3/907:09208 4:9    47547..943 .08.9438.9.039.70.3/4907 3.3/908941.

:/0831472.$419.9..3..8708:941.70 .943950 ..9430.9.9433.30.03...20 /.943389.0397:0-032.9438  #05708039.48419.90.0-0037:3.7074:5%.0/  97070/.94389.039#:0 2439473 %7070/.

0/   47547.0881:47349  97070/.800.:90/8:..9439..3.943 .30.9800.9.0397:08 2.:90/.800...90/1470.:90/03..70.943389.08.920039 .3/19.

943 .947088.147.5.039#:0 2439473 507.9439.70 .2470 0.47/.3.08480.84390%7070/ .8708:941.09..93.$419..10/ .0.09.08.795041.48419.909:.79.33902088.4088..439.47708543/370.04390%7070/.:/08.0   47547.943889 850.0909  507.1.947088.9.840/.08  3 507.34907.9438.43840 044 100  4:-0..943841 90 4088.7074:5%.039.0 950  %8.947088.08705708039.-0948001470. 507..947088.0.:.2088.943389..

.90892439473.039!74.9.38000907.943 8   47547.35071472.48419.3 .07 4:.039243947331472.039#:0 2439473 4789..3800090790$$43947303987:333 4:..$419.0/94840.3.870.0/90.94384390800.431:7.38000907904789.943 ..943835.8-00303.70 .0.4789.08847$07.0.943890.943 4:./23897.943.7074:5%.90/4789..0.9438      %0 4789.943 4:.

039574.039574.943 .4/079.08847807.:9 23:908 03.:9 23:908  40. 59438:80/-%.422:3.-0/ 850.08847!479 00 54794190%.:9  48947  3:2-0741/.348947/.-08:804190%%!$57494.7/07 .494.1084419030.9439900.9.-0/  03.0794.08 . 59438 0307.:942.0794.94310.7/0/ /01.039!74.07 /01.9  147.2047!.//70884190%807.03474.943 0/  /0542039706:03.07!479 95 4893.0398.48419.:94.908.9:70 /01.-08900.3//0540/9490%$.$419. .039574..9435:3  %$07.459438147  03.0397..550/43900..70147.8 .943.07.03947.:9$ 803.08847.:9 850.0.70147.9437:38.:9   47547.0398 /01.8147.039/7.0393907.3/40/2088./.9.20 9  %$07.07 /01.7074:5%.0397:0:5/./:942..89474197070/7:0389.3:5706:03.0.70059390%$/.4 0  0.088479958!7494.08.:9$ %%!$803.3.4.-0847/8.2:89-0/0090/ /01.-..08847807.0398.70.039!74. /1 03.80 /01.994900.7/0/ /01.70 4-.4330.489 54794190%807.03474.10844190394441478947/.-0847/8.

:79 %$ 9480.$03/07 .070/ /01.-08:8041$0.07$0.-08:807.4330..4:9430 2.70/0.07 $$ 9480.48419. 59438 59438:80/-.:9 %$8/8.4330.:9 $$8/8.70 4-.-0/ 03..:70$4.070/ /01.70/0.:9 03.:94.20 83  8295$07.:7090.489 54794190$%!807.8.4:9430 2.9439490$%!807.//70884190$%!807.-0/ 03.07.07 /01.9439490$%!807.2047!.8.-08:8041%7.:7090.-0847/8.07 /01.$419.-0847/8.-0847/8.07974:.07!479 85  8295&80$$ :8  8295&80%$ 9 4893.9435:3  8295$07.07974:.098.385479.7074:5%.

943 .5.-0/ /01.-0/ 3.803/0794-0:80/1470 2.9438/8.943803.07 /01.90990$%!807.8847/ :5  2.-0/ /01.943.:9349809 3.943 :.:909.07 1.20 28   47547....:9  ..:9039..20419098*:807 5.:9%$  8295&80:9039.:9039..90990$%!807.88039-%$ /01.204190:80794-0:80/94.8847/4190:80794-0:80/94..  8295&807.07 1.:9039.2041902.:93.:9039..:909.20 :3  8295&807!.8847/.38990$%!807.943803.$03/07.

790/. .99089.432.70 4.432. 59438 59438.039574.08847 0  .9.8..3574.90/0.432.07085438-941-03.39.422.3:.943 .84.3/ ...48419...3/-..0398 84:/-0.07.0.3-00.459810147 &% $%#%     %08090747349902432.:52.:98$ 1472.439740/2.-:8390 .708:941.:52.088478  /01.8907  1474907!&8 %0809074734998!&.389..30.7074:5%.:98$ '%!# $$ #   574.3/8 /01.0881472439473410307.08847 .389.:942.$419..039   47547.3.3-0.3574.79243 .32.8907/42.422.3/90-.8907.3/ 43902.8907.89.039574.088.38945243 .79:54198!& 902432.//0/94904.

943 .7074:5 %$ %3907.0  47547.07.943 . $419.

3/.9. $07.9:70 %0%$ 39075780439473$07.-0.07 :- %.55.439075780439473$07.943 . 039 74807...07..07 %0%! %.943 .  2..70 39070890/3  %.7074:5%.4814770970.9..439075780439473 $07..88902 %0%!$0058.3#$ 389.439075780!479.$419.4330..:8942.4330. .9438 5..0399/3.40.9. 574..88419 9300/8.3/..0/ &3.507889039.40..55.3-0 .439075780!479.07 8900 .70/.4:.35:.4824394734390/.9:70.48419.0/43908.43974/.2058.-090039..2439473/.70 %7.3.9439490:- %.09.3/.9.40.9..4.2.9.4254303943.9.9.1: 10. -.07 %.94902439473807...425430398 /0503//70.0..40.9478 0398243947889028.438/070/.07 89070548947 147.9438 %0%.9:70/ 390039702490.90//.5.90.3/.2439473/.90.4390757804394730398./08.989490%!$94.7.039.3/.3/90%! #$ %.9.039 & %0&8.70.84..$07.88390.0398 %0%!$ 39075780!479.0 .90.4907.80/:80739071.98.039 8.439075780!479.078..0/ 1742..-9089.

3//.08945 $89028-03 2439470/ .9. .4 39075780439473 0398  47547.90/ :83%.40.943 .

9.9.97057080399039071. 574.243947389:./08.3/.9  %0%./0789.7074:5%.078..4:.7931742 90%$574.:80/.3898/.0307./078-:9%$:8089441902 W 0..9.574.70/1107039/./07 94.30//..0//.03941%.108 94/08..0394-9.0..48419.4&3.078..038/0%!94243947904-8.3/897:.4. 8:550/-90/.078.%!9850.33907.9438 %070.431:70/94243947.3/ .../0139438108 209.$419..3-0..9:704190/.9439% !  .9..174239071.9.0.&3.084190%&3.!74.9.039 $9.039 %0%.9.9.0398.078.9./078 .3/089:83/.9.7-09084:7.08 .70 %$ %3907.574.4&3.943.574./078 %04-9.1.3-0 8003..40.

943 ..0838/0%!9424394790%$7084:7.08808   47547..3/574.4.308 W $./07 94.0..759..28 89.!74.08 .9.4-8970.9:8.

%4:.70.9.90%70.943 470.9438 %01443%$7084:7.3/574.%$89:.0/4   47547.759.0:80/-  89/89  8.90%431 8.07 489.90.0108 %$85.75994.2.08808.943 .431:7090&94243947%$ .078.3//85.!74..9438 8.-9 !.%!            3092.2.:3.3 ..585..7074:5%.3-02439470/..:3..-9 %$/81700 %$088..70 $..48419./073907.90$9:.03984:/-0389.0/439 431:7..9.94389058706:70/   .431:7090%!94.0.3 4-2.3%&3.3 55807..08.$419...3994243947.04:9 $.75994.3 -.

943 99085488-094 3907.79574/:.98% 3.55.390903/8908.90%.74419707390474.48419.4439473 .//9439490&3.$419.0398 1742902 %8831.943 .70 903/%$3907.-9997/5./8:-28843   47547.7074:5%..00.3/3 0307./$.4474.792439473..0393907.0.03.0/:07 9%.997/5.9438 347/079470.078.

.7074:5%.70 .:5    47547.$419.943 .48419.

74 $2503491.3/90-4/41900 2.9089.9430 2.:942.909093.90/-90%$  %$89.89940.7074:5%....98.9 390920 3/4  $%  4:8.10/4-8 ..84304190850.:/0890041904-03/0/307747 %0.748 $.475 ..  4:70.70 !488-0.$419.30 2.0....039#:09.943  4:/0130901443.42 390 8:-0.7982439473.03.0.090.48419.9.:8942078.88443. 949043 8292.0900 2.9.039#:08./17420.3/.90850.9:841904-8   47547.03..943 .039#:0 034-8  90723.9.908307747 903 803/.3/.10/4-803/8 307747 9803/903491.

3904789.98.9438.3/904789.93  23:908 803/.03.79824394739089.943!&  88443.0 6:070890..3.430870.039 !&30/ 834970.943!& 834930/-.090.90/-90%$  %$89..42  4:8.0890774702.79890 23:908 9204:9  1900.70 !488-0.0.:8942078.03.74 %707%$039889.9:841904789.9:8  4:/0130901443.9..3 .02039 39071..$419. 947.748 $.3774702. 4089490%$..3/90%$89.7074:5%..  #..:942.48419.039#:0 2.943!& 8:330/ .94389..9.0.8904789.0/3 23:908 %$803/890774702.039#:0 03.425.9:88:330/.039#:09. 4308.

0070.897070/390.9089490!& 389...3.3.35071472.88   47547..1789574-02.7:089.3/1742 90703.9.89 23:908.943 .

203%!.90/3/70.425090/  4:/0130901443.:8942078.74 $:-29.4-$970.108.03.748 $.70.$419.947.48419.70 !488-0.039#:0 03.03.7074:5%.

3/908.30* .9.90/-90%$  %$89.039#:08...89940..9.2010834247024/10/ 903 89.7990%$ 4-8970.090.798243947310.2  %0...-.039#:09.98.9 390920 3/4  $%  4:8...:942.432./17420..

-..

039#:0.10 432.2   4:.9:8   47547.3/.897070/390.890108.190.89944:78..30* .88443.0.90/.70.3/9 8349.324703:80 98:-298904-8970.943 .3/8009889.

.90/  3.039 8455397.9432088.0398 84553706:089 870.331472.4-*47/07*/0.:89420.039 8455397..98..4-*47/07*/0.:942..:942.:89420.37747 02.$419.9.03.943 .:8942078.9.42 490780.94350728843 834970.....9432088.039#:0 0390.9490:807 490780948.38.099097.0/ .425..3 .90/-90%$  %0.0.9..3/ 90%$ /4.0.331472.0 84:/-0 40/ ..0.039#:09.38.9.74 %707.943 50728843 834970.48419.3/90.748 $..090.94389.0/ %$89.3774702.3/ 8:-29890%$/4.7074:5%.38.9:8.943  4:/0130901443. 9490:807..0/323:90 %$84:/803/.70 !488-0.38.03.039 84553706:089 870.7989023:909204:9  1900.9*9 84:/-08:-2990/  4:8.9*9   47547.84553433097.039#:0 8.0.0900.0/323:90 %$803/8.

48419.748 $.039 4- 8:.70 !488-0.03.80/439204:9  4:/0130901443.039 4- 00.74 %70743/:7.3/900.9434-8-.:8942078.7074:5%.$419.039#:0 03900. .03.

798904-8970..039#:0 3/7.-03/ .9:8 190710/.70.3/89.8349 /7.7989023:9089204:9  1900..943 ..9.3/8:-298904-8970.2    47547.0904- 89.090.039 4- 8:.2  490780984:/803/... 02..0.02.. %$89.0.308 9002.949098 4507.7070.-03/ 834970.5039.1989.3 .:942.90  4:8.9:8800..943.0881:47.4907809705080894574259  .3/8.425.890:807700/98907:0 .90/  3.19  %0.0793147.0/323:908 %$803/890 31472.943.4-3.42 .9.09.039#:0 8.331472.0/323:908 %$ 84:/7050894574259  ..

.8349.5078439.0/.9.79:70 .90/  88443..3/.9.19  %01443...90/  %01443.0398147908.03..9.70 !488-0.0.700307..74 754796:0:0147.943 .90/  23:908-01470.2019 9.039 50784336:0:0 8 0307.99490507843  %07:088.0/ 904-94.7070.$419.0.4-94.:8942078.//0/94906:0:01479019.48419.:89420.98 8:-2990/   47547.920.8.0/ 3 .0.:942..039 50784336:0:0 .8839080...748 $.03.3 8:-29.039#:08/0130/ 03900.7074:5%.9.0398.7070.19/05.0...0/147908.2019..4:500.-0 147 0.3/900..4-87:3803/3..8839080.30.039 80.039 80.9.5078438.-0 .

:8942078.$419.03.748 $.:9090 .422.48419.9439$! .9448  4:/0130901443.30.039#:0 03..07 3 %$2:8900.90/43$!807.3/09073.03.039.7074:5%.74 3907.70 !488-0.0/80307.3/ .

:87.

558..

9.03994%..039#:09.890850.30.0508 4503%.90/4390388902  88443.422.98.807.0/089.:90890850.0398.03994%..:942.039897070/43$! %$00.3/803/8..9.090.90/-90%$  %$89.9.43907578043840  4:8.2090743$!88902 83...0883077475.9:841$!0.10/0..79824394739089.09 %$84:/.3/..20 944503.10/05 /08.30.7.84 803/.09 909 !74..

039#:03/7..370...039#:03.  190784205074/ 4:80990.-4..0..9.:942./0.039#:08 ..9..90/-%$  4:.9.1989.943 .9:8 %0.907920   47547.9090.

Sign up to vote on this title
UsefulNot useful