We performed a comparison between ActiveBatch Workload Automation and Automic Workload Automation based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: ActiveBatch Workload Automation is highly regarded for its flexibility, simplicity, and ready-made tasks. It provides live monitoring, automatic scheduling, and effective resource management. Automic Workload Automation receives acclaim for its strength, scalability, and straightforward integration. It enables control over various operating systems and products, offering a wide array of features and a user-friendly interface.
ActiveBatch Workload Automation can be enhanced in areas such as managed file transfer, licensing, cloud aspect, user interface, reliability of triggers, monitoring dashboard, price, documentation, support, and integration capabilities. Automic Workload Automation requires improvement in automation sets, language support, functionality, interface, web-based edition, file transfer, pricing, and support.
Service and Support: ActiveBatch Workload Automation has been praised for its customer service, specifically its helpful and responsive technical support. However, there are concerns about the service model and availability of the hotline. Automic Workload Automation has received mixed reviews, with some customers appreciating quick response times and helpful knowledge articles. However, others have faced challenges in reaching support and experienced delays in issue resolution.
Ease of Deployment: The setup process for ActiveBatch Workload Automation is straightforward and uncomplicated, although it can be slightly challenging when implementing it on various operating systems. The initial setup for Automic Workload Automation can be time-consuming and intricate, taking anywhere from one to five days.
Pricing: ActiveBatch Workload Automation is highly regarded for its flexible and reasonably priced setup cost. Users find it to be competitive when compared to other tools. Automic Workload Automation has experienced pricing changes. While some users view it as expensive, they still consider it affordable in comparison to similar solutions.
ROI: Active Workload Automation has been highly regarded for its ability to generate positive financial outcomes, resulting in a notable increase in net revenue ranging from 20% to 30%. Automic Workload Automation did not provide much ROI for users and was perceived as an added expenditure.
Comparison Results: ActiveBatch Workload Automation is the preferred choice when compared to Automic Workload Automation. Users appreciate ActiveBatch for its straightforward setup process and intuitive interface, while Automic is acknowledged to have different degrees of complexity. ActiveBatch is also praised for its versatility, offering prebuilt jobs and a user-friendly configuration.
"ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy."
"The REST API adapters and native integrations for integrating and orchestrating the software stack are very flexible."
"Using this tool, if there are any huge failures, we immediately get an email notification, and the proper team will be informed, at which time they can act accordingly."
"The Jobs Library has been a tremendous asset. For the most, that's what we use. There are some outliers, but we pretty much integrate those Jobs Library steps throughout the process, whether it's REST calls, FTP processes, or file copies and moves... That has helped us to build end-to-end workflows."
"Managing the workload and monitoring the tasks were very difficult with manual interventions. Now, by using ActiveBatch, the process is automated and it runs tasks on a scheduled basis."
"The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially."
"One of the most valuable features of this solution is the versatility of the prebuilt jobs."
"ActiveBatch's Self-Service Portal allows our business units to run and monitor their own workloads. They can simply run and review the logs, but they can't modify them. It increases their productivity because they are able to take care of things on their own. It saves us time from having to rerun the scripts, because the business units can just go ahead and log in and and rerun it themselves."
"I like the script engine of CA, where you can build everything you want."
"The initial setup was quite simple because they have a manual which tells you in a simple way of how to install it step-by-step."
"The most valuable parts are the scalability and flexibility, where you can do whatever you think, then you can realize it in the product and have many ways to do it."
"The most valuable features are the predefined templates for application-specific jobs and the access for different users."
"Stability has been great. My team, we call ourselves "the invisibles" because things run so well that sometimes you almost feel like you have to try to break something to actually get acknowledged."
"It's easy to train other people. A new developer could come in and learn it very quickly."
"Automic Workload Automation is a highly complex yet versatile tool."
"The most valuable feature is that I do not have to wait for one job to finish, then manually click on the next one to start. Automation is the best feature."
"The UI could potentially offer a more refined and user-friendly experience, fostering smoother interactions and facilitating easier navigation for users engaging with the application."
"It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring."
"The user interface can be improved so that it is more appealing and accessible to new users."
"Whenever there is an overload, we are seeing crashes happening."
"I have faced struggles to understand, set up the tool, and implement it in my early days as a new user."
"There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch."
"I can't get the cleaning up of logs to work consistently. Right now, we are not setup correctly, and maybe it is something that I have not effectively communicated to them."
"ActiveBatch UI could use a little more help, and video tutorials would be greatly appreciated for user guides."
"In talking with other customers as well, they would like to see a few enhancements done where you can pull in outside data sources to get a cumulative view from one centralized place."
"We would like some advantages, which we had with the Java UI, with the automation engine."
"We would like a way to test our cloud-based automations on-premises, and then migrate them to the cloud after they have been tested, without needing an additional license."
"The manage file transfer area could be better. The file transfer area needs improvement. Other products like Control-M have some good features in this area."
"The new user interface AWI could improve. It is quite easy to use and work around, but it has lost some of the functionality that we used to have in our Vim client user interface."
"We would also like improved SLR monitoring. There are SLR objects, but I can't define an SLR object plus one, or end days. I can only do it for one day. As we are time shifting to another day, it is not possible. This should be improved."
"The one big issue that we have is around passwords and not being able to update passwords through a different tool. This is not available yet."
"For power users, it does not work well for them at the moment."
ActiveBatch by Redwood is ranked 4th in Workload Automation with 35 reviews while Automic Workload Automation is ranked 7th in Workload Automation with 85 reviews. ActiveBatch by Redwood is rated 9.2, while Automic Workload Automation is rated 8.2. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". On the other hand, the top reviewer of Automic Workload Automation writes "A tool requiring an easy setup phase that provides its users with flexibility and flow chart visibility ". ActiveBatch by Redwood is most compared with Control-M, AutoSys Workload Automation, Tidal by Redwood, Redwood RunMyJobs and MOVEit, whereas Automic Workload Automation is most compared with Control-M, AutoSys Workload Automation, Red Hat Ansible Automation Platform, Dollar Universe Workload Automation and Fortra's GoAnywhere MFT. See our ActiveBatch by Redwood vs. Automic Workload Automation report.
See our list of best Workload Automation vendors.
We monitor all Workload Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
