We performed a comparison between ActiveBatch Workload Automation and Control-M 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 praised for its versatility and ease of use. Users appreciate the prebuilt jobs, scheduling, monitoring, and alerting mechanism provided by the software. It is also commended for its scalability and intelligent automation features. Control-M stands out in areas such as Managed File Transfer, credentials vault, integration capabilities, Role-Based Administration, collaboration, and forecasting. Users find the software to be particularly useful for these functionalities.
ActiveBatch improvements include managed file transfer, subscription model transition, cloud aspect, interface, crashes, triggers, monitoring dashboard, price, documentation, help center, setup process, email alerts, lag/stability issues, customization options, and customer support. Control-M needs enhancements in microservices, API integration, web interface, testing/quality assurance, reporting, customization, upgrade process, distributed architecture, third-party tool integration, FTP job logs visibility, and QA testing.
Service and Support: ActiveBatch Workload Automation has been praised for its customer service, with users appreciating the helpful, reliable, and responsive support team. Control-M has received mixed feedback. Some customers have praised the prompt and knowledgeable support team, while others have faced slow response times and a lack of proactive assistance.
Ease of Deployment: The setup process for ActiveBatch Workload Automation was smooth and uncomplicated. Nevertheless, there is a minor requirement for additional instructional material when importing files. Control-M had a direct setup procedure, although a few users mentioned a learning curve and the necessity to manually convert jobs and scripts.
Pricing: ActiveBatch Workload Automation is highly regarded for its flexible and reasonably priced setup cost. Users appreciate the ease and speed of the process. Control-M's pricing and licensing elicit varied opinions, with some users considering it costly and perplexing.
ROI: ActiveBatch Workload Automation has proven to be highly effective, leading to substantial financial gains for users. It has resulted in a significant boost in net revenue. Control-M offers a more cost-effective solution, improving overall efficiency and providing advanced automation features.
Comparison Results: ActiveBatch Workload Automation is the preferred product over Control-M according to user reviews. It is praised for its simplicity and ease of use during setup. ActiveBatch offers more versatility and ease of configuration, with prebuilt jobs and a user-friendly interface. Its pricing is considered reasonable and competitive, especially for smaller companies.
"From a scheduling point of view, it is pretty good."
"The product offers a centralized platform for managing activities across many environments, applications, etc."
"ActiveBatch has reduced work by providing automated workflows across several different applications."
"ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy."
"ActiveBatch can automate predictable, repeatable processes very well. There is no real trick to what ActiveBatch does. ActiveBatch does exactly what you would expect a scheduling piece of software to do. It does it in a timely manner and does it with very little outside interference and fanfare. It runs when it is supposed to, and I don't have to jump through a bunch of hoops to double check it."
"We leverage the solution's native integrations regularly. We have to get files from a remote server outside the organization, and even send things outside the organization. We use a lot of its file manipulation and SFTP functionality for contacting remote servers."
"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."
"It is very useful in sending confidential files through FPP servers."
"We value Control-M mainly for the ability to control multiple nodes in a coordinated manner. Control-M has the ability to really coordinate across a lot of nodes."
"BIM is a good tool to monitor SLAs, and being a financial organization, this is a very good feature for us."
"If they have ad hoc requirements, then they can theoretically schedule their own file transfers with the Self Service. We are trying to push as much work back to the customers or developers that have that requirement, because they prefer to help themselves, if possible. We try empowering them and enabling them through Control-M, especially for file transfers, because it is a much broader base of the business then just with batch scheduling. Typically, with SAP batch scheduling, it would work with dedicated teams. With file transfers, the entire business is involved. There are business users, end users, etc. It definitely needs to be as simple as possible and as managed as well as possible. They need to manage it themselves, if possible, because our team is not growing but the number of customers, applications, and jobs are growing. We need to hand back some of the responsibility to the customer for them to resolve and action it."
"Monitoring is a valuable aspect of it. The monitoring tool is very good, and it is easy for expert and entry level users to use on a short notice."
"Self Service for repeatable, low impact workload automation processes."
"The solution is innovative. Specifically for the overseas and time differences, you can feel the efficiency of Batch Impact Manager on jobs, batch processing, and impact management. It works the best on these kinds of issues. It saves us time and money, which is important. We save a lot using Control-M."
"Most valuable feature would be the ability to detect and notify when a process has not completed successfully."
"My organization has been able to script scheduled jobs in Control-M to potentially replace legacy products that are at end of life or end of service. The previous backup applications that were being used for specific files, folders, or applications were no longer being supported, therefore being able to use Control-M to replace that has been very valuable."
"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."
"Some improvements can be made to the user interface."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."
"ActiveBatch UI could use a little more help, and video tutorials would be greatly appreciated for user guides."
"Any product is going to have some room for improvement, no matter what. I see the company has already ventured into AWS and they're constantly trying to improve the managed file transfer which they have recently improvised. I think they bought a software called JSCAPE and they're trying to improve it, which is good. I am not sure if JSCAPE would be part of the base product but currently, you have to buy a separate license for it, which doesn't make sense. If it was Microsoft, ServiceNow, or integrating with other software vendors, I would understand but JSCAPE is now in-house and I'm not sure if they can justify having a separate license for JSCAPE. I would probably expect them to be packaging JSCAPE into the base product. They did switch over from a perpetual license model to a subscription model, which hurt the company a little bit. Nobody is offering the perpetual model anymore. As long as the transition is fair for both the companies, I think it should be fine and not burn us out."
"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."
"The monitoring dashboard could have been more user-friendly so that in the monitoring dashboard itself we can see the total number of jobs created in the system and how many were currently active/scheduled/chained."
"The user interface can be improved so that it is more appealing and accessible to new users."
"It can definitely expand promotions, so that a single job can be moved. Currently you can only promote a job by promoting the entire table."
"With the current version update, I'm not sure why we needed a separate database upgrade. Why not put it all in one package? Previously, you could do it either via a manual upgrade or an in-place upgrade but it wasn't separate."
"I would like not to have to reach out to a third-party application company to do automated notifications. Right now, we still have people manually calling people and emailing people. There's a company called xMatters - and there are others - that has an API through Control-M that can automate any aspect of failure management. I'd like to see it build right into the product. I'd like to see a better notification product."
"I would like to see automatic license management. And probably more importantly, some kind of machine learning to help identify the optimum automation path."
"I would like to see more auditing capabilities. Right now, it has the basics and I've been trying to set those up to work with what our auditors are looking for."
"In general, it is a very good product, and we are very happy with it. It meets all of our expectations."
"The unifying features between Control-M for different platforms needs improvement. The scheduling options on the Control-M mainframe jobs are different than they are on our Linux server. There are a few differences here and there."
"The performance could be better. Control-M Enterprise Manager tends to slow the system down even on a server with a six-core processor and 32 gigabytes RAM. The console is Java-based, so maybe OpenJDK 16 or 17 would be a performance improvement."
ActiveBatch by Redwood is ranked 6th in Process Automation with 35 reviews while Control-M is ranked 4th in Process Automation with 110 reviews. ActiveBatch by Redwood is rated 9.2, while Control-M is rated 8.8. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". On the other hand, the top reviewer of Control-M writes "We have seen quicker file transfers with more visibility and stability". ActiveBatch by Redwood is most compared with AutoSys Workload Automation, Tidal by Redwood, Redwood RunMyJobs, VisualCron and IBM Workload Automation, whereas Control-M is most compared with AutoSys Workload Automation, IBM Workload Automation, Rocket Zena, ESP Workload Automation Intelligence and Automic Workload Automation. See our ActiveBatch by Redwood vs. Control-M report.
See our list of best Process Automation vendors, best Managed File Transfer (MFT) vendors, and best Workload Automation vendors.
We monitor all Process 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.