No more typing reviews! Try our Samantha, our new voice AI agent.

AutoSys Workload Automation vs Axway Automator comparison

Sponsored
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

JAMS
Sponsored
Ranking in Workload Automation
3rd
Average Rating
8.8
Reviews Sentiment
6.6
Number of Reviews
44
Ranking in other categories
No ranking in other categories
AutoSys Workload Automation
Ranking in Workload Automation
4th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
84
Ranking in other categories
No ranking in other categories
Axway Automator
Ranking in Workload Automation
31st
Average Rating
6.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Workload Automation category, the mindshare of JAMS is 3.0%, up from 2.0% compared to the previous year. The mindshare of AutoSys Workload Automation is 6.8%, down from 11.7% compared to the previous year. The mindshare of Axway Automator is 1.3%, up from 0.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS3.0%
AutoSys Workload Automation6.8%
Axway Automator1.3%
Other88.9%
Workload Automation
 

Featured Reviews

LV
Principal Data Base And Infrastructure Engineer at a outsourcing company with 501-1,000 employees
Automation has replaced nightly monitoring and delivers reliable, unified job scheduling
We have really enjoyed working with JAMS in terms of notifications, alerts, and streamlining. There used to be a process with Automate, which is another product from Fortra, but even before that, the other division of the company that we were merging with had a tool that was built in-house called a file handler or file distributor. It was an in-house developed tool, but it was not as streamlined or as efficient as JAMS is. We literally had to have a dedicated nighttime person monitoring. Although we are 24/7, the divisions of the company that we were using JAMS for have been small scale. While we have automated it, we have streamlined it in such a way that notifications go out and alerts go out, but if there is anything, then we get paged and alerted, and if anything needs to happen at midnight, we can wake up. On the other hand, with the tool I mentioned, the file handler and distributor, we used to have a dedicated nighttime person that had to be sitting and monitoring it to see when a file arrived, whether it met the conditions, and then execute the next particular job. By using JAMS, we have gained a lot more efficiencies in terms of all of those to streamline it, and there is no necessary need for having an overnight engineer just keeping an eye on all of this.
PK
Assistant VP at a financial services firm with 10,001+ employees
Experience significant automation with robust integration and user-friendly interfaces
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancements in the R24 release. The web UI needs some improvement. Cloud integrations are limited to 25 or 30 configurable plugins and integrations to the cloud. They can improve in that area. They have separate tools, not AutoSys Workload Automation, such as Atomic and other SaaS-based solutions that can run inside the cloud. AutoSys Workload Automation can be configured in the cloud, but it requires a substantial number of VMs depending on the load. For on-premises deployment, it is a very good solution. They need to increase their footprint in the cloud and improve the web UI. They are making excellent progress in the R24 release.
it_user656310 - PeerSpot reviewer
Senior Systems Engineer at a financial services firm with 501-1,000 employees
A scheduler that runs scripts on servers of most platforms. I would like it to export information about the configuration in a meaningful format.
* The finance departments are able to run complex processes using scheduled scripts. For example, receiving extract data from service providers via Axway ST, processing the data, reformatting it, sending it out to another system, processing it further, and automating the resulting general ledger reports. These are then viewed by application users. * The IT department is also able to automate complex functions. For example, receiving Bloomberg data from Axway ST, automating the decryption, running a program to filter the data, sending it out to various recipients, and sending email alerts on job failures (scripted). * With routine maintenance procedures, it is a simple thing to pause and restart schedules. It is simple to view the status of schedules and the error outputs from within the console.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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."
"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"Getting JAMS in place was a game changer for us back then."
"The ability to sequence jobs is excellent; it means we don't have to schedule them individually, and if one fails, it doesn't unwind the entire workflow."
"The dashboard is intuitive."
"The feature or capability to import a job is most valuable. We can import an existing job from different platforms, and all the configurations get migrated as well without modifying the code, job schedule, etc."
"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."
"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."
"This solution provides us with more details on jobs failing and also gives us restorability, bridging our platforms and giving us the ability to recover as the environment has become more complex over the last 10 years."
"We have gotten great support from CA; they are there whenever we need them, and whenever we open a case, they are very receptive to the issues that we have and resolve them in a timely manner."
"AutoSys significantly reduces manual effort."
"We are able to process hundreds of thousands of jobs a month, it is pretty good, and with failover we maintain continuous uptime."
"We’ve never had any issues; we run over 300,000 jobs a day and we have thousands of end users, at least 10,000 who can evaluate their flows and manage schedules."
"Its stability and reliability, that it's been there for 20 years and 30 years, and it's always been the number one scheduler."
"The ability to create calendars, calendering for batch jobs to run on a scheduled frequency."
"Automation of patch process."
"With routine maintenance procedures, it is a simple thing to pause and restart schedules."
 

Cons

"One issue which can prevent jobs from running is when a script gets into a loop."
"The UI could be better. There were some things that were not quite intuitive, such as the search tool. When we tried to search for jobs, we had to clear the entire search and then go in and enter the new search query. That's something that wasn't intuitive for a new user."
"I would enhance the compatibility feature of JAMS because sometimes when the server is under high load, it does not inform us and we cannot get answers."
"I want JAMS to implement a global search function."
"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive."
"The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back."
"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."
"It needs improvement in the high-availability side. It needs improvement in WCC console and EEM console to make it user-friendly."
"Documentation and cross-application externals could be improved."
"CA Workload Automation is not part of CA's strategic vision going forward."
"I would like to see two-factor authentication, since you see a lot of companies in the news for security breaches. That is a really big thing for us."
"We've had stability problems with the tool."
"With requirements, they have "always" and "skip" on them. That would be nice, for them to have it on triggers also."
"Because this product only computes processing days, it is hard when things need to be scheduled according to non-processing days."
"A couple of key features would be really being able to support a scheduler that, instead of a centralized scheduler, maybe a distributed one, so where a scheduler doesn't come down; not everything stops all at one time and so on."
"I would give technical support a rating of 4/10. It was difficult to communicate in English with this team."
 

Pricing and Cost Advice

"For what it does, the product is priced very well."
"The product is reasonably priced, and we don't have any add-ons."
"Take advantage of its scalability. You can start small. The initial cost is very reasonable. Once you have started picking up the tool and adopting it, then you can scale up from there and buy more agents."
"The product is reasonably priced, and we don't have any add-ons."
"The pricing is reasonable."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year."
"I haven't been involved in the financial side for several years, but we buy one host and unlimited agents, and we get a reasonable price for that. We're happy with the amount we pay and the scalability it provides."
"The price of this solution is reasonable and there is an annual license required."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"People need to pay attention to how they use their ESP agents on the distributed platform. That's where some of the cost comes in, based on how many you need or how many you use."
"I certainly think the pricing is worth the value."
"CA pricing has been a problem, and not looked upon favorably here at all."
"There is an annual license to use AutoSys Workload Automation."
"I don't have information on the exact licensing cost of AutoSys Workload Automation because that's managed by the tools and financing teams. For agents, it's close to $4,00, but for the server setup, it's usually a one-time license initially, and it's AMC which is paid every year and comes close to $8,000 to $10,000."
"We paid to use the solution monthly."
Information not available
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
902,270 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
12%
Manufacturing Company
8%
Comms Service Provider
7%
Financial Services Firm
38%
Manufacturing Company
9%
Insurance Company
5%
Retailer
4%
Construction Company
15%
Manufacturing Company
12%
Financial Services Firm
11%
Insurance Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business14
Midsize Enterprise14
Large Enterprise20
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise79
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
I was not really involved in the pricing, setup cost, and licensing at that level. I am more involved in the technica...
What needs improvement with JAMS?
To improve JAMS, it should resolve the issues with the JD Edwards application and the need for the SSH client connect...
What is your primary use case for JAMS?
My main use case for JAMS is to install, set up, and configure for customers working with JD Edwards application. A s...
How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful b...
What needs improvement with AutoSys Workload Automation?
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancement...
Ask a question
Earn 20 points
 

Also Known As

No data available
CA Workload Automation, CA Workload Automation AE
No data available
 

Interactive Demo

Demo not available
Demo not available
 

Overview

 

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
Metropolitan Borough of Wirral
Find out what your peers are saying about BMC, Broadcom, JAMS Software and others in Workload Automation. Updated: June 2026.
902,270 professionals have used our research since 2012.