Test 000-021: IBM Tivoli Workload Scheduler V8.5 Implementation

Section 1: Planning

1. Given a list of operating systems, their versions upon which IBM Tivoli Workload Scheduler will be installed, database, WebSphere Application Server (WAS)-required kernel patches, and kernel configuration parameters, determine required patch level and kernel parameters so that a list of patches and kernel parameters can be documented.


With emphasis on performing the following tasks:

1. Determine required operating system patches and kernel parameters.
2. Execute UNIX command to determine version and patch level.
3. Execute Windows command to determine version and patch level.


2. Given a list of servers, their hardware specifications, and their roles in the Tivoli Workload Scheduler network topology, identify available memory and disk space so that requirements for additional memory and disk space can be documented.


With emphasis on performing the following tasks:

1. Identify available memory and disk space.
2. Determine if additional memory and disk space is required.


3. Given a customer's organizational structure, applications, and existing naming conventions, identify security, reporting, and operational requirements so that a Standards and Procedures document can be created.


With emphasis on performing the following tasks:

1. Identify security access requirements.
2. Identify reporting requirements.
3. Identify operational requirements.


4. Given a customer's environment and requirements, WebSphere application and SSL requirements, document an IBM Tivoli Workload Scheduler network layout, including all networks, geographical locations, time zones, servers, and applications such as SAP, Oracle, z/OS, and PeopleSoft extended agents so that a Tivoli Workload Scheduler network topology document can be created.


With emphasis on performing the following tasks:

1. Analyze TCP/IP network topology (including any firewall).
2. Determine the network name resolution and bandwidth are appropriate.
3. Identify geographically remote servers (as well as time zones).
4. Identify server operating systems.
5. Identify the appropriate requirements for databases.
6. Identify the appropriate requirements for WAS.
7. Identify the critical workload and the requirements for availability.
8. Identify applications that will require extended agents.
9. Identify network ports.
10. Determine the number of users who can access the Tivoli Dynamic Workload Console.


5. Given an IBM Tivoli Workload Scheduler network topology, determine a method of installation for each Tivoli Workload Scheduler agent so that the installation method for each agent can be documented.


With emphasis on performing the following tasks:

1. Reference product documentation to determine a method of installation for each Tivoli Workload Scheduler agent.
2. Identify operating systems in environment.
3. Obtain access to root or Administrator login.
4. Verify file system space availability.
5. Verify availability of suitable Web interface.
6. Determine installation methods.


6. Given the customer's production run cycle, analyze the workflow so that an optimal 'start of production cycle' time can be determined.


With emphasis on performing the following tasks:

1. Identify workflow steps.
2. Identify Time Zones.
3. Identify workflow step dependencies.
4. Assess workflow.

Section 2: Installation

1. Given an IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler) network topology, install or select from a list of potential database servers (already existing) so that a Tivoli Workload Scheduler database instance can be created.


With emphasis on performing the following tasks:

1. Install or select an existing local or remote database server where the Tivoli Workload Scheduler master will connect.
2. Specify the Tivoli Workload Scheduler database instance.
3. Ensure that the Oracle prerequisites are met.


2. Given an installation method, server, and root/admin access, define install user and group (if required), locate installation package, and define workstation and domain objects so that IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler can be installed and connected.


With emphasis on performing the following tasks:

1. Define user if needed.
2. Locate installation package.
3. Identify installation method.
4. Install Tivoli Workload Scheduler instance.
5. Define workstations and domain objects as appropriate.


3. Given that a situation requires IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler to be uninstalled and reinstalled, back up necessary files and remove appropriate files and directories so that Tivoli Workload Scheduler can be successfully reinstalled.


With emphasis on performing the following tasks:

1. Review installation prerequisites.
2. Shut down all components of Tivoli Workload Scheduler.
3. Back up Tivoli Workload Scheduler configuration files.
4. Uninstall Tivoli Workload Scheduler.
5. Remove Tivoli Workload Scheduler files and directories.
6. Reinstall Tivoli Workload Scheduler.
7. Verify that Tivoli Workload Scheduler network is working correctly.


4. Given that an IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler instance is installed, obtain the extended agent documentation and installation media, configure the target application so that the extended agent can be installed on the hosting Tivoli Workload Scheduler instance.


With emphasis on performing the following tasks:

1. Ensure the configuration of the target application is completed.
2. Install the extended agent.


5. Given the installation media and a supported IBM Tivoli Workload Scheduler instance, perform the necessary steps to migrate to V8.5 so that the upgraded agent can be validated.


With emphasis on performing the following tasks:

1. Select optional installation method per documentation.
2. Migrate the Tivoli Workload Scheduler instance.
3. Migrate the Tivoli Workload Scheduler Framework users, if necessary.
4. Migrate the Tivoli Workload Scheduler scheduling objects.
5. Migrate the Tivoli Workload Scheduler Security file.
6. Re-enter user object passwords.


6. Given the installation media and a list of workstations on which the Job Scheduling Console (JSC) or Tivoli Dynamic Workload Console (TDWC) is to be installed, run the installation so that the console is successfully installed on each workstation.


With emphasis on performing the following tasks:

1. Determine the architecture for the use of TDWC.
2. Start Launchpad.
3. Select installation method.
4. Install the JSC.
5. Install the TDWC.


7. Given a customer's environment, IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler documentation, and the need to schedule jobs through extended agents (SAP, Oracle, z/OS, and PeopleSoft), install and configure the required agents so that a Tivoli Workload Scheduler for application agent can be operational.


With emphasis on performing the following tasks:

1. Identify SAP transports needed.
2. Identify R/3 batch user ID and passwords.
3. Identify PeopleSoft batch processing ID.
4. Identify Oracle-related directories and files.
5. Identify media for installation on z/OS.
6. Identify media for Tivoli Workload Scheduler distributed host.
7. Ensure SAP transport and correction files were imported.
8. Ensure R/3 security profiles were created.
9. Ensure PeopleSoft batch processing ID was created.

Section 3: Configuration

1. Given administrative access to the Master Domain Manager (MDM), add final schedule and create production plan so that a current plan is created.


With emphasis on performing the following tasks:

1. Ensure IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler) processes are started.
2. Verify a connection to the RDBMS.
3. Verify Start of Day.
4. Verify Final Start Time.
5. Verify the Time Zones defined for Master.
6. Verify default plan length.
7. Add final schedule to database.
8. Create production plan.
9. Verify that the production plan has been correctly generated.


2. Given a valid user ID/password and a list of environment variables to set, customize the customer’s scheduling environment so that jobs run as expected.


With emphasis on performing the following tasks:

1. Customize the Windows environment.
2. Customize UNIX environment.
3. Create Windows users (Windows).


3. Given administrative access to the IBM Tivoli Workload Scheduler security functions, update the Tivoli Workload Scheduler Security and WebSphere configuration so that Tivoli Workload Scheduler access is defined by identified user roles and responsibilities.


With emphasis on performing the following tasks:

1. Configure Tivoli Workload Scheduler Security file.
2. Configure WebSphere Application Server security.
3. Modify the local options file.
4. Confirm that user options file has been created and is correct.


4. Given administrative access to Tivoli Workload Scheduler, configure Tivoli Workload Scheduler so that Tivoli Workload Scheduler works with LDAP.


With emphasis on performing the following tasks:

1. Set the Tivoli Workload Automation environment.
2. Find the WebSphere tools directory.
3. Identify the LDAP Server properties information.
4. Modify the WebSphere settings on the Tivoli Workload Scheduler configuration.
5. Update the Security file.
6. Verify the settings are correct.


5. Given access to a Tivoli Workload Scheduler instance, modify configuration so that Tivoli Workload Scheduler is configured and tuned.


With emphasis on performing the following tasks:

1. Modify global options as needed.
2. Modify local options file.
3. Modify Tivoli Workload Scheduler services configuration.
4. Enable time zones for upgrades.
5. Set audit levels.


6. Given an installed extended agent (XA) and access to a target application server, configure option files so that the extended agent is operational.


With emphasis on performing the following tasks:

1. Identify settings for option files.
2. Configure extended agent option files (global and local XA option files).
3. Configure extended agent in Tivoli Workload Scheduler GUI and the command-line interface.
4. Verify that the agent and workstation are connected and working properly.


7. Given that the relational database environment changes, update the Tivoli Workload Scheduler connection to the relational database so that Tivoli Workload Scheduler is operational.


With emphasis on performing the following tasks:

1. Extract current relational database properties.
2. Update relational database properties.
3. Set current relational database properties.


8. Given a running MDM or Backup MDM, root user access (UNIX) or Administrator access (Windows), perform the required modifications so that the WebSphere connection is updated.


With emphasis on performing the following tasks:

1. Set the Tivoli Workload Automation environment or locate WebSphere tools subdirectory.
2. Capture host properties.
3. Edit captured host properties.
4. Apply changes to host properties.


9. Given a list of backup domain managers and backup masters, execute the switch manager command so that the backup server becomes the active server.


With emphasis on performing the following tasks:

1. Determine the extent of the switch required.
2. Determine if switch will be temporary or permanent.
3. Validate prerequisites are in place to run the switch command.
4. Run the switch commands (temporary and permanent).
5. Validate that the original manager is in place to resume control.
6. Switch back to original master or domain manager.


10. Given a requirement to run a job with specific environment settings, configure Tivoli Workload Scheduler so that the job runs correctly.


With emphasis on performing the following tasks:

1. Configure workstation specific environment.
2. Configure user specific environment.

Section 4: Scheduling and Operations

1. Given CLI access to the IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler) database, define scheduling objects so that jobs can be scheduled.


With emphasis on performing the following tasks:

1. Define global variables and local parameters.
2. Define users.
3. Define jobs.
4. Define calendars.
5. Define resources.
6. Define prompts.
7. Define workstation classes.
8. Define job streams.
9. Define variable tables.
10. Define event rules.


2. Given Job Scheduling Console (JSC) access to the Tivoli Workload Scheduler database, define scheduling objects so that jobs can be scheduled.


With emphasis on performing the following tasks:

1. Define global parameters.
2. Define users.
3. Define jobs.
4. Define calendars.
5. Define resources.
6. Define prompts.
7. Define workstation classes.
8. Define job streams.


3. Given Tivoli Dynamic Workload Console (TDWC) access to the Tivoli Workload Scheduler database, define scheduling objects so that jobs can be scheduled.


With emphasis on performing the following tasks:

1. Define global variables.
2. Define users.
3. Define jobs.
4. Define calendars.
5. Define resources.
6. Define prompts.
7. Define workstation classes.
8. Define job streams.
9. Define variable tables.
10. Define event rules.


4. Given production requirements, plan production job streams so that production objectives are met.


With emphasis on performing the following tasks:

1. Identify dependencies.
2. Plan event driven objects.
3. Determine which jobs are critical.
4. Identify appropriate run cycles.
5. Identify dependency resolution criteria.


5. Given customer operational monitoring requirements, perform tasks so that the customer monitoring objectives are met.


With emphasis on performing the following tasks:

1. Perform operational monitoring tasks.
2. Flag critical jobs through Workload Service Assurance.
3. Configure for NetView integration.
4. Configure for Tivoli Enterprise Console integration.
5. Configure for Tivoli Monitoring.


6. Given operational scheduling requirements, perform tasks using the CLI so that production objectives are met.


With emphasis on performing the following tasks:

1. Cancel a production job that is not executing.
2. Kill a production job.
3. Add/delete production job dependencies.
4. Release a production job submitted with priority 0.
5. Use fence to prioritize production jobs.
6. Use limits to prioritize production jobs.
7. Release resources.
8. Release dependencies.
9. Adhoc submit existing jobs and jobs streams.
10. Adhoc submit jobs and job streams.
11. Rerun jobs and job streams.
12. Re-submit job and job streams.
13. Work with operational plans.
14. Deploy event rule.


7. Given operational scheduling requirements, perform tasks using JSC so that production objectives are met.


With emphasis on performing the following tasks:

1. Cancel a production job that is not executing.
2. Kill a production job.
3. Add/delete production job dependencies.
4. Release a production job submitted with priority 0.
5. Use fence to prioritize production jobs.
6. Use limits to prioritize production jobs.
7. Release resources.
8. Release dependencies.
9. Adhoc submit existing jobs and jobs streams.
10. Adhoc submit jobs and job streams.
11. Rerun jobs and job streams.
12. Re-submit job and job streams.
13. Work with operational plans.


8. Given operational scheduling requirements, perform tasks using TDWC so that production objectives are met.


With emphasis on performing the following tasks:

1. Cancel a production job that is not executing.
2. Kill a production job.
3. Add/delete production job dependencies.
4. Release a production job submitted with priority 0.
5. Use fence to prioritize production jobs.
6. Use limits to prioritize production jobs.
7. Release resources.
8. Release dependencies.
9. Adhoc submit existing jobs and jobs streams.
10. Adhoc submit jobs and job streams.
11. Rerun jobs and job streams.
12. Resubmit job and job streams.
13. Work with operational plans.


9. Given customer reporting requirements, run reports so that reporting objectives are met.


With emphasis on performing the following tasks:

1. Run reports via command line.
2. Schedule jobs to run reports.
3. Run reports via the TDWC.


10. Given a working Tivoli Workload Scheduler environment, set up TDWC so that access is available.


With emphasis on performing the following tasks:

1. Create engine connection to appropriate Tivoli Workload Scheduler environment(s).
2. Share a created connection to other users.
3. Share tasks.


11. Given a working Tivoli Workload Scheduler environment, set up JSC so that access is available.


With emphasis on performing the following tasks:

1. Create engine connection to appropriate Tivoli Workload Scheduler environment(s).
2. Share a created connection to other users using.
3. Share views.

Section 5: Administration and Maintenance

1. Given access to an IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler) instance, administer the instance using the appropriate utility so that production objectives can be met.


With emphasis on performing the following tasks:

1. Unlink, link, stop, and start Tivoli Workload Scheduler workstation.
2. Change Tivoli Workload Scheduler user password.
3. Change the DB2 user password.
4. Define a new workstation.
5. Add new Windows users.
6. Modify users and roles in the Security file.
7. Migrate objects from one workstation to another.
8. Change limit and fence.


2. Given access to a Tivoli Workload Scheduler environment, maintain the environment so that production objectives can be met.


With emphasis on performing the following tasks:

1. Determine current Tivoli Workload Scheduler environment FixPack level.
2. Maintain Tivoli Workload Scheduler environment FixPacks.
3. Monitor Tivoli Workload Scheduler filesystem consumption.
4. Back up and restore Tivoli Workload Scheduler scheduling objects and critical files.
5. Maintain logs.
6. Back up Tivoli Workload Scheduler configuration.


3. Given access to the application server, maintain the application server so that production objectives can be met.


With emphasis on performing the following tasks:

1. Change passwords.
2. Back up and restore application server configuration files.
3. Modify application server hostname or TCP/IP ports.
4. Modify security settings.
5. Update the application server Windows service after modifications.
6. Determine location of application server scripts.
7. Stop and start application server.


4. Given access to a relational database, administer and maintain the relational database so that production objectives can be met.


With emphasis on performing the following tasks:

1. Change password.
2. Verify database connectivity.
3. Back up and restore the relational database.
4. Reorganize the relational database.
5. Change relational database hostname and port.
6. Run required relational database scripts as necessary.




5. Given a working Tivoli Workload Scheduler environment extend the plan so that the production plan is refreshed.


With emphasis on performing the following tasks:

1. Determine if connections to WebSphere and database are active.
2. Start DB2 if not active.
3. Start WebSphere if not active.
4. Run new plan options as necessary.


6. Given an existing Tivoli Workload Scheduler environment, sourced Tivoli Workload Scheduler environment variables, and authorized user, verify the health of the environment so that the Tivoli Workload Scheduler network remains operational.


With emphasis on performing the following tasks:

1. Verify status.
2. Start, stop, or restart Tivoli Workload Scheduler processes.
3. Make corrections if processes do not restart.


7. Given a working Tivoli Workload Scheduler environment, identify steps required to configure Tivoli Workload Scheduler so that Tivoli Workload Scheduler integrates with other IBM products.


With emphasis on performing the following tasks:

1. Identify the products that will be integrated with Tivoli Workload Scheduler.
2. Determine the integration mechanism for the identified product.
3. Perform the integration as specified.

Section 6: Troubleshooting

1. Given a failed IBM Tivoli Workload Scheduler (Tivoli Workload Scheduler) instance installation, troubleshoot the install process so that the Tivoli Workload Scheduler installation completes successfully.


With emphasis on performing the following tasks:

1. Review all install logs.
2. Recover from a failed installation step.
3. Verify that Tivoli Workload Scheduler processes are running.
4. Confirm the installation is complete.


2. Given issues with the Tivoli Workload Scheduler production plan, diagnose and resolve the issues so that Tivoli Workload Scheduler production runs as expected.


With emphasis on performing the following tasks:

1. Verify that the extension of the plan completed successfully.
2. Verify that Tivoli Workload Scheduler key processes are running.
3. Review logs.
4. Verify that all agents were initialized with the current Symphony file.
5. Verify connectivity and run number.
6. Run new plan options as necessary.


3. Given issues with Tivoli Workload Scheduler linking, diagnose and resolve the issues so that Tivoli Workload Scheduler connections function as expected.


With emphasis on performing the following tasks:

1. Verify connectivity to all Tivoli Workload Scheduler agents.
2. Verify node.
3. Use TCP/IP networking commands to troubleshoot connectivity.
4. Verify Tivoli Workload Scheduler services on Windows.
5. Analyze the appropriate logs.


4. Given issues with Tivoli Workload Scheduler WebSphere Application Server connectivity, diagnose and resolve the issues so that Tivoli Workload Scheduler connections function as expected.


With emphasis on performing the following tasks:

1. Verify WebSphere and database connections.
2. Use TCP/IP networking commands to troubleshoot connectivity.
3. Analyze appropriate logs.
4. Review connections properties.
5. Modify database connections properties if required.


5. Given that a job is not running as expected, diagnose and resolve the issue so that the job runs as expected.


With emphasis on performing the following tasks:

1. Identify the internal status of the job that is not running as expected.
2. Validate the job definition and compare to user environments.
3. Verify that logon user's environment is available when running Tivoli Workload Scheduler jobs.
4. Validate the logon used to run the job.
5. Validate access to the executable using the logon.
6. Review the appropriate log.


6. Given issues with the Tivoli Workload Scheduler event driven workload automation, diagnose and resolve the issues so that Tivoli Workload Scheduler event driven workload automation runs as expected.


With emphasis on performing the following tasks:

1. Verify the monitoring processes are active on required agents.
2. Verify the event rules have been deployed.
3. Verify that the appropriate event processor is active and monitoring the event rules.
4. Verify that event rule content is correct.
5. Verify the event has been received.
6. Verify the action mechanisms are in place.


7. Given issues with the Tivoli Dynamic Workload Console (TDWC), diagnose and resolve the issues so that TDWC runs as expected.


With emphasis on performing the following tasks:

1. Verify the WebSphere application is running.
2. Verify the TDWC URL.
3. Verify the WebSphere configuration for TDWC and Tivoli Workload Scheduler.
4. Verify the network connection between TDWC and Tivoli Workload Scheduler.
5. Analyze the WebSphere log and trace files.