Skip to main content

Test 000-569: IBM Tivoli Workload Scheduler V8.6 Implementation

Tab navigation

Section 1: Installation and Planning

  1. Given a number of servers on which workload is required to be managed and an organizational or network topology, identify which role each server will perform (agents, master domain manager, backup domain managers, etc.) so that IBM Tivoli Workload Scheduler V 8.6(TWS) can be correctly installed and configured.
    With emphasis on performing the following tasks:
    1. Identify servers and parameters (resources, operating system, etc.) for master domain manager (MDM) and backup master domain manager roles.
    2. Identify servers to host TWS DB and Tivoli Dynamic Workload Console (TDWC).
    3. Identify domains.
    4. Identify domain manager.
    5. Identify agents.
    6. Confirm platforms for identified agents that are supported.
  2. Given the need to install TWS on a compliant system, determine the TWS system and user requirements to verify that TWS can be installed successfully.
    With emphasis on performing the following tasks:
    1. Determine operating system prerequisites for Unix/Linux or Windows.
    2. Determine hardware prerequisites for Unix/Linux or Windows.
    3. Determine software prerequisites for Unix/Linux or Windows.
  3. Given a compliant computer with the RDBMS installed, check that the database server is prepared so that TWS can be installed locally or remotely.
    With emphasis on performing the following tasks:
    1. Ensure supported RDBMS is installed.
      1. DB2 Enterprise Server Edition is installed as a server.
      2. DB2 Enterprise Server Edition is installed as a client.
      3. Oracle Enterprise Edition is installed as a server and a client.
      4. Oracle Standard Edition is installed as a server and a client.
    2. Optionally, create the database and all the tables
      1. Customize the properties file for DB2 or Oracle.
      2. Generate the SQL files for TWS database installation by using the customize SQL script.
      3. Run the SQL scripts to create the database and tables.
    3. Record the database settings required to install TWS.
  4. Given a compliant system and access to TWS installation media, perform the necessary steps so that TWS is installed successfully.
    With emphasis on performing the following tasks:
    1. Determine type of TWS engine to install (MDM, BKM, fault-tolerant agent , Domain Manager, Dynamic Domain Manager, LFTA, Dynamic Agent).
    2. Determine installation method (LaunchPad, Integrated Service Management Processes (ISMP) wizard, silent, twsinst, SWD).
    3. Obtain proper user access for the installation user.
    4. Determine the information necessary to fill in required fields (what DB used, existing TWA instance, other TWS engines already installed, installation directory, eWAS user ID, etc.).
    5. Extract TWS installation media files.
    6. Install TWS by using chosen installation method (Launchpad, Setup.bin, twsinst, etc.).
    7. Verify installation is complete.
  5. Given a compliant system and access to TWS for Applications installation media, perform the necessary steps so that TWS for Applications is installed successfully.
    With emphasis on performing the following tasks:
    1. Determine operating system where TWS for Applications will be installed.
    2. Determine installation method (LaunchPad, ISMP wizard, silent, twsinst, SWD).
    3. Obtain proper user access for the installation user.
    4. Determine specific access method prerequisites for installation (PeopleSoft, Oracle).
    5. Determine the information necessary to fill in required fields (access method, xagent host name, method user ID, TWS user ID).
    6. Extract TWS for Application installation media files.
    7. Stop all TWS scheduling or monitoring processes are running.
    8. Install TWS for Applications by using chosen installation method (Launchpad, Setup.bin, twsinst, etc.).
    9. Verify installation is complete.
  6. Given a compliant system and access to TDWC installation media, perform the necessary steps so that TDWC is installed successfully.
    With emphasis on performing the following tasks:
    1. Determine operating system where TDWC will be installed.
    2. Determine if internal, shared, or external WebSphere is to be used.
    3. Determine installation method (Launchpad, ISMP wizard, silent).
    4. Obtain proper user access for the installation user.
    5. Check installation prerequisites,
    6. Determine the information necessary to fill in required fields.
    7. Extract TDWC installation media files.
    8. Optional: Complete steps to install Tivoli Integrated Portal instance.
    9. Install TDWC by using chosen installation method (Launchpad, ISMP wizard, silent).
    10. Verify installation has completed successfully.
  7. Given an existing TWS instance and upgrade media, perform the necessary steps so that TWS is successfully upgraded.
    With emphasis on performing the following tasks:
    1. Confirm that hardware and software prerequisites have been met.
    2. Extract (gnu-tar).
    3. Stop TWS by using conman stop.
    4. Run the installer by using response files, GUI, twsinst, or twspatch.
    5. Examine TWS instance to confirm the installation was successful.
  8. Given TWS master or backup master, check upgrade prerequisites, determine the upgrade method, run the upgrade as root or Administrator, and check the TWS instance to confirm a successful upgrade so that TWS is upgraded.
    With emphasis on performing the following tasks:
    1. Check hardware and software prerequisites.
    2. Extract installation media (GNU -tar on AIX).
    3. Acquire root or Administrator credentials.
    4. Determine upgrade method (Direct or parallel).
    5. Determine installation method (response files or GUI installation).
    6. Switch to the backup master.
    7. Run installer.
    8. Examine TWS instance to check that the upgrade was successful.
    9. Switch back to the master.
  9. Given the TWS 8.6 is installed on a Unix/Linux or Windows system, perform the necessary steps so that TWS is uninstalled from the system.
    With emphasis on performing the following tasks:
    1. Log on as root user or a Windows administrator account with Act as Part of the Operating System rights.
    2. Check that there are no jobs pending or running.
    3. Ensure that the workstation is no longer part of the plan. (Delete the workstation definition of the agent from the database or set the workstation to IGNORE. Unlink the workstation or run JnextPlan-for 0000 the workstation (enCarryForward = ALL).
    4. Stop all processes/services.
    5. Determine the method used to install the product and choose same method to uninstall.
    6. Determine if uninstall is successful.
    7. Remove any leftover files/or directories as needed.

Section 2: Configuration

  1. Given an IBM Tivoli Workload Scheduler V 8.6(TWS) instance with eWAS, configure WebSphere's security, database access, and network configuration so that TWS can operate in an existing environment.
    With emphasis on performing the following tasks:
    1. Configure security and authentication with {show|change}SecurityProperties.sh (or the ISC) to utilize LDAP, Federated Repositories, or Local authentication.
    2. Configure database access configuration with {show|change}DatabaseProperties.sh
    3. Configure network configuration with {show|change}HostProperties.sh.
    4. Apply modifications by restarting WebSphere and updating Windows services.
  2. Given a Tivoli Dynamic Workload Console (TDWC) V8.6 instance, configure user access so that defined users will have access to needed panels.
    With emphasis on performing the following tasks:
    1. Assign Administrative rights to an Admin user.
    2. Set the global account security type.
    3. Configure realm settings.
    4. Identify user/LDAP group.
    5. Assign TDWC user roles.
    6. Set the global account security type.
    7. Export/import users' tasks from existing TDWC.
  3. Given a TWS Master instance, configure the local and global options so that TWS can operate in the desired manner.
    With emphasis on performing the following tasks:
    1. Configure global options (56 options).
      1. Auditing
      2. Start of day
      3. Enable time zones
      4. Legacy
      5. Carryforward
    2. Configure local options.
  4. Given a TWS V8.6 instance, configure user authentication so that defined users will have access to perform necessary tasks.
    With emphasis on performing the following tasks:
    1. Define user/group authentication in the security file for workstation.
    2. Configure localopts for CLI authentication.
    3. Create useropts for users other than TWS_user.
    4. Define Windows User in database.
  5. Given a TWS instance, configure authorization for TWS (Security file) and TDWC (Tivoli Integrated Portal (TIP) so that users have the appropriate access.
    With emphasis on performing the following tasks:
    1. Display current TWS settings to the screen - dumpsec.
    2. Limit TWS access based on a variety of criteria by editing Security file. (run root jobs, workstation, name of object, default variable table).
    3. Use makesec to put changes in effect.
    4. Use TIP, assign appropriate roles so that users have correct access in TDWC. (TWSWEBUIAdministrator, TWSWEBUIOperator, TWSWEBUIDeveloper, TWSWEBUIAnalyst, TWSWEBUIConfigurator, TDWBAdministrator, TDWBOperator, TDWBDeveloper, TDWBConfigurator)
  6. Given TWS agents must be able to launch all jobs, create, review, and edit necessary TWS, user, and environment settings so jobs can complete successfully.
    With emphasis on performing the following tasks:
    1. Edit TWS Security.
    2. Check user rights and privileges.
    3. Check file permission and execute rights.
    4. Edit jobmanrc, /bin/taskLauncher.sh.
    5. Create /.jobmanrc or \djobmanrc.cmd and specify system, user and application settings.
    6. Edit /localopts.
    7. Review jobmanager.ini and ita.ini config files in the /ITA/bin directory.
  7. Given system administration access to the TWS environment and an understanding of the network topology, configure connection security features such as IP validation, SSL communications and Federal Information Processing Standards (FIPS) 140-2 so that they meet the requirements of the organization's security policies.
    With emphasis on performing the following tasks:
    1. Configure IP validation.
    2. Configure SSL connections between DM's and fault-tolerant agents.
    3. Configure SSL connections between DM's and dynamic agents.
    4. Customize the SSL connection for the TDWC.
    5. Customize the SSL connection to the master domain manager (MDM) and Dynamic Domain Manager.
    6. Customize the SSL connection for a command-line client.
    7. Configure TWS to be compliant with the FIPS.

Section 3: Scheduling Objects

  1. Given a number of IBM Tivoli Workload Scheduler V 8.6(TWS) agents, the network, functional or organizational topology, define domains so that the TWS network runs with improved scalability and availability.
    With emphasis on performing the following tasks:
    1. Choose which agents should become domain managers and backup domain managers and which agents to become domain members.
    2. Configure DM as full status fault-tolerant agent (FTA) and Manager for a specific domain by using composer or the Tivoli Dynamic Workload Console (TDWC).
    3. Configure agents to become members of the previously defined domains by using composer or the TDWC.
    4. Ensure global carry forward option is set to all.
    5. Run JnextPlan -for 0000 to include domain configuration in the plan.
    6. Change workstation limit to allow jobs to run on the workstation.
    7. Revert back the global option carry forward to the previous value.
  2. Given access to a TWS V8.6 database, perform the necessary steps so that workstation definitions are correctly created in the TWS database.
    With emphasis on performing the following tasks:
    1. Define a workload broker workstation.
      1. Among the various attributes, specify: variable table (vartable), domain, settings when communicating in HTTP, security level, server.
    2. Define a remote engine workstation in environment A. This workstation will be hosted by the workload broker workstation and will point to the master domain manager (MDM) on environment B.
      1. Specify to use the HTTPS protocol when communicating with environment B.
      2. Specify as TIMEZONE property of the remote engine workstation the timezone set on the operating system of the remote MDMs it points to.
      3. On another new remote engine workstation specify to use the HTTP protocol when communicating with environment B.
    3. In the agent workstation specify variable table (vartable).
    4. Define a manager workstation.
      1. Among the various attributes, specify: variable table (vartable), domain, settings when communicating in HTTP/HTTPS, security level .
    5. Define a FTA workstation.
      1. Among the various attributes, specify: variable table (vartable), settings when communicating in HTTP/HTTPS, security level, server.
    6. Define a standard agent workstation.
      1. Among the various attributes, specify: variable table (vartable), settings when communicating in HTTP/HTTPS, security level, server.
    7. Define an extended agent workstation.
      1. Among the various attributes, specify: variable table (vartable), node, domain, settings when communicating in HTTP, security level.
    8. Define dynamic domain manager workstation (dynamic domain manager = DM + TDWB and its database.
      1. Specify database parameters.
      2. Specify workstation configuration (full status, manager, domain).
  3. Given a TWS environment with workload broker workstation and dynamic agents defined, create pool and dynamic pool workstations so that the definitions of pool and dynamic pool workstations are added to the database.
    With emphasis on performing the following tasks:
    1. Define a dynamic pool workstation hosted by the workload broker.
      1. Use variable table (vartable).
      2. Use different JSDL files in the resources attribute.
      3. Choose logical resources to define the pool.
      4. Choose operating systems to define the pool.
    2. Define a pool workstation hosted by the workload broker.
      1. Use variable table (vartable).
      2. Specify dynamic agents in members.
  4. Given a TWS V8.6 instance, create job definitions so that defined jobs will run.
    With emphasis on performing the following tasks:
    1. Determine job type.
    2. Supply the name, workstation where it will run and logon information.
    3. Define the command or script name.
    4. Set the recovery option.
  5. Given access to the TWS database, define scheduling objects to facilitate the scheduling of jobs which meet production objectives.
    With emphasis on performing the following tasks:
    1. Define/use Calendars, ON key word.
      1. Freedays
    2. Define/use Run Cycles, ON key word.
      1. Freedays
    3. Utilize +/- days.
    4. Define critical jobs.
    5. Use time dependencies (at, until, deadline, every, UNITL, onuntil).
    6. Carryforward
    7. Use timezones.
    8. Use FOLLOWS dependencies.
    9. Use dependency resolution criteria.
    10. Use variable tables.
    11. Use resources.
    12. Use workstation, workstation class, pools, dynamic pools, shadow jobs.
    13. Draft (validto, validfrom)
    14. File dependency by using opens keyword.
    15. Use job stream limit.
  6. Given an event to monitor, define an event rule (with a specific event type and information that will be reported) that performs a specified action.
    With emphasis on performing the following tasks:
    1. Identify the event to be monitored.
    2. Identify type of event monitored, single event, set of events or sequence of events.
    3. Identify information that is used for correlating the change in the event.
    4. Identify the timing of monitoring.
    5. Identify the type of action(s) that will be performed (email, update file, perform command).
    6. Identify the information that will be included in the defined action.
    7. Define the action that will be performed.
  7. Given access to a TWS database create dependency objects so they can be added later to job streams.
    With emphasis on performing the following tasks:
    1. Define logical resources.
    2. Define prompts.
    3. Define parameters.
    4. Define variable tables.
    5. Define calendars.
  8. Given an existing Workload broker workstation and hosted dynamic agent and remote engine workstation, define dynamic jobs so that the dynamic jobs definitions are correctly added to the database.
    With emphasis on performing the following tasks:
    1. Define shadow jobs on the remote engine workstation by using different matching criteria.
    2. Define web services jobs on the dynamic agent.
      1. Use HTTP connection.
      2. Use HTTPS connection and configure the security certificates for Job Manager on the workstation where the job is to run.
    3. Define file transfer jobs on the dynamic agent.
      1. Use different protocols.
      2. Use different transferMode.
    4. Define database jobs on the dynamic agent.
      1. Use a custom database.
      2. Use DB2 or Oracle or Microsoft SQL Server.
      3. Specify JDBC jar class path.
      4. Specify username and password.
    5. Define J2EE jobs on the dynamic agent.
      1. Use different jms operation (send(with a message to be sent) /receive)
      2. Specify a user name and password.
      3. Specify a timeout.
    6. Define Java jobs on the dynamic agent.
      1. Use parameter key.
      2. Specify a jarPath.
    7. Define executable jobs on the dynamic agent by using the value attribute to specify the name and value of one or more arguments.
    8. Define XA jobs on the dynamic agent.
      1. Use target attribute to specify an option file.
      2. Specify a step.
    9. Define IBM i jobs on the dynamic agent.
    10. Define JCL jobs.
  9. Given a working TWS database and appropriate access, work with objects in the database via composer so that database objects are accurate.
    With emphasis on performing the following tasks:
    1. Extract objects from database by using extract/create.
    2. Replace objects in database by using replace/add.
    3. Use Modify to change properties of database objects.
    4. Set up composer connection parameters by using localopts, useropts, parameter file, or part of the command string.
    5. Manage objects in the database particularly (authenticate;edit;redo;rename)
    6. Set up command line options. MAESTRO_OUTPUT_STYLE;MAESTROCOLUMNS;MAESTROLINES
    7. Create/Modify variable tables.
  10. Given the appropriate access to the TWS database, create variables and local parametersso that they can be used as substitutes for repetitive values used when defining jobs, job streams and prompts.
    With emphasis on performing the following tasks:
    1. Define variable tables.
    2. Create variable definitions.
    3. Create local parameters (parms).
    4. Change the default variable table
    5. Set variable tables in workstations, job streams, and run cycles.
  11. Given a TWS,MDM, create logical resource definitions so that they can be referenced in other scheduling objects.
    With emphasis on performing the following tasks:
    1. Create a resource in the TWS dynamic scheduling database.
      1. Create a new logical resource.
      2. Define the resource type.
      3. Assign computers to the resource.
      4. Define the number of available units of the resource.
    2. Create a TWS resource.
      1. Assign a workstation.
      2. Assign a quantity.
  12. Given jobs that are required to run as existing local or domain Windows users, create the user objects in the TWS database so that jobs can be defined to run as the user.
    With emphasis on performing the following tasks:
    1. Specify user name (Computer\user, user, DOMAIN\user).
    2. Specify user password.
    3. Verify appropriate user rights are assigned to user on target workstation.
    4. Specify workstation (workstation can be blank).

Section 4: Monitor the workload

  1. Given a running IBM Tivoli Workload Scheduler V 8.6(TWS) network, monitor the workload by using appropriate tools (conman, Tivoli Dynamic Workload Console (TDWC)) so that it can be managed appropriately
    With emphasis on performing the following tasks:
    1. Check jobs in the plan.
    2. Check job streams in the plan.
    3. Check the hot list, the critical path.
    4. Check workstation status in the plan.
    5. Check event rules, triggered actions and operator messages.
    6. Identify reasons for unreleased dependencies (e.g. files, prompts, predecessors, ext. dependencies) and jobs not launching (e.g. unreleased dependency, fence, limit, priority).
  2. Given a TWS environment, by using TDWC, complete tasks to ensure the production workload runs as it should.
    With emphasis on performing the following tasks:
    1. Submit/cancel/release/hold/altpri/rerun jobs (priority GO/HI disregard limit) (priority is tie breaker - if more jobs are ready than limit allows, higher priority jobs run first.).
    2. Submit/cancel/release/hold/altpri job streams.
    3. Identify how to change password for a windows user for the production workload - altpass - not available in TDWC.
    4. Add/delete dependencies on jobs or job streams.
    5. Switch to a new master/manager.
    6. Change the number of available resources.
    7. Utilize planman deploy command.
  3. Given that TWS must be actively running jobs, review TWS processes, limits, and file systems so that TWS jobs launch.
    With emphasis on performing the following tasks:
    1. Review CPU job limit.
    2. Review *.msg file size.
    3. Review available disk space.
    4. Review fence limit.
    5. Review file system size.
    6. Review agent link statuses.
    7. Verify Symphony is current.
    8. List active TWS processes.
  4. Given proper TWS and/or eWAS authorization, manage eWAS and TWS processes, workstation states, and file sizes so that TWS jobs will run.
    With emphasis on performing the following tasks:
    1. Start TWS processes by using appropriate commands.
    2. Stop TWS processes by using appropriate commands.
    3. Start eWAS processes.
    4. Stop eWAS processes.
    5. Link/unlink TWS workstations.
    6. Switch TWS master to another TWS workstation.
    7. Change message file sizes by using evtsize.
    8. Manage the event processor.
    9. Set the limit and fence of workstations.
  5. Given a deployed TWS environment, monitor the CPU and IO utilization of TWS processes as well as the free space of relevant file systems so that TWS can remain operational and performing at capacity.
    With emphasis on performing the following tasks:
    1. Monitor file systems for free space.
    2. Monitor the CPU and IO utilization of TWS processes.
    3. Monitor network I/O.
  6. Given an existing TWS network, adjust platform specific parameters (file system size, network, CPU) so that the TWS installation is running at optimum performance and stability.
    With emphasis on performing the following tasks:
    1. Request file system space adjustment.
    2. Perform RDBMS maintenance and reorg.
    3. Identify and request additional CPU and I/O capacity.
    4. Identify network bottleneck and request network configuration change.
    5. Adjust mailman setup.
    6. Adjust eWAS internal configuration.
  7. Given that TWS operations may be managed locally, perform command line operations like adding or changing dependencies so that TWS operations perform as required.
    With emphasis on performing the following tasks:
    1. Identify active event rules.
    2. Identify job and job stream dependencies.
    3. Identify job durations.
    4. Identify job launch time.
    5. Identify cpu job and fence limits.
    6. Cancel jobs or job streams.
    7. Reply to prompts.
    8. Release jobs or job streams.
    9. Identify status of resources.
    10. Identify link status of agents (for dependency resolution).
    11. Change Windows user password.
    12. Add or delete job or job stream dependencies.

Section 5: Troubleshooting

  1. Given access to IBM Tivoli Workload Scheduler V 8.6(TWS) documentation, commands, and system logs, address TWS scheduling issues to ensure proper job throughput by using TWS.
    With emphasis on performing the following tasks:
    1. Address scheduled jobs not running correctly (for fault-tolerant agents (FTA)).
    2. Address scheduled jobs not running correctly (for dynamic agents).
    3. Address non-scheduled jobs (ad-hoc) not running correctly.
    4. Address job streams in ready, stuck, waiting, or hold states.
    5. Set TWS logging and tracing properties (for FTA).
    6. Set TWS logging and tracing properties (for dynamic agents).
    7. Locate and use TWS engine logs and trace files (for FTA).
    8. Locate and use TWS engine logs and trace files (for dynamic agents)
    9. Install and use "Engine Log Analyzer".
    10. Address Tivoli Workload Assurance jobs not running correctly.
  2. Given an upgrade, migration, or installation scenario, monitor for, diagnose, and solve any issues that may arise so that TWS can be successfully upgraded, migrated, or installed.
    With emphasis on performing the following tasks:
    1. Monitor installer for any issues that arise.
    2. Diagnose any failures that arise (installation logs in temp directory).
    3. Solve common installation, migration, upgrade issues (cannot find previous instance, TWS processes not down, etc.).
    4. Resume failed installation.
  3. Given a TWS installation and users with unnecessary or unwanted elevated privileges, address these security issues to propose a proper security configuration.
    With emphasis on performing the following tasks:
    1. Check log files for unauthorized activities.
    2. Check the plan and database audit log for unauthorized activities.
    3. Re-evaluate the users security requirements (with regard to privileges).
    4. Propose an updated security configuration.
  4. Given TDWC is installed and configured, resolve issues so that it is able to be utilized by users.
    With emphasis on performing the following tasks:
    1. Find the correct URL and port #.
    2. Ensure eWAS is running.
    3. Check that user is a valid TDWC user.
    4. Check that the engine is available on network.
    5. Check that the engine is available.
    6. Check user roles.
    7. Check workstation permissions.
  5. Given DBA and system administration privileges plus access to RDBMS and eWAS logs, diagnose and correct database issues such as no connection to the database, expired database user password and database being offline so that database issues which are adversely impacting TWS can be resolved.
    With emphasis on performing the following tasks:
    1. Address no connection to database.
    2. Address locking issues.
    3. Address database unavailable.
    4. Address expired password.
  6. Given a problem with eWAS, turn on tracing, review logs, and make changes to ensure eWAS is running properly.
    With emphasis on performing the following tasks:
    1. Update eWAS settings to fix error connecting to LDAP server. (changeSecurityProperties, ISC)
    2. Update eWAS settings to fix error connecting to database. (changeDataSourceProperties)
    3. Change heap settings due to out of memory errors.
    4. Turn on tracing to identify errors.
    5. Review the logs for errors.
    6. Ensure ports are correct. (showHostProperties).
    7. Change ports because of port conflict. (changeHostProperties).
  7. Given that an XA job is not running correctly, verify the XA settings so that jobs defined for extended agents run properly.
    With emphasis on performing the following tasks:
    1. Ensure that the hosting Agent has the appropriate binary available in the methods directory.
    2. Ensure that the methods directory has the appropriate settings.
    3. Verify the XA workstation definition for host and method.
    4. Change setting for XAs at different levels (local, global, job).
    5. Verify global and local option files settings in the methods directory.
    6. Identify hierarchy of settings. (inherited, but if identified, the most specific wins)
  8. Given that TWS job must launch jobs, review and resolve problems found in the .msg files, available disk space, TWS file system and TWS logs so that TWS engine issues that prevent jobs from launching are resolved.
    With emphasis on performing the following tasks:
    1. Review and resolveproblems seen regarding the size of .msg files.
    2. Review and resolve problems seen regarding the available disk space.
    3. Review and resolve problems seen regarding the file system size.
    4. Review and resolve problems seen in the TWSMERGE files in trace and logs directories
    5. Review and resolve problems seen in the SystemOut.log file.
    6. Review and resolve problems seen regarding the workstation definition.
    7. Review and resolve problems seen regarding the workstation localopts file.
    8. Review and resolve problems seen regarding the active TWS processes.
    9. Reset the FTA (if appropriate use conman resetFTA).
  9. Given access to TWS logs and job output, diagnose and correct system issues such as TWS failing to start or jobs not launching correctly so that operating system configuration issues which are adversely impacting TWS can be resolved.
    With emphasis on performing the following tasks:
    1. Resolve situation when TWS fails to start due to kernel maximum number of open files limit being exceeded either system wide or per process (e.g. nfile, maxfiles, maxfiles_lim) or ulimit max open files limit being exceeded.
    2. Resolve situation when error encountered on attempt by a TWS process to read a message file due to kernel file locks limit being exceeded (e.g. nflocks).
    3. Resolve situation when a job fails to run successfully, stdlist file contains the Unix error such as "Resource temporarily unavailable" or "fork failed". Kernel maximum number of processes (nproc) or ulimit max open processes limit being exceeded.
    4. Resolve situation when eWAS is using UCT instead of local time. Operating system time zone setting is not recognized by eWAS.
    5. Resolve situation when there is an error locating or accessing file (file permissions).
  10. Given a job scheduled on a pool or dynamic pool with resource allocation errors, find the resource allocation problem, so that TWS can run the job successfully.
    With emphasis on performing the following tasks:
    1. Check that computers are online.
    2. Check that agents are available.
    3. Check that logical resources are properly assigned and available.
    4. Check that the TWS master domain manager(MDM) or dynamic domain manager can contact the agent.
    5. Configure the TWS agent with an address that the MDM can reach.
  11. Given a production plan that is in error, or a FTA that has a corrupted Symphony, recover the plan so that TWS can resume running jobs.
    With emphasis on performing the following tasks:
    1. Check the health status of a FTA with the conman checkhealthstatus command.
    2. Reset the FTA by using the conman resetfta command.
    3. Log the completed job streams with the logman -prod command.
    4. Reset the plan with the ResetPlan command, but do not scratch it so that completed jobs are not repeated.
    5. Scratch the plan with the ResetPlan -scratch command, so that all new job streams are selected, but completed jobs repeat.
    6. Extend the plan so that a new Symphony is created, by using the JnextPlan command
    7. Use the RecoveryPlanProcedure script to automate the plan reset process.
    8. Unlock the planner database by using the planman unlock command.
  12. Given event rule actions that must be performed, review logs and configurations to resolve event rule issues to resume event rule defined actions.
    With emphasis on performing the following tasks:
    1. Review event definition.
    2. Review optmanls output for email settings, event rule deployment frequency setting, enEventDrivenWorkloadAutomation setting.
    3. Review SystemOut.log for event rule messages.
    4. Review event rule monmaneif.confconfig file.
    5. Review monmancache.dat and ssmcache.dat (should be 0 bytes).
    6. Issue startmon (starts the monman process) andstartevtproc (starts event processing ) or switchevtproc.
    7. Define simple action that updates a file.
    8. Review active event rule related processes (monman).
    9. Verify that WebSphere Application Server (WAS) process is active (appserver).
    10. Deploy the rules to the agents by using planman deploy.

Section 6: Administration

  1. Given the required privileges and a IBM Tivoli Workload Scheduler V 8.6(TWS) installation with a non-existing, invalid, or wrong production plan, perform the necessary actions so that a valid plan is available for TWS to process.
    With emphasis on performing the following tasks:
    1. Create the plan by using planmancrt.
    2. Unlock the plan.
    3. Extend the plan.
      1. Check current plan status (creation date, last extension, extension to, run number confirmed).
      2. Check current setting of the related global options (CS, CF, sd, etc.).
      3. Check FINAL stream.
      4. Extend the plan by using JnextPlan -for (or -from -until).
      5. Validate plan status by using planman show.
    4. Reset the preproduction plan by using planman reset.
    5. Reset the preproduction plan by using ResetPlan command.
  2. Given a TWS instance, remove old stdlist logs and perform db2 maintenance to maintain optimal disk utilization and performance.
    With emphasis on performing the following tasks:
    1. Remove old stdlist logs (rmstdlist).
    2. Perform db2 maintenance (dbrunstats, dbreorg, etc).
    3. Remove other log files (audit, atjobs, schedlog, trial, forecast).
  3. Given system administrator access to a TWS instance, remove old files so disk space utilization is managed.
    With emphasis on performing the following tasks:
    1. Remove aged archive plan (Symphony) files, Trial Plans and Forecasts (master domain manager(MDM) and backup master domain manager (BMDM)).
    2. Remove aged audit log files (MDM, BMDM, fault-tolerant agent (FTA)).
    3. Use rmstdlist to remove aged job stdlist files, NETMAN and TWSMERGE log/trace files (MDM, BMDM, FTA, DA).
    4. Remove trace files (r3batch, eWAS, java core) once they are no longer needed for problem determination purposes.
  4. Given a running TWS environment, integrate TWS with Tivoli Monitoring, IBM High Availability Cluster Multi-processing(HACMP), Microsoft Windows Cluster Services, or Tivoli Storage Manager so that TWS can forward status, perform in a cluster, or schedule backups.
    With emphasis on performing the following tasks:
    1. Install the TWS integration with Tivoli Monitoring by using the ITMconfig command.
    2. Integrate TWS with HACMP to do passive-active failovers of a FTA.
    3. Integrate TWS with Microsoft Cluster Service by installing the Windows Cluster Enabler and running the twsClusterAdm command.
    4. Integrate TWS with Tivoli Storage Manager by configuring the tsmxagent.opts file and creating a TSM workstation.
  5. Given a MDM, create a variety of trial and forecast plans so that the plans are correctly generated.
    With emphasis on performing the following tasks:
    1. Log in to the MDM with the specified user ID.
    2. Create a trial plan (the plan will be created based on the existing preproduction plan).
      1. Specify a file name for the file containing the trial plan.
      2. Specify -from -to.
      3. Specify -from and the length in days.
      4. Specify no parameters.
      5. From a command line installed on a workstation different from the MDM.
    3. Create a trial plan extension.
      1. Specify a file name for the file containing the trial plan.
      2. Specify -to.
      3. Specify the length in days.
      4. Specify no parameters.
      5. From a command line installed on a workstation different from the MDM
    4. Create a forecast plan (the plan will be created based on the definitions contained in the database).
      1. Specify a file name for the file containing the trial plan.
      2. Specify -from -to
      3. Specify -from and the length in days
      4. Specify no parameters
      5. From a command line installed on a workstation different from the (MDM)
      6. Setting the option enForecastStartTime to yes (it is assumed that the workload service assurance is enabled). By doing so the average run duration for each job is calculated based on all previous runs.
    5. Access historical plans by using set alternate plan or from CLI (setsym, listsym, listsym fore, listsym trial, setsym fore, setsym trial).
  6. Given a working TWS environment, prepare the environment and run reports and batch reports from the command line or the Tivoli Dynamic Workload Console (TDWC) so that outputs are correctly displayed.
    With emphasis on performing the following tasks:
    1. Set up the environment to run reports from the command line.
      1. Set the PATH and TWS_TISDIR variables by running one of the following scripts:./TWS_home/tws_env.sh for Bourne and Korn shells in UNIX./TWS_home/tws_env.csh for C shells in UNIXTWS_home\tws_env.cmd in Windows
      2. Set the global option MAESTRO_OUTPUT_STYLE to LONG to use full length (long) fields for object names.
      3. Change the date format by editing the date format local option stored in the localopts file.Run report commandreptr.
    2. Set up the environment to run batch reports from the command line.
      1. Extract the TWSBatchReportCli package available in the TWSBatchReportCli directory of the TWS installation image.
      2. If you are on a Unix platform ensure that the latest GNU version of tar (gtar) is installed to extract the files successfully.
      3. Make sure that you run the following commands in the directory where you extracted the files: On Unix/Linux, chmod -R +x *, chown -R username *, On Windows, setown -u username *where username is the TWS user that will run the reports.
      4. Configure the template file .\config\common.properties specifying the information to:-Connect to the database where the historical data are stored.-Set the date and time format, including the time zone.-Make available the report output on the URL specified in ContextRootUrl field.-Send the report output by using a mail.
      5. Customize the correspondingtemplate file under \reports\templates directoryby specifying:specify: The information to display in the report header, How to filter the information to display the expected result., The format and content of the report output.from a FTA defined in the local scheduling environment).
    3. Run a batch report.
      1. Use the -k parameter to override the values set for a parameter in the .\config\common.properties file.
      2. Select different output format (HTML,CSV,PDF/table or chart format).
    4. Run a Custom SQL report and make available the output of the report at a specified URL.
      1. Configure the ContextRootUrl parameter in the common.properties.
      2. Specify as output_report_dir a directory that points to the same HTTP directory specified in the ContextRootUrl.
      3. Select from database views to meet report requirements (JOB_HISTORY_V, JOB_STATISTICS_V, etc.).
    5. Configure the TDWC to access the databasesand view historical reports.
    6. From the TDWC run the supported reports selecting different output format (HTML,CSV/table or chart format).
  7. Given a running TWS environment, use the built-in utility commands to perform date calculations, start and stop the dynamic agent, and retrieve job information from inside a running job to keep TWS functioning properly.
    With emphasis on performing the following tasks:
    1. Compute the Julian date of the next work day by using the datecalc command.
    2. Set the availability of a dynamic agent within a logical resource by using the resource.sh command.
    3. Start the lightweight agent and JobManager daemon by running the StartUpLwa command.
    4. Stop the lightweight agent by running the ShutDownLwa command.
    5. Determine if a job's command is being run as a recovery job by using the jobinfo command.
    6. Find the directory by using the maestro command.
    7. Use other utility commands as needed (tws_inst_pull_info, morestdl, jobstdl, version, makecal) (Do not include report commands: use rep#, r11xtr, paxtract, caxtract, syxtract).
  8. Given a working TWS environment, identify what is needed to prepare for and recover from a disaster.
    With emphasis on performing the following tasks:
    1. Identify TWS, TDWC directories to be backed up if not using full system back up.
    2. Back up database objects by using composer commands.
    3. Back up eWAS configuration by using backupConfig.
    4. Install/restore TWS, TDWC and ensure directory specific data is available.
    5. Populate recovery database by using composer and datamigratecommands.
    6. Restore eWAS configuration by using restoreConfig.
    7. Ensure there is a workstation defined to be a short-term backup master/manager.
    8. Switch to an appropriate short-term backup master/manager by using switchmgr.
    9. Recover from a corrupt Symphony file on a FTA by using conman resetFTA.
  9. Given a working TWS environment, ensure that passwords are updated accurately to keep the environment running.
    With emphasis on performing the following tasks:
    1. Change useropts password (edit file, utilize composer, use changePassword).
    2. Change eWAS user password (manually editSecurityProperties, use changePassword).
    3. Change j2cPassword/database user password (manually edit SecurityProperties).
    4. Avoid the potential problems involved with manually editing SecurityProperties. (could set other passwords to "******").

Register for a test

Register for an IBM Certification test at Prometric and take a step into your future.

IBM at Prometric