Skip to main content

 
Professional certification

  >  
Certifications

  >  
Test information

Test 435: IBM Tivoli Workload Scheduler V8.4 Implementation


Overview Objectives Test Preparation

Section 1 - Planning

  1. Given a list of operating systems and their versions upon which TWS will be installed and database and WAS-required kernel patches and kernel configuration parameters, determine required patches and kernel parameters so that a list of patches and kernel parameters can be documented. With emphasis on performing the following steps:
    1. Determine required patches and kernel parameters
    2. Execute Unix command to determine version and patch
    3. Execute Windows command to determine version and patch

  2. Given a list of servers, their hardware specifications, and their roles in the TWS 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 steps:
    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 standardized naming convention document can be created. With emphasis on performing the following steps:
    1. Identify security access requirements
    2. Identify reporting requirements
    3. Identify operational requirements

  4. Given a customer's environment and requirements, WebSphere port application, and SSL requirements, document a TWS 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 TWS network topology document can be created. With emphasis on performing the following steps:

    5. Analyze TCP/IP network topology (including any firewall)
    1. Identify geographically remote servers (as well as time zones)
    2. Identify server operating systems
    3. Identify applications that will require extended agents
    4. Identify supported relational database requirements
    5. Identify Bootstrap Port

  5. Given a TWS network topology, determine a method of installation for each TWS Agent so that the installation method for each agent can be documented. With emphasis on performing the following step:

    6. Reference product documentation to determine a method of installation for each TWS Agent.
    1. Identify operating systems in environment
    2. Access to root or Administrator login
    3. Check file system space availability
    4. Check availability Mozilla or Firefox on Unix, Internet Explorer or Firefox or Mozilla on Windows.
    5. Determine Optional ISMP or Launchpad installation methods.
    6. Determine if Install Shield silent installation required
    7. Determine if command-line installation required
    8. Determine if Tier 2 command-line installation required

  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 step:
    1. Identify workflow steps
    2. Identify Time Zones
    3. Identify workflow step dependencies
    4. Assemble workflow

Section 2 - Installation

  1. Given a TWS network topology, install or select from a list of potential database servers (already existing), so that a TWS database instance can be created. With emphasis on performing the following steps:

    2. Select an existing local or remote relational database where the TWS master will connect
    1. Install a relational database
    2. Create the TWS database instance
    3. Create or identify the necessary tablespaces in the Oracle instance.

  2. Given an installation method, server and root/admin access, define user and group (if not already defined) and @locate installation package so that TWS can be installed. With emphasis on performing the following steps:
    1. Define user if needed
    2. Locate installation package
    3. Install TWS instance

  3. Given that a situation requires TWS to be uninstalled and reinstalled, backup necessary files and remove appropriate files and directories, so that TWS can be successfully reinstalled. With emphasis on performing the following steps:
    1. Review installation prerequisites
    2. Shut down all components of TWS.
    3. Back up TWS configuration files
    4. Uninstall TWS
    5. Remove TWS files and directories
    6. Reinstall TWS
    7. Verify that TWS network is working correctly

  4. Given that a TWS instance is installed, obtain the extended agent documentation and install media, configure the target server so that the extended agent can be installed on the hosting TWS instance. With emphasis on performing the following steps:
    1. Configure the target server
    2. Install the extended agent
    3. Configure the extended agent to connect to the target server

  5. Given the installation media and a supported TWS instance, perform the necessary steps to migrate to V8.4 so that the upgraded agent can be validated. With emphasis on performing the following steps:

    6. Select optional installation method per documentation
    1. Migrate TWS Instance
    2. Migrate TWS Framework users using migrfwkusr utility (only where TWS Connectors are deployed)
    3. Migrate TWS scheduling objects
    4. Re-enter user object passwords

  6. Given the install media and a list of workstations on which the Job Scheduling Console or Tivoli Dynamic Workload Console is to be installed, run the installation so that the console is successfully installed on each workstation. With emphasis on performing the following steps:
    1. Select installation method (ISMP, ISMP/silent)
    2. Install the Job Scheduling Console
    3. Install the Tivoli Dynamic Workload Console if needed

  7. Given a customer's environment, TWS 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 TWS for application agents can be operational. With emphasis on performing the following steps:
    1. Identify SAP transports needed
    2. Identify R/3 batch user ID and passwords
    3. Identify PeopleSoft batch processing ID
    4. Identify Oracle $APPL_TOP and related directories/files
    5. Identify media for installation on zOS
    6. Identify media for TWS distributed host
    7. Import SAP transport and correction files
    8. Create R/3 transport and correction files
    9. Create R/3 security profiles
    10. Create PeopleSoft batch processing ID
    11. Verify that the agent and workstation are connected and working properly
    12. Create and configure options files for specific access method, PeopleSoft, SAP, Oracle, or z/OS

Section 3 - Configuration

  1. Given administrative access to the Master Domain Manager, add Sfinal and run JnextPlan so that a current plan can be created. With emphasis on performing the following steps:
    1. Composer add Sfinal
    2. Run JnextPlan

  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 steps:
    1. Customize jobmanrc.cmd (Windows)
    2. Create and customize .jobmanrc (UNIX)
    3. Create Windows users (Windows)

  3. Given administrative access to the TWS security functions, update the TWS security configuration so that TWS access is limited by identified user roles and responsibilities. With emphasis on performing the following steps:
    1. Configure TWS Security file
    2. Configure LDAP login authentication for the TWS console
    3. Configure DB2 security
    4. Configure WebSphere Application Server security

  4. Given access to a TWS instance, modify configuration so that TWS is configured and tuned. With emphasis on performing the following steps:
    1. Modify globalopts as needed
    2. Modify localopts
    3. Modify netconf
    4. Enable time zones for upgrades
    5. Set audit levels
    6. Edit BmEvents.conf and configure event logging (Plus Module, magent, etc.)
    7. Configure Unix remote or Unix local method as needed
    8. Configure TWS using optman utility

  5. Given an installed extended agent and access to a target application server, configure option files so that the extended agent is operational. With emphasis on performing the following step:
    1. Configure extended agent option files (global and local XA option files)
    2. Configure extended agent in TWS GUI

  6. Given that the relational database environment changes, update the TWS connection to the relational database so that TWS is operational. With emphasis on performing the following step:
    1. Run showDatabaseProperties.sh to extract current relational database properties.
    2. Update relational database properties
    3. Run changeDatabaseProperties.sh to set current relational database properties.

  7. Given showHostProperties output, root user access (Unix). Administrator access (Windows), perform the required modifications, so that the WebShpere connection is updated. With emphasis on the following steps:
    1. Locate wastools subdirectory
    2. Run showHostProperties and capture output to a text file
    3. Edit text file to update WebSphere connection properties, including passwords
    4. Run changeHostProperties, passing modified text file as argument.

Section 4 - Scheduling and Operations

  1. Given access to the TWS database, define scheduling objects so that jobs can be scheduled. With emphasis on performing the following steps:
    1. Define parameters
    2. Define users
    3. Define jobs
    4. Define calendars
    5. Define resources
    6. Define prompts
    7. Define job streams

  2. Given production requirements, schedule production jobs so that production objectives are met. With emphasis on performing the following steps:
    1. Schedule production job streams.
    2. Add dependencies.
    3. Define event driven objects

  3. Given customer operational monitoring requirements, describe how to perform tasks so that the customer monitoring objectives are met. With emphasis on performing the following steps:
    1. Perform operational monitoring tasks (views, filters, state, CLI filters etc.)
    2. Configure NetView integration

  4. Given operational scheduling requirements, describe how to perform tasks so that production objectives are met. With emphasis on performing the following steps:
    1. Cancel a production job that is not executing
    2. Cancel a production job that is executing
    3. Kill a production job
    4. Add/delete production job dependencies
    5. Release a production job submitted with priority 0
    6. Use fence to prioritize production jobs
    7. Use limits to prioritize production jobs
    8. Release resources
    9. Release dependencies
    10. Adhoc submit existing jobs and jobs streams
    11. Adhoc submit jobs and job streams
    12. Rerun jobs and job streams
    13. Resubmit job and job streams
    14. Set alternate plan

  5. Given customer reporting requirements, schedule jobs so that reporting objectives are met. With emphasis on performing the following step:
    1. Schedule jobs to run reports.

  6. 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 steps:
    1. Determine if switchmgr will be temporary or permanent
    2. Validate prerequisites are in place to run the switchmgr command
    3. Run the switchmgr command (temporary and permanent)
    4. Switch switchmgr back to original master

Section 5 - Administration and Maintenance

  1. Given access to a TWS instance, administer the instance so that production objectives can be met. With emphasis on performing the following steps:
    1. Unlink, link, stop, and start TWS Workstation
    2. Changing TWS user password
    3. Define a new workstation
    4. Add new Windows users
    5. Modify users and roles in the Security file
    6. Migrate objects from one workstation to another
    7. Change limit, fence
    8. Use TWS CLI conman and composer commands

  2. Given access to a TWS instance, maintain the instance so that production objectives can be met. With emphasis on performing the following steps:
    1. Check current TWS patch level
    2. Upgrade TWS patches
    3. Apply TWS interim fix
    4. Monitor TWS filesystem consumption
    5. Backup and restore TWS scheduling objects and critical files
    6. Remove old schedlogs and audit logs on a daily basis (MDM and BKM only)
    7. Use rmstdlist to maintain logs
    8. Backup TWS 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 steps:
    1. Changing passwords
    2. Backup 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. Determining location of application server scripts
    7. Stopping and starting 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 steps:
    1. Change password
    2. Verify database connectivity
    3. Backup 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 TWS environment variables sourced, authorized user logon, active WAS, established database access, plan start, end, or duration, optionally time zone, running embedded WebSphere, and running database connection, perform an execution of JnextPlan, so that the production plan is refreshed.

    6. With emphasis on the following steps:
    1. Run “optman ls” to determine connections to WebSphere and database are active
    2. Use db2start if db2 is down
    3. Use startwas if WebShphere is down
    4. Analyze JnextPlan joblog (if jnextplan abended)
    5. Run JnextPlan with appropriate start, stop and duration arguments
    6. Use ResetPlan -scratch to reset the production objects

  6. Given an existing TWS environment, sourced TWS environment variables, and authorized user, verify the status, start, stop or restart TWS processes so that the TWS network remains operational.

    7. With emphasis on the following tasks:
    1. Run on Unix to check for active TWS processes and ownership
    2. Run task manager or use listproc on windows to check for active tws processes
    3. Execute conman “stop;wait” on Unix and windows to stop tws processes
    4. Execute TWShome\shutdown to stop TWS services on windows
    5. Execute TWShome\StartUp on Unix and Windows to start TWS processes
    6. Execute conman start to start BATCHMAN process
    7. Use ls -l to determine ownership and permissions on Unix
    8. Check logon type of all TWS Windows Services

Section 6 - Troubleshooting

  1. Given a failed TWS instance installation, troubleshoot the install process so that the TWS installation completes successfully. With emphasis on performing the following steps:
    1. Review all install logs
    2. Recover from a failed installation step
    3. Verify that TWS processes are running
    4. Run a test job

  2. Given issues with the TWS production plan, diagnose and resolve the issues so that TWS production runs as expected. With emphasis on performing the following steps:
    1. Verify that the FINAL job stream completed successfully
    2. Verify that TWS key processes are running
    3. Review the TWS_MERGE log
    4. Review the job logs for the jobs in the FINAL job stream
    5. Verify that all agents were initialized with the current Symphony file
    6. Run conman ”sc” to verify connectivity and run number
    7. Run conman “sj @#@” and verify that the command completes successfully
    8. Run ResetPlan –scratch command
    9. Run Planman command

  3. Given issues with TWS connectivity diagnose and resolve the issues so that TWS connections function as expected. With emphasis on performing the following steps:
    1. Verify connectivity (linking, ports, netstat, netman, telnet etc.) to all TWS agents
    2. Verify connectivity to WebSphere Application Server
    3. Verify connectivity to the RDBMS
    4. Run conman “sc;l” to verify node
    5. Use TCP/IP networking commands to troubleshoot connectivity
    6. Verify DNS name resolutions
    7. Check logon type and password for TWS services on Windows

  4. 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 steps:
    1. Identify the internal status of the job that is not running as expected
    2. Validate the logon used to run the job
    3. Validate access to the executable using the logon (check permissions and file path)
    4. Browse the job log for abended jobs
    5. Browse TWSmerge logs for failed jobs
    6. Check job dependencies
    7. Check job stream dependencies
    8. Review the TWSmerge log

  5. Given access to database user and authorized TWS user accounts, analyze logs, processes and status related to database and WebSphere, so that an active, running database and WebSphere connection with TWS is restored. With emphasis on the following steps:
    1. Run planman "show info" and optman ls to verify WebSphere and database connections.
    2. Analyze database and WebSphere logs for error diagnostic messages.
    3. Log in as database and WebSphere logs for error diagnostic messages.
    4. Run showDatabaseProperties.sh (Unix) or showDatabaseProperties.cmd (Windows) and store output in a text file.
    5. Modify text file as necessary to update database connection properties if they have changed.
    6. Run changeDatabaseProperties.sh (Unix) or changeDatabaseProperties.cmd (Windows), passing modified text file as argument to configure database connection properties.
Test registration

Authorized Prometric test centers (worldwide testing)