|
Softpanorama |
May the source be with you, but remember the KISS principle ;-)
Softpanorama Search
|
TWS 8.4 is using embedded WebSphere like TWS 8.3. It provides integration with ITM 6.1 via the Tivoli
By Pete Meechan
Tivoli Workload Scheduler (TWS) 8.4 distributed builds upon the functionality provided by the previous TWS 8.3 release.
Architecturally built upon the same infrastructure as TWS 8.3 using embedded WebSphere and DB2 or Oracle, the major focus of TWS 8.4 is to provide:
- Event driven scheduling
- Web based reporting
- LDAP support for the Web interface
- Integration with ITM 6.1 via the Tivoli
- Enterprise Portal (TEP)
- Support for IP V6
- Support for DB2 V9.1 (bundled)
- Event Rule Definition
Event Driven Scheduling
TWS 8.4 includes support for scheduling based upon real time events in addition to the more common calendar based scheduling. Event driven scheduling is supported as a component part of TWS 8.4 without having any dependency on additional products. Event rules are held as XML files and can be managed using the command line composer command, or the Tivoli Dynamic Workload Console (TDWC).
Event rules consist of one or more rules, an optional correlation rule and an action (or actions) to be taken under these circumstances. There are a number of predefined event rules and actions supplied with TWS 8.4, with the ability to
add customized events. Future releases of TWS will add additional predefined rules and actions.The types of events that can be included with the rules, covers internal TWS events, such as those listed below, as well as File Monitoring events.
- Job Status Changed
- Job Until
- Job Submitted
- Job Cancelled
- Job Restarted
- Job Late
- Job Stream Status Changed
- Job Stream Completed
- Job Stream Until
- Job Stream Submitted
- Job Stream Cancelled
- Job Stream Late
- Workstation Status Changed
- Application Server Status Changed
- Child Workstation Link Changed
- Parent Workstation Link Changed
- Prompt Status Changed
Job Stream Definition
By setting rules for events that occur, TWS allows you to react to job status changes (such as late or cancelled jobs) by specifying an Action to be taken under these conditions. Typical Actions that are available include:
- TWS Actions
- Submit job stream
- Submit job
- Submit ad hoc job
- Reply to prompt
- Non-TWS Actions
- Send mail
- Run command
- Message logger
- Forward event to Tivoli Enterprise
- Console
- Web Based Reporting
Tivoli Dynamic Workload Console 8.4 includes enhanced reporting based upon the open source Business Intelligence and Reporting Tools (BIRT), which provides out-of-the-box reporting capability.
The historical reports listed below can be executed from the TDWC - the equivalent TWS report is listed in brackets if applicable:
- Job run history (report 07)
- Job run statistics (report 01)
- Workstation workload summary
- Workstation workload runtimes (report 08)
- Custom SQL reports
TDWC also provides some production reports:
- Actual production details (report 10b)
- Planned production details (report 9b)
LDAP Support
TWS 8.4 supports a single sign-on capability between TDWC and TWS, rather
than the separately managed users in previous releases. The TDWC authenticates the logon user against LDAP, and then passes the authenticated user details using a security token (Lightweight Third-Party Authentication - LTPA) to TWS allowing automatic sign-on.Integration with ITM 6.1
TWS 8.4 provides out-of-the-box integration with IBM Tivoli Monitoring (ITM) 6.1 with FP5. The integration provides situations for monitoring the overall health of the TWS infrastructure, and portal views for the Tivoli Enterprise Portal (TEP).
Following the TWS installation, the ITM directory within the TWS install directory contains scripts to configure a Universal Agent (UA) and to create ITM situations for monitoring TWS. The monitoring covered by this includes:
- Host availability
- Application status
- Tivoli Workload Scheduler used space
- Tivoli Workload Scheduler available disk space
- Page-outs
- Swap space available
- Free space
- Tivoli Workload Scheduler Message file size
Additional New Features
TWS 8.4 also includes support for IP V6 and DB2 V9.1 (bundled with TWS 8.4
limited use license).
A future Message Broker article will look at these new features in more detail.
Is it possible to install Tivoli Workload Scheduler (TWS) v8.3 with an existing DB2 ESE v9 instance installed?ISMP installation fails at the check DB2 step
Answer
The ISMP installation method with the "-options response_file" parameter will allow a TWS v8.3 installation with DB2 v9.
To install IBM Tivoli Workload Scheduler (TWS) v8.3 with DB2 V9 already present on the system, perform the following steps:
Copyright © 1996-2009 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. Submit comments This document is an industrial compilation designed and created exclusively for educational use and is placed under the copyright of the Open Content License(OPL). Site uses AdSense so you need to be aware of Google privacy policy. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
Disclaimer:
Last modified: September 12, 2009