"Control-M provides us with a unified view, where we can easily define, orchestrate, and monitor all our application workflows and data pipelines. It also provides the ability to filter. So, if I don't want to see everything, I can also narrow it down or open ViewPoint. This is very important since we have thousands of jobs to monitor. If we did not have this ability, it would be very difficult to see what is going on."
"We have a team called pro-mon and they monitor all the jobs for us. A single view for them makes it easy for them to monitor things."
"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."
"The scheduling feature and scheduling tool are the most valuable features. I like the scheduling services that we have in Control-M, which are very beneficial to our organization because they are automating things. There is also less manual work. We can schedule a task without any manual interruptions."
"Control-M has helped to improve our data transfers because it allows us to monitor the execution of the process. With other technologies, we cannot do that."
"The ability to integrate file transfers has been instrumental in allowing us to accomplish the things we need with Control-M. In our industry, we take a lot of data and either push it down to the stores or retail grocery stores. We take files and push them down to the stores or pull files and information from the stores and bring it back to corporate. So, it's two-way communication with file transfers. One of the bigger things that we do with Control-M is scheduling data moves and moving data from one location to another."
"Control-M has helped us resolve issues 70% to 80% faster. It provides us with alerts instead of having someone go to that particular server and check the logs to determine where the issue is. We can simply click on the alert information, then everything is in front of us. This provides us with time savings, human effort savings, and process savings."
"It provides a unified view where you can orchestrate and monitor all your application workloads and data pipelines. That's very important because with cloud, software as a service, edge computing, traditional data center, and legacy apps, there are all these environments. If you don't have that single pane of glass or that one place to look at, you're going to invest a lot of time and resources into tracking things down when they go wrong."
"Ansible is agentless. So, we don't need to set up any agent into the computer we are interacting with. The only prerequisite is that the host with which we are going to interact must have the Python interpreter installed on it. We can connect to a host and do our configuration by using Ansible."
"Being a game-changer in configuration management software is what has made Ansible so popular and widespread. Much of IT is based on SSH direct connectivity with a need for running infrastructure in an agentless way, and that has been a big plus. SSH has become a great security standard for managing servers. The whole thing has really become an out-of-the-box solution for managing a Unix estate."
"Ansible provides great reliability when coupled with a versioning system (git). It helps providing predictability to the network by knowing exactly what's being pushed after validating it in production."
"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."
"One of the most valuable features is that Ansible is agentless. It does not have dependencies, other than Python, which is very generic in terms of dependencies for all systems and for any environment. Being agentless, Ansible is very convenient for everything."
"While they have a very good reporting facility, the reports that I'm asked to produce, a lot of times aren't necessarily what we need."
"The reporting functionality needs a lot of work. We have faced problems with different versions where we run the right report, but it gives us blank entries. Then, when we run the same report again, it gives the correct data."
"A Control-M on-prem license is based on the number of jobs, which is the number of tasks a particular customer wants to have. These tasks have to be run within 24 hours window. For example, if you have a license for 100 jobs, you can run a maximum of 100 jobs in a 24-hour window. If your operations could not run 10 jobs, and they ran only 90 jobs, they just carry over to the next day, but the next day, they will have 110 jobs. Control-M asks you to buy those 10 more licenses because you were out of compliance in terms of the number of licenses. This is something that needs to be indicated in Control-M GUI so that customers know the number of licenses they're going to use in this time window. Their support and documentation should be improved. I am not that satisfied with their customer support. Sometimes, they don't have the answers. Their documentation is very poor. It is not well written, and it is not in a very logical manner. You can use it on Unix, Linux, Windows, and AIX, but it needs some improvement on iSeries. It needs a built-in mechanism inside the system to give you an option to restore from the last point of failure. If a process crashes, the Control-M needs to have a mechanism in iSeries where the process can be restored from the last point of failure."
"A lot of the areas of improvement revolve around Automation API because that area is constantly evolving. It is constantly changing, and it is constantly being updated. There are some bugs that are introduced from one version to the next. So, the regression testing doesn't seem to capture some of the bugs that have been fixed in prior versions, and those bugs are then reintroduced in later versions."
"We've also had a few database bugs within our organization. I think we are migrating to OpenJDK rather than just regular Java and that has since shown some issues with our Control-M instance, timing out and causing our jobs to stop running. We are still working with BMC to fine-tune that and get that resolved."
"Its architecture is old. AutoSys gives more flexibility."
"I would like to see more audit report templates added, and perhaps more customizability in terms of reporting."
"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."
"The area which I feel can be improved is the custom modules. For example, there are something like 106 official modules available in the Ansible library. A year ago, that number was somewhere around 58. While Ansible is improving day by day, this can be improved more. For instance, when you need to configure in the cloud, you need to write up a module for that."
"Accessibility. Ansible uses a CLI by default. Those accustomed to it can find their way and adopt the YAML files easily over time. But, some users are more comfortable using UIs..."
"Some of the modules in Ansible could be a bit more mature. There is still a little room for further development. Some performance aspects could be improved, perhaps in the form of parallelism within Ansible."
"Ansible is great, but there are not many modules. You can do about 80% to 90% of things by using commands, but more modules should be added. We cannot do some of the things in Ansible. In Red Hat, we have the YUM package manager, and there are certain options that we can pass through YUM. To install the Docker Community Edition, I'll write the yum install docker-ce command, but because the Docker Community Edition is not compatible with RHEL 8, I will have to use the nobest option, such as yum install docker-ce --nobest. The nobest option installs the most stable version that can be installed on a particular system. In Ansible, the nobest option is not there. So, it needs some improvements in terms of options. There should be more options, keywords, and modules."
"When you set up Playbooks, I may have one version of the Playbook, but another member of the team may have a different vision, and we will not know which version is correct. We want to have one central repository for managing the different versions of Playbooks, so we can have better collaboration among team members. This is our use case for using Git version control."
Control-M simplifies application and data workflow orchestration on premises or as a service. It makes it easy to build, define, schedule, manage, and monitor production workflows, ensuring visibility, reliability, and improving SLAs.
Control-M is ranked 1st in Process Automation with 36 reviews while Red Hat Ansible Automation Platform is ranked 2nd in Configuration Management with 5 reviews. Control-M is rated 8.8, while Red Hat Ansible Automation Platform is rated 8.4. The top reviewer of Control-M writes "Allows us to integrate file transfers more readily, resolve issues quickly, and orchestrate a diverse landscape of vendor products". On the other hand, the top reviewer of Red Hat Ansible Automation Platform writes "Enables us to efficiently manage an almost unlimited number of nodes". Control-M is most compared with AutoSys Workload Automation, IBM Workload Automation, Automic Workload Automation, ActiveBatch Workload Automation and Stonebranch Universal Automation Center, whereas Red Hat Ansible Automation Platform is most compared with Microsoft Endpoint Configuration Manager, Red Hat Satellite, VMware vRealize Automation (vRA), BigFix 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.