Skip to main content

  alt="" height="6"
Professional certification
 alt="" height="6"
  >  
Certifications

  >  
Test information

Test 888: IBM Tivoli Workload Scheduler V8.3 Implementation


Overview Objectives alt="" height="1" width="30" Test Preparation

Section 1 - Planning

  1. Given a customer's environment and 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:
    1. Analyze TCP/IP network topology
    2. Identify geographically remote servers (as well as time zones)
    3. Identify server operating systems
    4. Identify applications that will require extended agents
    5. Identify supported relational database requirements

  2. Given a list of operating systems and their versions upon which TWS will be installed, determine required patches and kernel parameters so that a list of patches and kernel parameters can be documented. With emphasis on performing the following step:
    1. Determine required patches and kernel parameters

  3. 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.

  4. 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 requirements
    2. Identify reporting requirements
    3. Identify operational requirements

  5. Given the customer's production run cycle, analyze the workflow so that an optimal 'start of day' time can be determined. With emphasis on performing the following step:
    1. Analyze the workflow.

  6. 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:
    1. Reference product documentation to determine a method of installation for each TWS Agent.

Section 2 - Installation

  1. Given an installation method, server and root/admin access, define user (if needed) 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 agent

  2. Given that a TWS agent 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 agent. With emphasis on performing the following steps:
    1. Configure the target server
    2. Install the extended agent

  3. Given the install media and a list of workstations on which the TWS Console (Job Scheduling 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, TCM)
    2. Install the TWS Console

  4. Given that a situation requires TWS to be 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. Back up TWS configuration files
    3. Uninstall TWS
    4. Remove TWS files and directories
    5. Reinstall TWS

  5. Given the installation media and a supported TWS agent, perform the necessary steps to upgrade to V8.3 so that the upgraded agent can be validated. With emphasis on performing the following steps:
    1. Select installation method (ISMP, ISMP/silent, twsinst)
    2. Upgrade TWS Agent
    3. Migrate TWS Framework users using migrfwkusr utility (only where TWS Connectors are deployed)

  6. Given a TWS network topology and a list of potential database servers, select a local or remote relational database server so that a TWS database instance can be created.

    7. With emphasis on performing the following steps:
    1. Select a local or remote relational database server to install a TWS database instance
    2. Create  the TWS database instance

Section 3 - Configuration

  1. Given a valid user ID/password and a list of environment variables to set, customize the customer’ s scheduling environment so that jobs runs as expected. With emphasis on performing the following steps:
    1. Set user default shell to ksh (UNIX)
    2. Customize jobmanrc
    3. Customize .jobmanrc (UNIX)

  2. Given access to a TWS agent, modify configuration so that TWS is configured and tuned. With emphasis on performing the following steps:
    1. Modify globalopts
    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.)

  3. 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. Validate prerequisites are in place to run the switchmgr command
    2. Run the switchmgr command

  4. Given an installed extended agent and access to a target application, configure option files so that the extended agent is operational. With emphasis on performing the following step:
    1. Configure extended agent option files

  5. 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. Add Sfinal
    2. Run JnextPlan

  6. 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.

    7. With emphasis on performing the following steps:
    1. Configure Security file
    2. Configure LDAP login authentication for the TWS console
    3. Configure DB2 security
    4. Configure WebSphere Application Server security

  7. 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. Use wastools utilities to update the TWS relational database connection.

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 step:
    1. Define database objects.

  2. Given production requirements, schedule production jobs so that production objectives are met. With emphasis on performing the following step:
    1. Schedule production jobs.

  3. 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.

  4. Given customer operational monitoring requirements, describe how to perform tasks so that the customer monitoring objectives are met. With emphasis on performing the following step:
    1. Describe how to perform operational monitoring tasks (views, filters, state, CLI filters etc.)

  5. Given operational scheduling requirements, describe how to perform tasks so that production objectives are met. With emphasis on performing the following steps:
    1. Describe how to perform operational scheduling tasks
    2. Cancel a job that is not running
    3. Cancel a job that is running
    4. Kill a job
    5. Add/delete job dependencies
    6. Release a job submitted with priority 0
    7. Fence jobs
    8. Schedule and workstation limits
    9. Release resources
    10. Submit jobs and schedules
    11. Rerun jobs

Section 5 - Administration and Maintainance

  1. Given access to a TWS agent, administer the agent so that production objectives can be met. With emphasis on performing the following steps:
    1. Unlink and stop TWS
    2. Change TWS user password
    3. Define a new workstation
    4. Add new Windows users
    5. Add new users to the Security file
    6. Migrate objects from one workstation to another
    7. Change limit, fence, priority

  2. Given access to a TWS agent, maintain the agent so that production objectives can be met. With emphasis on performing the following steps:
    1. Upgrade TWS agent to current patch level
    2. Apply TWS interim fix
    3. Monitor TWS filesystem consumption
    4. Backup and restore TWS scheduling objects and critical files
    5. Remove old schedlogs and audit logs on a daily basis (MDM and BKM only)
    6. Backup TWS security configuration
    7. Schedule rmstdlist on all TWS agents

  3. 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. Backup and restore the relational database
    3. Reorganize the relational database
    4. Change relational database hostname and port
    5. Run required relational database scripts as necessary

  4. 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. Backup and restore application server configuration files
    2. Modify application server hostname or TCP/IP ports
    3. Modify security settings
    4. Update the application server Windows service after modifications

Section 6 - Troubleshooting

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

  2. 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 error messages and the exit code
    5. Check job dependencies
    6. Check job stream dependencies
    7. Review the TWS_MERGE log

  3. 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. Review the TWS_MERGE log
    3. Review the job logs for the jobs in the FINAL job stream
    4. Verify that all agents were initialized with the current Symphony file
    5. Run conman “sj @#@” and verify that the command completes successfully

  4. 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
Test registration

Authorized Prometric test centers (worldwide testing)