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."It scales very well. We can add jobs and remove jobs. We do not have problems maintaining the product across multiple environments and multiple servers."
"The most valuable feature of AutoSys Workload Automation is batch processing."
"It is very valuable for us when we are trying to arrange or orchestrate jobs into a system. It is helpful for triggering jobs for a scheduled task."
"It works constantly and is pretty seamless. You do not have to open up many support tickets."
"It is a fairly stable solution."
"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."
"This solution enables us to improve our daily processing times. We can do everything faster than before we used this solution."
"The actual scheduling of our jobs has helped us tremendously. Before it was all done manually, and we've totally automated the whole functionality, so there's no longer a case where somebody didn't run something."
"I have supported this product in literally 100s of different environments and its unmatched in its ability to scale to any size."
"The support from Cisco is very good. I was with them as a company for 40 years"
"The whole product is valuable because it is a tool for batch automation."
"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 DWC, when configured correctly, is a great GUI tool to provide Self-Service Scheduling capabilities to the user community."
"The initial setup is easy."
"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."
"Jobs can be triggered in multiple nodes."
"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."
"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."
"You can click Ctrl-G and bring a diagram view. You're able to view in a diagram format. The view that it provides is easy, and you can move to the left, up, or down. You can double-click on a certain process. It'll drill into that process and all of its underlying components. You can double-click on an arrow or a component, and it'll bring up a screen that'll have all the variables that are assigned to that particular piece, as well as the values at run time. So, the diagram feature of it, at least for me, is pretty valuable."
"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."
"I have used other tools with similar capabilities; it's the ease of use."
"The most valuable feature is the FTP file transfer."
"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."
"I am looking forward to more of their dashboard features. I think it would be very valuable for us to have dashboard features that could be delivered to our customers in the form of a URL, and they could refresh that URL whenever they wanted to get up to date performance metrics out of our systems."
"They could do better supporting it. They have too many of the same type of products, so sometimes it doesn't get as much attention as it should."
"This product needs to improve its graphical user interface."
"There is a slow response time by tech support. Unless, you say it's severity level one. That will give you a two hour timing window for them to call you. It doesn't really happen exactly in two hours, but they try."
"The cross-platform arena, where you can run work on multiple platforms, needs improvement."
"Documentation and cross-application externals could be improved."
"We have to escalate through channels to get to somebody who knows what's going on. It takes time that we do not necessarily have."
"Some support issues need to be addressed, but not through email, through personal contact via phone or WebEx."
"The performance of the previous versions could be better."
"This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly."
"It should support other schedulers that aren't IBM products."
"The schedule refreshes daily and that's a challenge for us."
"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."
"The configuration of IBM Workload Automation has some challenges. We have a difficult time customizing it, but it is similar to other solutions."
"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."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"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."
"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."
"The UI is not intuitive, and it would be nice if there was a web interface."
"The documentation has room for improvement."
"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."
"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 the user experience to be improved. The user interface should be more appealing to gen-z."
"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."