We performed a comparison between Fortra's JAMS and IBM Workload Automation based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: Fortra's JAMS is praised for its efficient handling of job dependencies and its automation features such as File Watchers, notifications, and code-driven automation. IBM Workload Automation is highly regarded for its ability to incorporate additional features upon user request, trigger jobs in multiple nodes, and maintain stability in monitoring batch applications.
Fortra's JAMS could enhance their user interface, search functionality, exception management, and reporting features. IBM Workload Automation requires improved navigation, job dependencies, daily schedule updates, and reporting visibility.
Service and Support: Customers have expressed satisfaction with Fortra's JAMS customer service, describing it as responsive, knowledgeable, and always helpful. The support team promptly addresses concerns and provides solutions to different problems. IBM Workload Automation's support is also highly praised, especially for assisting with issues that are out of customers' control. Nonetheless, some difficulties may arise in pinpointing the cause of specific problems.
Ease of Deployment: Users find the initial setup for Fortra's JAMS to be uncomplicated and user-friendly, as they are able to easily follow instructions on the webpage and deploy tasks efficiently. The initial setup for IBM Workload Automation may pose difficulties for individuals unfamiliar with IBM tools; however, with guidance, it becomes relatively easy.
Pricing: Fortra's JAMS has an initial investment in the first year, along with a yearly upkeep fee. Users consider the pricing reasonable and budget-friendly and appreciate its flexibility to accommodate expansion. IBM Workload Automation's pricing structure is personalized to each customer's agreement, varying between five and a thousand licenses based on usage.
ROI: Fortra's JAMS has been commended for its impressive return on investment, offering time savings, enhanced productivity, and cost-effectiveness. IBM Workload Automation's ROI is more uncertain and necessitates thorough research and analysis to gain a clearer comprehension.
Comparison Results: Fortra's JAMS is the preferred choice over IBM Workload Automation. Users appreciate JAMS for its user-friendly setup process, efficient handling of job dependencies, automation features, interactive agents, code-driven automation, flexible scheduling options, and detailed logging for problem-solving.
"It has definitely drastically improved our capabilities to scale our automation. Before JAMS, there were a lot of manual processes. We had a couple of operators who spent all day doing that. A lot of the time with human intervention and human processes, it is as good as the person who may be following a procedure and human error is a big problem."
"The interface is good, and it's very easy to define and create jobs. If a job is not running or there is an error, the solution will send an email. That's all very good and very useful."
"The fact that we no longer need to use Excel spreadsheets is huge. Before JAMS, every group was keeping track of their own batch jobs. Nobody really knew what the other jobs were. So, if jobs failed, other groups wouldn't necessarily know. With JAMS, everything is done through a single scheduler. You can choose who to notify."
"It makes everything that we want to do so much easier. We have had a number of instances in the past where we have had developers who have been working on a project, and even though we have had JAMS for all these years, they will create some SQL Server Agent job, or something like that, to run a task. When it is in code review and development is complete, the question always comes around, "Can JAMS do this?" The answer has always been, "Yes." Pretty much anything we have ever developed could be run by JAMS."
"Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution."
"It's a full-featured job scheduling tool. The part that I liked the best was the support team. This tool was new, and we were all learning it and setting up the different jobs that were complex in nature. Their support team was very responsive in helping us out through the setup and resolving the issues. They have been incredibly awesome."
"Our company is based on data. Everything we do is data-driven, so it has been very valuable having one place where we can process all of the data and do batch schedules with chunks of data."
"While I appreciate the other features, the agent stands out for its ease of installation and configuration for JAMS monitoring."
"Jobs can be triggered in multiple nodes."
"The project we worked on involved the running of nearly 24,000 job instances in a single day, so I would say that the solution is stable."
"Provides a robust, full spectrum enterprise-wide WLA platform."
"Jobs can be triggered in multiple nodes."
"The technical support is great, the product is easy-to-use, and it is stable."
"I have supported this product in literally 100s of different environments and its unmatched in its ability to scale to any size."
"The support from Cisco is very good. I was with them as a company for 40 years"
"The initial setup is easy."
"JAMS handles exceptions fairly well but there are some areas where it might improve a little bit. It has to do with being able to automatically handle exceptions, out-of-the-box, rather than having to code them."
"It does validations when you try to delete an object and if there are any dependencies in place, the deletion process will not proceed... there is no information provided as to what it was that caused the validation to fail... it's quite a tedious process to find which object is getting in the way."
"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"The documentation is not super... It's not as quick and slick as I'd like it to be."
"The search capability needs to be improved because when we try to search for a job, it's hard to do."
"The only thing that they could improve on is the fact that they don't have a browser version of JAMS. They've got all the bits and pieces there if you want to build your own web version of it. It does come with a web client, but it's pretty clunky. They could improve on that."
"The biggest area with room for improvement is the area that my organization benefits the most from using JAMS, and that is in custom execution methods. I happen to have a very good C# developer. Ever since we got JAMS, he has spent a lot of time talking to JAMS developers, researching the JAMS libraries, and creating custom execution methods. He's gotten very good at it. He is now able to create them and maintain them very easily, but that knowledge was hard-won knowledge. It was difficult to come by, and if I should ever lose this developer, then I would be hard-pressed to find anyone who could create JAMS custom execution methods quite as well as he can since there really isn't all that much help, such as documentation or information, available on how to create custom execution methods."
"I would like to see the ability to interface with Microsoft group-managed service accounts, but they're still in the research phase. They need to ensure everything's legit and safe. The report designer and dashboards could also be improved. We're running 7.3, so I don't know if they have updated the reporting in 7.5, but I think the reports and dashboards could be better."
"The performance of the previous versions could be better."
"The schedule refreshes daily and that's a challenge for us."
"Scalability-wise, it can be a little bit challenging."
"This solution does have bugs and could be improved in this regard. However, these bugs are resolved relatively quickly."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"Slow down on the releases a bit. I fully understand that IWA functionality is increasing at an amazing rate, but trying to keep up with the upgrades is rough."
"There should be more custom documentation, specifically around Java APIs. There should also be more training. In terms of features, we are currently using only 50% of its features. We don't use all features that are available, but there is always room for improvement in all of the tools."
"It should support other schedulers that aren't IBM products."
Fortra's JAMS is ranked 5th in Workload Automation with 27 reviews while IBM Workload Automation is ranked 13th in Workload Automation with 28 reviews. Fortra's JAMS is rated 9.0, while IBM Workload Automation is rated 8.2. The top reviewer of Fortra's JAMS writes "We can scale up our organization's scheduling and automation without having to add staff to the department". On the other hand, the top reviewer of IBM Workload Automation writes "With an easy setup phase in place, agent-based installation can be done in minutes". Fortra's JAMS is most compared with Control-M, AutoSys Workload Automation, Redwood RunMyJobs, Tidal by Redwood and VisualCron, whereas IBM Workload Automation is most compared with Control-M, AutoSys Workload Automation, HCL Workload Automation, Red Hat Ansible Automation Platform and Tidal by Redwood. See our Fortra's JAMS vs. IBM 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.