WIXLIB

Determining the actions to take . . . . . .Action 1 - change the WebSphere ApplicationServer user ID password . . . . . . . .Action 2 - change password used bycommand-line clients to access the masterdomain manager . . . . . . . . . . .Action 3 - change password used byfault-tolerant agent systems to access the masterdomain manager (for conman) . . . . . .Action 4 - update the engine connectionparameters in the GUIs . . . . . . . . .Action 5 - change the j2c user ID password . .Action 6 - UNIX - update SOAP properties . .Action 7 - Windows - update Windows servicesAction 8 - change the Tivoli Workload SchedulerWindows user definition . . . . . . . .Using the changePassword script . . . . . . Unlinking and stopping Tivoli Workload SchedulerChanging the database host name, port, ordatabase name . . . . . . . . . . . . .Change the DB2 host name, port, or databasename . . . . . . . . . . . . . . .Changing the Oracle host name, port, ordatabase name . . . . . . . . . . . .Changing the security settings. . . . . . . .Changing security settings - general . . . . .Modify or display security settings - customuser registry . . . . . . . . . . . . .Managing the event processor . . . . . . . . Starting, stopping and displaying dynamic workload broker status . . . . . . . . . .Application server - starting and stopping. . . .Application server - automatic restart after failureAppservman - how it works . . . . . . .Controlling appservman. . . . . . . . .Starting and stopping the application server andappservman . . . . . . . . . . . . .Configuring user and password for running1conman stopappserver . . . . . . . . .1Monitoring the application server status . . .Obtaining information about application serverfailures . . . . . . . . . . . . . .Events created by appservman . . . . . .Application server - encrypting the profileproperties files . . . . . . . . . . . . .Encrypting profile properties usage . . . . .Application server - updating the Windowsservices after modifications . . . . . . . . .Updating the embedded WebSphere ApplicationServer services usage . . . . . . . . . .Application server - updating the SOAP propertiesafter changing the WebSphere Application Serveruser or its password . . . . . . . . . . .Updating the SOAP properties usage . . . .Application server - configuration files backup andrestore. . . . . . . . . . . . . . . kup usage . . . . . . . . . . . .Restore usage . . . . . . . . . . . .Application server - changing the host name orTCP/IP ports . . . . . . . . . . . . .Changing host properties . . . . . . . .Application server - changing the trace propertiesApplication server - using the utilities that changethe properties - reference . . . . . . . . .Understanding the templates . . . . . . .Application server - background information aboutthe utilities . . . . . . . . . . . . . .272272273274276277278278Chapter 10. Performance . . . . . . 281Network traffic . . . . . . . . . . . .Tracing . . . . . . . . . . . . . .Logging . . . . . . . . . . . . . .Maintaining the database . . . . . . . .Symphony file sizing . . . . . . . . . .Tuning a UNIX domain manager to handle largenumbers of fault-tolerant agents . . . . . .Tuning job processing on a workstation . . .Tuning the database . . . . . . . . . .Tuning the embedded WebSphere ApplicationServer . . . . . . . . . . . . . . .Inadequate Java heap size . . . . . . .Too many manual job submissions . . . . .Too many file dependency checks . . . . .Workload spreading . . . . . . . . . .Improving job-processing performance . . . .Mailbox caching - advantages and disadvantagesSetting the synch level parameter. . . . . .The fault-tolerant switch manager - impact onperformance . . . . . . . . . . . . .Network Traffic . . . . . . . . . .Disk Space . . . . . . . . . . . .Scalability . . . . . . . . . . . . .Impact on JnextPlan . . . . . . . . .Impact on reporting . . . . . . . . .Impact on event rule deployment . . . .Increasing application server heap size . . .Increasing maximum DB2 log capacity . . .Multiple Tivoli Dynamic Workload Consoleproduction plan reports . . . . . . . . .Tivoli Dynamic Workload Console - adjustingsession timeout settings . . . . . . . . .281281282282282. 282. 282. 283.284284284284284285285. 286.287287287288288288289289289. 292. 293Chapter 11. Availability . . . . . . . 295Resolving Windows user ID account .Using a temporary directory on UNIX . 295. 296Notices . . . . . . . . . . . . . . 297271271Trademarks . 298Index . . . . . . . . . . . . . . . 301272Contentsv

viIBM Tivoli Workload Scheduler: Administration Guide

List of figures 1.2.3.4.List of tasks . . . . . . . . . . . . 72Tivoli Workload Scheduler network domainstructure . . . . . . . . . . . . . 143Symphony file synchronization . . . . . 147Process creation on domain manager andfault-tolerant agent. . . . . . . . . . 148 Copyright IBM Corp. 2001, 20105.6.Typical Tivoli Workload Scheduler networkflows. . . . . . . . . . . . . .SSL server and client keys . . . . . . 153. 180vii

viiiIBM Tivoli Workload Scheduler: Administration Guide

List of tables1.2.3. 11 .23.24.25.26.27.28.Workload service assurance feature . . . . . 6Event-driven workload automation feature general . . . . . . . . . . . . . . 7Event-driven workload automation feature event mailing . . . . . . . . . . . . 7SSL . . . . . . . . . . . . . . . 7Job management . . . . . . . . . . . 8Job stream management . . . . . . . . . 8Stageman . . . . . . . . . . . . . 8Planman . . . . . . . . . . . . . . 8Logging . . . . . . . . . . . . . . 9General . . . . . . . . . . . . . . 9Shortcuts for encryption ciphers. . . . . . 30JOA JOB ARCHIVES database table . . . . 46JRA JOB RESOURCE ARCHIVES databasetable . . . . . . . . . . . . . . . 47MEA METRIC ARCHIVES database table47Job statuses in the historical tables . . . . . 48J2EEJobExecutorConfig.properties filekeywords . . . . . . . . . . . . . 49Workload broker workstation configurationproperties . . . . . . . . . . . . . 55Actors and their roles . . . . . . . . . 56Trace and log configurable properties of theTivoli Workload Scheduler agent . . . . . 60Common launchers configurable properties ofthe Tivoli Workload Scheduler agent . . . . 62Native job launcher configurable properties ofthe Tivoli Workload Scheduler agent . . . . 63Java job launcher configurable properties ofthe Tivoli Workload Scheduler agent . . . . 63Resource advisor agent configurable propertiesof the Tivoli Workload Scheduler agent . . . 64System scanner configurable properties of theTivoli Workload Scheduler agent . . . . . 65Default port numbers . . . . . . . . . 68Tivoli Workload Scheduler predefined roles77Tivoli Dynamic Workload Broker predefinedroles . . . . . . . . . . . . . . . 79Product versions and default server names83 Copyright IBM Corp. 2001, 20101 29.1 .47.1 48.1 49.50.51.52.53.54.55.1 56.1 57.58.59.60.61.62.Syntax for special characters . . . . . .Variables used in the URL definition . . .Object attribute types for each object typeAccess keywords for composer actionsActions - access keywords . . . . . .Calendar - additional access keywordsCpus - additional access keywords . . .Events - access keywords . . . . . .Files - access keywords . . . . . . .Jobs - additional access keywords . . . .Parameters - additional access keywordsPrompts - additional access keywordsFiles- access keywords . . . . . . .Resources - additional access keywordsJob streams - additional access keywordsUsers - additional access keywords . . .Variable tables - access keywords . . . .Critical flow errors. . . . . . . . .Queue sizing conditions. . . . . . . .Example for the ge operator . . . . .Example for the le operator . . . . . .Calculation of internal Symphony tableFiles for Local Options . . . . . . .Type of communication depending on thesecuritylevel value . . . . . . . . .Changes allowed in Tivoli WorkloadScheduler key and trust stores . . . . .Algorithm for calculating the approximatesize of the plan data in the Symphony file .Algorithm for calculating the approximatesize of the database data in the Symphonyfile . . . . . . . . . . . . . .Example for the ge operator . . . . .Example for the le operator . . . . . .Log and trace file maintenance. . . . .If and where password changes are requiredValues of activeUserRegistry to checkPassword change actions. . . . . . .Options for tuning job processing on aworkstation . . . . . . . . . . . 87. 87109114. 116117. 118. 119. 120. 121124125. 126127128. 129. 130. 154. 155. 156. 157162. 173. 174. 180. 204.205206206207242243. 244. 283ix

xIBM Tivoli Workload Scheduler: Administration Guide

About this publicationIBM Tivoli Workload Scheduler: Administration provides information about theadministration of the main components of IBM Tivoli Workload Scheduler (oftencalled the engine).What is new in this releaseFor information about the new or changed functions in this release, see TivoliWorkload Automation: Overview. For information about the APARs that this release addresses, see the TivoliWorkload Scheduler Download Document at http://www.ibm.com/support/docview.wss?rs 672&uid swg24024804, and Tivoli Dynamic Workload ConsoleDownload Documents at http://www.ibm.com/support/docview.wss?rs 672&uid swg24024805.What is new in this release for administrationThis section describes what has changed in this release with regard toadministration since version 8.5:v A new scheduling agent with z-centric and dynamic scheduling capabilities, theTivoli Workload Scheduler agent, is available in this release.v Support of Federal Information Processing Standards (FIPS) compliance forconnection security is provided.For more information about the new or changed functions in this release, see IBMTivoli Workload Automation: Overview.What is new in this publication for version 8.5.1This section describes what has changed in this publication since version 8.5.Changed or added text with respect to the previous version is marked by a verticalbar in the left margin. If the changed or added text applies only after a particularfix pack is installed, the mark in the left margin is the number of the fix pack. Forexample, 1 to refer to Fix Pack 1, and so on.v A new chapter describing the configuration of the dynamic schedulingcapabilities has been provided.v A new section describing how to configure security for Federal InformationProcessing Standards (FIPS) compliance has been provided.v The possibility to disable HTTP and Administration ports has been added to theApplication Server changeHostProperties tool.v A new script for changing key Tivoli Workload Scheduler passwords has beenprovided.111What is new in this publication for version 8.5.1.1This section describes what has changed in this publication with regard toadministration since version 8.5.1: Copyright IBM Corp. 2001, 2010xi

What is new111111111111111111v The tcp connect timeout local option was added in “Setting local options” onpage 20.v Section “Configuring the Tivoli Workload Scheduler agent” on page 59 wasupdated to include new log and trace management information for the TivoliWorkload Scheduler agent.v Section “Specifying object attributes” on page 108 was changed to add newattributes for object job.v Section “Configuring for LDAP” on page 135 was improved.v A new section was added to “Network links” on page 145 to describe the newchkhltst service used to verify that the workstation mailbox can be successfullyread, and check if there are errors in the mailbox header.v Sections “Monitoring the status of Tivoli Workload Scheduler processes” on page150 and “Monitoring the size of Tivoli Workload Scheduler message queues” onpage 155 were added in Chapter 6, “Network administration,” on page 143.v Section “Monitoring the disk space used by Tivoli Workload Scheduler” on page205 was added in Chapter 8, “Data maintenance,” on page 201.v Section “Configuring user and password for running conman stopappserver” onpage 268 was added in Chapter 9, “Administrative tasks,” on page 233.1All updates are marked with a 1 (one) on the left page margin.11For an update on the new or changed functions in this release, see: IBM TivoliWorkload Automation: Overview.Who should read this publicationThis publication provides information about the day-to-day administration of theproduct, and is aimed at the IT administrator or Tivoli Workload Scheduler ITadministrator whose job it is to ensure that the product runs smoothly andcorrectly. This person will find information about making routine changes to theconfiguration, for example to add a user, and information about periodicprocedures that ensure the integrity of the product, such as backups.The reader of this book should be an expert systems programmer, who has areasonable understanding of the Tivoli Workload Scheduler infrastructure and itsinter-component interactions.PublicationsFull details of IBM Tivoli Workload Automation publications can be found in TivoliWorkload Automation: Publications, . This document also contains information on theconventions used in the publications.A glossary of terms used in the product can be found in Tivoli Workload Automation:Glossary, .Both of these are in the Information Center as separate publications.xiiIBM Tivoli Workload Scheduler: Administration Guide

AccessibilityAccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. With this product,you can use assistive technologies to hear and navigate the interface. You can alsouse the keyboard instead of the mouse to operate all features of the graphical userinterface.For full information with respect to the Tivoli Dynamic Workload Console, see theAccessibility Appendix in the Tivoli Workload Scheduler: User's Guide and Reference,SC32-1274.For full information with respect to the Job Scheduling Console, see theAccessibility Appendix in the Tivoli Workload Scheduler: Job Scheduling Console User'sGuide, SC32-1257.Tivoli technical trainingFor Tivoli technical training information, see the following IBM Tivoli EducationWeb upport informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:OnlineGo to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html and follow the instructions.IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceabilityworkbench that helps you resolve questions and problems with IBMsoftware products. The ISA provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe ISA software, go to oting GuideFor more information about resolving problems, see the problemdetermination information for this product.For more information about these three ways of resolving problems, see theappendix on support information in Tivoli Workload Scheduler: Troubleshooting Guide,SC32-1275.About this publicationxiii

xivIBM Tivoli Workload Scheduler: Administration Guide

Chapter 1. Getting started with administrationThis publication describes how to perform administrative tasks on Tivoli WorkloadScheduler and Tivoli Dynamic Workload Console. Many of the proceduresdescribed in it require you to identify a file in the installation path of the productand its components. However, they can have more than one installation path, asdescribed in “Where products and components are installed.”Where products and components are installedThis section describes how to determine where Tivoli Workload Schedulercomponents are installed, as follows:Tivoli Workload Scheduler installation pathYou can install more than one Tivoli Workload Scheduler component on asystem. Each master domain manager, backup master domain manager,domain manager, backup domain manger, agent, or connector is installedin a path called a Tivoli Workload Automation instance. Only one componentcan be installed in each instance. The default path for the Tivoli WorkloadAutomation instance is:UNIX /opt/ibm/TWA n WindowsC:\Program Files\ibm\TWA n where n is an integer value ranging from null for the first instanceinstalled, 1 for the second, and so on.This path is called, in the publications, TWA homeThe installation path of Tivoli Workload Scheduler is:TWA home/TWS Dynamic workload broker installation pathThe files pertinent to workload broker are installed in the following path:TWA home/TDWBTivoli Dynamic Workload Console installation pathThe Tivoli Dynamic Workload Console can be installed in more than onepath:v It can be installed alongside Tivoli Workload Scheduler or alone in aTivoli Workload Automation instance using the embedded version ofWebSphere Application Server. In this case its path is:TWA home/TDWCv It can be installed on your own external instance of WebSphereApplication Server. In this case its path depends on where your instanceof WebSphere Application Server is installed (except for the uninstaller,which is installed in a path of your choice). The administrativeprocedures in this publication do not address problems that occur withthe external version of WebSphere Application Server.If you are using the Tivoli Dynamic Workload Console on an externalversion of WebSphere Application Server, and an administrativeprocedure refers to the path TWA home/TDWC, substitute it with the Copyright IBM Corp. 2001, 20101

Where products and components are installedinstallation path of the Tivoli Dynamic Workload Console on yourexternal version of WebSphere Application ServerThe embedded WebSphere Application Server installation pathThe embedded WebSphere Application Server is automatically installedwhen you create a new Tivoli Workload Automation instance. Its installationpath is:TWA home/eWASThe command line client installation pathThe command line client is installed outside all Tivoli Workload Automationinstances. Its default path is:UNIX /opt/ibm/TWS/CLIWindowsC:\Program Files\IBM\TWS\CLIThe application server tools installation pathBecause the embedded WebSphere Application Server is not supplied withan administration GUI, many of its administration tasks are performed byrunning tools supplied with Tivoli Workload Scheduler, that perform therequired configuration changes. These tools are known as the wastools, andare installed in:TWA home/wastoolsHowever, the information above supplies only the default paths. To determine theactual paths of products and components installed in Tivoli Workload Automationinstances, see “Finding out what has been installed in which Tivoli WorkloadAutomation instances”Finding out what has been installed in which Tivoli WorkloadAutomation instancesIf you are not the installer of Tivoli Workload Scheduler and its components, youmight not know what components have been installed, and in which instances ofTivoli Workload Automation. Follow this procedure to find out:1. Access the following directory:UNIX /etc/TWAWindows%windir%\TWA2. List the contents of the directory. Each Tivoli Workload Automation instance isrepresented by a file called: twainstance instance number .TWA.properties.These files are deleted when all the products or components in an instance ar

the Tivoli Workload Scheduler agent .63 22. Java job launcher configurable properties of the Tivoli Workload Scheduler agent .63 23. Resource advisor agent configurable properties of the Tivoli Workload Scheduler agent . . . 64 24. System scanner configurable properties of the Tivoli Workload Scheduler agent .65 25. Default port .