No more typing reviews! Try our Samantha, our new voice AI agent.
reviewer2770605 - PeerSpot reviewer
Cloud Engineer at a financial services firm with 501-1,000 employees
Real User
Top 20
Oct 22, 2025
Has streamlined complex job scheduling across scripting languages while reducing manual effort
Pros and Cons
  • "JAMS offers diverse scheduling capabilities for any kind of job, including Linux, PowerShell scripts, and SQL, enabling automation of jobs, which has proven beautiful after three years of usage."
  • "JAMS could be improved with a web client that is accessible and as fast as a normal website, eliminating the need to RDP to the servers to access the JAMS client."

What is our primary use case?

My main use case for JAMS is to manage over 6,000 jobs to schedule on a daily or weekly basis, which include different types of jobs such as Python, Linux scripts, and more.

JAMS is used for monitoring purposes, as we have scripts running every five minutes that check the stability of our systems.

What is most valuable?

JAMS offers diverse scheduling capabilities for any kind of job, including Linux, PowerShell scripts, and SQL, enabling automation of jobs, which has proven beautiful after three years of usage. The UI is very friendly, specifically in version 7.0 onwards, and it's a very stable product with few observed problems. The documentation is neat and clear whenever needed, providing exactly what we seek, and the support team at JAMS is really helpful, replying within two to three hours, which is greatly appreciated.

The feature I rely on most day-to-day is the concept of having a sequence of jobs. This simplifies scheduling for clients by allowing us to create a sequence that includes all jobs for that client. Whenever a new job needs to be scheduled, we create the job and add it to the sequence without much hassle.

JAMS has positively impacted my organization by completely removing the headache of scheduling jobs, not just for the organization but for all internal operations teams need. As an SRE, I write numerous scripts in different languages such as Python, Linux, and PowerShell, which I can simply schedule on JAMS, helping us sort out tasks efficiently.

What needs improvement?

JAMS could be improved with a web client that is accessible and as fast as a normal website, eliminating the need to RDP to the servers to access the JAMS client.

A functionality running on the JAMS server to continuously check the JAMS agents would ensure they are working properly. If an agent is not responding, a feature to restart the service from the job server machine would be beneficial.

The upgrade process, particularly when switching from V6 to V7, could be clearer in terms of documentation, ideally with screenshots showing exactly what needs to be done on each screen.

For how long have I used the solution?

I have been using JAMS for more than three years now.

Buyer's Guide
JAMS Scheduler
November 2026
Learn what your peers think about JAMS Scheduler. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
922,942 professionals have used our research since 2012.

What do I think about the stability of the solution?

In my experience, JAMS is stable.

What do I think about the scalability of the solution?

JAMS's scalability is noteworthy; we run 6,000 jobs per day without facing any problems, so it handles growth and increased workloads effectively.

How are customer service and support?

The customer support is excellent; they are fast, technically strong, and the people I've interacted with know what needs to be done.

Which solution did I use previously and why did I switch?

I had my first interaction with JAMS in my current company, where no prior automation or third-party tool was used, as we relied solely on writing scripts and manually scheduling them on Linux or PowerShell.

What was our ROI?

JAMS has helped me save about 40% of my time specifically related to scheduling or script tasks in my daily work. The design of JAMS makes it very easy to copy jobs and make minimal changes while ensuring functionality. The architecture of JAMS is neat and clean, enabling us to run agents on different machines while having the job scheduler and servers on one machine, which simplifies understanding its operations and helps in troubleshooting.

Which other solutions did I evaluate?

I did not evaluate other options before choosing JAMS, as it was already in place when I began.

What other advice do I have?

If you have a huge number of jobs to schedule, you can definitely opt for JAMS. While I'm unsure about the costs, JAMS is especially beneficial for those needing to manage a large volume of jobs. I rate JAMS 8 out of 10.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
System Engineer at a financial services firm with 1,001-5,000 employees
Real User
Top 10
Apr 24, 2025
User-friendly interface and active monitoring simplify task management
Pros and Cons
  • "The most valuable feature of JAMS is its user-friendly interface, especially after upgrading from version six to seven."
  • "They recently switched to subscription-based pricing, which increased."

What is our primary use case?

We use JAMS to replace manual scheduled tasks on our server environment. It serves as a centralized environment to manage scheduled tasks for around 1200 jobs that perform various functions. I'm one of the administrators, and we also use it for smaller tasks on our end as engineers. JAMS handles SFTP uploads and data copying, among other things.

What is most valuable?

The most valuable feature of JAMS is its user-friendly interface, especially after upgrading from version six to seven. The monitoring tab allows easy monitoring of various jobs, showing where they might be stuck and their progress percentage. The overall audit trail makes it simple to find jobs that didn't run as expected. The user-friendly logging system includes more in-depth logs if needed. Their support is also excellent.

What needs improvement?

A major improvement would be the integration of AI to help us accomplish various tasks. AI could assist in simplifying operations and could potentially enhance the tool's capabilities.

For how long have I used the solution?

I have been using JAMS for approximately eight to ten years.

What was my experience with deployment of the solution?

The initial setup was easy and took about four to eight hours to establish the base environment, excluding job migration. We went through a migration with JAMS's professional services. I installed the environment myself, while they helped migrate the jobs and users.

What do I think about the stability of the solution?

Being on the new version, there's been zero downtime. We have a DR server for emergency use, but using it once a year is rare. JAMS is very stable.

What do I think about the scalability of the solution?

The scalability is adequate. We might be underutilizing it, but as more jobs require processing, additional servers would be necessary. It meets the current needs effectively.

How are customer service and support?

The support is top-tier. They are responsive, even for generic issues, and are very quick to respond depending on the issue's severity. Support is a significant factor for us.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We previously used Windows scheduled tasks, which were unorganized and lacked management and alerting on failures. Switching to JAMS was a significant improvement.

How was the initial setup?

The initial setup was easy, taking around four to eight hours for the base setup. Recently, in a migration, JAMS's professional services helped migrate jobs, while I set up the environment.

What about the implementation team?

The implementation was carried out in-house with help from JAMS's professional services. It was primarily done by one person, though I have a counterpart as backup.

What's my experience with pricing, setup cost, and licensing?

They recently switched to subscription-based pricing, which increased. The price is fair considering the functionality and importance of the tool, although the increase did unsettle our management.

Which other solutions did I evaluate?

During our transition from Windows scheduler, we did not evaluate other solutions; we were focused solely on JAMS.

What other advice do I have?

I would rate JAMS an 8 out of 10, providing room for improvement. It's very user-friendly and powerful, and for new users, there's not much advice needed due to its straightforward nature.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
JAMS Scheduler
November 2026
Learn what your peers think about JAMS Scheduler. Get advice and tips from experienced pros sharing their opinions. Updated: November 2026.
922,942 professionals have used our research since 2012.
Senior Analytics at a financial services firm with 201-500 employees
Real User
Top 20
Oct 20, 2026
Centralized scheduling has improved job monitoring and now streamlines our daily operations
Pros and Cons
  • "One of the best features JAMS Scheduler offers is that it is cheaper than any other scheduler, making it a significant advantage alongside its user-friendliness that allows easy checking of logs and failures."

    What is our primary use case?

    I use JAMS Scheduler for the Databricks job scheduler, where I utilize the Databricks API to call the Databricks jobs from JAMS Scheduler. In JAMS Scheduler, we can see which jobs are failing, which jobs are succeeding, the times, logs, and everything.

    My main use of JAMS Scheduler is to schedule a Databricks job via the Databricks API on the scheduler at precise times, as we are not using the Databricks scheduler. Instead, we actively use JAMS Scheduler in our day-to-day operations, integrating it with Outlook to notify us via email for any failures so we can quickly check the JAMS Scheduler log to investigate the failure.

    Apart from that, we use JAMS Scheduler to write Python scripts as well, and we can run a single Python script with a single job, which illustrates how we are utilizing JAMS Scheduler.

    How has it helped my organization?

    JAMS Scheduler positively impacts our organization by allowing us to maintain day-to-day operations, as we are integrated with a mail trigger system. Therefore, we don't have to keep the JAMS Scheduler screen open all day to monitor running jobs, and we receive emails for any failures, checking the JAMS Scheduler UI only when we need to investigate a failure.

    Lots of time is saved because earlier, multiple people were needed to monitor jobs. Now one person can manage the monitoring during day shifts and another during night shifts, allowing two people to handle everything smoothly.

    What is most valuable?

    One of the best features JAMS Scheduler offers is that it is cheaper than any other scheduler, making it a significant advantage alongside its user-friendliness that allows easy checking of logs and failures.

    In our main workflow, we can call out the sub-workflows, and we are able to check each and every workflow's job logs and failure statuses, whether they fail or succeed, which makes it very easy for any developer to check the logs.

    What needs improvement?

    Currently, I don't see anything that needs improvement as everything is useful and the scheduling works perfectly in my view.

    From my perspective, JAMS Scheduler is currently perfect, and there is nothing that I think could be improved or added.

    What do I think about the stability of the solution?

    JAMS Scheduler is stable.

    What do I think about the scalability of the solution?

    The scalability of JAMS Scheduler is great and perfect.

    How are customer service and support?

    Customer support is good.

    What other advice do I have?

    I rate JAMS Scheduler ten out of ten from my perspective.

    I choose ten out of ten because all my use cases are met and everything I need to accomplish my work is satisfied by JAMS Scheduler, which is why I give it a perfect score.

    At this moment, I am not looking into the governance and security aspect of JAMS Scheduler, as I am only using JAMS Scheduler. The security part is managed by the DevOps team, and I cannot comment on that.

    The accuracy and reliability of JAMS Scheduler's output are perfect, everything works great, and there's nothing to improve.

    I would advise others looking into using JAMS Scheduler that it is time-efficient and provides a great user-friendly experience, which I appreciate and encourages me to use JAMS Scheduler more and more.

    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    Last updated: Oct 20, 2026
    Flag as inappropriate
    PeerSpot user
    Papisetty Manikanta - PeerSpot reviewer
    ETL Data Engineer at a tech vendor with 10,001+ employees
    Real User
    Top 10
    Oct 9, 2025
    Has supported timely job scheduling and smooth monitoring across complex setups
    Pros and Cons
    • "JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
    • "If around 5,000 or more jobs run at a time, JAMS slows down, and we have to wait around five to 10 minutes or restart JAMS scheduler services."

    What is our primary use case?

    We mainly use JAMS for monitoring purposes, to schedule, unschedule, and properly time the jobs at specific times they need to run.

    From my project perspective, there are numerous setups and jobs that we run on a regular basis. For example, a setup name would be SYSCFG, and under that setup, there are numerous jobs again.

    I can describe the bifurcation with an example. There are thousands of jobs, and within those thousands, there will be hundreds of jobs under one setup. As mentioned, SYSCFG is one setup name, and under that setup, we have around 200 to 300 jobs. Another setup name is METOP, which follows our naming conventions in JAMS scheduler, and we have defined the resources with the setup name.

    The main expectation from our project is timely delivery, where we schedule jobs at specific times, and the jobs get triggered accordingly. Once completed, the data is delivered automatically into the tables, and users can access the data from the database.

    What is most valuable?

    JAMS offers features that stand out, especially when compared with Control-M monitoring tool, where JAMS is easily accessible and simple to understand regarding the setups and jobs being bifurcated, and we can bifurcate accordingly.

    JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users. The jobs we trigger run on JAMS, but in the backend, they run in Informatica or in SAP. From this perspective, we have been able to deliver goods and services in a timely manner using JAMS.

    What needs improvement?

    As far as we are using JAMS version 6, it looks good and there is nothing major to add about it. Everything is functioning properly.

    From the past three years, it has remained the same, but sometimes we face issues. If around 5,000 or more jobs run at a time, JAMS slows down, and we have to wait around five to 10 minutes or restart JAMS scheduler services. After restart, the services will be up and running, and we do not observe any delay.

    There is scope for improvement, specifically when there are a larger number of jobs running, as JAMS becomes slower. That is one area where it can be improved. Apart from that, creating resources, adding resources, creating setups, adding setups, or adding jobs, everything functions properly.

    For how long have I used the solution?

    I have been using JAMS for the past three years.

    What do I think about the stability of the solution?

    Sometimes we experience crashes or downtime, but JAMS remains stable as far as I know.

    What do I think about the scalability of the solution?

    JAMS can handle jobs effectively, with the only issue being occasional slowdown during heavy loads.

    How are customer service and support?

    I have interacted with the support team regarding an issue where we canceled a setup but were unable to cancel it in JAMS. It was showing as canceling, but the status was not being updated. We contacted JAMS vendor, who guided us through the necessary steps, and after following their guidance, everything was resolved.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    The project requirements determine the solution used. Previously in our project, we used Control-M as the scheduling tool, and after my project changed, I have been using JAMS monitoring tool for the past three years.

    How was the initial setup?

    The setup primarily focuses on smoother scheduling, with jobs running at particular times. I did not observe any return on investment because access to pricing, setup cost, and licensing information is limited to higher management levels.

    Which other solutions did I evaluate?

    If anyone asks for advice about using JAMS, I would recommend it as a monitoring tool where everything operates smoothly and effectively, and it is a reliable product that we can use.

    What other advice do I have?

    The factors which I have shared would suffice to summarize what JAMS offers. On a scale of 1-10, I rate JAMS a 10.

    Disclosure: My company does not have a business relationship with this vendor other than being a customer.
    PeerSpot user
    Senior IT Manager at a wholesaler/distributor with 5,001-10,000 employees
    Real User
    Jun 17, 2024
    The solution has immensely improved our productivity
    Pros and Cons
    • "JAMS has improved our productivity immensely because everything flows. I don't think we could operate at our current staffing levels without it."
    • "The JAMS automation code isn't so clean."

    What is our primary use case?

    We primarily use JAMS to coordinate jobs between our JD Edwards environment and SSIS packages that we had built to process packages through our SQL server. 

    How has it helped my organization?

    JAMS enables us to organize all these jobs. We have so many jobs that need to run in a specific order, and it's nice to have one place to put them instead of having to look in 18 different places. I still have jobs that aren't in JAMS, so we must go to each machine to find which jobs are running.

    Before we had JAMS, we had a set of jobs running in JD Edwards' scheduling system and SQL jobs in its scheduling system. Those two sets of jobs were constantly interrupting each other. If the SQL jobs stopped running, the JD Edwards jobs would stop, so we had to troubleshoot and restart them. It was the same for JD Edwards jobs. JAMS allows us to coordinate the timing between them so the JD Edward jobs finish before the SSIS package runs or vice versa. 

    JAMS has improved our productivity immensely because everything flows. I don't think we could operate at our current staffing levels without it. While we haven't eliminated monitoring tools, JAMS has freed up staff who were previously responsible for monitoring the systems. It's hard to estimate how much staff time has been saved, but we've been running JAMS for so long that we've probably saved years.  

    The solution eliminated data slack because we can rerun some of these jobs as soon as they are completed, making the data more flexible and available to the end user. 

    JAMS can save time when troubleshooting jobs. It depends on the case. Usually, it's an issue in the database, where someone entered an incorrect value. JAMS can't fix that because it's a human problem, but it brings the issue to our attention much faster because we get a failure report. It helps us solve the problem quicker once we notice something is broken. 

    What is most valuable?

    The JAMS agents are extremely important because we use them to run most of the jobs for the SSIS packages and anything coming out of our JD Edwards environment. It helps our users focus more on their business processes because they don't need to worry about figuring out what's working and what isn't. 

    The solution's code-driven automation is pretty good. We've had a lot of success with it. 

    What needs improvement?

    They recently made changes to JAMS global search feature that I don't like. The search function helps locate jobs. I enter a query, and it gives me a general idea of where it might be instead of having to click the jobs folder and look for it. They changed this with the last update. 

    We used to do a thing called "setups." I inherited the system, so maybe this is just how they did it before me, but in the old days, they built a setup for each job. The setup would manage the job in case you wanted to add more jobs. Now, the setups are only good if you want to run multiple jobs in a chain or in parallel. If you are running one job, you should schedule the individual job. 

    We still haven't cleaned that mess up. I'm unsure if that's an issue for anyone else, but we have lots of single-setup jobs running in JAMS. JAMS sees that as two instances, assigning the same amount of resources and memory to the setup and the jobs running under it. If a setup fails, it doubles up the resources. That has almost brought us to our knees a few times when multiple jobs fail. We're using twice as many resources when all the setup is doing is ensuring that the jobs launch. 

    On the one hand, it's our fault because we need to change how we do things. On the other hand, the older version focused on using setups for everything. It would be nice if they had a tool to convert the old single-job setups into one job.  

    The JAMS automation code isn't so clean. 

    The error handling is good overall. Sometimes when there is an exception, the error messages are a little vague, but not nearly as vague as Windows. However, I'm not sure it's a JAMS issue. It may depend on the system it's talking to, such as JD Edwards, SQL, or SSIS. JAMS will tell you that a job broke and you may want to look into it. I generally don't have any issues with its internal reporting, which is straightforward. 

    For how long have I used the solution?

    I have used JAMS for about six or seven years.

    What do I think about the stability of the solution?

    The downtime has been minimal. Sometimes, we manually kill off jobs and the machine runs slowly because all the memory and CPU resources are at capacity. I would love to have a command line tool that just resets everything. Our biggest issue wasn't JAMS' fault. We didn't pick up where other people were. Now, I watch it. I check the nonproduction server once weekly to see if any jobs are hung and kill them. I report the issues to the appropriate people, but it's a nonproduction server, so it isn't life or death. 

    It has been extremely stable aside from that. The only time it breaks is when we let it go too long. It's like a 5-year-old with a box of crayons. You can't leave it in a room too long or it will start throwing them at the walls. It does a great job as long as you keep an eye on it. 

    What do I think about the scalability of the solution?

    JAMS scales well. It has a little scheduling screen you can open to see what's running. We have around 12,000 jobs a day, and we're a small company. I can only imagine what larger enterprises are doing. The scalability is only limited by the amount of memory you have and your servers' performance. That's the only thing holding us back at this point. 

    How are customer service and support?

    I rate Fortra support eight out of 10. I talked to support yesterday. Typically, I'm not calling them about something critical, but I had a few serious cases. I can usually get them on the phone immediately in an emergency. They respond quickly, and I've been pleased with them overall. 

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    I wasn't involved in deploying JAMS, but I understand it was a significant mindset change for us. It took about six months to integrate JAMS with our ERP and SSL. From what I've heard, they loved it. We keep using it and just upgraded to the newer version of JD Edwards. Upgrading was a somewhat painful process because it involved a lot of conversions. JAMS doesn't require much maintenance aside from the occasional upgrade and checking on the jobs once weekly.

    What's my experience with pricing, setup cost, and licensing?

    All licensing models are a little overpriced, but JAMS offers a good value, especially given their support response times and ability to handle unforeseen issues like the SFTP transfers. I hope to find more use cases to get a better bang for our buck.  

    Which other solutions did I evaluate?

    We looked at another tool when we were upgrading our document management solution OnBase from an on-prem version to the cloud. One of the requirements was that we had to scan the documents through our copy machines and put them on a network. We had to put them into a ZIP file and SFTP it to the cloud API server, and stick it in the right directory. 

    They had me look into two companies, and I started researching SFTP automation. One of my searches turned up JAMS, and I called support to ask about transferring SFTP. I also talked to the other company, and their tool was awesome. It was highly intuitive, but it would be another $15,000 to $20,000 for one set of processes. We already had JAMS in-house, so we decided to use what we had. 

    What other advice do I have?

    I rate Fortra's JAMS eight out of 10. I recommend reading the manual from front to back. I did that when we were preparing to upgrade, and it helped tremendously. It gets you in the right mindset and helps you understand the requirements. For example, we have JD Edwards, which requires a special setup. In addition to deploying the agent, you need to do more work on your enterprise servers to integrate JAMS correctly, so it knows how to talk to JD Edwards correctly. JD Edwards is very temperamental. 

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    PeerSpot user
    Kevin Gore - PeerSpot reviewer
    Software Developer Consultant at Broward Health
    Consultant
    Jul 30, 2024
    Helps us proactively address issues, reduce troubleshooting times, and is reliable
    Pros and Cons
    • "The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
    • "JAMS notifications for hung jobs could be improved."

    What is our primary use case?

    JAMS streamlines our programming job scheduling. It handles both C# projects and PowerShell scripts, allowing us to categorize and schedule critical and non-critical tasks. JAMS also alerts us via email of any job failures. While JAMS boasts features for complex, load-balanced environments, our setup is simple. Everything runs on a single production server with a backup, eliminating the need for a client-server structure.

    How has it helped my organization?

    JAMS effectively alerts us to potential job disruptions, enabling us to address issues proactively. We rely on it for timely problem notifications and monitor it daily. The Runaway feature is invaluable for identifying jobs that take too long to complete, preventing backlogs. We can effectively manage and resolve these issues by configuring the runaway limit, ensuring smooth job execution.

    JAMS is highly versatile in handling exceptions. We can easily prevent a job from running on specific dates by creating exceptions within the scheduler. For instance, we can configure an exception if we don't want a job to run next Wednesday, July 4th. Additionally, JAMS allows us to skip specific dates and times or even run jobs hourly if needed, providing the flexibility to accommodate various scheduling scenarios.

    JAMS centralizes job management across all our platforms and applications. We can install the JAMS client on any machine to manage it directly, and some programmers, including myself, have done so. I have the client installed on my laptop and can access all features from there. Alternatively, users can connect to the JAMS server and run the client remotely, limited to one or two people at a time. I prefer having the client installed for convenient and unrestricted access.

    JAMS significantly reduces troubleshooting time for stalled jobs by providing a centralized monitor. Instead of manually checking the status of numerous jobs, we can quickly assess their progress on a single screen. While it's difficult to quantify the exact time savings, it's evident that monitoring hundreds of jobs individually would be far more time-consuming than glancing at a single monitor for a few minutes daily.

    JAMS has replaced our previous homegrown program scheduler, which was used to monitor job success. Considering this legacy system, we adopted JAMS as our new monitoring and scheduling tool, eliminating the need to develop and maintain the outdated program further.

    JAMS is a scheduler, so setting up a new job is easy. Once we configure it, it doesn't take much time. We create jobs all the time. We have over 200 jobs running. So, if we need a new job, creating it in a few minutes is easy, saving us time. We don't have much time to set up a new job. It's swift to do, saving us time for other projects.

    What is most valuable?

    The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios. JAMS offers valuable features such as Runaway job settings, enabling easy pausing and scheduling for maintenance periods. It provides a complete job history and effective notification options. Overall, it is simple to use, versatile, and exceptionally reliable, meeting all our scheduling needs without issue.

    What needs improvement?

    JAMS notifications for hung jobs could be improved. A hung job can remain on the monitor for days without a configured Runaway Limit, preventing scheduled resumptions. Ideally, the system should proactively notify users when a daily scheduled job is imminent but the previous day's job is still running and unlikely to be completed. Currently, this information is only available with a Runaway Limit configured. Implementing automatic notifications for Runaway Limits exceeding the scheduled timeframe would be a valuable enhancement.

    For how long have I used the solution?

    I have been using Fortra's JAMS for five years.

    What do I think about the stability of the solution?

    JAMS is a stable solution with no lagging or crashing that we have experienced.

    What do I think about the scalability of the solution?

    JAMS is a scalable solution, but our current needs are limited. We only run a few hundred jobs, which JAMS handles without issue. If our workload doubled, we could quickly expand the system by adding more servers and agents. JAMS supports load-balancing and distributed architectures, allowing for seamless growth, but we haven't needed to utilize these features yet.

    How are customer service and support?

    JAMS's technical support is excellent. They worked with us during our initial set-up, and we will contact them again for another installation on our development servers. They are easy to get a hold of and offer good documentation. The support team is accommodating, which is one of the areas we like about JAMS.  

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    We switched from a homegrown solution to JAMS.

    How was the initial setup?

    The initial deployment is straightforward because JAMS offers excellent support.

    While someone unfamiliar with JAMS will likely require assistance with the initial setup, the platform's support system ensures users can obtain the necessary help. Although I didn't handle the original installation, I successfully upgraded JAMS with minimal difficulty thanks to the documentation and support resources provided. While individuals without a technical background might encounter challenges, JAMS' support is designed to guide users through the process, making it accessible to many users.

    While I wasn't involved in the initial deployment, it likely took several days due to the extensive decision-making required for the initial structure. We developed a specific framework with defined sections for critical and non-critical jobs, further categorized into nine types such as financial, business intelligence, programming, and database roles. This structure was designed to be flexible and adaptable to various scenarios, requiring careful consideration but ultimately easy to implement by following guidelines.

    What's my experience with pricing, setup cost, and licensing?

    The pricing is reasonable.

    Which other solutions did I evaluate?

    We looked at a couple of different schedulers, and they gave us the free trial software. We tested it out, and we liked JAMS enough to purchase it.

    I advocated for Windows Task Scheduler because it was free and met most of our needs. While it lacked monitoring capabilities, I developed a proof-of-concept program to address this. However, the programming team manager preferred a more enterprise-grade solution instead of our homegrown approach using Windows Task Scheduler as a foundation. They aimed to eliminate the perceived custom-built nature of our solution.

    What other advice do I have?

    I would rate Fortra's JAMS nine out of ten.

    We currently do not use agents, though we understand the possibility of deploying them in a client-server environment across multiple servers for job scheduling. However, we've opted against this approach due to the increased complexity, server requirements, and associated costs. Instead, our scheduling agent resides on the same server as the JAMS scheduler, providing a consolidated solution. As a backup, we leverage a development server capable of executing jobs. We have implemented several contingency plans, including scheduling on the development server, manual execution, or utilizing Windows Task Scheduler. After careful consideration, we believe this configuration adequately meets our needs without the overhead of managing additional client servers or agents.

    We don't use workflows or similar processes. As developers and programmers, our programs are designed to function independently once initiated at the correct time. Creating a workflow to manage these tasks isn't necessary because our programs are particular in their objectives. We primarily develop in C# but occasionally use PowerShell scripts. We experimented with workflow tools but ultimately determined they weren't essential for our needs.

    Migrating from our old solution to JAMS was not a straightforward integration; we moved jobs manually, one by one. This process has been time-consuming due to the many jobs, and some require specific software or configurations that are not easily transferable. Unlike a typical migration, we cannot simply export jobs from the old system to JAMS; we must carefully assess each job's requirements and ensure the necessary conditions are met on the JAMS server before moving it. While this has been a lengthy process, we are steadily progressing and anticipate completing the migration to JAMS soon.

    JAMS provides good documentation and support for use. The solution is straightforward, but if users need hand-holding, that is a good place to start. 

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    PeerSpot user
    JAMS Admin at a energy/utilities company with 10,001+ employees
    Real User
    Jul 18, 2024
    Significantly reduces troubleshooting time for stalled jobs
    Pros and Cons
    • "The most valuable aspect of JAMS is its robustness."
    • "I want JAMS to implement a global search function."

    What is our primary use case?

    We use Fortra's JAMS primarily for SFTP file transfer.

    How has it helped my organization?

    The agents are essential because they are the core of the job scheduler process. The scheduler server only schedules the time to run the job, but the agents are the ones that execute it. We only connect to Windows systems, but it can connect to Linux systems and SQL databases. The agents have many features, including remote execution. There is so much possibility with the agents.

    Running tasks help our users focus on their business processes more. Before I started using JAMS, I wasn't monitoring the server side, and I had no idea that so many file transfers go on. It's not just file transfers. So many services are running, and they need to be scheduled. There is no way a human can execute scripts, file transfers, or any process on time if we don't have a scheduler. So, the scheduler is like the company's backbone, taking care of all the processes and file transfers that need to run per the scheduled time and date.

    The agents help us bridge the gap between structured batch automation and processes that occur on desktops and web browsers. I'm using it not for desktops as it is generally used; it is all about server-to-server. So, the files are created on some server and must be transferred to another server. And outside of our network using SFTP, both in and out. So, again, it's possible to execute any job locally or remotely. It can be a script. So, sitting locally or remotely, we can schedule it to run on demand, assuming it is trigger-based, like when it sees a file, it transfers by itself. Or if I email on demand, I want to run a specific job, I can email it, and then it executes that job. Or it can be time-based, like running this job every Monday at ten a.m. There are so many excellent options.

    JAMS handles exceptions easily, and most configurations are straightforward. Over the past three to four years of using the tool to meet company requirements, I've always been able to find answers to my questions. I typically find a solution within the tool if I encounter an issue. The support team is also excellent; they provide clear and helpful responses, often including screenshots to guide me through the process.

    It significantly reduces troubleshooting time for stalled jobs, benefiting teams like SAP and payroll that frequently transfer files internally or externally. For instance, payroll's bi-weekly file transfers to and from banks would previously consume hours when handled manually via email or other methods. Now, JAMS automates this process by retrieving files from the payroll application and delivering them to external banks. Similarly, incoming bank files are automatically fetched from their servers at specified times, eliminating manual intervention.

    JAMS streamlines file transfers, saving countless hours for teams like SAP and payroll. Traditionally, tasks like sending bi-weekly payroll files to banks involved manual methods like email, consuming significant IT staff time. JAMS automates these transfers, freeing up staff and eliminating manual processes like email, ServiceNow copying, or using Box.net. JAMS recognizes a file and automatically sends or receives it whenever a file is created, saving countless hours for various departments daily.

    What is most valuable?

    The most valuable aspect of JAMS is its robustness. We can configure it, and it will keep running without glitches for years. There is no issue regarding the scheduler portion and how it is easy to configure. There are so many tools they will get hung up, but JAMS starts the process once we schedule it, and then it's all good. It just keeps running.

    What needs improvement?

    I want JAMS to implement a global search function. Currently, jobs are organized into folders like HR and IT. To find a specific job, such as job number 500, I must navigate to the correct folder to search for it. A global search would allow me to type the job number in the root folder and be directed to the appropriate location. Additionally, the reporting functionality needs improvement, as the current version frequently crashes when generating historical reports.

    For how long have I used the solution?

    I have been using Fortra's JAMS for three years.

    What do I think about the stability of the solution?

    I have never experienced lag, crashes, or downtime in all the years I have been using JAMS. 

    What do I think about the scalability of the solution?

    I use only one agent on a single server, so I can't definitively assess JAMS's scalability. However, I've observed reliable failover behavior. When the primary server was rebooted for security patching, the secondary server seamlessly took over without interrupting file transfers, which occurred every five minutes. This suggests that JAMS can handle unexpected disruptions gracefully.

    How are customer service and support?

    Whenever I contact JAMS technical support with questions, I typically receive answers via online chat the same day. In the last three years, I've only needed to call them two or three times, and those issues were related to Windows system crashes rather than JAMS itself. The support team has always been helpful, offering assistance through Zoom or video calls to resolve problems promptly.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    We previously used a solution that no longer functioned, so we switched to JAMS. As the centralized tool approved by cybersecurity for job scheduling and file transfer, JAMS is the only tool we can use for these purposes.

    We are using an SAP system called Maestro Scheduler, and I'm working to migrate its jobs to JAMS. Compared to Maestro, JAMS is significantly more straightforward and reliable. Maestro frequently experiences job failures, requiring extensive troubleshooting efforts. On the other hand, JAMS is straightforward to install and offers clear error messages for issues like FTP or SFTP failures. Day-to-day operations are smoother with JAMS, and problem identification is much quicker.

    How was the initial setup?

    The initial setup is easy. One week ago, I installed JAMS in my dev environment because that AWS server was somehow decommissioned. So I had to reinstall JAMS, which was easy—like reinstalling any simple Windows application.

    Under optimal conditions, JAMS can be deployed within an hour. A previous deployment was delayed due to network security restrictions in an AWS environment, which required creating a security group to allow necessary JAMS ports. With prerequisites, deployment time can be reduced to under an hour, potentially as little as 30 minutes.

    The JAMS deployment is straightforward and does not require many people.

    What's my experience with pricing, setup cost, and licensing?

    Two years ago, the JAMS tool was transferred to a new team focused on IT automation. When I informed my director of approximately ten thousand dollars of the tool's annual cost, she expressed surprise at its affordability. She mentioned that other server-side automation tools typically cost hundreds of thousands of dollars. On the other hand, JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals.

    What other advice do I have?

    I would rate Fortra's JAMS nine out of ten. If the global search is added and the reporting is improved, I would rate JAMS a ten out of ten.

    We are planning to upgrade JAMS to the latest version this year. Next year, we may demonstrate a demo for SAP integration or other integrations that could benefit the company. If the budget permits, we will implement these integrations. While many integrations are possible, we currently do not utilize any.

    We currently use code-driven automation only limitedly and are evaluating its potential. As we utilize JAMS version 7.1.407, an older version compared to the available 7.5, we are exploring demos to determine the best fit for our future needs based on our current system.

    I maintain JAMS for our organization.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    PeerSpot user
    Alejandro Parro Jr. - PeerSpot reviewer
    Presales Engineer - IT Automation at Bridgeway Communication System, Inc.
    Reseller
    Top 5
    Oct 9, 2026
    The logs are helpful, and the verbose option provides lots of information about the issue.
    Pros and Cons
    • "I didn't know about JAMS because I don't have a person with any challenges with the purchase administration. The feature or the user interface is user-friendly because of the readable icons or very descriptive icons. Though I'm a beginning user of JAMS, I had no issues using it."
    • "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."

    What is our primary use case?

    We use JAMS for technical and workload automation. It's sometimes used for transfer, but it's mostly for workload automation.

    How has it helped my organization?

    We did a POC for one of our customers recently. Our client had some SSIS packages that were hard to automate. They had to be manually executed periodically. They didn't have any automation. When I introduced JAMS, we learned how to integrate their SSIS packages. The solution made a great impression on the company.

    We had a good session with the company and having or upon them having these JAMS. They have 500 different SSIS packages that need to have separate schedules. I showed them how easy it is to convert and store at a large scale. We can use code-driven automation to address complex scheduling requirements. It enables you to integrate multiple applications and API connections. If you need different kinds of schedules, you can accomplish this using the command list. That's helpful to our current and upcoming clients.

    JAMS helps centralize job management because I can orchestrate different job types across multiple kinds of operating systems, including Oracle jobs and SQL jobs like the SSIS packages. Multiple types of scripts can be collected into one application. It provides a single pane of glass in its monitoring view. That's another advantage JAMS has over other solutions. The monitoring console provides the administrator with a broad overview of those channels.

    When the data is ready to go wherever I need it, JAMS ensures the specific job should be executed on its given schedule. We can provide different notifications or set up recovery in case the job fails. We can always ensure there are other retries. We can configure it to run a set number of retries if needed. If the data still hasn't been transferred after several attempts, we can send an email notification to the administrator to take action. 

    JAMS saves us time troubleshooting job failures. The logs are helpful, and you can select the verbose option so JAMS can provide lots of information about the issue.  It also reduces the number of monitoring tools we need. Its ability to integrate with various operating systems using its agents and database connectors eliminates the need for other monitoring tools.  Job scheduling in Linux and Windows can be orchestrated and monitored through a single pane of glass.

    What is most valuable?

    I didn't know about JAMS because I don't have a person with any challenges with the purchase administration. The feature or the user interface is user-friendly because of the readable icons or very descriptive icons. Although I'm a beginner user of JAMS, I did not have any issues using it. 

    Whenever we propose JAMS to one of our clients, we always highlight its ease of use. The interface for scheduling jobs is user-friendly. I also appreciate its strong integration with Fortra's other tools. You can integrate it with the other products to create a total automation solution. 

    I rate JAMS 10 out of 10 for its ability to make us aware of and handle common issues that can prevent jobs from running. I rate JAMS nine out 10 for exception handling. You can configure exceptions to the rules in the scripts. For example, the process might not be executed on specific national holidays or days the offices are closed. 

    Our clients are impressed with JAMS's ability to operate across platforms. Most of them use Linux with a combination of SSIS or Oracle packages. If it's a Windows-only solution, the support will be very limited, but most customers do not use Windows anymore. Most of them are on the Oracle and Linux side. The fact that it's a multi-platform system helps us scale up our clients.

    JAMS is highly flexible in terms of error recovery and job dependencies. That's something I typically stress in our demos. The use of workflows is easy to understand. While I don't have any experience with other workload automation solutions, I think JAMS can provide this high-end feature, where you can accumulate multiple jobs at the same time with different requisitions. 

    What needs improvement?

    I am also supporting and reselling Fortra's GoAnywhere MFT and am interested in Genesys' file-transfer solution of Genesys. Compared to GoAnywhere, Genesys has limited options. 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.

    For how long have I used the solution?

    We have used JAMS for four years.

    What do I think about the stability of the solution?

    I rate JAMS nine out of 10. The software is stable, but it depends on the resources of the system where it is deployed. 

    What do I think about the scalability of the solution?

    I rate JAMS 10 out of 10 for scalability. Most of our clients are small or medium-sized businesses, but we have used this for government clients, so we're confident it can scale. 

    How are customer service and support?

    I rate Fortra support nine out of 10.  The support could be better. I have a favorite support engineer, and I wish the others could be like him. When I send an email, he responds in less than an hour. With some of their other technicians, it may be 24 hours. They are very responsive whenever I send questions or technical issues to their support team.

    Which solution did I use previously and why did I switch?

    Stonebranch. Gartner leader quadrant.

    How was the initial setup?

    JAMS can be installed through Active Directory integration, so it's all straightforward. Any technical team or data center manager would not have any challenges installing JAMS. Typically, we can have it running in under a week. We needed two or three personnel to deploy it. The project manager handles it and there are one or two technical staff to assist. Afterward, we need to train every person who will be working with JAMS. 

    What other advice do I have?

    I rate Fortra JAMS nine out of 10. We recommend JAMS to all our existing clients. We have 10 to 15 GoAnywhere MFT users, but by the year's end, I expect to demo JAMS to at least half of our current base so they can see how powerful this solution is. They can have GoAnywhere for their file transfers and JAMS for their workflow automation. 

    Our GoAnywhere MFT clients need to automate commands, batch file transfers, and PowerShell scripts. JAMS gives you better insights and more options than natively executing commands in Azure MFT. 

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
    Last updated: Oct 9, 2026
    Flag as inappropriate
    PeerSpot user
    Swadhin Pattnaik - PeerSpot reviewer
    Manager of Application Development and Integrations at a manufacturing company with 1,001-5,000 employees
    Real User
    Oct 8, 2024
    It helps us know where the files are going and enables us to track errors if anything fails
    Pros and Cons
    • "Previously, we manually managed file transfers by writing our scripts. The automated MFT feature is great for me and the company. It helps us know where the files are going and enables us to track errors if anything fails. It also makes the connection seamless for third-party vendors."
    • "JAMS doesn't allow us to implement SOC controls. We are a company that trades stocks on the New York Stock Exchange, so all our transactions are audited. It has a feature that saves the file for only a month but doesn't segregate the data between finance and SOC-related compliance."

    What is our primary use case?

    We use JAMS for managed file transfer and job scheduling with Fortra's diverse enterprise application. The managed file transfer is both internal and with external third-party vendors.

    How has it helped my organization?

    JAMS has streamlined our job management across all platforms and applications by offering a centralized, single-pane control. This allows us to easily view, test, and manage all job connections, reruns, and schedules in one place. Instead of relying on older, manual scripting methods, JAMS provides a clear visual interface that shows exactly which jobs are running and when.

    The centralized control and visual clarity have greatly improved our workflow. When troubleshooting stalled jobs, the error-handling feature helps pinpoint failures quickly, allowing us to retrieve delayed information or identify processing issues. As a result, we've reduced troubleshooting time by 10 to 25 percent.

    What is most valuable?

    Previously, we manually managed file transfers by writing scripts, but the automated MFT feature has been a game-changer for our company. It allows us to track where files are going and detect errors if anything fails, ensuring seamless connections with third-party vendors.

    If a file between vendors is missing, JAMS quickly locates it. It also alerts us if a connection is lost, helping us resolve the issue before attempting a file transfer. Effective error handling is crucial in job scheduling, and while some scripting is needed to properly view errors, JAMS supports PowerShell commands, making error navigation straightforward and helping us identify job run issues.

    JAMS handles exceptions well, though each error must be configured based on specific customer needs. Once set up, it provides the data we need in the desired format.

    Code-driven automation is one of JAMS' most critical features. We run nearly 3,000 jobs daily across various time slots, with some scheduled on specific days, such as the first day of the month. How we schedule and run these jobs is vital to our operations.

    What needs improvement?

    JAMS currently lacks the ability to implement SOX controls, which is a limitation for us as a company listed with Stock Exchange, where all transactions are audited. While it offers a feature to save files for a month, it doesn't segregate data between finance and SOX-related compliance.

    Incorporating SOX-related features would save us from manually reviewing last year's data and gathering evidence for audits. A more robust audit feature within JAMS would be a valuable enhancement.


    For how long have I used the solution?

    We have been on the JAMS platform for almost 18 months now.

    What do I think about the stability of the solution?

    We had some initial issues with JAMS because we had trouble understanding the number of connections we expected JAMS to handle. We undersized our servers with a lower CPU and memory, so the server was always at 90 percent utilization. Once we provided them with adequate resources to process the data, we did not see any issues. Rightsizing the server and understanding your workload will help you know what your end product should look like.

    What do I think about the scalability of the solution?

    We are still evaluating this and don't think it will be difficult.

    How are customer service and support?

    I rate Fortra support eight out of 10. We've contacted technical support about concerns and enhancements, and we've received a positive responses. There's some room for improvement, and once they make those improvements, I will change it to a nine. 

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    We had a homegrown SFTP solution that required updates whenever we wanted to do something new, so we switched from a manual SFTP method to an automated MFT system. It has helped us a lot because of the automated monitoring and alert system. It sends emails to users when jobs end or fail. 

    How was the initial setup?

    The initial setup was fairly simple. We had a misunderstanding about how it should be set up that took some time to correct, but it was fairly easy once we understood how it should work. 

    The core configuration was completed in a couple of days, but configuring the applications and vendor took almost six months. This was not due to the product, but because of the limitations we had working with different vendors and switching from one system to another. That switching took time.

    It requires a little maintenance every week or every couple of weeks. We recycle the servers to free up the connections. All Java connections need some maintenance. We haven't seen any instability. It's effective and comfortable to use.

    What about the implementation team?

    Initially, we sought help from a JAMS consultant. Their technical representative was available every time, and their support team was great. Whenever we had any questions or doubts during the initial days of implementation, they were very responsive. They helped us through the process of getting it running.

    What's my experience with pricing, setup cost, and licensing?

    The licensing model for JAMS is straightforward and based on the number of agents, not the number of jobs you run. It's cheap and fairly simple.

    Which other solutions did I evaluate?

    We looked at two or three other products, like BMC Control-M and the AWS MFT solution.

    What other advice do I have?

    We rate Fortra JAMS a nine out of ten. One important consideration is file retention. If you need to keep files for more than 30 days, you’ll need to archive them elsewhere to avoid losing them. Maintaining job history beyond 30 days is crucial to us, especially for SOX and audit purposes, so it’s important to plan for that.

    Additionally, if you don’t want to expose your JAMS implementation to the internet, it’s necessary to set up a DMZ and establish a secure connection between the DMZ and JAMS to protect it from external threats.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    PeerSpot user
    Peter Hegland - PeerSpot reviewer
    Peter HeglandManaging Director, Automation at a tech vendor with 201-500 employees
    Top 20MSP

    Hi Swadhin –


    Thank you so very much for leaving us such a detailed review and for being a JAMS customer! I am the managing director / general manager for JAMS at Fortra.


    If you have time, I’d really like to speak with you more about how we can improve SOX-related features to help with audits and also file retention. Also, would you be willing to elaborate on what improvements our support team could make to improve your rating from an 8 to a 9?


    Always happy to chat anything and everything JAMS! My email is peter.hegland@fortra.com if you ever need anything.


    Best,


    Peter Hegland

    IT Director at a wholesaler/distributor with 1,001-5,000 employees
    Real User
    Sep 3, 2024
    It helps centralize job management and save time, but there is a steep learning curve
    Pros and Cons
    • "The dashboard is intuitive."
    • "The error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."

    What is our primary use case?

    We use Fortra's JAMS to schedule jobs.

    How has it helped my organization?

    JAMS agents are instrumental in supporting our growth and scalability.

    We have been using JAMS for eight years, and the majority of its benefits were realized early on. However, it remains a valuable scheduling software that consolidates our over 500 jobs into a single platform. JAMS allows us to clearly organize our tasks for the data warehouse, web, and other applications. While we could run these jobs independently, JAMS provides a structured approach that simplifies management and reduces manual overhead.

    JAMS helps centralize job management on all of our platforms and applications. This is crucial, and it is the reason we still use JAMS.

    JAMS has enabled the IT team to allocate more time to other tasks. Without JAMS, job automation would consume significantly more of our resources.

    JAMS has also helped us free up a moderate amount of time by making it easier to troubleshoot stalled jobs.

    What is most valuable?

    The dashboard is intuitive.

    What needs improvement?

    The error messages from JAMS need clarification, hindering our ability to resolve issues swiftly.

    The JAMS client requires attention. Its behavior can be erratic, and certain features lack intuitiveness. For instance, the search function, while powerful, is not user-friendly and can be challenging to master. The overall user interface also needs refinement.

    The JAMS report viewer can be improved and needs a lot of work.

    For how long have I used the solution?

    We have been using Fortra's JAMS for eight years.

    What do I think about the stability of the solution?

    The upgraded JAMS system has significantly improved stability compared to its previous versions. Before the upgrade (last year), we were experiencing frequent issues due to the system's age. However, since the update, performance has been much more reliable.

    What do I think about the scalability of the solution?

    It scales very well

    How are customer service and support?

    The technical support response time is good but the quality of the response varies.

    How would you rate customer service and support?

    Positive

    Which solution did I use previously and why did I switch?

    In my previous organization, we used Jenkins, a powerful continuous integration and continuous delivery tool. While I cannot definitively compare it to JAMS, I found Jenkins' user-friendly interface and extensive integrations with various backend systems significantly streamlined our development processes. Unfortunately, my experience with Fortra's licensing and sales practices was less favourable. I have concerns about the company's integrity, particularly following their recent changes to our licensing arrangement, which seemed to be implemented in bad faith. Such actions raise questions about their trustworthiness and future intentions, leaving me uncertain about what to expect from them.

    How was the initial setup?

    In our complex environment, the initial setup for someone with no JAMS experience would be difficult, but it would be straightforward in a simple environment.

    What about the implementation team?

    When we upgraded JAMS last year, we purchased the consulting services from Help Systems.The consultant assigned to us was excellent.

    What's my experience with pricing, setup cost, and licensing?

    Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra. Previously, both Help Systems and MVP offered more favorable pricing and licensing terms. However, Fortra's current pricing and licensing practices are unnecessarily complicated far less customer friendly. In addition to standard licensing fees, numerous additional costs are associated with using JAMS. Fortra's approach of charging for seemingly minor components, such as separate agents and schedulers, is frustrating and adds to the overall cost of ownership.

    What other advice do I have?

    I would give Fortra's JAMS a rating of five out of ten. While the software is excellent, my experience with the company could have been better. As a result, I would not consider purchasing any other Fortra products in the future.

    We have two JAMS users in our organization.

    JAMS is a technically powerful tool, but it has a learning curve for new users. It's crucial to understand the user interface and how agents communicate with the back-end system. Before connecting JAMS to other applications, it's important to familiarize yourself with its capabilities. For example, some scripts can be executed directly within JAMS, allowing you to create jobs using JAMS' features before relying on external scripts. However, debugging failed JAMS jobs can be time-consuming due to the complexity of the logs. Once you've mastered it, JAMS functions effectively, though the licensing structure is a notable caveat.

    We exchange files on a nightly basis with vendors.

     The ability to protect the data we exchange against cybersecurity threats varies depending on the type of data being exchanged. 

    Which deployment model are you using for this solution?

    Private Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    PeerSpot user
    Peter Hegland - PeerSpot reviewer
    Peter HeglandManaging Director, Automation at a tech vendor with 201-500 employees
    Top 20MSP

    Hi Rahul -Thank you for taking the time to leave us a review. I am the Managing Director/General Manager for JAMS. I appreciate you sharing your views - both positive and negative. If you are willing to speak with me, I'd like to discuss your frustrations with our licensing model as well as the enhancements/fixes you'd like to see in the product. My email is peter.hegland@fortra.com. Best, Peter Hegland

    See all 2 comments
    Buyer's Guide
    Download our free JAMS Scheduler Report and get advice and tips from experienced pros sharing their opinions.
    Updated: November 2026
    Product Categories
    Workload Automation
    Buyer's Guide
    Download our free JAMS Scheduler Report and get advice and tips from experienced pros sharing their opinions.