We performed a comparison between ActiveBatch Workload Automation and Fortra's JAMS based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: ActiveBatch Workload Automation offers a versatile and user-friendly experience with prebuilt jobs, real-time monitoring, scalability, and support for a wide range of platforms. Fortra's JAMS stands out for its strong job dependency tracking, automation capabilities, warnings, support, and emphasis on code-driven automation.
ActiveBatch could enhance its managed file transfer, user interface, trigger reliability, documentation, support services, software setup process, customization options, and pricing. Fortra's JAMS would benefit from improvements in client interface, search functionality, training resources, documentation, UI responsiveness, integration capabilities, source control features, and access permission management.
Service and Support: ActiveBatch Workload Automation has received positive feedback regarding its customer service, specifically highlighting the helpful and reliable technical support. However, there are concerns regarding the service model and availability of the hotline. Fortra's JAMS is highly praised for its responsive and knowledgeable support team, promptness of responses, and availability of documentation and training resources. Customers express overall satisfaction with JAMS' customer service.
Ease of Deployment: The initial setup for ActiveBatch Workload Automation was straightforward, with a minor need for additional documentation during file import. Configuring it on different operating systems like Windows and Linux proved to be slightly complex. Fortra's JAMS had a simple and easy setup procedure, with users easily following instructions on the webpage and swiftly deploying new tasks. Although some users encountered confusion or difficulties, they were able to seek assistance from JAMS support.
Pricing: Users find the setup cost for ActiveBatch Workload Automation to be quick and simple, with reasonable and competitive pricing. Users consider the pricing of JAMS to be fair and affordable.
ROI: ActiveBatch Workload Automation has been highly regarded for its positive impact on net revenue. Fortra's JAMS is admired for its cost-effectiveness, time-saving features, and improved productivity, all achieved without requiring additional staff.
Comparison Results: ActiveBatch Workload Automation is the preferred choice when compared to Fortra's JAMS. Users praise ActiveBatch for its versatility, easy-to-use interface, prebuilt jobs, and user-friendly configuration. It stands out in scheduling, monitoring, and providing valuable insights.
"The software offers real-time monitoring and reporting features that let IT teams keep tabs on the progress of their batch operations and workflows."
"The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially."
"It is very useful in sending confidential files through FPP servers."
"One of the most valuable features of this solution is the versatility of the prebuilt jobs."
"The Jobs Library has been a tremendous asset. For the most, that's what we use. There are some outliers, but we pretty much integrate those Jobs Library steps throughout the process, whether it's REST calls, FTP processes, or file copies and moves... That has helped us to build end-to-end workflows."
"The user interface is really incredible."
"ActiveBatch helped us automate and schedule routine tasks such as data backups, file transfers, database updates, and report generation, which frees IT staff to focus on other studies."
"Approximately ~20 hours of manual effort have been reduced to ~5 hours with the help of ActiveBatch."
"The most valuable feature for us is that it's DR-ready. With respect to disaster recovery, it has the built-in capability for failover to our DR site. If all of the required ports are open, it can be done seamlessly."
"I like how you can add new execution methods on the fly. It isn't overly complex to add Python script support to an execution method in the JAMS system. The scheduling is excellent. You can schedule a maintenance window and take that resource unit out of everything. It halts all of the jobs."
"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."
"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."
"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."
"While I appreciate the other features, the agent stands out for its ease of installation and configuration for JAMS monitoring."
"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."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"Some of the advanced features in the user interface are a bit confusing even after referring to the documents."
"The monitoring dashboard could have been more user-friendly so that in the monitoring dashboard itself we can see the total number of jobs created in the system and how many were currently active/scheduled/chained."
"There are very few documents that provide us with detailed information on the troubleshooting of errors that occur during integration with the existing environment."
"They should offer pricing that is more affordable."
"There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."
"Except for the GUI, everything looks good."
"Setting up the software was hard."
"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 tabs in the JAMS file transfer could be clearer. It would help us demonstrate to our client that JAMS not only automates jobs but also does fast transfers, and it's an alternative that supports and filters different kinds of platforms. Filtering file transfers will be highly beneficial to them."
"The search capability needs to be improved because when we try to search for a job, it's hard to do."
"JAMS lacks source control features. Our previous solution had job control language, but JAMS doesn't. When migrating between versions, JAMS doesn't migrate all the data, like job change history, etc. Also, the scheduler doesn't have a way to make jobs invisible, so you can temporarily turn a job off if you decide not to run it today."
"It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added."
"I'm not sure if they have fixed it in a newer version, but there is no global search in the version I have. If I have multiple sub-folders that are named for business units, like HR or IT, and I have to search for a job, I cannot search from the top. I have to go to the HR folder to search for a particular job, or to the IT folder."
"The client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."
ActiveBatch by Redwood is ranked 4th in Workload Automation with 35 reviews while Fortra's JAMS is ranked 5th in Workload Automation with 27 reviews. ActiveBatch by Redwood is rated 9.2, while Fortra's JAMS is rated 9.0. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". On the other hand, 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". ActiveBatch by Redwood is most compared with Control-M, AutoSys Workload Automation, Tidal by Redwood, Redwood RunMyJobs and IBM Workload Automation, whereas Fortra's JAMS is most compared with Control-M, AutoSys Workload Automation, Redwood RunMyJobs, Tidal by Redwood and VisualCron. See our ActiveBatch by Redwood vs. Fortra's JAMS 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.