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.

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.

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.

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

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.

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.

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.

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.

Positive

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

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.

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.

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.

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

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.

On-premises

We use Fortra's JAMS as our orchestration and scheduling platform to manage workloads executed on various timelines, from daily to every few minutes. Additionally, we incorporate ad hoc workloads, manually scheduled by individuals as needed.

JAMS support has been among the most helpful and knowledgeable we've ever worked with. They're always eager to assist and quickly find solutions. While a few minor issues required escalation, we've been able to resolve them all within the current version of JAMS. 

After initial misuse, we have optimized the use of several agents deployed in our environment. This improvement was made possible through collaboration with internal stakeholders and guidance on JAMS best practices. While agents might appear to directly solve user problems due to their ability to perform custom tasks on machines, in our cases, they operate behind the scenes, unseen by users.

JAMS handles exceptions well, especially when calling PowerShell scripts, successfully bubbling up errors.

It centralized our job and orchestration management functionalities into a single control plane, providing visibility into previously siloed work. This consolidation streamlined operations and enhanced oversight through a unified dashboard. Additionally, JAMS empowered us to build advanced processes by effectively managing retries, workflows, and sequences. Without JAMS, replicating this functionality would have been manual and inefficient, lacking the comprehensive visibility and control JAMS provides.

Data Slack refers to delays in data pipelines caused by disparate and siloed processes. Using JAMS, while powerful for scheduling and orchestration, can exacerbate this issue if teams break down processes into isolated tasks within different tools. This fragmentation leads to data sitting in queues and folders, awaiting processing. To improve efficiency and timeliness, it's recommended to consolidate these fragmented processes entirely under JAMS. This allows JAMS to execute the entire workflow from start to finish within a single execution, eliminating data slack and ensuring timely data delivery.

JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful.

I appreciate JAMS for its readily available templates that allow me to create and deliver stand-up presentations within minutes quickly. This efficient feature has been invaluable, enabling us to streamline our workflow and enhance productivity.

JAMS' flexibility by allowing the use of PowerShell scripts adds to its value.

The monitoring of the JAMS product and its performance is an area of concern for me. I also need better tools to adopt version seven. Another area for improvement would be the addition of source control for jobs internally, as this feature would solve several problems for me.

JAMS has some quirks. It has a bit of a learning curve.

Some exceptions are not intuitive, such as when a job is terminated due to exceeding its defined runaway time limit. This generates a misleading exception message that is difficult for new users to understand and requires experience to interpret correctly.

Stalled jobs present a unique challenge, particularly when pushing a system like JAMS version six to its limits. While rare, these instances occur when jobs become unresponsive despite appearing in API queries but not in the monitoring console. Although workarounds exist, they highlight the need for improved native monitoring capabilities within JAMS. Currently, the system assumes flawless operation, necessitating supplemental monitoring tools to detect issues like excessive pending or stalled jobs, ensuring timely intervention by our teams.

I've been the platform owner of Fortra's JAMS for four years now. Before that, I used JAMS at Fortra for several years.

Through our outdated JAMS version 6 installations, we process approximately half a million executions per hour, significantly exceeding the supported capacity. Despite surpassing the rated limits by five times, we generally maintain stability. However, we experience periods of major incidents annually due to capacity constraints, which result in job failures. These performance concerns are attributed to the high execution volume. Conversely, our version 7 environment, which handles fewer jobs, has proven to be much more stable.

If I am below those capacity issues, JAMS scales very well. However, at higher capacities, like over three hundred thousand executions, there are significant performance issues.

The customer service is of high quality, and their response is prompt, exemplifying how support should be.

Neutral

The initial deployment of JAMS is deceptively easy. However, there are some caveats, particularly regarding SQL permissions when setting up the database, which my team encountered. Beyond the permissions aspect, the process is straightforward; my team completed the initial setup in less than a week, with most of that time spent resolving permission issues. 

I have experience with Ansible, which can handle similar workloads as JAMS. Both have their pros and cons.

I would rate JAMS a six out of ten. It is a solid platform with caveats in scalability.

First, understand the inheritance system in JAMS, as it is not apparent. Then, consider using execution methods to streamline processes and reduce variance between jobs. 

On-premises

We use Fortra's JAMS to schedule jobs.

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.

The dashboard is intuitive.

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.

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

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.

It scales very well

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

Positive

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.

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.

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

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.

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. 

Private Cloud

Microsoft Azure

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.

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.

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.

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.

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

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

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.

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.  

Positive

We switched from a homegrown solution to JAMS.

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.

The pricing is reasonable.

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.

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. 

On-premises

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.

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.

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.

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.

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

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.

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

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. 

Positive

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. 

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.

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.

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.

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

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.

On-premises

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

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.

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.

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.

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

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

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.

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.

Positive

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.

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.

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.

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.

Public Cloud

Amazon Web Services (AWS)

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. 

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. 

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. 

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. 

I have used JAMS for about six or seven years.

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. 

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. 

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. 

Positive

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.

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.  

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. 

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. 

On-premises

I've used the solution across three employers. I've used it in the context of government, tech services and health care. Everything is IT-related, so everything from ordering supplies to finance applications, everything gets filtered through JAMS. It helps with automation. 

At my previous employer, we were working on a project with the tax controller of our state. And the company I worked for was providing a tax solution for them. Part of that was us being able to provide a solution, but they also had to have their own users be able to interact with the software solution that we provided them. That required them to have their own user accounts and privileges and all that for JAMS, and it was all tied into an SQL database. Instead, if someone joined the controller office or they changed positions or roles, typically, someone would have to go to that SQL database and manually update those records. What I did was I created a series of JAMS jobs that would allow someone just to run a job. It would ask for the basic stuff: their name, their role, and their privilege, and it would update that for them. It made something that was really complicated and annoying super easy.

I really like PowerSchool scripting. It's really easy for me to produce some really cool code. People will ask if a certain job is possible to do with JAMS and I tell them it is. 

The JAMS database offers a lot of flexibility in tapping into it. It's good at offering additional functionality. 

The automation aspect is fundamental to what JAMS is for. If you want to schedule something to run every Monday at 8 AM or whatever, it will work without fail.

The code-driven automation is good for helping us handle complex scheduling requirements. That's a cool thing. JAMS has a lot of flexibility with being able to automate. You can just use the built-in features to run a job. However, you can also just code that into a job using PowerShell. I lean more into writing codes rather than relying on built-in functionality. That is really big for me.

Currently, we use both Windows and Linux servers, and that creates a lot of issues when it comes to talking between two different operating systems. But we're able to get by with that since JAMS has built-in capabilities to call Oracle directly and it can also call SQL. It doesn't really matter what operating system you're running on. 

JAMS is good for helping us be aware and handle common issues that prevent our jobs from running. I have jobs I've built and checked on. I can look at the state of servers to foresee if there are going to be any issues. If we have critical processes that run at 5 AM and the server is offline, then the job will fail. However, we can check-in, or it will give us alerts so that we can see what's going on and fix the issue before the job can fail. 

The solution's ability to handle exceptions that we have created has been sufficient.

JAMS helped eliminate data slack across our applications. We get these reports in, and they need to be run from a Windows server into a Linux server and ingested there. I just created a job this morning that would transfer these files to the Linux server, and then we would run some sort of features that would load them up. It's easy to do that.

The built-in triggers are great. If a file comes in, someone doesn't have to manually look for it. We just have jobs that will scan folders to see if files come in or if they're removed. It makes remedial tasks obsolete as they can just be automated. We've freed up about 20% of staff time as there have been a lot of opportunities to automate manual effort.

JAMS has built-in reporting. I've never really used it. I tried using it a few years ago and I couldn't figure it out. It was wonky. It could be improved upon.

There's a projected schedule pipeline that's never really worked for me. They could fix that and make it more user-friendly. 

I've used the solution for about nine years overall. 

It's an absolutely stable product. While I don't mean to sound negative about the web version, I will say the desktop client version has been rock solid. I'd rate stability seven out of ten since the web version skews a bit slow. If we were just talking about the desktop version, I'd rate the stability ten out of ten. 

The scalability is good. I'd rate it nine out of ten.

About 20 people use the product in my current organization.

JAMS support is fantastic. I've been bothering them for years, and they always get back to me right away. They're amazing.

There was a different solution in place that the company chose not to use. My current company migrated all of the jobs over to JAMS.

The initial setup is straightforward. We did a migration and were able to set it up in one to two hours and five people were involved. The migration itself was finished within a month's time. The main issue was handling the volume of everything they had to migrate.

There isn't really any maintenance needed. There are just some backend things, like whenever a job runs, it creates a log file, and those need to be cleaned up. Otherwise, they begin to build up. Then, every once in a while, you may have to do an update. That's about it. 

Resource-wise, we've definitely witnessed an ROI. 

The pricing is completely reasonable. 

The solution has positively impacted productivity. The ability to able to automate manual tasks and being able to check on file transfers, et cetera, has been great. It helps tremendously.

Right now, we're using version 6 of the solution; however, we're actively talking about getting version 7 this summer. 

I'd rate the solution ten out of ten. 

On-premises

We use Fortra's JAMS as a job scheduling tool for state agencies across the country. We primarily use it for scheduling jobs and development tasks related to taxation processes.

I find the historical tracking feature of JAMS invaluable for reviewing past events. Customizable workflows with dependencies and variables allow for more complex task management. Additionally, notifications through JIRA and excellent customer support enhance the overall experience with the software.

Improvements could be made in the service desk's knowledge and communication skills among engineers to better address customer needs and ensure issues are fully resolved. Additionally, reintroducing or offering a mobile platform could enhance accessibility and usability for users.

I have been using Fortra's JAMS for almost nine years.

We haven't had any stability issues with the solution so far.

Scalability in JAMS could be improved by enhancing word-of-mouth marketing and providing more training or demo videos for new users. Additionally, incorporating performance monitoring features could help users better scale their usage of Fortra's product.

Tech support for JAMS is generally good, with responsive and helpful engineers. However, there have been instances where the initial engineer wasn't able to address the issue and needed to escalate it to another resource. Overall, I would rate the support as an eight out of ten.

Positive

The deployment of JAMS was straightforward once we bought the solution. Additionally, the sales team responsible for handling licenses and project costs was also easy to work with.

I rely on JAMS to help me identify and address common issues that may prevent jobs from running smoothly. I typically start by checking their support site and documentation for solutions. If I can't find a solution, I search for existing tickets or create one myself. It would be beneficial if JAMS provided a community forum where users could share and resolve issues together, enhancing support for all customers.

Agents are crucial for our organization as they enable us to scale and balance processes across multiple servers. They effectively bridge the gap between structured batch automation and tasks happening on desktops and web browsers. However, we encountered an issue with a specific server's agent, which was initially challenging to diagnose. While JAMS eventually identified the problem as a database issue, there was some initial uncertainty about the cause. Overall, while agents are valuable, there can be challenges in fully understanding and addressing issues related to them.

JAMS handles exceptions effectively, but it requires users to have programming knowledge to implement them. It is not a no-code or low-code product, so users need to understand programming languages to utilize its full capabilities. Simplifying this aspect could make it more accessible and user-friendly.

Centralizing job management across all platforms and applications is highly important to our organization. It ensures that schedules and processes are properly handled, which is critical for both our customers and the public, especially for public-facing processes. Effective management reduces the risk of errors and enhances accountability for all stakeholders.

JAMS's code-driven automation is beneficial for handling complex scheduling requirements. While the website documentation may not cover all scenarios, support tickets allow engineers to assist. However, the quality of the response can vary based on the engineer's experience, leading to different levels of resolution.

JAMS saves us a significant amount of time when troubleshooting stalled jobs.

JAMS has helped us eliminate the need for monitoring tools like AutoMate. AutoMate was a simpler tool we used in the past, but JAMS provided more advanced features and functionality.

JAMS has helped free up our IT staff's time by automating tasks, which reduces the need for manual QA and troubleshooting efforts.

Before purchasing JAMS, new users should consider the scale of their operations, including the number of jobs, servers, and agents needed. Understanding these factors will help determine the budget and ensure the system meets their requirements.

Overall, I would rate Fortra's JAMS as a nine out of ten.

Hybrid Cloud

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

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.

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. 

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.

We have used JAMS for almost a year 

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

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. 

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.

Positive

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. 

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. 

On-premises