DBA at a marketing services firm with 11-50 employees
Real User
Top 20
Good DR capabilities, responsive and knowledgeable support, good PowerShell integration adds flexibility
Pros and Cons
  • "The most valuable feature for us is that it's DR-ready. With respect to disaster recovery, it has the built-in capability for failover to our DR site. If all of the required ports are open, it can be done seamlessly."
  • "The search capability needs to be improved because when we try to search for a job, it's hard to do."

What is our primary use case?

The initial use case is that we use it to centralize everything, including all jobs from across different environments. Our goal is to be able to do all of the maintenance centrally.

When our jobs run, our team handles the jobs and they are not assigned to other teams. The output, which is on the backend and put into the database, is available for everyone.

How has it helped my organization?

JAMS helps us to deal with the small issues that come up here and there because we implement notifications for jobs. Whenever a job fails, it sends a notification and most of the time, there is a setting in the configuration that has to be changed. We have JAMS configured in a data-driven setup.

Whenever a job runs, it reads the configuration settings that are specific to it. If ever there is an issue, it's typically because we have the wrong configuration. In cases like this, we tweak the configuration and then somebody runs the job again by right-clicking on it.

We have JAMS set up so that we are running two interactive agents. One is a scheduler and the other is exclusive for SSIS execution. These are important to us and without them, it's going to negatively affect the business.

The way that we implemented and use JAMS is in a centralized configuration. We don't have people running jobs on their desktop because it would mean that we don't have visibility of it. Instead, everything has been migrated to JAMS so that it can run centrally. If anybody needs to run a job or perform any execution, especially for production, they can do so in JAMS. Later, we can look and see who ran what jobs at what times, and if ever there is a modification then we will know who modified it.

JAMS is able to handle exceptions in different ways. The way that we have it configured is to notify us. The process may be retried several times and we can set the limit for this. We also configure what the delay is between retries. It will depend on the use case and how long it takes. However, if it fails then it has to notify another group so that they can take a look at what the exception was.

We have a job that is similar to a report subscription, and this is done for each of our 50 partners. Prior to JAMS, we were required to run 50 different jobs. As it is now, given that JAMS is data-driven, we have only created a single job. It is written as a workflow with those configuration items. We don't need to change the job or add to it. Instead, it reads the configuration table and runs the 50 processes right away.

If there is a process that needs to be disabled then we do so in the configuration table, and the workflow picks up the changes. Having a single job taking care of the 50 processes makes the system more flexible.

JAMS helps free up time for our IT staff because it's centralized and the logging is there. The time that IT spends troubleshooting a job has been significantly reduced. The amount of time it saves varies on a case-by-case basis. For a more complex job, it can save more time. If we consider SSIS, it has its own logging capabilities but it requires that somebody with the right permissions go in and open the logs. Not everybody has permission for that, so the job depends on perhaps a single person. Often, that person has several responsibilities and other things to do, so the task can take longer to complete. JAMS collects all of the relevant logs, and having them centralized means that several people can view them, rather than only those with that application-specific set of permissions. This is one of the reasons that it saves us time.

What is most valuable?

The most valuable feature for us is that it's DR-ready. With respect to disaster recovery, it has the built-in capability for failover to our DR site. If all of the required ports are open, it can be done seamlessly.

We test the disaster recovery capability every now and then because it is important for us to be able to failover to another site. As long as that works, if we have a problem then it's business as usual. A problem doesn't impede our work because there's no interruption in the service.

Writing the JAMS schedule is nice because we can use natural language in English. For example, we can specify days by writing "the first of March" or "the second of March". It's clear. Being able to specify the schedule in this way is good.

JAMS saves us time when it comes to troubleshooting stalled jobs because of the logging that it provides. It allows us to go to the execution history, look at the log, and find the problem. Even if the log is very large, it provides a path for us to follow and find what we need to look at. We can typically solve issues in an hour or less because of the logging.

The PowerShell integration is great. When there are things that we couldn't do out of the box, they have execution methods that we can use in PowerShell that make things more flexible for us.

What needs improvement?

The search capability needs to be improved because when we try to search for a job, it's hard to do. We have to know where it is. This is really the functionality that I think is lacking.

Buyer's Guide
Fortra's JAMS
June 2023
Learn what your peers think about Fortra's JAMS. Get advice and tips from experienced pros sharing their opinions. Updated: June 2023.
708,544 professionals have used our research since 2012.

For how long have I used the solution?

We have been using JAMS for approximately three years.

What do I think about the stability of the solution?

JAMS is a pretty stable solution that handles the resources very well. 

What do I think about the scalability of the solution?

This product is highly scalable.

We have two people on the administration side and another ten people who are working with it. They are using it as part of their support role with the helpdesk. We also have a developer that creates the jobs, which are then scheduled by JAMS.

We will probably increase our usage in the future. Right now, we're implementing the web client of JAMS. When we get to the point that we are fully using it, including the web component, then that may be the time for us to look into expanding our usage. At this point, we want to be able to maximize the use of JAMS, and so far, it seems that there's a lot to JAMS that we haven't really used yet.

How are customer service and support?

I would rate the support very high.

First, the response time is very good. When we engage the support engineers, they always know what to provide us with so that we can figure out what's wrong. Whenever we need to go to meetings, it's always a learning experience. They're very smart.

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

JAMS did not replace other monitoring tools and it was able to solve the problem that we had.

How was the initial setup?

I was not the person that initially set up JAMS. It's not complex but that person didn't follow the procedure fully. When I took over the implementation and setup, JAMS provided a checklist. It was good because I was able to follow each of the steps. From what I can tell, in the initial setup, we didn't follow it to a tee, and this caused some complexity on our end.

The deployment took about a year in total, although in a typical situation, I think that two weeks would be enough time to implement it. Depending on how much work needs to be done, it may take a month to complete.

In our team, we have a two-week scrum process and it would be quicker for us to do. Our security and infrastructure are also different than it is in the rest of the organization. For example, we can set up our own VM, database, and scheduler if they are not already set up.

JAMS provides a list of the best practices with regard to security. 

What about the implementation team?

We have two people in-house that are responsible for maintenance.

What other advice do I have?

There are a lot of features in JAMS that we haven't used yet. For example, there is a special calendar and we haven't even tried to utilize it. However, we would like to eventually use it to its full potential.

In summary, this product is top class. I would like to commend all of the engineers and support team at JAMS, and I highly recommend it to others.

I would rate this solution a nine out of ten.

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
Ashley Raak - PeerSpot reviewer
Ashley RaakMarketing Manager at Fortra
MSP

Hi JAMS customer – I wanted to follow-up on your review to let you know our development team is finalizing JAMS v7.5 which will include search capabilities. Be on the lookout for this update coming Fall 2022.

CTO at a financial services firm with 51-200 employees
Real User
Having a single pane of glass enables us to track the success of all of our automations throughout the day
Pros and Cons
  • "JAMS has improved my organization by taking a myriad of manual processes and allowing us to automate them. It enables our folks to focus more on tasks that require their human intelligence and their creativity and less on just mundane tasks. It increases efficiency, accuracy, and consistency."
  • "One thing that I know that the JAMS people said that they were working on that would be huge for us is a search capability so that you could search for tasks. It may be available in version 7 or in a future release of 7. I think that's on their roadmap. But right now, for us to do a search, we have to search through database queries."

What is our primary use case?

Our primary use case is for batch automation. We don't use the RPA product. We use the scheduling agents that can run on other machines so that when the scheduler kicks off the job, it can run either on the main JAMS server or it can run on an agent box.

We do have some interactive jobs that interact with the desktop mainly in Excel, but that's not our preferred method. We want to be, as much as we can, a more structured batch. As far as interactive, we don't have folks that are interacting with the jobs. The jobs are built to run standalone. They may interact with the desktop or with the computer itself to run the job, but the users interact directly with the jobs.

How has it helped my organization?

JAMS has improved my organization by taking a myriad of manual processes and allowing us to automate them. It enables our folks to focus more on tasks that require their human intelligence and their creativity and less on just mundane tasks. It increases efficiency, accuracy, and consistency.

Over the past few years, JAMS has saved them at least 20% of their time. At least.

Its ability to centralize the management of jobs on all of our platforms and applications is a huge advantage. Before we used JAMS, there were pockets of what I would call semi-automation in different places and it was somewhat restricted and not very flexible. We were able to really combine a lot of the automations that were being done throughout the company, add a whole lot more, and all monitor it from the central JAMS console.

JAMS has helped eliminate monitoring tools. We do have some JAMS-related monitoring that goes on. We have jobs that we were having some difficulty with some connections and we implemented some jobs in JAMS that monitor those connections throughout the day. This helped us identify issues faster than some of our vendors which we would have expected to be able to identify those issues. We were able to identify them even faster and actually warn us of issues before they made an impact.

What is most valuable?

Batch scheduling and having a single pane of glass that we can track the success of all of our automations throughout the day are the most valuable features. 

JAMS is very good at helping to handle common nuisances preventing our ops from running. We set up warnings whenever a job is having trouble, and that allows us to address it before it becomes business impacting. JAMS support has always been very helpful in providing us any guidance on how to address issues.

We use their interactive agents. We use agents on a few machines. We have some automations that will run the first part and then wait for a user to release or run a second part. That is used frequently and is very useful, but we don't have a ton of straight-up interaction. We do have some users that interact with JAMS, to release jobs or kickoff new jobs after they've done their checks.

Running interactive tasks helps our users focus on their business processes. Running tasks out of JAMS really helps us to do more with less and rerun as a fairly lean organization. That helps us to maintain that leanness so that we can do more with less. Since adopting JAMS, we have been able to actually reduce staff in areas and not replace them, just because of attrition. We didn't lay people off but we didn't have to hire replacements because JAMS processes were helping.

I think JAMS has a very good engine for being able to identify exceptions. We're probably not using it to its fullest extent, but I think it has pretty good capabilities as far as handling exceptions and if a job fails, how to react to it. 

The code driven automation for helping us handle complex scheduling requirements has been great. We have somewhat complex scheduling that we need to do based on business and holiday schedules and running it on a certain business day of the month and that kind of thing, and it has been no sweat. The support at JAMS has been very helpful in helping us to use that effectively.

What needs improvement?

We are still using JAMS 6.5, so I don't really feel comfortable talking about room for improvement as much because we're still using a little bit of the older version. My understanding is that the newer version has some additional capabilities. One thing that I know that the JAMS people said that they were working on that would be huge for us is a search capability so that you could search for tasks.

It may be available in version 7 or in a future release of 7. I think that's on their roadmap. But right now, for us to do a search, we have to search through database queries.

For how long have I used the solution?

I have been using JAMS for almost seven years. 

What do I think about the stability of the solution?

It's been rock solid. We haven't had JAMS have issues that weren't introduced by other products. It's been rock solid and we depend on it as a mission-critical system.

What do I think about the scalability of the solution?

We have the ability to scale out using more agents on other agent machines so that we could run more jobs simultaneously. I don't think scalability has ever been a problem honestly. I don't know that we really push JAMS all that hard. A bigger company would probably push JAMS a lot harder than we do, but scalability from our perspective has never been an issue.

We run hundreds of jobs a day. We don't have a ton of users of JAMS, but I would say that JAMS benefits almost the entire company in its automation.

How are customer service and technical support?

JAMS support is as near to perfect as we can get, so I would rate them a nine out of ten. They are the best support that we deal with of any of our vendors.

They help to save time when troubleshooting stalled jobs. They're great. They're responsive. They're always willing to jump in and help whenever they can. They're always very knowledgeable and engaging. We love JAMS' support. They've always been very good.

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

We used the Microsoft Windows Task Scheduler, but it wasn't anywhere near what JAMS is.

I had used Tidal before and I found JAMS more cost-effective and easier to use.

The bottom line for me in selecting JAMS was that it was cost-effective, it was not a hugely expensive product to purchase or maintain, and it did pretty much everything we needed it to do for what we were looking for. It has high capability and lower costs compared to its competitors, and that was the deciding factor for us.

How was the initial setup?

The initial setup was pretty straightforward. We have a relatively simple setup. So when we started out with JAMS, it was one JAMS server and we were running most of our jobs on that server. Then we grew with JAMS over the years and expanded it to other machines to run jobs because of the capabilities or the setups of those machines. That was all really pretty straightforward. If we ever ran into any questions or anything, JAMS support has been great.

What other advice do I have?

We've been able to do more with less. In other words, we've either not had to increase staff in some cases, or when people left, we didn't replace them. We've been able to reduce staff. We didn't have layoffs, but when people left, we didn't replace them, and that was largely due to the automation efforts through JAMS.

If I had to do it all over again, I would probably use their professional services to kickstart things. We did a lot of self-training on JAMS, so we've learned a lot along the way, but if I had to do it over again, I would probably have used more of their training capabilities and maybe some of their professional services. My advice to anybody considering JAMS is to get started and because it really helps us a ton for that single pane of glass for managing automated processes.

I would rate JAMS a nine out of ten. 

Which deployment model are you using for this solution?

Public Cloud
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
Ashley Raak - PeerSpot reviewer
Ashley RaakMarketing Manager at Fortra
MSP

Hi Garth – I wanted to follow-up on your review to let you know our development team is finalizing JAMS v7.5 which will include search capabilities. Be on the lookout for this update coming Fall 2022!

See all 2 comments
Buyer's Guide
Fortra's JAMS
June 2023
Learn what your peers think about Fortra's JAMS. Get advice and tips from experienced pros sharing their opinions. Updated: June 2023.
708,544 professionals have used our research since 2012.
Application & Cloud Migration Administrator at State of Minnesota
Real User
Top 20
The scheduling features are nice, and I like how you can add new execution methods on the fly
Pros and Cons
  • "I like how you can add new execution methods on the fly. It isn't overly complex to add Python script support to an execution method in the JAMS system. The scheduling is excellent. You can schedule a maintenance window and take that resource unit out of everything. It halts all of the jobs."
  • "I would like to see the ability to interface with Microsoft group-managed service accounts, but they're still in the research phase. They need to ensure everything's legit and safe. The report designer and dashboards could also be improved. We're running 7.3, so I don't know if they have updated the reporting in 7.5, but I think the reports and dashboards could be better."

What is our primary use case?

I use JAMS to run repetitive tasks that I need to do each day, like loading database entries, performing backups, and building daily reports. The organization uses it for complex workflows, sequences, and ad hoc jobs.

We aren't using JAMS for much complex scheduling. We schedule tasks on weekdays, but we aren't using a calendar to specify holidays. That is something on the to-do list. We want to have it scheduled to run on the work week except for holidays or other exceptions. However, it can run jobs based on sets of schedules and sequences. 

How has it helped my organization?

We consolidated several Windows scheduling servers into the dev and production JAMS environments. A few servers still have custom-scheduled tasks, but we moved most jobs from Windows Task Scheduler to JAMS.

JAMS helps us troubleshoot stalled jobs. For example, if I get a work ticket to check out a failing job, it's easy to look at the log file tab on the job and quickly get the details I need. Error logs are verbose and well-written, so I know what is wrong, whether it's the credentials or a file that can't be found. 

If a job fails or there's a trigger for a bad read text pattern, JAMS will send an email alert. I usually don't hear or see the functions, and I don't know if anybody is watching the monitor tab in the scheduler to see if there are any failing jobs. Aside from any email alerts when a job fails, I have found no real dashboards—at least not with 7.3. It may not be the case with the latest version.

It hasn't enabled us to eliminate monitoring tools so far. Only a few teams use JAMS to send custom monitoring reports, and additional software comes with the VM build. It hasn't been removed. All of the organization-wide tools stay, but some of them might be utilized less. If those teams are using custom JAMS reports more than other tools, it's probably because they could tailor their JAMS script to display the information that's most relevant to their team's needs. 

JAMS provides some flexibility in that aspect. They can run jobs to check the status of the database or Windows services. It gives them the freedom to build those tasks into a sequence or a workflow and get that report back fast instead of using a tool like SolarWinds. You'd need to create a dashboard and find an admin person, and that'll take time, whereas they can just do this quick job, and it gives them the exact information they want. JAMS frees up some at-instance time. Job automation, scheduling, and the ability to pause while other jobs finish saves time. 

What is most valuable?

I like how you can add new execution methods on the fly. It isn't overly complex to add Python script support to an execution method in the JAMS system. The scheduling is excellent. You can schedule a maintenance window and take that resource unit out of everything. It halts all of the jobs. 

We did that when we upgraded the last time. It's helpful because we don't need to worry about upstream and downstream jobs or any triggers and kickoffs. I also like that the JAMS uses PowerShell and has a PowerShell module. 

Regarding JAMS' exception handling, I will say that the person scripting a job should try to catch those exceptions and do their own internal logic for it. JAMS will generate an error if I write a script with an exception, and it'll display that error in the log. JAMS catches it. 

What needs improvement?

I would like to see the ability to interface with Microsoft group-managed service accounts, but they're still in the research phase. They need to ensure everything's legit and safe. The report designer and dashboards could also be improved. We're running 7.3, so I don't know if they have updated the reporting in 7.5, but I think the reports and dashboards could be better.

If I open one of JAMS' pre-installed reports but don't launch it on the server where the scheduler's installed, it will take forever to load through our VPN connections. It may be related to how we have our servers set up. I don't know if that's an issue with JAMS or not, but I need to be careful about where I open the report designer. Otherwise, I will sit there with an endless blue circle. I can open it on my workstation or use a remote desktop to access the server and open it via that. 

It would be helpful if the data in that report designer could be leveraged in Power BI. I don't know if they have that already, but that could be one way to improve the reporting and dashboards. Maybe there's already a way to do that. I should look at their website first or contact support because Fortra's support is fantastic and always super helpful.

For how long have I used the solution?

The company has been using JAMS for about two years, but I've only used it for a year and a half. 

What do I think about the stability of the solution?

JAMS has been pretty stable. We have a single instance, so we're not running high availability, and the uptime has been solid. We have only had to go down to do scheduled reboots for server patching.

What do I think about the scalability of the solution?

It's easy to scale the VM vertically where JAMS is deployed. To scale horizontally and install more agents, we would need to buy more licenses for the agents. It's a matter of contacting support and having the money to buy more licenses. It isn't too difficult to contact our account rep. We don't have problems buying licenses for additional agents. 

It would be cool if we could install multiple agents and have the scheduler server ensure we only use the number of licenses or agents allotted under our licensing agreement. For example, if our prod environment has licenses for three agents, we could deploy six agents that are available to run jobs, but the scheduler would ensure that only three agents are active simultaneously within that environment. That would be an interesting feature.

How are customer service and support?

I rate Fortra's support a ten out of ten. The turnaround is always quick when I email them. They're knowledgeable about it. I can send them a few screenshots and logs, and they respond with some suggestions. They typically resolve the problem on the first try. I haven't used their telephone support, but other people have told me that works just as well.

How would you rate customer service and support?

Positive

How was the initial setup?

I wasn't around for the initial installation when the company first purchased JAMS, but I was indirectly involved with the upgrade from version 7.2 and to 7.3. The upgrade process was extremely straightforward. Fortra's support provided a Wiki article to walk us through it. We backed up the files and performed the steps. You go through the installer to upgrade it.

What other advice do I have?

I rate Fortra's JAMS a ten out of ten.

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.
Flag as inappropriate
PeerSpot user
Aaron Warnke - PeerSpot reviewer
Senior Business Intelligence Developer at a financial services firm with 51-200 employees
Real User
Saves us time, allows sequencing of complex workflows, and has outstanding customer support
Pros and Cons
  • "The ability to sequence jobs is excellent; it means we don't have to schedule them individually, and if one fails, it doesn't unwind the entire workflow."
  • "Fortra is getting much better with documentation and examples, but there is still room for improvement."

What is our primary use case?

We have many uses for JAMS, primarily for jobs in our data warehouse, but also jobs for debt integration, ETL, moving data between organizations, scheduled archives and database maintenance, data quality work, and triggering analytics model updates.

How has it helped my organization?

We used to have a job scheduled to start at 03:00 AM, and it would run to 10:00 or 11:00 AM because we had to add enough buffer time between jobs to account for time variability in individual tasks. This often caused problems in production because the database would still be in use when our staff came in the morning, leading to user reports of sluggishness in the database. With JAMS, this process is completed by 06:30 or 07:00 AM, long before our users get in, so they're happy, and I'm happy. Everything is done by the time I get in to work, and I just have to take care of exceptions if there are any. JAMS is a win for our organization.

JAMS helps to centralize the management of jobs on all our platforms and applications; I transitioned everything over to it so we have a single application to control all tasks, which has been tremendously helpful.  

JAMS helped eliminate ''data slack'' across our applications, ensuring that current data is ready when users need it. Referring back to my previous example, the data warehouse job took until 10:00 to 11:00 AM to be completed, and users had to wait until then for full reports. Now, that's all done before they get into the office.   

The product helped to free up the IT staff's time, especially mine as the primary administrator. It saves me at least two to three hours a week on average.  

The product reduced the time it takes to carry out data warehouse jobs and send out reports by half. 

What is most valuable?

The ability to sequence jobs is excellent; it means we don't have to schedule them individually, and if one fails, it doesn't unwind the entire workflow.

JAMS is excellent for helping us be aware of and handle common issues that can prevent jobs from running. The solution notifies us when jobs go sideways, which is extremely helpful. Additionally, we can change our parameters if the network changes or if adjustments are made, allowing us to quickly alter a bunch of jobs just by updating a parameter. 

We use the solution's Interactive Agents; we deploy them on different servers to run the jobs directly. Adding interactive processes is very important to our organization.   

Running interactive tasks helps users focus on business processes. I'm the primary administrator for JAMS. It helps tremendously by allowing me to offload all the problems that can occur with jobs and all the associated rescheduling and rerunning of them. With JAMS, my job is much easier.  

JAMS is second to none when it comes to handling exceptions, exceptions meaning issues where a job might fail for one reason or another. I can dive into the job, and the log files are centrally located so that I can find the root cause very quickly. I can then address the issue, fix it, and rerun it all from one application.  

The platform's code-driven automation is excellent for helping us handle complex scheduling requirements. There hasn't been anything we haven't been able to do through PowerShell. 

JAMS helps us troubleshoot stalled jobs; it points us in the right direction as the centrally located log files allow us to see how far the job progressed and the specific point of failure. It gives us a good starting point for troubleshooting.  

What needs improvement?

Fortra is getting much better with documentation and examples, but there is still room for improvement.

There are a few minor issues on the schedule for items to be fixed; there are workarounds, but I'm looking forward to a patch that will resolve them more conclusively. There's a built-in report executer to deliver reports, which we can send to an individual, but we can't CC other staff, for example.

For how long have I used the solution?

We've been using the solution for a little over three years. 

What do I think about the stability of the solution?

The solution is exceptionally stable; I can't think of a time when we had any issues.

What do I think about the scalability of the solution?

The solution is scalable, as far as I can tell. We don't do rocket surgery here, so we haven't had to scale, but we could if needed. We have three users in total; two regular and one occasional. 

How are customer service and support?

The JAMS customer service and support staff are unmatched in their ability to assist us and help us resolve issues. I rate them ten out of ten. 

How would you rate customer service and support?

Positive

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

We previously used Windows Scheduler and SQL Server Agent, so these aren't really third-party products or competitors to JAMS as such.  

We didn't migrate from a third-party product but switched from using a SQL agent built into SQL servers. Those jobs are triggered by JAMS now. We did a POC before migrating, and it took about two weeks. 

The migration process was as easy as it could be. Migrations are never easy, but it was as easy as possible.  

How was the initial setup?

I was involved in the solution's deployment, and it was straightforward; it took less than a day. We didn't have much of an implementation strategy as we're a small shop. Usually, one other employee and I work with setting up servers and installation. He did the server setup, and then we configured the product, making minor tweaks as needed.

We did not use a consultant, though we contacted support for some advice, and they were extremely helpful.

What was our ROI?

In time, we have seen an ROI with JAMS, and the ease of use is a significant factor here. I reflect on how much time it has saved me, two to three hours a week, but it likely saves much more time in terms of setting up jobs and so on. On top of that, the visibility into where jobs fail, and the ability to fix issues as a result, makes our entire process more robust.

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

The product is reasonably priced, and we don't have any add-ons.

Which other solutions did I evaluate?

We did a POC with ActiveBatch Workload Automation, but JAMS is the more modern tool, the price is much better, and the ability to script using PowerShell is a big plus.

What other advice do I have?

I rate the solution nine out of ten. 

My advice to others considering the solution is that they will be surprised by how much it will help.

JAMS did not help eliminate any monitoring tools because we had none.

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.
Flag as inappropriate
PeerSpot user
Scott Basham - PeerSpot reviewer
Senior Consultant at Concentrix
Real User
Top 10
Enables complex scheduling and easy-to-build workflows with outstanding customer support
Pros and Cons
  • "The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database."
  • "When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing."

What is our primary use case?

We run thousands of tasks for various purposes, including data manipulation, human resources, data flow, data management, and scripting. We use the solution for any task involving data management that must be scheduled.

How has it helped my organization?

The product gives us an excellent idea of what is happening and when. We have much control over job scheduling, and the workflows work very well. We've also built a lot of complex processing in the workflows where we can configure tasks to run at certain times or only when specific conditions are met, such as if another job succeeds or builds a particular file. The control JAMS gives us is outstanding.

JAMS helps centralize the management of jobs on all our platforms and applications, as it's all in one console. This is very important because we don't need to go to 50 different servers to get the big picture; instead, we can see it from one.  

The solution helped eliminate data slack across our applications; we have much control over the timing and sequencing of jobs, so the data is available precisely when needed. If we can determine when data is required, JAMS can help facilitate that. This availability is essential as data timing is central to many critical applications. 

JAMS saves us time when troubleshooting stall jobs because it's a centralized console where we can see all the failed jobs together and access the logs. Occasionally, we have situations where 20 or 30 jobs fail simultaneously, and we can manage it all in one place, which works very well. The time saved is about four hours per day. 

The product helped free up our IT staff's time, and the team would be larger if we didn't have it, which also frees up time. Using JAMS saves approximately 50% of our time.  

What is most valuable?

The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database.

The workflows are easy to build, and we have a lot of control over how, when, and where jobs will run, which gives us a lot of flexibility. We've been able to do everything we want in JAMS at an excellent price. We've used the solution on many different servers for many applications, so that worked well.

JAMS helps us be aware of and handle common issues that can prevent our jobs from running. We receive emails that show logs from the application, which gives us a good picture of the situation in a failure, with essential information, including the problem and what we need to do about it. 

The solution's ability to handle exceptions is complete, and we have no problems at all with that. 

The tool's code-driven automation for helping us handle complex scheduling requirements is fantastic. It addresses advanced scheduling in our workflows very well and allows us to factor in sequencing, time, dependency on other jobs, etc., giving us great flexibility. This is important to us and a significant part of the solution's capability. If we didn't have JAMS, we would have to build our own mechanisms to manage job sequencing, but JAMS provides that capability in a straightforward WYSIWYG interface that works well. 

What needs improvement?

When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing.

Sometimes it's difficult to find which workflow or workflows a job is in which could be improved.

For how long have I used the solution?

I've been using the solution for about ten years. 

What do I think about the stability of the solution?

Overall, the solution is stable, and that improved over time. We had the occasional issue, but those were more to do with factors on our end than with JAMS. For example, we had the JAMS database running on a very slow server, and we sometimes ran out of server space, which isn't an issue with the solution. When we run out of room, we have to restart JAMS, and it doesn't recover particularly well, but this doesn't cause too much of a problem.

What do I think about the scalability of the solution?

JAMS is highly scalable; we run tens of thousands of jobs daily, and there seems to be plenty of room for more. We have about 50 total users in our company. 

How are customer service and support?

The tech support is fantastic; they're highly responsive, skilled, and knowledgeable. We usually get a good response within an hour when we contact them. We contacted them by phone and used screen sharing when encountering nasty problems. In one case, they spent several days assisting us through a big issue by phone. They've been very supportive and knowledgeable, so I rate them ten out of ten.

How would you rate customer service and support?

Positive

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

I don't remember what product we were working with before JAMS, but when we switched, it was like a breath of fresh air, as the previous solution was very difficult to work with. 

How was the initial setup?

The initial setup was very complex as we had a lot of jobs, and we worked with JAMS Professional Services. The most significant factor is the learning curve. Now I'm familiar with the product, I could go into a new site and set it up within a few hours; experience is an important element. One staff member is sufficient for maintenance. 

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

I haven't been involved in the financial side for several years, but we buy one host and unlimited agents, and we get a reasonable price for that. We're happy with the amount we pay and the scalability it provides.

What other advice do I have?

I rate the solution ten out of ten. 

JAMS eliminated virtually all our other monitoring tools, as 99.9% of what we do is with the solution. We do a few minor tasks in Linux for crime jobs, and we have to use Task Scheduler in a few situations because we can't have centralized processing. We use JAMS 100% where we can.

My advice to those evaluating the solution is to set up your server to run the jobs you need to run beforehand. Those are generally already in place if you're switching from another tool. JAMS is a very lightweight application, so you don't need a lot of processing power. Dictate a host and a failover host server, and you can build a development environment. Still, it is optional as there are decent ways of promoting code from development to production. The solution is relatively straightforward and lightweight.

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.
Flag as inappropriate
PeerSpot user
Student Services SQL Server Manager at Health Care Compliance Association
Real User
Top 20
Saves time when troubleshooting stalled jobs because of the fact that more people can get into it without having the access to the backend
Pros and Cons
  • "The overall product is fantastic. I love it. It has been a fantastic, solid product. If I have one tiny bit of a problem with it, the support team gets in touch with me right away. I don't know if I've had another service that has been as fantastic as the JAMS support team."
  • "I would like a simple web interface that I could give to my team to go in and kill jobs or see why jobs died so that we don't have to drill down deeper into the application and know everything about it. It would be good to have a really clean web engine that would say here are the jobs running. We can then click to see the time running and whether any of them fails and other similar things. I know they have one, but it's not very simplistic."

What is our primary use case?

We have a student information system (SIS) for education. We have 50 school districts that run on the same database, and they all can run reports through the GUI. JAMS manages the reports. We have a throttle so that they don't overpower the system. So, the stuff comes through the system and the throttle manages it, and then if there's a certain report that runs over, we can kill it. They can run it again with better parameters. That's pretty much the main use. We have a lot of nighttime jobs that we schedule through that as well.

It's deployed on our private cloud. We run our own server. In terms of its version, we're on the most recent version.

How has it helped my organization?

If JAMS has a deadlock, we get a notification. When there's a deadlock, it'll kill the job. If something runs too long, it kills it. We also have a throttle, which also helps the whole system to work. If we didn't have the throttle, it would be bedlam. It would be crazy. 

It absolutely helps to eliminate data slack across the applications. It'll kill jobs; it'll kill deadlocks faster; and it'll kill long-running queries. We can get in there, and where the software doesn't allow us to kill the job, we can get into the SQL Server, but JAMS is much cleaner, and more people can get into it without having to expose the database access to people. We can give them JAMS access where they can kill the job.

It saves time when troubleshooting stalled jobs because of the fact that more people can get into it without having the access to the backend. 

It has 100% helped to free up the IT staff’s time. Previously, there used to be two or three of us for monitoring, but now, we've boiled it down just to me. I get the notifications, and I handle them. It has absolutely reduced staff time.

What is most valuable?

The overall product is fantastic. I love it. It has been a fantastic, solid product. If I have one tiny bit of a problem with it, the support team gets in touch with me right away. I don't know if I've had another service that has been as fantastic as the JAMS support team. 

What needs improvement?

I would like a simple web interface that I could give to my team to go in and kill jobs or see why jobs died so that we don't have to drill down deeper into the application and know everything about it. It would be good to have a really clean web engine that would say here are the jobs running.  We can then click to see the time running and whether any of them fails and other similar things. I know they have one, but it's not very simplistic. It would be awesome to have a simple one. 

For how long have I used the solution?

I have been using this solution for about 15 years.

What do I think about the stability of the solution?

It's 110% rock solid. JAMS has never failed us. It has been rock solid.

What do I think about the scalability of the solution?

We only use it for one thing. I don't have any input on its scalability because we don't use it for anything else. We only use it on one platform. So, there's no centralization. We have one main application. It has the front end, the back end, the middleware, and all that jazz. All the jobs to maintain the software are run through JAMS.

We probably use the simplest features of JAMS. We have no complex code-driven things.

How are customer service and support?

I would rate them a 10 out of 10. They get back to you faster than your mom will call you back. When we've had problems, such as if I've had a job that keeps on failing and then I say, "Here's the error code, and I don't know why it's failing," they're right back. They are fantastic. Although I haven't contacted them in probably a year, when we first started up, our software code was sketchy or a little weak, and it failed. JAMS was right there when we had problems with scheduling things. They were fantastic. Their support is amazing. The product is solid. It's as solid as it can be.

How would you rate customer service and support?

Positive

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

JAMS was our first and only one. I know they did a lot of research on it, and they picked JAMS. The whole state uses it. They picked it, and we didn't know. We didn't come from anybody, and we aren't going to anybody, that's for sure.

How was the initial setup?

I've installed it many times. It's simple as a pie. With a few clicks, you are done. It gets done as fast as you can click. It's very simple. As long as you have all the parameters, a database, and your web front end, it's super easy.

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

Our licensing is pretty cheap because we have a state solution. So, we pay only $1,000 a year. 

We're a software provider for school systems. We are state-owned. There are 13 of us throughout Ohio, and we have a collective agreement with JAMS or a collective licensing through JAMS. Because we have so many licenses, we get a discount on the renewal, etc.

What other advice do I have?

I would absolutely recommend it to anybody. If you don't give it a try, you're a fool. At least give it a try because you'll find that it's an easy install. It's an incredibly easy management tool to go around. The setup wizards are nice. It's a little slow on some of the history look-ups, and I don't know why. Other than that, it's very clean with a good front end and easy manageability.

In terms of helping us to be aware of and handle common issues that can prevent our jobs from running, we haven't had anything. It will kill a job if there's a deadlock, and obviously, we get notifications if there are bad parameters in the job run, but I don't have any notifications about not running because of permissions, low resources, or anything like that. We don't have that kind of thing set up.

I would easily rate it a 10 out of 10. With the stability and the support, to me, every day, it's a 10.

Which deployment model are you using for this solution?

Private Cloud
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.
Flag as inappropriate
PeerSpot user
Systems Engineer at Umpqua Holdings
Real User
Top 20
Enables us to identify and address common issues that may impede the execution of our jobs
Pros and Cons
  • "Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution."
  • "It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added."

What is our primary use case?

We utilize Fortra's JAMS to automate tasks within our banking organization.

We utilize a range of jobs for different tasks. Specifically, I possess 1,500 jobs that handle file movements. Additionally, we have approximately 600 SQL jobs, consisting of SQL commands, SSI jobs, and various other types of jobs. Our jobs run on Linux and Oracle, and perform functions such as encryption, decryption, zipping, unzipping, and uploading or downloading through SFTP or FTPS. Furthermore, we employ some visual basic jobs.

How has it helped my organization?

Fortra's JAMS enables us to identify and address common issues that may impede the execution of our jobs. This is of great significance to our organization.

The interactive agents are critical components since we cannot use a JAMS server for SQL jobs due to permission issues. Therefore, we delegate this task to another server. However, this causes the job to be offloaded from JAMS' scheduler, hence the need to distribute the process to another server.

We centralize all of the tasks in our bank, which include Microsoft Windows tasks, scheduled tasks, batch jobs, and scripts. This is a replacement for the SQL job that we previously scheduled across approximately one hundred servers. By centralizing and scheduling these tasks together, the entire process is visible to everyone in the bank. This is critical because if the system goes down, it would affect all banking processes, including ACS payments, ATM, reporting, and other functions. This software is essential for the bank's operations, and without it, we cannot function properly.

Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution. Managing permissions has always been an issue, but we've now centralized permissions for all jobs based on department.

Code-driven automation assists us in managing complex scheduling needs. The system includes a built-in template form. Fortra's JAMS provides the ability to improve the form within the code. This feature is beneficial because we can create our own custom scripts and add them to the system. However, it would be even better if we could add additional forms to the system.

Fortra's JAMS helps to eliminate data inconsistencies across our applications. Essentially, all of our activities occur at the system level, primarily through batch processing. We are not end-users and they do not directly access our system. Instead, we upload reports to SharePoint or similar systems, from where end-users can access them. However, end-users access our reports indirectly and not directly through the JAMS server. We typically share our reports with customers via email, by sending attachments, or by uploading them to SharePoint, OneDrive, or a shared folder. End-users do not directly access our system.

Fortra's JAMS saves us time when troubleshooting. Using the sequence log I have 14,000 jobs running every day.

Fortra's JAMS streamlines our monitoring processes by centralizing scheduling and management, eliminating the need for multiple tools.

Fortra's JAMS freed up the time of our IT staff. Previously, we had 20 servers, each running a different type of application. However, we have now consolidated all of these applications into one system.

Fortra's JAMS saved us the costs of a few full-time employees.

What is most valuable?

All the features are valuable and we utilize all critical features of the solution, such as scheduling, automation, and notifications.

What needs improvement?

It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added.

Fortra's JAMS has an encryption code, but they are not compliant with the open-source GPG program, which is a requirement. They are planning to add the GPG program by customizing and bundling it with JAMS, which would be great. Currently, we are using open-source software, and it begs the question of why we are using JAMS. JAMS has an encryption code, but it lacks a PGP engine in the server or an extra connection. They have added it, but version 7.3 is not functional. However, version 7.5 offers more job features, increased connections to the store, and enhancements to the cloud base, such as Azure, which makes it easier to access the cloud.

For how long have I used the solution?

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

What do I think about the stability of the solution?

Fortra's JAMS stability is great.

What do I think about the scalability of the solution?

Our requirements are met by Fortra's JAMS, and we have not experienced any scalability issues.

How are customer service and support?

The technical support is great. They respond quickly even after hours and are knowledgeable.

How would you rate customer service and support?

Positive

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

Before we switched to Fortra's JAMS, we utilized a MOVEit SQL Server. However, we found that JAMS is a superior solution.

How was the initial setup?

The initial setup is straightforward. A single server can be set up within a few hours while deploying multiple servers may take a few days to complete.

What about the implementation team?

The implementation was completed in-house.

What was our ROI?

We have seen a great return on investment with Fortra's JAMS.

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

There are no additional costs other than the license for Fortra's JAMS which is affordable.

Which other solutions did I evaluate?

I reviewed several solutions online before going with Fortra's JAMS because of the features and price.

What other advice do I have?

I give Fortra's JAMS a nine out of ten.

There are 50 users in our system, but only my team has administrative privileges. This means that while all users can access the JAMS client and run, release, or cancel their jobs, they cannot delete or modify anything. The remaining 46 users are simply managing their own jobs, whereas my team of four has the ability to modify settings.

I used Fortra's JAMS successfully across a variety of jobs and it is highly recommended. The solution saved me a significant amount of money, time, and effort through effective monitoring and other features. Overall, I believe Fortra's JAMS is a great product that can benefit many people.

I have come to understand the importance of centralizing management within our organization for the benefit of both the company and its employees. This facilitates prompt troubleshooting and efficient communication of notifications.

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.
Flag as inappropriate
PeerSpot user
Sr Analyst at a manufacturing company with 1,001-5,000 employees
Real User
Top 20
Centralizes management, provides excellent visibility when a job fails, and has incredibly good support
Pros and Cons
  • "It's a full-featured job scheduling tool. The part that I liked the best was the support team. This tool was new, and we were all learning it and setting up the different jobs that were complex in nature. Their support team was very responsive in helping us out through the setup and resolving the issues. They have been incredibly awesome."
  • "The UI could be better. There were some things that were not quite intuitive, such as the search tool. When we tried to search for jobs, we had to clear the entire search and then go in and enter the new search query. That's something that wasn't intuitive for a new user."

What is our primary use case?

We used it for scheduling our jobs. Our jobs were set up on different servers, which made the maintenance very difficult, and the main reason we switched over to JAMS was that we could have all our jobs from different servers in one single place. Secondly, we had many workflows that had to be triggered automatically, and JAMS was pretty much the tool that we wanted. We found it very useful to do workflow scheduling. 

How has it helped my organization?

JAMS provided all the audit trails. When a job failed, we looked into those trails and then went ahead and fixed those jobs right away to avoid future failures. There were many reasons for failures. Sometimes, it failed to connect to our Microsoft Exchange Server. At certain times, there used to be connectivity issues with our Microsoft Exchange Server. We changed the timing of the job accordingly so that there was not much business impact. That was one of the most common issues that we faced. The other issue was when a file was not received, and it was waiting for a prerequisite to be met. With the email feature that JAMS has, we made sure a proper notification email was sent to the right system instantly so that if a file is not received, the job does not fail. We had set up two hours of time for the job to wait for the file to arrive. That was a very good feature that we did not find in the other scheduling tools that we used.

JAMS saved time when troubleshooting stalled jobs. Because of its audit trail, we could directly go into the error log and see where the error was. With the email notification that we used to get for the failed jobs, the error used to be there as an attachment error log. In case we were not able to log into the JAMS system, we could directly open the log and find the error.

JAMS helped centralize the management of jobs on all the platforms and applications. We previously had different servers, and the maintenance was hard. Some jobs were on SSI servers, and some were on the Windows server. We also had jobs on other servers. We had at least four different servers. Everything was pretty disjointed, and this was our key use case to switch over to JAMS.

What is most valuable?

It's a full-featured job scheduling tool. The part that I liked the best was the support team. This tool was new, and we were all learning it and setting up the different jobs that were complex in nature. Their support team was very responsive in helping us out through the setup and resolving the issues. They have been incredibly awesome.

The email notification that we received was also valuable. I liked that part because if there was any job that failed, it was good that we were notified instantly. That's one part that we liked. Also, we had to run multiple interfaces on the JAMS server, and we were able to do that very easily.

It's the best tool to schedule jobs. It's super easy and super transparent. Once you know how to set up a job, you can easily train the users. It provides excellent visibility if something fails. 

What needs improvement?

The UI could be better. There were some things that were not quite intuitive, such as the search tool. When we tried to search for jobs, we had to clear the entire search and then go in and enter the new search query. That's something that wasn't intuitive for a new user.

Sometimes, when we used to search for jobs, it did not give us the status. There was system slowness or something like that. I am not sure if that had to do with JAMS, but that was something that we noticed.

For how long have I used the solution?

We used it for almost two years. 

What do I think about the stability of the solution?

It's very stable.

How are customer service and support?

Customer support was the best part of JAMS. When we needed instant help, especially when something in production failed, their support team was excellent. I would rate them a nine out of ten.

How would you rate customer service and support?

Positive

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

We had separate systems for scheduling. We did not have a single centralized solution, and that's why we went for JAMS, but now, we have moved to a different platform, which has an in-built scheduling system. The usage of JAMS is very limited now. Our IT team uses it, and I use it when there is a failure and I get notified.

Which other solutions did I evaluate?

We evaluated a couple more schedulers, but JAMS received the highest score overall. That was the reason why we went ahead with it. We did the initial feasibility and analysis of various different tools. There were about three solutions that were short-listed, and out of those, JAMS made it.

What other advice do I have?

We are not using JAMS much now because of the new platform, but based on the time for which we used it, I would definitely recommend it to others. We were pretty impressed with it because we were not sure how much to expect from this job scheduler. We were very happy with it.

It's definitely something that we can vouch for. It's an easy-to-use tool, and it's full-featured. There are so many other features that were shown to us during the demo. We didn't use all of them, but it does come with a whole lot of features. It's very stable. 

Overall, I would rate it an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user