IBM Tivoli Workload Scheduler - license + 1 Year Software Subscription and

Mfg.Part: D56MTLL-BL | CDW Part: 1324302 | UNSPSC: 43232802
Availability: In Stock Ships same day if ordered before 4 PM CT
Warranties
$38.99 Advertised Price
Advertised Price
Product Details
  • License + 1 Year Software Subscription and Support
  • 1 value unit
  • Passport Advantage Express
  • Linux
  • Win
  • OS/390
  • IBM OS/400
View Full Product Details
Better Together
Quick View
Total Price:

Product Overview

Main Features
  • License + 1 Year Software Subscription and Support
  • 1 value unit
  • Passport Advantage Express
  • Linux
  • Win
  • OS/390
  • IBM OS/400
  • UNIX
IBM Tivoli Workload Scheduler automates, monitors, and controls the flow of work through your enterprise's entire IT infrastructure on both local and remote systems. From a single point of control, the suite analyzes the status of the production work and drives the processing of the workload according to installation business policies. It supports a multiple-end-user environment, enabling distributed processing and control across sites and departments within your enterprise.

IBM Tivoli Workload Scheduler provides leading-edge solutions to problems in production workload management. It can automate, plan, and control the processing of your enterprise's entire production workload, not just the batch subset. The suite functions as an "automatic driver" for your production workload to maximize the throughput of work, and optimize your resources, but also allows you to intervene manually as required.

IBM Tivoli Workload Scheduler - license + 1 Year Software Subscription and is rated 3.5 out of 5 by 4.
Rated 3 out of 5 by from Dynamic scheduling helped us schedule jobs on servers with restricted access. It doesn’t have in-built monitors to capture and report READY/INTRO state jobs. Valuable Features:Dynamic scheduling: This is one feature which helped us achieve some important business objectives without the need to install TWS on a server. Some of the servers in our organization have restricted access and dynamic scheduling helped us schedule jobs on these servers without the need to install TWS.Room for Improvement:* Monitoring* ReportingTWS doesn’t have in-built monitors to capture and report READY/INTRO state jobs. In our environment, we use TWS to schedule jobs in SAP and without an in-built monitor to capture these, we use custom-built scripts to report jobs stuck in READY/INTRO state.Use of Solution:I have used the product for seven years.Stability Issues:There were real stability issues. The WebSphere process gets hung on TWS masters running TWS 9.1. WebSphere is used heavily in our environment and a restart of WAS is really required at least once in a month.Scalability Issues:There were no scalability issues.Technical Support:Technical support was not always the best. You need a little bit of patience until the PMR is routed to the right layer of support.Initial Setup:Initial setup using the GUI was straightforward. However installing/upgrading a TWS master using the silent approach is a little bit tricky, as the details and the steps have to be collected from many other documents. There was no single document to help us to install the TWS, WAS, and IBM Installation Manager using the silent approach.Other Advice:I would recommend other users to definitely consider TWS, as it has proven to be a powerful tool in our environment so far.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-03-07
Rated 3 out of 5 by from Dynamic scheduling helped us schedule jobs on servers with restricted access. It doesn’t have in-built monitors to capture and report READY/INTRO state jobs. Valuable Features:Dynamic scheduling: This is one feature which helped us achieve some important business objectives without the need to install TWS on a server. Some of the servers in our organization have restricted access and dynamic scheduling helped us schedule jobs on these servers without the need to install TWS.Room for Improvement:* Monitoring* ReportingTWS doesn’t have in-built monitors to capture and report READY/INTRO state jobs. In our environment, we use TWS to schedule jobs in SAP and without an in-built monitor to capture these, we use custom-built scripts to report jobs stuck in READY/INTRO state.Use of Solution:I have used the product for seven years.Stability Issues:There were real stability issues. The WebSphere process gets hung on TWS masters running TWS 9.1. WebSphere is used heavily in our environment and a restart of WAS is really required at least once in a month.Scalability Issues:There were no scalability issues.Technical Support:Technical support was not always the best. You need a little bit of patience until the PMR is routed to the right layer of support.Initial Setup:Initial setup using the GUI was straightforward. However installing/upgrading a TWS master using the silent approach is a little bit tricky, as the details and the steps have to be collected from many other documents. There was no single document to help us to install the TWS, WAS, and IBM Installation Manager using the silent approach.Other Advice:I would recommend other users to definitely consider TWS, as it has proven to be a powerful tool in our environment so far.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-03-07
Rated 4 out of 5 by from The new servers automatically get monitored with the alerts going to the server administrator or application developers. Valuable Features:The API is a valuable feature as it allowed us to integrate the inventory, change and ticketing systems to fully automate most of the monitoring processes for new devices, decommissioned devices and during approved changes.Improvements to My Organization:The new servers automatically get monitored with the alerts going to the server administrator or application developers, without the need for someone to submit a request.The alerts automatically go to a command center, when a server is classified as production in the inventory system. The alerts get automatically suppressed during an approved change.Room for Improvement:A lot of the automation that we added to the product should come built into it, so that every customer doesn't have to reinvent the wheel. This will eliminate the need for us to modify our code, in order to make it compatible with each future release.Below are examples of automation that we developed which should be built into the product:* Integration with the inventory system, so that alerts go to the proper teams. For example, alerts for servers classified as development would go to the apps support team or alerts for servers classified as production would go to the monitoring center. Also, alerts would stop when a server is marked as decommissioned.* Integration with the change management system so that alerts would be suppressed during the change window for approved changes. Thus, alerts would begin for approved changes adding new servers.Use of Solution:I have used this solution for five years.Stability Issues:There were some stability issues but we lit a fire under IBM's feet and they corrected them.Scalability Issues:There were no scalability issues; we managed to deploy over 85,000 server with no issues.Technical Support:The level of technical support is top notch. If the support team can't fix an issue, they don't hesitate to engage the product development team.Previous Solutions:Initially, we were using a home-grown product that didn't scale as well and had no ability for cross-product automation.Initial Setup:The setup was very complex and required on-site support, mostly due to the cross-product automation that we implemented.Cost and Licensing Advice:Talk to your IBM sales representative to see what they can offer you.Other Solutions Considered:We did not evaluate other solutions.Other Advice:Talk to other customers using this product, who are similar in size and configuration, so as to get feedback, ideas and what to watch out for.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-03-02
Rated 4 out of 5 by from Fault Tolerant Agents can run jobs without a network connection. POF is only one time a day. Valuable Features:With FTA (Fault Tolerant Agent) on remote servers, you have Agents to run jobs. An FTA does not need a network connection to do the job, except when the master sends the daily production plan to the FTA. This feature is very nice because POF is only one time a day. So FTA removing POF from the final schedule is very valuable.Room for Improvement:Have a more simple GUI for end-users. This is simply because I am used to using the command line. The GUI is not easy for non-technical users.Use of Solution:I have used the solution for 15 years.Stability Issues:We had stability issues when managed by not enough skilled people.Scalability Issues:There were no scalability issues using DM.Technical Support:Technical support was excellent.Initial Setup:Initial setup was simple.Cost and Licensing Advice:It is expensive.Other Advice:Spend time to define a robust architecture, and day-to-day operations with a specialist.Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2017-01-11
  • y_2018, m_8, d_12, h_19
  • bvseo_bulk, prod_bvrr, vn_bulk_2.0.8
  • cp_1, bvpage1
  • co_hasreviews, tv_0, tr_4
  • loc_en_US, sid_1324302, prod, sort_[SortEntry(order=SUBMISSION_TIME, direction=DESCENDING), SortEntry(order=FEATURED, direction=DESCENDING)]
  • clientName_cdw