Sometimes we have issues with the solution's stability. So, stability can be improved. Reporting and visibility of the solution need improvement. These days, we need more visibility. We need to access the logs and databases easily. You need to keep track of the running number of logs, like which ones are executed, completed, etc. So if there would be a good reporting dashboard, then it would be good. There's room for improvement in the solution since it is a challenging thing when we want to use the solution's technology with our new technologies. For example, if we need to use TWS on our OpenShift platform, the solution's API is not capable enough. So the product itself needs to be aligned with new technologies.
Information Technology Advisor at a wellness & fitness company with 10,001+ employees
Real User
Top 20
2023-02-13T20:29:28Z
Feb 13, 2023
Each day the schedule refreshes and that's a challenge for us. In comparison, the ESP scheduling tool refreshes immediately and automatically reconnects. The simulation in Workload Automation is very complicated and difficult.
The performance of the previous versions could be better. We encountered certain issues with the lower version of it, the 9.2. Things have greatly stabilized since then. However, as with any IBM tool, things are a bit tricky. I would give a rating of four or five out of ten, as we encountered certain issues with the domain controller with the lower versions. It would be nice if we could get support for earlier versions. Generally speaking, IBM insists that we move on to their latest one. In respect of the dependency diagrams, the job dependencies across the business process should be improved.
IT Specialist TWS at a financial services firm with 10,001+ employees
Real User
2021-05-08T09:35:00Z
May 8, 2021
There should be more custom documentation, specifically around Java APIs. There should also be more training. In terms of features, we are currently using only 50% of its features. We don't use all features that are available, but there is always room for improvement in all of the tools.
Other solutions like Control-M are better than this solution. IBM should have better integration with the cloud. It should support other schedulers that aren't IBM products.
Manager Production Applicative at a financial services firm with 10,001+ employees
Real User
2020-02-24T06:02:44Z
Feb 24, 2020
I would like to be able to access the return value or result from one job, in the following job. This is a feature that other solutions have and is very helpful. I had to create my own workaround for it because the capability is important for me. It would be helpful to have a mobile app that could be used to follow the job schedule. Most IT applications now have mobile app support.
IT Manager at a manufacturing company with 10,001+ employees
Real User
2020-02-16T08:27:36Z
Feb 16, 2020
The interface for the operator is not so good. I do not think it is as complete as something like Control-M by BMC Software (named for former Shell executives Scott Boulette, John J. Moores, and Dan Cloer). A few other things could be better like the scheduler and linking between jobs and dependencies.
All businesses search for ways to reduce costs and maximize productivity. In order to achieve this, companies often need to get creative in just what kind of practices they implement. One of the methods that many companies turn to to achieve this goal is workload automation.
Sometimes we have issues with the solution's stability. So, stability can be improved. Reporting and visibility of the solution need improvement. These days, we need more visibility. We need to access the logs and databases easily. You need to keep track of the running number of logs, like which ones are executed, completed, etc. So if there would be a good reporting dashboard, then it would be good. There's room for improvement in the solution since it is a challenging thing when we want to use the solution's technology with our new technologies. For example, if we need to use TWS on our OpenShift platform, the solution's API is not capable enough. So the product itself needs to be aligned with new technologies.
Each day the schedule refreshes and that's a challenge for us. In comparison, the ESP scheduling tool refreshes immediately and automatically reconnects. The simulation in Workload Automation is very complicated and difficult.
This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly.
The performance of the previous versions could be better. We encountered certain issues with the lower version of it, the 9.2. Things have greatly stabilized since then. However, as with any IBM tool, things are a bit tricky. I would give a rating of four or five out of ten, as we encountered certain issues with the domain controller with the lower versions. It would be nice if we could get support for earlier versions. Generally speaking, IBM insists that we move on to their latest one. In respect of the dependency diagrams, the job dependencies across the business process should be improved.
There should be more custom documentation, specifically around Java APIs. There should also be more training. In terms of features, we are currently using only 50% of its features. We don't use all features that are available, but there is always room for improvement in all of the tools.
Other solutions like Control-M are better than this solution. IBM should have better integration with the cloud. It should support other schedulers that aren't IBM products.
I would like to be able to access the return value or result from one job, in the following job. This is a feature that other solutions have and is very helpful. I had to create my own workaround for it because the capability is important for me. It would be helpful to have a mobile app that could be used to follow the job schedule. Most IT applications now have mobile app support.
The interface for the operator is not so good. I do not think it is as complete as something like Control-M by BMC Software (named for former Shell executives Scott Boulette, John J. Moores, and Dan Cloer). A few other things could be better like the scheduler and linking between jobs and dependencies.