11.07.2015 Views

Tivoli Workload Automation v.8.5.1 SPE/FP - Nordic TWS conference

Tivoli Workload Automation v.8.5.1 SPE/FP - Nordic TWS conference

Tivoli Workload Automation v.8.5.1 SPE/FP - Nordic TWS conference

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Flora Tramontano Guerritore<strong>Tivoli</strong> <strong>Workload</strong> <strong>Automation</strong>:- Latest major themes- Focus on current version <strong>TWS</strong> v8.5.1 + <strong>SPE</strong>s/<strong>FP</strong>s© 2011 IBM Corporation


Agenda Latest major themes– End-to-end consolidation– SLA management– Virtualization Focus on <strong>Tivoli</strong> <strong>Workload</strong> <strong>Automation</strong> v8.5.1• Conditional dependencies• z-Centric end-to-end• Broker integration• TDWC modeling• TWDC graphical views2<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Evolution timeline and sense of investments20062007 2008 2009 2010<strong>Tivoli</strong> <strong>Workload</strong>Scheduler for z/OS<strong>Tivoli</strong> <strong>Workload</strong>Scheduler<strong>Tivoli</strong> Dynamic<strong>Workload</strong> BrokerV8.3 V8.3 <strong>SPE</strong>s New web-based console Critical Path Deadlock detection & analysis Enhanced planning capabilities End-to-end new configuration TEP integrationV8.3 New web-based console RDBMS integration Enhanced planningfunctionalities J2EE and WEB servicesAPIV1.1 TCP/IP protocolsupport Advanced Reporting Virtual workstation IPV6 compliance Advanced Event Triggering Alert norification Advanced Reporting TEP integration TDWC Trial and forecastplanning CCMDB data exporting Standard LDAP , IPV6V1.2V8.4V8.4<strong>FP</strong>V8.3 <strong>SPE</strong>s <strong>Workload</strong> ServiceAssurance Enhanced jobvariables/directivesV8.5 CCMDB Integr. Events for business logic Eclipse-based <strong>TWS</strong> Workbench VarIable tables for streams Streamline configuration(simplify deployment scheme) <strong>Workload</strong> Service AssuranceV1.3V8.5 V8.5.1 Conditional Logic Enhanced event drivenautomation (additionalvariations on file z and dist) Eliminate OPC references New zCentric end-to-endsolution Step level dependencies Graphical view in web consoleV8.5.1 Dynamic scheduling (<strong>TWS</strong>/TDWBIntegration) Graphical Plan Vision andModeling FIPS 140-2V8.5.1 <strong>SPE</strong>s zCentric enhancementsfor dynamicconfiguration andfilewatcher Out-of-the-boxexecutors for Java,J2EE, FTP, SQL, WebServices Enhancementstofacilitate migrationsV8.5.1 <strong>FP</strong>s Out-of-the-boxexecutors(webservices, Sql,FTP) TDWC Usabilityimprovements Product vital pointhealth checks<strong>Tivoli</strong> <strong>Workload</strong>Scheduler forApplications Brand new componentfor policy-basedallocation of bestavailable resources toworkloadV8.3 Enhanced SAPscheduling PeopleSoft andOracle extendedsupport Extended platformcoverage (Solaris, HP) Auditing Oracle RDBMS support SAP Event monitoring Load balancing for SAP jobs3 <strong>Nordic</strong> <strong>TWS</strong> Guide 2011 - CopenhagenV8.4 <strong>TWS</strong> topology integration Easier Deployment Variables TablesV8.4<strong>FP</strong> Advanced Process Chain mgmt Manage IDOC Embed BDC sessionsLegenda: Release / Modification Release Small Program Enhancement / FixPackV8.5 Basic Job throttling Monitor Alerts Solution Manager integrationand certification© 2011 IBM Corporation


From job scheduling to workload automation: evolution and strength pointsJob SchedulingAutomatecalendar-basedinto plan-drivenproduction batchOrchestration ofworkflows, efficientmonitoringHigh availability,scalabilityautomaticrecovery of errors<strong>Workload</strong> <strong>Automation</strong>Automatecalendar-basedand eventbasedintoplan-drivenproduction batchSophisticatedorchestrationof workflows,monitoringandreportingHigh availability,scalability, faulttolerance,flexibility,advancedautomationEnd-to-endconsolidationSLAmanagementResourceawarenessandvirtualizationLegenda: Bold = evolutionary themes4 <strong>Nordic</strong> <strong>TWS</strong> Guide 2011 - Copenhagen© 2011 IBM Corporation


End-to-end consolidationSingle agnostic point of that integrates composite and complexservices and applications workloads, including new “emerging”workloads, across multiple platformsBusiness benefitsIdeal in CONSOLIDATIONscenarios, to reduce software,hardware, and labor costs andimplement shared services (cut costsdown 15%-20%)Flexible components, to be deployed in various configurations, andadhere to any organizational structureVarious forms of <strong>TWS</strong> for z/OS end-to-end: plan-based end-toendvs z-centric end-to-endVisibility, Control, <strong>Automation</strong>with a SINGLE POINT OF CONTROLon heterogeneous workloadsLower training and maintenancecosts, through intuitive web-based UISchedulingPlanCommoninterface: WEBconsole / ITMintegrationconsoleDistributedEnginez/OSEngineSysplexSchedulingPlanz/OSSingle point ofmonitoring,management, andreporting from a webbased user interfaceProofpoints – CustomerquotesDomainManagerDomainManagerFault-TolerantAgents with optionalERP X-Agentsbrokering capabilities Distributed z-centric agentsAgentz/OSAgents“A single tool that can accommodatea heterogeneous environmenteliminates the need to maintainmultiple technologies. This meanslower software licensing costs andfewer, more efficient ITadministrators” – Belgium bank5 <strong>Nordic</strong> <strong>TWS</strong> Guide 2011 - Copenhagen© 2011 IBM Corporation


More on end-to-end consolidationGraphical productionplan View for centralizedmonitoring ofheterogeneousworkloadsImpact graphicalview to walk throughyour networkdependenciesGraphical <strong>Workload</strong>Designer for centralized andintuitive manipulation ofscheduling objectsReports are available withhistorical workloadstatistics, workloadsdistribution, for tuning andoptimization purposesHistorical loadsand runtimesDashboards forat-a-glance viewof job statusesProofpoints – Customer quotes6<strong>Nordic</strong> <strong>TWS</strong> Guide 2011“With the ability to manage the entireworkload through a single Web-basedconsole, staff can easily see when jobshave failed and pinpoint the problem,which saves a great deal of time” – USAFarmaceutical.© 2011 IBM Corporation


7SLA managementAssurance of SLA objectivesthough dynamic prioritizationof business criticalworkloadsEffective monitoring throughdashboard of critical points,and dynamic views ofprogresses to criticalmilestonesHigh riskcritical jobOn trackcritical jobPotential riskcritical job21:00 5:001:00Risk-level notion todrive intelligent manualinterventionUnique leveraging ofWLM integration for<strong>TWS</strong> for z/OS toaccelerate theexecution of criticalworkloads<strong>Nordic</strong> <strong>TWS</strong> Guide 20116:00Business benefitsAwareness of different levelof importance of workloadsMeet your Service LevelAgreements reducing the needfor human intervention to aminimum levelProofpoints – CustomerquotesA Spanish Bank has improvedthe efficiency of its batch jobs,saving time and resources. TheCritical Path management) givesthe company tighter control overbatch jobs, and it is able toprocess time deviations withoutinterruption.© 2011 IBM Corporation


8VirtualizationPolicy-based IT resource utilization and optimization, through dynamicdistribution of workloads to virtualized pool of resources, driven byuser policies, workload requirements, and resource availabilityAutomatic discovery ofnewly provisionedmachines to the poolAutomatic provisioning ofnew machines foraddressing increasingdemand of workloads /SLAAutomatically adapt theworkload execution to ITenvironment changesAlso, <strong>TWS</strong> z/OS usesWLM SE integration andVirtual Workstation tomake workloads followingresource movementsJob1Job2Job3Balancedresource usageUser policies and jobs requirementsJob4Job5<strong>Nordic</strong> <strong>TWS</strong> Guide 2011NewlyprovisionedresourceJob6Business benefitsDrive transformation toDYNAMIC DATA CENTERBuild a virtual environment,decoupling workloads fromunderlying resourcesHelps getting the most out ofexisting assets and meeting SLAIncreased business efficiency,improved high availability, betterperformanceProofpoints – Customerquotes“With <strong>Tivoli</strong> Dynamic <strong>Workload</strong>Broker technology, we caneasily adapt workloadexecution to incidences,problems and configurationchanges, and automate keyservice execution”- USAFarmaceutical© 2011 IBM Corporation


Focus on <strong>Tivoli</strong> <strong>Workload</strong> <strong>Automation</strong> v8.5.11H092H091H102H10<strong>Tivoli</strong><strong>Workload</strong>Schedulerfor z/OS<strong>Tivoli</strong><strong>Workload</strong>SchedulerV8.5 Conditional dependencies Enhanced event-drivenmanagement OPC removal TEP improvementsV8.5.1 Step Level dependencies Z-centric end-to-end TDWC Modeling TDWC Graphical ViewsV8.5.1V8.5.1 <strong>SPE</strong>s Conditional dependenciesenhancements Z-centric enhancements (filewatcher, dynamicreconfiguration, newexecutors) Users Fields<strong>Tivoli</strong>Dynamic<strong>Workload</strong>Broker<strong>Tivoli</strong><strong>Workload</strong>Scheduler forApplicationsV8.5 Basic Job throttling Monitor Alerts Solution Managerintegration andcertification FIPS TDWB/<strong>TWS</strong>integration Graphical UI<strong>TWS</strong> z/OSV8.5.1Conditional dependenciesStep Level dependencieszCentricConditionalend-to-enddependencieszCentricStepfileLevelwatcher,dependenciesdynamicreconfiguration, new executorsTDWC graphical views and monitoringUsers Fields9<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - Value propositionHelps mapping dynamic business processes, increases the automationand the self-recovery, improves run time executionConditional Dependency abstractPossibility to define/monitor for a jobcomplex conditions on predecessorsError Codes and/or StatusesCustomer scenariosModel and monitor branches of workflows performing processes that depend on realtimeconditionsImplement self-recovery system, triggering automated processes to recover differenterror conditions10<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - IntroductionA dependency can be...Normal = 1-1 relationship betweenpredecessor and successorConditional = 1 to many relationship between one“conditional successor” and one or more“conditional predecessors”The successorstarts if andonly if thePredecessor Successor predecessorConditionalcompletesPredecessorsConditionalSuccessorThe conditionalsuccessor starts if acombination of statusesand return codes ofpredecessors is matchedA conditional dependency can be...At job levelAt step levelConditional successorchecks the status or returncode of the job in theconditional predecessorConditional successor checks the return code of aspecific step in the job of the conditional predecessors11<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - DetailsDefined in AD at operation levelRelational OperatorCondition TypeRuleGE, GT, LE, LT, EQ, NE, RGRC : nnnn,Sxxx,UxxxST : S, C, E and XAND, OR, n out of m(<strong>SPE</strong> on <strong>TWS</strong>z 8.5.1)12RC < 4ARC > 4Evaluated by the Scheduler at run timeBCThe schedulerevaluates if apossible path forprogression exists<strong>Nordic</strong> <strong>TWS</strong> Guide 2011YESNOScheduler evaluatesconditions and the status canbe U, T, F, and theconditional successor statusbecomes W, R, XPredecessor is flagged withUnexpected RC, successoris in Waiting status until anaction is done© 2011 IBM Corporation


Conditional dependency - ExampleSample scenario Suppose that job JOB1 performs calculationson invoices and produces a summarization filewhich is taken in input by job JOB5, to createa final report. JOB5 has to start if JOB1 completedsuccessfully. Moreover, we want to createrecover jobs to manage the situations ofempty file1 (RC=4 of JOB1) or corrupted file1(RC=8 of JOB1). To this purpose we createjobs JOB2 and JOB3. So, JOB5 has to starteven when JOB2 or JOB3 completessuccessfully.JOB2Process of backupinvoicesemptyJOB1file1Process of invoices andproduction of summarizationfile1errorJOB3Rollback and processof bakupi invoicesHow to implement the scenario anddefine the workflow?JOB5Processe of file1 or backup fileand production of a final report13<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - ExampleScenario implementationNOERROR JOB1 RC=4 and RC=8 JOB2 must run if JOB1 RC=4, skippedotherwise JOB3 must run if JOB1 RC=8, skippedotherwiseJOB1 RC=4JOB1JOB1 RC=8 JOB5 must run unconditionally when JOB1completes successfully, JOB2 and JOB3are either completed or skippedJOB2JOB3 Define a NOERROR statement in order tomake JOB5 running when theirpredecessors completeLegenda:= ConditionaldependencyJOB5= Normaldependency14<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - ExampleNOERROR JOB1 RC=4 and RC=8Transition of statuses1. JOB1 ends with ST=C and RC=02. JOB1 ends with ST=C and RC=4and JOB2 runs successfullyFalseJOB1 RC=4RC=0JOB1 CFalseJOB1 RC=83. JOB1 ends with ST=C and RC=4and JOB2 ends in errorXJOB2XJOB34. JOB1 ends with ST=E andRC=U2345(<strong>SPE</strong> on <strong>TWS</strong>z 8.5.1)X is equivalent to NOPED operation,successor startsYou can use conditions to propagatethe X statusJOB5RCYou can manage X status to be W15<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - ExampleNOERROR JOB1 RC=4 and RC=8RC=4Transition of statusesJOB1C1. JOB1 ends with ST=C and RC=02. JOB1 ends with ST=C and RC=4and JOB2 runs successfullyTrueJOB1 RC=4FalseJOB1 RC=83. JOB1 ends with ST=C and RC=4and JOB2 ends in errorRCJOB2XJOB34. JOB1 ends with ST=E andRC=U2345JOB5RC16<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - ExampleNOERROR JOB1 RC=4 and RC=8RC=4Transition of statuses1. JOB1 ends with ST=C and RC=02. JOB1 ends with ST=C and RC=4and JOB2 runs successfullyTrueJOB1 RC=4JOB1CFalseJOB1 RC=83. JOB1 ends with ST=C and RC=4and JOB2 ends in errorREJOB2XJOB34. JOB1 ends with ST=E andRC=U2345JOB5RW17<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - ExampleNOERROR JOB1 RC=4 and RC=8Unexpected flagTransition of statusesUndefinedJOB1E1. JOB1 ends with ST=C and RC=02. JOB1 ends with ST=C and RC=4and JOB2 runs successfullyJOB1 RC=4JOB1 RC=83. JOB1 ends with ST=C and RC=4and JOB2 ends in errorWJOB2WJOB34. JOB1 ends with ST=E andRC=U2345JOB5RW18<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Conditional dependency - ExampleRecovery jobsJOB1EAPPLA In a self-recovery scenario, recovery jobscan optionally be flagged (CONDRECOVERY flag). In this case:FalseJOB1 RC=4TrueJOB1 RC=8 Recovered jobs are recognizable(RECOVERY BY COND field set to YES)to not trigger further corrective actions.RXJOB2CJOB3 The whole instance APPLA, altough inError, is deleted at Daily Plan, because itcan be considered successfully completedin the whole.JOB5RC19<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Step level dependencyStep level dependenciesStep level dependency allows a job to startwhile a predecessor is still running, avoidingthe user to wait for the whole predecessorcompletionThe benefit is especially evident for longrunningjobs having steps with very differentdurations20<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Focus on <strong>Tivoli</strong> <strong>Workload</strong> <strong>Automation</strong> v8.5.11H092H091H102H10<strong>Tivoli</strong><strong>Workload</strong>Schedulerfor z/OS<strong>Tivoli</strong><strong>Workload</strong>SchedulerV8.5 Conditional dependencies Enhanced event-drivenmanagement OPC removal TEP improvementsV8.5.1 Step Level dependencies Z-centric end-to-end TDWC Modeling TDWC Graphical ViewsV8.5.1V8.5.1 <strong>SPE</strong>s Conditional dependenciesenhancements Z-centric enhancements (filewatcher, dynamicreconfiguration, newexecutors) Users Fields<strong>Tivoli</strong>Dynamic<strong>Workload</strong>Broker<strong>Tivoli</strong><strong>Workload</strong>Scheduler forApplicationsV8.5 Basic Job throttling Monitor Alerts Solution Managerintegration andcertification FIPS TDWB/<strong>TWS</strong>integration Graphical UI<strong>TWS</strong> z/OSV8.5.1Conditional dependenciesStep Level dependencieszCentricConditionalend-to-enddependencieszCentricStepfileLevelwatcher,dependenciesdynamicreconfiguration, new executorsTDWC graphical views and monitoringUsers Fields21<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


z-Centric end-to-endAddressed to customers with:• Mainframe culture• Subordinate distributed workloadExtend the reach of <strong>TWS</strong> z/OS to distributed environments, with minimum TCOSimplified access to distibuted workloads from a mainframe-centric conceptMinimize TCO and disruption for managing distributed workloads in mainframecentricmodeReuse of processes and producedure already in place22<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


What’s different with the previous end-to-end?Plan-based End-to-end Hierarchical topology– Optional multi-level configuration– Communication layer, USS Server Network Fault Tolerance– Distribution of plan to agents (decentralizedcontrol)Z-centric end-to-end Simple architecture– Flat topology– Simplified deployment and configuration– No communication layer, no Server Fully centralized and homogeneous control– Jobs scheduled by <strong>TWS</strong> z/OS (centralized control)ControllerMainframeDistributedControllerMainframeDistributedServerServer----------ISPF----------End-to-endDomainManager----------ISPF----------End-to-endTrackersFaultTolerantAgentTrackers23<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Some criteria to choice Elements in your plan-based end-to-end that should you let thinking aboutmoving plan-based end-to-end to a zCentric end-to-endReliable network, FaultTolerance benefits notexploitedFlat configurationToo manydependencies withthe mainframe(special resources,mainframe jobs)You want to dochanges to the planCentralized scripts24<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


z-Centric end-to-end : detailszCentric agent InstallationNo infrastructure, no WAS, No restart of Operating SystemLess than 5 minutes for installingEasy configurationROUTOPTS HTTP/HTTPS parameter to define the network address of thezCentric agentHTTPOPTSDefine the zCentric workstationSecure network connectionSSL protocol for secure, authenticated, encrypted network connectionKey ring used for connect cliente-server security certificatesSecure Windows users and passwordsWindows User ID and passwords defined in USRREC statementSample jobs for encryption25<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


z-Centric end-to-end : detailsCommunicationHTTP communication protocolConnectionless – one of the main advantages over old tracker angentsAt Controller startup, agents status “Active” and xstatus “Waiting for first submission”Recovery mechanismAutomatic attempt to re-establish the connection if the communication failsStore and forward event mechanism, in case of failureJob definitionJobs residing in JOBLIBBrowsing, editing as normal JCLs26Temporary modifications stored into JSVariable substitutionAutomatic RecoveryOptional JOBREC statement to define job properties<strong>Nordic</strong> <strong>TWS</strong> Guide 2011//JOBRECkeyword(value)keyword(value)//END JOBREC© 2011 IBM Corporation


z-Centric end-to-end : detailsAdditional functionsJOBLOG stored locally and send to Controller on requestSupport of SAP/Oracle/PeopleSoftNOERRORAlternate workstationSupport of workstation intervalSupport on z-centric workstations of all changes allowed on computer automaticworkstationsSupport on a z-centric operations of most commands allowed on z-operations (NOP, UN-NOP, MH, MR…)Kill jobsConditional dependencyChanging workstation in current planDynamic reconfigurationFile watcher27New job types<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


z-Centric end-to-end : new job executorsPossibility to extend the automation to the following new jobtypes: J2EE, Web Service, File transfer, Database, Java<strong>TWS</strong> z/OS zCentric end-to-end provides new JOBTYPEkeyword values, to be coded in the JOBREC statement, toschedule the different type of jobs.Customer valueExpand the reach of automation to new workloads that areentering the businessReduce the total cost of ownership aggregating new type ofjobs under a single point of management and28<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Z-Centric job executors : examples►►zCentric jobs are defined in JOBLIB dataset members, according to thesyntax belowFor scheduling J2EE, Web Service, File Transfer, Database and Javajobs, you have to specify the new job type and fill in the required parmsJOBLIBJob definition(JOBLIB member)//*OPC//*%OPC//*>OPC//JOBRECKeyword(value)Keyword(value)....//END JOBRECJob contentOptionalvariablesubstituion orautomaticrecoveryOptional statementto define jobparameters, andnew job typesJobcontent orscriptinvocation//JOBRECKeyword(value)JOBTYPE(/j2ee/jms |/j2ee/ejb | /web service | /filetransfer | /database | /java)Keywork(value)...//END JOBREC29<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Z-Centric job executors : examplesWeb ServiceFile Transfer//JOBRECJOBTYPE(/file transfer)TRANSFERTYPE(DOWNLOAD)SERVER(9.168.99.87)LOCALFILE(/FILE.TXT)REMOTEFILE(FILE.TXT)JOBUSR(Administrator)JOBPWD(YES)PROTOCOL(FTP)//END JOBREC//JOBRECJOBTYPE(/web service)PARM1(10)PARM2(20)JOBUSR(Administrator)JOBPWD(YES)OPNAME(getSum)URL(http://nc125166.romelab.it.ibm.com:9080/Sum/services/Sum/wsdl/Sum.wsdl)//END JOBREC30<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


z-Centric end-to-end : where it best fitsPredominant mainframeculture Simplified access to distributed workloads from amainframe concept, for customers with mainframe cultureand a subordinated distributed workload. Reuse ofprocesses and procedures already in place.Further simplification indeployment and maintenanceFully centralizationNew executorsSeamless synchronization of workWEB-based CentralizedManagement No Server customization, no USS skills required. Verysimple installation, configuration and maintenance.Minimized TCO and disruption for managing distributedworkloads in mainframe-centric mode Fully centralized control over distributed workload, expandthe <strong>TWS</strong> z/OS automation to distributed workloads. Expand the reach of automation to new type of jobs Dependencies are handled within one single engine Web-based single administrative and monitoring consolefor enterprise scheduling31Business reasonsTechnical reasons<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Focus on <strong>Tivoli</strong> <strong>Workload</strong> <strong>Automation</strong> v8.5.11H092H091H102H10<strong>Tivoli</strong><strong>Workload</strong>Schedulerfor z/OS<strong>Tivoli</strong><strong>Workload</strong>SchedulerV8.5 Conditional dependencies Enhanced event-drivenmanagement OPC removal TEP improvementsV8.5.1 Step Level dependencies Z-centric end-to-end TDWC Modeling TDWC Graphical ViewsV8.5.1V8.5.1 <strong>SPE</strong>s Conditional dependenciesenhancements Z-centric enhancements (filewatcher, dynamicreconfiguration, newexecutors) Users Fields FIPS TDWB/<strong>TWS</strong>integration Graphical UI<strong>Tivoli</strong>Dynamic<strong>Workload</strong>Broker<strong>Tivoli</strong><strong>Workload</strong>Scheduler forApplicationsV8.5 Basic Job throttling Monitor Alerts Solution Managerintegration andcertification<strong>TWS</strong> V8.5.1Conditional dependenciesStep Level dependenciesFIPSTDWB/<strong>TWS</strong> integrationGraphical UI32<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Evolution of distributed agent<strong>TWS</strong> 8.5.1 agent: twoexecutors<strong>TWS</strong> Server<strong>TWS</strong> Eventprotocol<strong>TWS</strong> Eventprotocol<strong>TWS</strong>BrokerServerHTTP/HTTPSprotocolHTTP/HTTPSprotocolHTTP/HTTPSprotocol<strong>TWS</strong>z ServerzCentric E2EClassic executor throughFTANew executor throughDynamic agentCovers native, XAprotocol (Apps, etc.)Covers the newextension protocolA platform for futuredevelopmentNetman<strong>TWS</strong>Engine<strong>TWS</strong>Executor<strong>TWS</strong> FTANew ITA Based AgentITATaskExecutionSubAgentOptionalNativeExecutorApps (SAP,…)JAVAExecutorJAVAResourceDiscoveryExtensibility to newapplicationsNative codeJava code33<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Dynamic <strong>Workload</strong>sDual Agent personality <strong>TWS</strong>d Agent can be configured to have– Fault-tolerance capabilities– Just the base execution/brokering capabilities <strong>TWS</strong>d dynamic agent uses a connectionlessprotocol (http/https) that helps to– Reduce impacts of network instability– Improve Master/DMs fan-out and reduces theneed of intermediate Domain Managers– Simplify configurations through firewalls<strong>TWS</strong> 8.5.1 ArchitectureConnection orientedprotocols requireadditional domainmanagers to scale<strong>TWS</strong>BrokeringServer<strong>TWS</strong>dServer<strong>TWS</strong> WEB-UIServerOffers to make your infrastructure moreflexible Zero risk of unwanted flexibility– Activate dynamical part after upgradingyour infrastructure to 8.5.1– Target specific agent through Brokeringserver– Introduce flexibility progressively<strong>TWS</strong>dAgent<strong>TWS</strong>dagent<strong>TWS</strong>d DomainManager<strong>TWS</strong>dFTA <strong>TWS</strong>dFTAConnection orientedprotocols are moresensitive to networkproblems<strong>TWS</strong>dFTA<strong>TWS</strong>dFTA<strong>TWS</strong>d DomainManager<strong>TWS</strong>dFTA<strong>TWS</strong>dFTASymphony file on theagent limits dynamicscheduling capabilities34<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Dynamic <strong>Workload</strong>sWorkstation SpecificationMix and match job types Jobstreams can always contain jobs onany type of workstationThree mechanisms to define destinations Jsdl definitions can be specified to go on aunique node– Equivalent to the FTA workstation Jsdl definitions can define any dynamicpool Possibility to attach an XA definition underthe Broker workstation, linked to aparticular Jsdl.Possible reasons to shape pools Presence of correct software for jobs Priority sets for high-risk SLA jobs Cluster node reliability (soft HA)Workstation=BROKERTask=“unique.jsdl hostname=agentAWorkstation=BROKERTask=“pool.jsdl –var exec=Script, var1=parameter1”Workstation=POOLA (XA, method “poolA.jsdl”)Task=“Script parameter1, parameter2”Dynamic Node Specification<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgent<strong>TWS</strong>dAgentIndividual nodespecificationthrough XA or jobJSDLPool specificationthrough JSDLPool specificationthrough XA35<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Focus on <strong>Tivoli</strong> <strong>Workload</strong> <strong>Automation</strong> v8.5.11H092H091H102H10<strong>Tivoli</strong><strong>Workload</strong>Schedulerfor z/OS<strong>Tivoli</strong><strong>Workload</strong>SchedulerV8.5 Conditional dependencies Enhanced event-drivenmanagement OPC removal TEP improvementsV8.5.1 Step Level dependencies Z-centric end-to-end TDWC Modeling TDWC Graphical ViewsV8.5.1V8.5.1 <strong>SPE</strong>s Conditional dependenciesenhancements Z-centric enhancements (filewatcher, dynamicreconfiguration, newexecutors) Users Fields<strong>Tivoli</strong>Dynamic<strong>Workload</strong>Broker FIPS TDWB/<strong>TWS</strong>integration Graphical UI<strong>TWS</strong> z/OSV8.5.1<strong>Tivoli</strong><strong>Workload</strong>Scheduler forApplicationsV8.5 Basic Job throttling Monitor Alerts Solution Managerintegration andcertificationStep Level dependenciesZ-centric end-to-endConditional dependenciesTDWC ModelingStep Level dependenciesTDWC Graphical Views36<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


TWDC modelingMass Update,Daily Planning,Service functions03/09GraphicalViewConditional LogicCalendar, VirtualWorkstation, <strong>Automation</strong>filtering criteria …Print Jobstream, CopyPaste dependenciesv8.5.18.5Dynamic Critical Path, Variable Table +Modeling Jobstream/Job, Resources, Workstation… + RuncycleEvent Management Reporting<strong>Workload</strong> Service AssuranceMonitoring Jobstream, Job, Resources, Workstation…. + Submit (Predefined job/Jobstream…)37<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Focus on <strong>Tivoli</strong> <strong>Workload</strong> <strong>Automation</strong> v8.5.11H092H091H102H10<strong>Tivoli</strong><strong>Workload</strong>Schedulerfor z/OS<strong>Tivoli</strong><strong>Workload</strong>SchedulerV8.5 Conditional dependencies Enhanced event-drivenmanagement OPC removal TEP improvementsV8.5.1 Step Level dependencies Z-centric end-to-end TDWC Modeling TDWC Graphical ViewsV8.5.1V8.5.1 <strong>SPE</strong>s Conditional dependenciesenhancements Z-centric enhancements (filewatcher, dynamicreconfiguration, newexecutors) Users Fields<strong>Tivoli</strong>Dynamic<strong>Workload</strong>Broker FIPS TDWB/<strong>TWS</strong>integration Graphical UI<strong>TWS</strong> and <strong>TWS</strong>z/OS V8.5.1<strong>Tivoli</strong><strong>Workload</strong>Scheduler forApplicationsV8.5 Basic Job throttling Monitor Alerts Solution Managerintegration andcertificationStep Level dependenciesZ-centric end-to-endTDWC ModelingTDWC Graphical Views38<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


<strong>Workload</strong> DesignerRun CycleOperator Instruction39<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Graphical view – <strong>Workload</strong> DesignerQuickly define your production workflow at the click of a mouseIntuitive view of yourobjects, through iconsflagged with specialsymbolsQuick search, anddrag and drop ofobjects to thegraphical view, tomodel objects andtheir dependencies(fromjobs/resources...)Intuitive view ofnetwork dependencies40<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


Graphical view – MonitoringGraphically see how your productionplan progresses and quickly assessimpact analysis Impact view to walkthrough your networkdependencies Chose the depth ofthe network youwant to visit Plan view to overseeyour production plan ina glance At-a-glance view ofnetwork links andworkload progressesPlan View41<strong>Nordic</strong> <strong>TWS</strong> Guide 2011© 2011 IBM Corporation


RussianTraditional ChineseThankGraciasSpanishThaiEnglishArabicYouMerciFrenchObrigadoBrazilian PortugueseBedanktNederlandsSimplified ChineseDankeGermanJapanese42© 2010 IBM Corporation


<strong>Tivoli</strong> <strong>Workload</strong> <strong>Automation</strong> - Physical architectureMainframeDistributedTDWCServerWebBrowser<strong>TWS</strong> z/OSConnector<strong>TWS</strong>Master<strong>TWS</strong> z/OSController<strong>TWS</strong> z/OSServer<strong>TWS</strong> z/OSStandbyControllerz/OSSysplexTWA End-toto-endConfiguration<strong>TWS</strong>DomainManagerBrokerServer43<strong>TWS</strong>zAgent<strong>TWS</strong>zAgent<strong>TWS</strong>zAgentERP<strong>TWS</strong>zCentricagents<strong>Nordic</strong> <strong>TWS</strong> Guide 2011<strong>TWS</strong>FaultTolerantAgent<strong>TWS</strong> XA<strong>TWS</strong>StandardAgent<strong>TWS</strong>FTABroker TDWBAgentsAgent© 2011 IBM Corporation

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!