C9560-517 - IBM Workload Automation V9.2 Implementation Practice Exam
C9560-517 - IBM Workload Automation V9.2 Implementation
About IBM Workload Automation V9.2 Implementation
This certification exam is designed for an individual who is responsible for planning, installing, configuring, customizing, troubleshooting, integrating, documenting, and transferring skills for an IBM Workload Automation V9.2 solution in a heterogeneous distributed (non z/OS) environment. This individual will be expected to perform these tasks with limited assistance from peers, product documentation, and support resources.
Prerequisite for the exam
The following qualifications are requirements for success:
• Knowledge of project plan development ( architecture, solution design, deployment environment analysis) - Skill level
• Knowledge of multi-platform systems (such as Linux/UNIX and Windows), including user accounts, file systems, and discs. - Skill level 3
• Knowledge of batch scheduling concepts in a production environment. - Skill level 3
• Knowledge of TWS for Applications and advanced job types - Skill level 2
• Knowledge of networking (TCP/IP, DNS, Firewall) - Skill level 2
• Knowledge of basic diagnosis of issues with IBM DB2 or Oracle RDBMS and the WebSphere Application Server. - Skill level 2
• Knowledge of IBM Installation Manager - Skill Level 2
• Knowledge of JazzSM and DASH - Skill Level 1
Course Outline
1. Planning and Installation
• Given a selection of servers with workload that requires managing, identify which roles each server will perform (master domain manager, agent, etc.), the components that need to be installed, and the interconnections so that IBM Tivoli Workload Scheduler (TWS) V9.2.0 can be correctly installed and configured.
With emphasis on performing the following tasks:
a. Determine the most appropriate topology.
b. Determine if other TWS instances or components exist on the servers.
c. Determine for the master domain manager / dynamic domain manager, the most appropriate RDBMS (DB2 or Oracle), where best to locate the RDBMS and High Availability any considerations.
d. Identify compatibility of OS platforms where TWS components are required to be installed.
e. Determine requisite components (MDM needs IM, WAS, RDBMS).
f. Determine implications of firewalls on the placement of TWS components.
g. Identify backups which need to be taken before beginning any installations.
h. Determine where components need to be installed (install paths, file systems that need to be creates / resized, file system mount options).
i. Determine authentication mechanism must appropriate to the existing user base.
j. Check the available installation media.
k. Determine any user's which need to be created prior to installation.
l. Determine if the Time Zone feature will be used.
m. Choose the most appropriate method for installing.
n. Collect the information necessary to complete the installation.
1. Database user
2. Install user and password.
• Given a requirement to install TWS on a compatible system, determine the system requirements to verify that TWS can be installed successfully.
With emphasis on performing the following tasks:
a. Check available disk space for component, installation, and run time.
b. Determine prerequisites:
1. Hardware
2. Operating System
3. Software
c. Determine path.
d. Determine RDBMS prerequisites:
1. Supported RDBMS
2. Determine if database/schema need to be created in advance or upgraded.
3. Database settings required by TWS installation.
• Given a running TWS environment plan integration with other Tivoli products So that the products will work well together.
With emphasis on performing the following tasks:
a. Plan to integrate TWS with Tivoli Monitoring Agent for Tivoli Workload Scheduler (ITM for TWS).
b. Plan to integrate TWS with Tivoli Endpoint manager (TEM).
c. Plan to integrate TWS with Tivoli System Automation for Multiplatform (TSAMP).
d. Plan to integrate dynamic workload broker with Tivoli Provisioning Manager (TPM).
e. Create actions that send events to SmartCloud control desk.
• Given a compliant system and access to TWS installation image(s), perform the necessary steps so that TWS is installed successfully.
With emphasis on performing the following tasks:
a. Download the software.
b. Create response files.
c. Encrypt user password for response file.
d. Determine if symbolic links will be used.
e. Create network repositories.
f. Install the Installation Manager.
g. Install the database:
1. Optionally create database and load schema in advance.
2. If required upgrade the TWS database tables
h. Install the WebSphere.
i. Install the master domain manager :
1. Interactive installation
2. Silent installation
j. Install Dynamic domain manager.
k. Install agents:
1. Install a fault-tolerant agent (FTA).
2. Install a Dynamic agent.
3. Install zCentric agent.
4. Install an extended agent.
l. Install in a clustered environment.
m. Install Tivoli Dynamic Workload Console (TDWC) including WebSphere and Jazz SM.
• Given an existing TWS environment at a lower release level upgrade to TWS 9.2.0 so that the TWS environment successfully upgraded to TWS 9.2.0 .
With emphasis on performing the following tasks:
a. Upgrade from 8.6.0:
1. Upgrade master domain manager.
2. Upgrade an agent.
b. Upgrade from 9.1.0:
1. Upgrade master domain manager.
2. Upgrade an agent.
c. Upgrade from an earlier release than 8.6.0:
1. Upgrade master domain manager.
2. Upgrade an agent.
d. Apply appropriate fixpack to instance.
• Given an installed TWS environment, and required service levels for execution of workload, plan for recovery in the event of a disaster affecting one of more components so that a disaster recovery plan is available.
With emphasis on performing the following tasks:
a. Prepare for loss of a domain manager due to hardware failure.
b. Prepare for loss of a master domain manager due to hardware failure.
c. Prepare for loss of TDWC.
d. Prepare for corrupt Symphony file.
e. Prepare for loss of database.
f. Prepare for loss of a FTA.
g. Prepare for loss of a dynamic agent.
h. Document disaster recovery plan.
• Given a successfully installed TWS workstation, complete the post installation configuration necessary
2. Configuration
• Given a fresh IBM Tivoli Workload Scheduler (TWS) installation, plan for configuration settings so that an Administrator has information to configure TWS environment.
With emphasis on performing the following tasks:
a. Determine ports for communication.
b. Decide what time will be the start of day.
c. Identify integration with other IBM Tivoli products.
• Given a completed installation, including TWS and Tivoli Dynamic Workload Console (TDWC), customize the components so that the configured software performs optimally and meets client requirements.
a. Customize WebSphere configuration, LPTA keys, heapsize, log size.
b. Configure z/OS Connector.
c. Change configuration parameters for the dynamic workload broker server.
d. Modify the values in the BrokerWorkstation.properties file.
e. Configure advanced settings in TdwcGlobalSettings.xml.
f. Set configuration details to enable the news notification beacon.
g. Configure the use of the Self-Service Catalog and Self-Service Dashboards mobile applications.
• Given a completed agent installation, configure the agent settings so that base performance, security, and feature availability requirements are met.
With emphasis on performing the following tasks:
a. Set the shell environment variables before configuring TWS components .
b. Customize and configure JobManagerGW.ini for opening communication between the gateway and the dynamic workload broker.
c. Customize and configure jobmanager.ini.
d. Customize and configure ita.ini.
e. Enable file monitoring on dynamic agent .
f. Edit jobmanrc / .jobmanrc / djobmanrc.cmd to customize how jobs are performed.
g. Customize localopts to tune fault-tolerant agent for better security and performance.
h. Load the user environment for native Windows jobs.
• Given a competed TWS installation, set the global options so that TWS performs as expected.
With emphasis on performing the following tasks:
a. Set the start of day.
b. Set the appropriate carry forward option.
c. Set auditing options.
d. Configure the option to automatically add workstations to the plan in the middle of the day.
e. Configure the option to automatically add a new windows user.
f. Configure for use of email by event rules.
g. Enable event driven workload automation proxy.
h. Configure workload service assurance.
i. Configure the OSLC service provider.
• Given a complete TWS master domain manager installation, create basic database definitions so that the base TWS network topology of domains is available.
With emphasis on performing the following tasks:
a. Migrate definitions from previous installations.
b. Create domains.
c. Define workstations.
d. Create domain managers/dynamic domain managers.
e. Define the backup domain managers/dynamic backup domain managers.
f. Set the time zone of the master domain manager workstation, of the backup master domain manager, and of any agents that are in a different time zone than the master domain manager.
g. Add the FINAL and FINALPOSTREPORTS job streams to the database.
3. Scheduling Objects
• Given a Tivoli Dynamic Workload Console (TDWC) instance, with proper user access rights to create objects and a command or executable item create advanced type job definitions so that scheduling object definitions are properly created.
With emphasis on performing the following tasks:
a. Log in to the TDWC or use the composer command.
b. Create job definitions:
1. Create shadow jobs
2. Create Web services jobs
3. Create file transfer jobs
4. Create SmartCloud provisioning jobs#Create J2EE jobs
5. Create datatabase jobs
6. Create java jobs
7. Create Executable jobs
8. Create remote command jobs
9. Create access method jobs
10. Create z/os jobs
11. Create IBM i jobs
12. Create OSLC Automation jobs
13. Create OSLC Provisioning jobs
14. Create SAP dynamic jobs
• Given the appropriate access to the IBM Tivoli Workload Scheduler (TWS) database, create variables so 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:
a. Log in to the Dynamic Workload Console or use the composer command.
b. Define variable tables.
c. Create variable definitions.
d. Create parameter definitions.
e. Change the default variable table.
f. Set variable tables in workstations, job streams.
g. Use parameters in job, job stream.
h. Reuse variable passing between jobs in the same job stream instance in dynamic scheduling environment.
• Given the appropriate access to the TWS database, create calendars so that they can be used in job stream definitions.
With emphasis on performing the following tasks:
a. Log in to the TDWC or use the composer command.
b. Create calendar definitions.
c. Use calendars in job stream definition.
d. Use makecal to create complex calendars.
• Given the appropriate access to the TWS database, create a run cycle group definition that can be used in a job stream.
With emphasis on performing the following tasks:
a. Log in to the TDWC or use the composer command.
b. Create a run cycle group definitions.
c. Use a run cycle group in a job stream definition.
d. Create run cycles in run cycle groups with Boolean AND logic.
• Given the appropriate access to the TWS database, create a job stream that contains multiple types of scheduling objects so that job stream has been created, saved and can be managed.
With emphasis on performing the following tasks:
a. Log in to the TDWC or use the composer command.
b. Create a job stream definition.
c. Add a set of jobs to a job stream definition.
d. Import a workload application using the wappman command
e. Create a mapping file for importing workload applications
• Given the appropriate access to the TWS database, create an event rule that can be used in event based scheduling so that an event rule definition can be created, saved, and added to a job stream.
With emphasis on performing the following tasks:
a. Log in to the TDWC or use the composer command.
b. Create an event rule definition.
c. Utilize the event rule in the execution of a job stream.
• Given a TWS instance, with proper user access rights to create objects, migrate a workload application so that a workload application can be exported and imported.
With emphasis on performing the following tasks:
a. Create workload Application Template in the TDWC.
b. Export the workload Application Template using TDWC
c. Customize the mapping file for the receiving the workload application.
d. Import the workload Application Template into a TWS instance using the wappman command.
• Given the appropriate access to the TWS database, create a job stream that contains scheduling objects so that it will be added to the production day or active cycle.
With emphasis on performing the following tasks:
a. Log in to the TDWC or use the composer command.
b. Add a run cycle group in a job stream definition.
c. Add a calendar in a job stream definition that would include the job stream in a future day.
d. Submit the job stream to add the job stream into the current production day.
4. Monitor the Workload
• Given an operational IBM Tivoli Workload Scheduler (TWS) and Tivoli Dynamic Workload Console (TDWC) instance, perform the necessary steps to successfully create an engine connection to TWS/d or TWS/z application from TDWC so that database reporting actions can be performed.
With emphasis on performing the following tasks:
a. Create a distributed engine.
b. Create a z/OS engine.
Given a running TWS V 9.2 network, monitor a batch workload environment by using TDWC panels or command line application (conman) so that plans can be monitored.
With emphasis on performing the following tasks:
a. Monitor Jobs.
b. Monitor Critical Jobs.
c. Monitor Job Streams.
d. Monitor Files.
e. Monitor Resources.
f. Monitor Prompts.
g. Monitor Event Rules.
h. Monitor Operator Messages.
i. Monitor Triggered Actions.
j. Monitor Workstations
k. Monitor Domains.
l. Monitor workload across multiple engines.
m. Monitor workload via conman.
n. Monitor Jobs on Broker.
o. Monitor Computers on Broker.
p. Monitor Logical Resources on Broker.
q. Monitor Resources groups on Broker.
5. Operations
• Given a running IBM Tivoli Workload Scheduler V 9.2 (TWS) network and agents, manage workstation settings, control job simultaneously run, control which jobs will run based on their priority, enable or disable workstations on the TWS environment so that workstations are managed.
With emphasis on performing the following tasks:
a. Change workstation limit.
b. Change the workstation fence.
c. Link / unlink Workstations.
d. List workstations.
e. Start / stop workstations.
• Given a running TWS V 9.2 network ,agents and scheduling objects, manage job priority run, view job log from either Tivoli Dynamic Workload Console (TDWC) or conman command line, list jobs on SAP and dynamic agents, perform direct query and change a user's password in plan using TDWC so that jobs are managed.
With emphasis on performing the following tasks:
a. Change the job priority.
b. Manage Jobs on SAP.
c. Manage SAP criteria profiles.
d. Manage jobs on Broker.
e. Manage Workload definitions.
f. Manage event rules.
g. Browse job log / stdlist.
h. Direct Query.
i. Alter user password in Plan.
• Given a running TWS environment leverage the workload service assurance so a client's requirement to map, monitor ,and alert critical jobs is satisfied.
With emphasis on performing the following tasks:
a. Enable & tune workload service assurance.
b. Use event processor's Job promoted and Job Risk Level Changed event.
c. Set a deadline and mark the job as critical.
d. Determine which jobs are at risk of missing deadlines.
e. Determine if a job has been promoted.
f. Determine if a job is on a critical path.
• Given a running TWS V 9.2 network and agents generate a new and functional plan so that a plan is built.
With emphasis on performing the following tasks:
a. Generate the plan with JnextPlan.
b. Manage the plan with JnextPlan (-noremove).
c. Manage the plan with ResetPlan, then regenerate.
• Given a running TWS V 9.2 network , agents, and scheduling objects, describe the basic commands TWS offers so that basic commands can be used to fix or resolve a user case scenario.
With emphasis on performing the following tasks:
a. Describe utility commands:
1. datecalc
2. cpuinfo
3. evtsize
4. jobprop
5. rmstdlist
b. Describe basic conman, commands:
1. showjobs
2. showcpus
3. rerun
4. submit
5. altpri
6. help
7. startappserver/stopappserver
8. startmon/stopmon
9. startbroker/stopbroker
10. startevtproc/stopevtproc
11. switchevtproc
c. Describe basic composer commands:
1. extract
2. list
3. display
4. delete
5. new
6. modify
7. add
8. replace
9. filter
d. Describe basic planman commands:
1. reset
2. crtfc
3. deploy
4. showinfo
5. confirm
6. unlock
7. exttrial
8. resync
9. checksync
• Given a running TWS V 9.2 network ,agents and scheduling objects, create plan, historical and custom SQL reports based on client's requirements, schedule a job to trigger a daily report and send it via e-mail so that reports have been created.
With emphasis on performing the following tasks:
a. Generate Historical reports.
b. Generate Plan Reports.
c. Generate Custom SQL reports.
d. Use batch reports command line tool.
• Given the need for using an alternate plan, use conman or Tivoli Dynamic Workload Console (TDWC) to generate a plan, access the plan and view data in the plan so that data can be viewed from the selected plan.
With emphasis on performing the following tasks:
a. Use archived production plan.
b. Generate a trial plan.
c. Generate a forecast plan.
d. Use conman or TDWC to list archived production, trial or forecast plans.
e. Use conman or TDWC to set the archived production, trial or forecast plan as current.
f. View preproduction plan.
• Given the need to manage job or job stream, use conman ,or TDWC to adjust or update the processing of jobs and job streams so that the workload is updated.
With emphasis on performing the following tasks:
a. Use conman or TDWC to add or remove job or job stream dependencies.
b. Use conman or TDWC to submit adhoc jobs, predefined jobs or job streams.
c. Use conman or TDWC to kill, cancel or confirm a job.
• Given TWS default features cannot address the user's requirement, extend the TWS capabilities utilizing open TWS interfaces so that the user's requirement is addressed.
With emphasis on performing the following tasks:
a. Implement the integration workbench:
1. Use JAVA API.
2. Use Web services interface.
b. Create custom job types.
c. Create custom event plugins.
d. Create a Java Job.
e. Use evtdef to extend the generic event plugin.
6. Administration
• Given a variety of scenarios with the plan and appropriate access/authority, manage the plan so that IBM Tivoli Workload Scheduler (TWS) continues to function properly.
With emphasis on performing the following tasks:
a. Identify available options for manipulating the plan:
1. JnextPlan
2. planman
3. ResetPlan
b. Utilize the appropriate option if:
1. Plan has unknown duration.
2. Plan has ended .Plan had to be refreshed with or without the -noremove.
3. Plan does not have current event rules deploy.
• Given a TWS environment with more than one instance installed and the current manager is unavailable, perform a TWS failover so that TWS continues to process workload.
With emphasis on performing the following tasks:
a. Identify possible backup managers.
b. Switch to backup manager.
c. Restore original manager.
d. Switch event processor.
e. Switch broker application.
• Given a working TWS environment, manage the message queues so that the message queues are managed.
With emphasis on performing the following tasks:
a. Plan space for message queues.
b. Monitor .msg files
c. Resize .msg files
d. mirrorbox.msg is responsible for synchronizing the symphony at the database.
e. Organize fault-tolerant agent (FTA) across multiple Mailman servers.
• Given a working TWS environment, identify the processes for the different components and their interactions so that the environment may be validated.
With emphasis on performing the following tasks:
a. Identify FTA processes.Workstation inter-process communicationBatchman, mailman, writer, jobman, netman
b. Identify event driven workload processes: monman; ssmagent.
c. Identify Agent processes.
d. Identify WAS DB TDWC.
• Given working TWS environment, perform maintenance so that disk space and performance are optimized.
With emphasis on performing the following tasks:
a. Remove files older then retention criteria.
1. Identify and remove files using rmstdlist.
2. Identify and manually remove files not handled by rmstdlist (audit, schedlog, trial and forecast plans, traces, cordump file).
3. configure log rotation on dynamic agents.MaxAge setting on dynamic agents
b. Utilize Event Rules to alert when system needs maintenance.
• Given a working TWS environment, configure authorization so that users have appropriate access.
With emphasis on performing the following tasks:
a. Configure security file access.
b. Set the user options required for each user on a workstation who needs them in the useropts file.
c. Assign roles for access to TWS functions within the TDWC.
• Given a working TWS environment, configure network security so that the TWA environment is secure.
With emphasis on performing the following tasks:
a. Replace default certificates with custom certificates.
b. Ensure that WebSphere Application Servers managing any Tivoli Workload Automation products have the same LTPA token_key.
c. Set connection security to enable SSL or GSKit for inter-component communications:
1. Agents
2. FTAs
3. Command line clients
4. DWC
5. TWS
• Given the need to manage the TWS database, use DB2 or Oracle commands and configuration tools so that the database is available.
With emphasis on performing the following tasks:
a. Use DB2 or Oracle to view predefined views in tabular form of data generated by a query.
b. Perform database tuning to optimize database.
c. Use DB2 db2stop or db2start to stop and start DB2 processes or Oracle Stop and start DB.
d. Change the password of the database instance owner (DB2) / database owner (Oracle)change the database host name, port, or database name.
• Given the need to manage WebSphere, use TWS specific WebSphere commands so that WebSphere is available.
With emphasis on performing the following tasks:
a. Perform WebSphere tuning for required changes.
b. Use conman stopappserv, startappserv or stopWas or startWas to stop and start WebSphere processes.
c. Verify appservman is running.
d. Start and stop all TWS processes including the event monitoring engine and the broker resource advisor.
e. Use conman commands startbroker or stopbroker commands or TDWC to stop and start dynamic workload broker.
• Given the need to manage Workload Scheduler, user TWS commands and configuration files manage the TWS and user environment so the TWS environment is available.
With emphasis on performing the following tasks:
a. Use conman command or TDWC to alter user password in plan.
b. Customize global, local, and user options (Perform localopts tuning).
c. Use startmon and stopmon commands to manage event rule processes.
• Given a working TWS environment, create, and troubleshoot an event rule deployment so that an active event rule is available.
With emphasis on performing the following tasks:
a. Use optman to check or configure event rule related global options.
b. Use startmon, stopmon, startevtproc, or stopevtproc commands to manage event rule processes.
c. Define event rule.
7. Troubleshooting
• Given a new or existing TWA environment locate required log files to resolve given issues with TWA processes, WebSphere or the Tivoli Dynamic Workload Console (TDWC) so that the log files are located.
With emphasis on performing the following tasks:
a. Locate installation logs.
b. Locate TWS Merge logs.
c. Locate TDWC logs.
d. Locate Websphere logs.
e. Identify potential problem with TWA processing issues.
f. Identify possible application server crash issue.
g. Determine location of log files for command line client.
h. Adjust log and trace levels.
• Given an existing IBM Tivoli Workload Scheduler (TWS) environment and all installed components, locate the properties file so that it can be determined which components are installed.
With emphasis on performing the following tasks:
a. Identify location of tws instance.
b. Determine what components have been installed.
c. Determine if Agent has Connector installed.
d. Determine if Agent has Connector and TDWC installed.
e. Adjust instance#.TWA.properties based on manual uninstall.
• Given an existing TWS environment and installed components, locate the registry file so that version verification, fixpack verification, Installation path, and
