Control-M from BMC is a platform for integrating, automating, and orchestrating application and data workflows in production across complex hybrid technology ecosystems. It provides deep operational capabilities, delivering speed, scale, security, and governance.
$29,000
per year
Red Hat OpenShift
Score 9.2 out of 10
N/A
OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
Anytime you have a process that has to do multiple things, transfer data, interact with other systems, Control-M is critical. Not only does it provide the insight to what is going on, but it also lets you keep tight audit controls over access, reduces the need to spend large amounts of time tracking down issues, reduces the need to write custom "code" to do integrations with other systems and helps you better manage and track critical SLAs for workflows across the business.
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
The good thing is that there are so many connectors available. Control-M provides lots of features, and we are using almost 60 to 70% of them. Control-M is providing us with so much capability to use during our daily problem-solving.
Most of the job creation is very simple and quick and worked as per expectations.
Testing and debugging are also very easy, and you can test multiple scenarios using temporary changes during job runs.
Log and output presentations are also very good, short and detailed.
To monitor specific job net, we can create viewpoint, which can be use on daily basis.
We had a few microservices that dealt with notifications and alerts. We used OpenShift to deploy these microservices, which handle and deliver notifications using publish-subscribe models.
We had to expose an API to consumers via MTLS, which was implemented using Server secret integration in OpenShift. We were then able to deploy the APIs on OpenShift with API security.
We integrated Splunk with OpenShift to view the logs of our applications and gain real-time insights into usage, as well as provide high availability.
I haven't come across too many spots where I'm not happy with the product. Most of the shortfalls were in my knowledge of the product as opposed to the actual product. Currently we're having a little bit of an issue with the deployment of the software to the servers, but it's more of an "us" problem than a product problem. I can't really give any good examples of shortfalls of the product that I've found so far.
OpenShift virtualization has a little room for improvement. I'm coming from it as a Rev customer. There's some things in that OpenShift virtualization that were in Rev that I would like to see in OpenShift virtualization. I realized that they're chasing the VMware crowd and that's fine, but from us old Rev customers, we'd like to see some things that was in Rev around via migration and things of that nature that could be in OpenShift virtualization, I hope is being planned to be put in.
It is one of the best solutions on the market, in terms of innovation, reliability and stability. Control-M provides security when used by the largest companies in Mexico such as banks, department stores and logistics. It has proven to be able to integrate with new technologies on the market and provide almost 100% availability, thanks to its automatic FailOver scheme.
OpenShift is really easy of use through its management console. OpenShift gives a very large flexibility through many inbuilt functionalities, all gathered in the same place (it's a very convenient tool to learn DevOps technics hands on) OpenShift is an ideal integrated development / deployment platform for containers
User experience is meeting my expectations. We had a manual checklist, which Control-M Reports has now replaced, that helped us check the jobs without any issues. So, being fair with the work, the ratings should also be fair. More to come as the AI progresses; this will not only help motivate the Control-M Developers but also lead to the development of advanced technology.
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
Secondary Instances: Control-M supports the installation of a secondary instance of the entire Control-M environment, Control-M/EM, or Control-M/Server.Automatic & Manual Failover: In case of a failure on the primary host, Control-M can automatically failover to the secondary host if using Oracle or MSSQL databases. Manual failover is also an option, enabling a controlled switch during planned maintenance.Fallback: After resolving the issue on the primary host, you can easily fall back to it, or even designate the secondary host as the new primary. Database Replication: For high availability, Control-M leverages database replication from the primary site to a disaster recovery site. While replication is essential, its implementation and maintenance are the user's responsibility.
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
good page load times, efficient report completion, and minimal impact on integrated systems. Specifically, the well-designed GUI contributes to a positive user experience, and the platform's ability to automate various stages of the workflow, including Big Data processes, is highlighted as a key strength. Fast Page Loads: Control-M is reported to have a responsive user interface with fast page load times, allowing users to quickly navigate and manage their workflows
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
Support is generally excellent. Getting lower priority ones resolved can take a while, but it's rare for something to have to be dumped in the "unfixable" bin. If you end up speaking to Houston or Tel Aviv, then you know you've got a "live one".
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
Very knowledgeable instructors provide a hands-on, collaborative learning experience and can interact directly with instructors to develop our Control-M skills. This format allows for immediate feedback, in-depth discussions, and tailored guidance, leading to a deeper understanding of Control-M concepts and practical application. Face-to-face interaction fosters higher engagement and a more dynamic learning environment.
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
Simple and easy to use web based, well paced. Available any time. All online courses are simple and easy to access and use. Very practical everyday use scenarios and solutions. Incorporates software simulations, learning games, and built-in assessments to enhance comprehension and engagement. Online subscriptions are regularly updated with the latest product information, ensuring users have access to the most current knowledge.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
As HA we have depend on the external DB, why don't we have HA feasibility with embedded DB. As with external DB, there are performance issues and fine tuning the DB. As if its embedded DB, Control-M it self take care of the functionality.
Control-M: Known for its comprehensive workload automation capabilities, handling complex job scheduling, dependency management, and IT process automation. TWS: Traditionally strong in Batch processing and job scheduling, focusing on high-performance computing environments. TIDEL: Offers a combination of workload automation and IT process management, often used in mainframe environments.AutoSys: Provides job scheduling and workflow management with a reputation for scalability and performance.
The Tanzu Platform seemed overly complicated, and the frequent changes to the portfolio as well as the messaging made us uneasy. We also decided it would not be wise to tie our application platform to a specific infrastructure provider, as Tanzu cannot be deployed on anything other than vSphere. SUSE Rancher seemed good overall, but ultimately felt closer to a DIY approach versus the comprehensive package that Red Hat OpenShift provides.
While Control-M offers flexibility with usage-based and subscription-based pricing, some users might prefer more predictable, upfront costs, especially for large-scale deployments. A potential area for improvement could be offering more options for fixed-term contracts with predictable pricing based on factors like the number of agents or jobs, providing a clearer budget for long-term planning
It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
awesome product.Control-M delivers advanced operational capabilities easily consumed by Dev, Ops, data teams, and lines of business.Control-M Workflow InsightsApplication and data workflow observability: Increased confidence that SLAs are being met for Control-M users and IT leadersComprehensive control and management capabilities: Enhanced dashboards and reporting with constant telemetry and intelligent analysis on executing workflowsSelf-service visibility: In-depth reporting to help teams work autonomously
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
Strengths: The vendor provided strong post-sales support, timely issue resolution, and effective onboarding. Their technical team was knowledgeable and responsive, ensuring smooth integration and minimal disruption. Training resources and documentation were comprehensive. Areas for Improvement: While overall service was excellent, occasional delays in advanced customization or escalations slightly impacted timelines. More proactive optimization suggestions could further enhance value.
Since centralizing all our workflows in Control-M, we've cut end to end processing time by nearly 30%
Before Control-M we were babysitting scripts, manually rerunning failed jobs, and chasing ghost errors. With automated recovery, smart notifications, and fewer failures slipping through the cracks, we have saved 3 hours a day across teams
Our workflows success rate sits at 99.95% and when things do fail, they are pinpointed immediately
All of the above. Red Hat OpenShift going into a developer-type setting can be stood up very quickly. There's a very short period to have developers onboard to it and they're able to become productive much faster than a grow your own type solution.
