We performed a comparison between AutoSys Workload Automation, IBM Workload Automation, and Rocket Zena based on real PeerSpot user reviews.
Find out what your peers are saying about BMC, Tidal Software by Redwood, Redwood Software and others in Workload Automation."The solution has been stable."
"The most valuable feature of this solution is the functions are easy to use."
"This solution has made my clients' workplaces a lot less labor-intensive."
"The most valuable features of AutoSys Workload Automation are the file transfer protocol and file watcher. The solution has a user-friendly user interface. It is very simple to use. You have a scope of all your jobs, jobs are what you call tasks that you will automate in the solution. It lets you monitor everything in these jobs."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"The web UI is beneficial and the granular security policies allow us to cover all of our audit requirements."
"I prefer AutoSys over the other ones out there for ease of use, ease of understanding, and getting people to understand how the tool works."
"We get better reports than we use to have."
"The whole product is valuable because it is a tool for batch automation."
"Provides a robust, full spectrum enterprise-wide WLA platform."
"The initial setup is easy."
"Technical support from IBM is very good."
"The most important feature is the creation of folders. It's a really great feature because you can organize the process with naming conventions."
"The project we worked on involved the running of nearly 24,000 job instances in a single day, so I would say that the solution is stable."
"The technical support is great, the product is easy-to-use, and it is stable."
"Jobs can be triggered in multiple nodes."
"I like the whole product, but specifically, I like the license part. It's very easy to acquire a license for this product."
"We haven't had any problems since we installed it. It runs as expected, we haven't had any critical problems. It helps keeps the business running 24/7."
"The most valuable feature is the FTP file transfer."
"From a Linux configuration point of view, Rocket Zena is straightforward. It's fairly easy to set up the server and agents once you know how to do it."
"Its FTP feature is very good, as is scheduling any process or task with the Zena client. I have found it to be very helpful. If a task fails, it gives you a prompt."
"I have used other tools with similar capabilities; it's the ease of use."
"I have found the scheduling feature the most valuable. I can map dependencies by using ASG-Zena. It gives a nice, quick visualization as to where things are."
"In the latest upgrade, Zena added a web-based client. The more I use it, the more I like it. It's an excellent interface. They do a good job of steadily improving the solution to make it more useful."
"This product needs to improve its graphical user interface."
"The lack of documentation, that is an issue. When we do need to bring it down for maintenance, it is always a scary moment for us because we have never had it crash."
"The reporting system, currently, could be better."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"It would be helpful to be able to monitor and manage workload windows so we could minimize downstream applications. This would allow us easier access to the applications."
"I would like to see two-factor authentication, since you see a lot of companies in the news for security breaches. That is a really big thing for us."
"The visibility and control features are somewhat limited."
"AutoSys Workload Automation could improve in the Linux environment. The previous versions of the AutoSys Workload Automation let you take the profile of the user that you were using to run the tasks that you're going to automate, but in the latest versions, you can't do that, you need to make more definitions and it's a little bit difficult. It was easier in the previous versions."
"The schedule refreshes daily and that's a challenge for us."
"Scalability-wise, it can be a little bit challenging."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"The performance of the previous versions could be better."
"It should support other schedulers that aren't IBM products."
"This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"Slow down on the releases a bit. I fully understand that IWA functionality is increasing at an amazing rate, but trying to keep up with the upgrades is rough."
"One area where it could be improved is communication between the different servers. Sometimes there are processes that have already been completed but we get a status notification that they're still active."
"In the next release, I would like to have an alert feature to indicate when an agent is down. Rocket Zena is not capable of sending alerts that the agent is down. As of now, you have manually monitor to see when the agent is down."
"Another one that is probably a little bit bigger for me is that when there is an issue or there's an error, it writes on a different screen. I have to find the actual process name and go to a different screen to view the alert that got generated. On that screen, everyone's processes, not just the processes of the folks in my department, are thrown. It takes me a while to find the actual error so that I could go in there and look at the alert. It could be because of the way it was set up, but at least for me, it isn't too intuitive."
"Rocket Zena is a mainframe-based job scheduler. I would like it to be more open so that we can use it on a distributed platform."
"In the next release, I would like the user experience to be improved. The user interface should be more appealing to gen-z."
"The UI is not intuitive, and it would be nice if there was a web interface."
"The scheduling mapping is a little disjointed. There is no wizard-type approach. There are a lot of different things that you have to do in completely different areas. They could probably add the functionality for creating all components of a mapping or an OPA schedule. The component creation could be done collectively rather than through individual components."
"The documentation has room for improvement."
