TWSd – New Best Practices

1. TWS Education & Training TWSd – New Best Practices

2. Agenda • Global options • Scheduling FINAL • Monitoring FINAL • EDWA/external monitoring/auto-ticketing • Monitoring EDWA • Other integrations • Other tips

3. Global options • enLegacyId / li = NO • YES was useful only for network with 8.2 FTAs • enTimeZone / tz = YES • Even with a single TZ, YES should be the preferred option • enLegacyStartOfDayEvaluation / le = NO • Easier to understand but it changes the schedulation

4. Global options – enLegacyStartOfDayEvaluation=NO Start Of Day = 0600 06:00 06:00 April, 12 Miami April, 12 Rome 06:00 06:00

5. Global options – enLegacyStartOfDayEvaluation=YES Start Of Day = 0600 06:00 06:00 Miami(Master) April, 12 April, 12 Rome 12:00 12:00

6. Scheduling FINAL Every working day at 7AM we extend the plan until 12PM of the next working day 07:00 12:00 12:00 of next working day

7. Scheduling FINAL • Required settings • enCarryForward / cf = ALL • extension to next work day w/ buffer • FINAL to run on every workday (at 7:00) • HOLIDAYS calendar defined • ignoreCals / ic = NO • Makeplan to be changed to extend until next work day MakePlan –to `datecalc today + 1 workday pic mm/dd/yyyy` 1200 TZ America/NewYork • Set Until Time on JS to remove from plan uncompleted JS • with cf=ALL JS are not removed when a new plan is created • Optional settings • startOfDay / sd = 0000 • enPreventStart = ???

8. Monitoring FINAL • STARTAPPSERVER • MAKEPLAN  Can be scheduled in advance • SWITCHPLAN  Most critical • CREATEPOSTREPORTS  No production impact • UPDATESTATS  No production impact

9. Monitoring FINAL • Monitor FINAL jobs status (EDWA or external product) • SwitchPlan abend may not be reported since TWS is down • Monitor SwitchPlan long duration (EDWA or external product) • E.g.: alerting if SwitchPlan does not complete within the double of its normal duration • Periodically check FNCJSI • the size of Pre-Production plan is related to that > planman showinfo ... Start time of first not complete preproduction plan job stream instance: 03/25/2011 00:00 TZ CET

10. Monitoring FINAL Job Status Changed FINAL.SWITCHPLAN to status EXEC Job Status Changed FINAL.SWITCHPLAN to status SUCC, ABEND, FAIL Timeout = double of normal time Timeout Action: Send mail to administrator

11. EDWA/external monitoring/auto-ticketing • Use monitoring tools to be notified of failure in TWS • Job abends • Unlinked WS (outside FINAL timeframe) • TWS processes down on master netman mailman batchman jobman WAS monman • TWS mailbox size • Forward the identified problem to ticketing application to automatically generate a ticket

12. EDWA/external monitoring/auto-ticketing • EDWA • Can be used to monitor Jobs, unlinked WS, TWS processes, TWS mailbox size • Need to monitor EDWA itself • IBM Tivoli Monitoring • Integration provided with TWS can be used to monitor Jobs, TWS processes, TWS mailbox size • Monitor unlinked WS currently not provided in the integration • Can be implemented using BMEvents.conf events • Other monitoring tool • Jobs, unlinked WS can be implemented using BMEvents.conf events • Evtsize can be called to determine mailbox usage • TWS processes should be monitored through OS (pids directory contains TWS processes pids)

13. Monitoring EDWA • Monitor WAS is running • This can be done monitoring the java process • Monitor that agents are monitoring (coming soon) • Agent monitoring status is turned off if the monitoring process are down or agent is not able to send events. • BMEvents.conf can be used to generate events on the master when an agent monitoring status goes down (261,262). • Monitor for failed Rule Actions • Message AWSAHL007E is written in SystemOut.log when the action fails

14. Other integrations • Self service (via conman/Java APIs) • Allow your end-users to operate directly on their scheduling activities • Product like IBM Tivoli Service Request Manager can be used to implement an approval process before the action is performed • Custom GUIs can provide a simplified and limited interface design on the enduser need • Change management (via composer/Java APIs) • Promote your scheduling defintion from Dev to Q&A and from Q&A to Prod • Product like IBM Tivoli Service Request Manager can be used to implement an approval process before the action is performed

15. Other tips • “conman” always return rc 0, you can workaround this limitation with a wrapper script that intercept returned errors and exit with different rc accordingly http://www-01.ibm.com/support/docview.wss?uid=swg21470088 • Unlink Tool (coming soon) • “Check Health Status” command fron conman and WebUI diagnose unlink problems, .msg and Symphony files • Prevent losing events with EDWA • Modify EIF/monmaneif.templ and ssm/eif/tecad_snmp_eeif.templ setting: ConnectionMode=connection_less

16. Other tips (TDWC) • Windows Domain Users? • Consider accessing it as LDAP user registry instead as LocalOS • Improve TDWC scalability • Set maxOpenConnections=“20000” for WC_adminhost and WC_adminhost_secure in eWAS/profiles/twaprofile/config/cells/DefaultNode/nodes/DefaultNode/servers/twaserver/server.xml • Improve Graphical View scalability • Set isGrowable=“true” for TWSWebUIWorkManager in eWAS/profiles/twaprofile/config/cells/DefaultNode/nodes/DefaultNode/servers/twaserver/resources-pme.xml