We performed a comparison between Control-M and Red Hat Ansible Automation Platform based on real PeerSpot user reviews.
Find out what your peers are saying about Camunda, Pega, Appian and others in Process Automation."Because it's a tool which allows us to do scheduled work, it allows for notifications when jobs aren't running within that scheduled time frame. This improves the opportunity to meet SLAs."
"BIM is a good tool to monitor SLAs, and being a financial organization, this is a very good feature for us."
"Before Control-M, we didn't have a centralized view and could not view what happened in the past to determine what will happen in the future. The Gantt view that we have in Control-M is like a project view. It is nice because we sometimes have some application maintenance that we need to do. So, in a single console, we can hold the jobs for the next hour or two. We can release that job when it is finished. This is a really nice feature that we didn't have before. It is something really simple, but we didn't previously have a console where we could say, "For the next two hours, what are the jobs that we will run? And, hold these jobs not to run." This is really important."
"The scheduling and management were really good. Monitoring was also better. It had a good visual presentation. It showed me charts and all such things. It was really good on that side."
"There is a batch monitoring tool called Batch Impact Manager, which proactively warns when processing is behind and SLAs are in jeopardy of being missed."
"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."
"It gives us the ability to have end-to-end workflows, no matter where they're running."
"The most valuable features are the managing of file transfers and the product keeping up with technology."
"The most valuable features of the solution are its configuration management, drift management, workflow templates with the visual UI, and graphical workflow representation."
"Installing it is a PIP command. So, it's pretty easy. It is a one liner."
"It has an easy-to-use interface. It is REST API driven, and it integrates with Active Directory. It provides the ability to grant permissions to other users who would not necessarily have those permissions via the GUI so that they could run other people's jobs. For example, you could have the Oracle team grant permissions to the Linux team so that they can use each of those playbooks or each other's code. It is called shift-left."
"Its checking and validating ensures our packages are properly patched."
"It has improved our organization through provisioning and security hardening. When we do get a new VM, we have been able to bring on a provisioned machine in less than a day. This morning alone, I provisioned two machines within an hour. I am talking about hardening, installing antivirus software on it, and creating user accounts because the Playbooks were predesigned. From the time we got the servers to the actual hand-off, it takes less than an hour. We are talking about having the servers actually authenticate Red Hat Satellites and run the yum updates. All of that can be done within an hour."
"It is all modular-based. If there is not a module for it today, someone will write it."
"The biggest thing I liked about Ansible is the check mode so that we can verify, after we've pushed, that the config there is actually what we intended."
"The playbooks and the code the solution uses are quite useful."
"We would recommend modernizing the look and feel of Control-M. They also need to move towards more self-service and development in their environment. It's very antiquated."
"After we complete FTP jobs, those FTP jobs will be cleared from the Control-M schedule after the noon refresh. So, I struggle to find out where those jobs are saved. Then, we need to request execution of the FTP jobs again. If there could be an option to show the logs, which have been previously completed, that would help us. I can find all other job logs from the server side, but FTP job logs. Maybe I am missing the feature, or if it is not there, it could be added."
"Integration with some applications and platforms is complex and requires development. We have done some integration with the application integrator, but it was more like a manual solution. This is an area that can be improved."
"You need to pay for extra features if you need them."
"The stability of Control-M has Not been great. A big thing we've been trying to work on with BMC is observability. Modern applications should be observable and resilient, but we're finding that sometimes Control-M is not very resilient and many times Control-M is not very observable."
"Finding documentation on the website can be a bit confusing."
"The MFT applications should have more functionality and flexibility within that tool. Having more flexibility with that tool for handling the one to many or many to one concept. Like being able to take data from one source and push it to many locations or pull data from many locations and bring it back into a single source. That's why we still use our TPS program for the file transfers just because we don't have some of those capabilities available to us within MFT."
"I would like to see automatic license management. And probably more importantly, some kind of machine learning to help identify the optimum automation path."
"One problem that I'm facing right now is the mismatch between the new version of Python and Ansible. Sometimes it's Python 2, and sometimes it's Python 3. When things get a bit dicey, I wish that Ansible would solve this issue by itself. I don't want to have to specify if it is Python 3 or version 2."
"There are some options not available in the community edition of the solution."
"What we need is model-driven, declarative software infrastructure management. However, things tend to break with new versions, requiring a lot of work to fix…The focus should be on improving the support for Ansible in the area of AI coding."
"From Red Hat Insights point of view, the product is not on top as it is not responding as per the demand...Like on cloud platforms, you can see the main parts of Red Hat Insights, along with the inventory of all your apps. So, that is missing in Red Hat Ansible Automation Platform."
"There needs to be improvement in the orchestration."
"The solution is slightly expensive, and its pricing could be improved."
"Additional features could be added."
"The job workflow needs to be worked on. It's not really clear to how you actually link things together. What they probably could do is provide an example workflow on how to stitch things together. I think that would be very helpful."
More Red Hat Ansible Automation Platform Pricing and Cost Advice →
Control-M is ranked 4th in Process Automation with 110 reviews while Red Hat Ansible Automation Platform is ranked 1st in Configuration Management with 58 reviews. Control-M is rated 8.8, while Red Hat Ansible Automation Platform is rated 8.6. The top reviewer of Control-M writes "We have seen quicker file transfers with more visibility and stability". On the other hand, the top reviewer of Red Hat Ansible Automation Platform writes "Capable of broad integrations with easy-to-operate infrastructure and user controls". Control-M is most compared with AutoSys Workload Automation, IBM Workload Automation, Rocket Zena, ESP Workload Automation Intelligence and Stonebranch, whereas Red Hat Ansible Automation Platform is most compared with Red Hat Satellite, Microsoft Configuration Manager, VMware Aria Automation, Microsoft Azure DevOps and AutoSys Workload Automation.
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.