JAMS Reviews

Previously, all the jobs were on different platforms, so the monitoring was not centralized. That was the main challenge about two years ago. After implementing JAMS, especially in staging and production, we have one dashboard or console that we look at every day. It's easier to monitor jobs. It's efficient. We can easily track which jobs have failed. The administrator can work in a productive and proactive way. In one dashboard, we can navigate and see which jobs are running and which jobs have failed or have been successful. We also have direct email notifications. In terms of administration and monitoring, it really helps administrators to monitor 24/7 operations, and when it comes to the business, we give them the capability to monitor the jobs. They can monitor the jobs as well when they are executed in one place. They can navigate to the domain structures from different domains, and they can monitor their own servers every day.

We started with the custom dashboard just two weeks ago. It's easier for us to monitor through the custom dashboard. We're able to customize the dashboard for the things that we want to monitor.

When it comes to automation, we have already implemented a couple of scripts. For example, we have a daily agent check, so we created a PowerShell script to monitor that. Every day, that job executes and checks which jobs agents are offline or inaccessible, and it will then send an email notification to the administrator. We can then check the server status and identify why the server is offline or inaccessible. In terms of automation, we are able to work with the developers based on their requirements. We have already implemented different jobs. We have automated some of the API jobs. We have also automated the process of restarting application services.

We have different batch-processing jobs. Some of them are weekly, and some of them are monthly. We can proactively monitor all batch-processing jobs that are recurring on a weekly or monthly basis.

JAMS saves time when troubleshooting stalled jobs. When we have an issue, we check the logs and the execution history. We also have documentation of the common issues in Confluence. We did not encounter any major issues so far. We haven't had any fatal or severity one issues. They have mostly been basic issues. Most of the time, it was an execution issue. For example, we had a monthly patching activity that affected our servers at times. During patching, the server was rebooted, and the jobs that were running at that time got terminated. We had raised our concern with the JAMS team about the synchronization. When the server is rebooted or restarted, the expectation is that JAMS and the server will synchronize. We encountered this issue in the previous versions. When we upgraded the version, we did not encounter that anymore.

Using an enterprise system like JAMS to manage our jobs gives us peace of mind. In addition, we don't require many administrators for monitoring the jobs. In our current environment, there are only three of us at the moment. I'm working during the daytime, and the other two are working during the nighttime. Three of us are enough to monitor and manage JAMS. It's a time saver because you don't need to monitor it from time to time. It automatically manages everything.

The feature or capability to import a job is most valuable. We can import an existing job from different platforms, and all the configurations get migrated as well without modifying the code, job schedule, etc.

Its integration capabilities are also valuable. There is API, and then there is integration with Snowflake and Power BI. The PowerShell integration is also very powerful.

It has been good so far. We are very satisfied with JAMS' capabilities and features. When I joined the company, we migrated all the jobs from different environments, such as from SQL and Oracle databases, Cron jobs, and Windows task scheduler, to JAMS. We onboarded different departments to JAMS. The product and the business teams are very satisfied as well with how JAMS works. They especially like the self-service capability wherein they can provision or deploy their own jobs in lower environments. Developers are able to leverage different development processing jobs. They are building their own PowerShell scripts and are integrating with other applications through APIs.

The ACL or access permission area needs to be improved. When it comes to defining and providing security permissions, it's a bit confusing if you are new to JAMS. JAMS needs to improve the features for security access or permissions.

I've been using JAMS for about two years. 

From time to time, the JAMS team will update you about the latest release. So, in terms of stability, the JAMS team will support you in maintaining your system. We haven't had any issues with stability. We are very satisfied with that because when they release a new version, we are informed ahead of time. We appreciate that kind of engagement.

Its scalability seems good. We have a lot of users using it. We have 12 to 15 internal departments using it, and we have 300 to 400 users. The roles of its users vary from department to department. The most common roles are developers, QA, business analysts, and managers. In terms of maintenance, there are three of us who are managing JAMS.

Currently, in staging, we have around 500 jobs, and in production, we have close to 1,000 jobs. We don't have any plans to increase its usage at this time. If the number of servers increases, we will plan ahead of time and increase its capacity. 

We encountered a few issues, but we didn't have any major issues so far. When we encountered an issue that wasn't familiar to us or that we couldn't resolve or troubleshoot, we created a ticket. They set up a meeting session with us. We collaborated and identified the issue and documented the issue so that if we encounter the same issue in the future, we have documentation about how to fix the issue.

I'd rate their customer service a nine out of ten. We don't have any issues. When you create a ticket, a good thing is that they respond immediately. Most of the time, I go to the JAMS portal to create and submit a ticket. There's chat support that will immediately respond to your inquiry. That's a good way to submit a ticket to JAMS support. They respond immediately via chat. They also ask you to provide the logs in case of any issues. For an in-depth investigation, they will also schedule a meeting so that they can have a working session to review the issue and resolve it as soon as possible.

Positive

We didn't use any other solution previously. As far as I know, my team was managing the jobs for each platform separately. We didn't have a central solution before. This is the first time that we have an enterprise platform like JAMS.

When I joined the company, the database engineering team had already started to deploy it. It was already set up.

Our setup is standalone at the moment. We have two environments. We have the staging environment. All of our platforms are deployed in staging, and then we have a separate box for production. There is a plan for high availability. This year, we are planning to include that option and implement it.

We have on-premises deployment, and we also have a private cloud. We have Azure, and we are also exploring AWS.

I do take care of the upgrades. The upgrade process is very simple. There is online documentation. The upgrade procedure is quite similar to other solutions.

Based on what I know, we only consulted our JAMS vendor. We did not go to a third-party consultant.

We would have got an ROI, but I'm not aware of the numbers. We are still using this product, so there must be an ROI.

It was already deployed when I joined this company.

We had two internal people who evaluated it and installed it in staging and production. They learned it on their own. When I joined the company, I didn't have any prior experience with JAMS, so they gave me training, and I learned from them. The main challenge was that while learning the platform and its functionalities, we were also doing onboarding. We were migrating different jobs to JAMS, and we encountered some issues. For example, while migrating the jobs, we had to disable them because there was another phase of the project for communicating with the product team and identifying the jobs that needed to be enabled and the jobs that weren't needed anymore. So, we encountered different challenges while importing the jobs, configuring the jobs, and assigning the access permissions, but from that experience, we learned a lot. Overall, it was a good experience.

I'd rate JAMS a 10 out of 10 for its features and capabilities. In terms of features, JAMS has almost all features. JAMS can meet the needs of most companies or organizations at the moment. We don't find any limitations.

We have batch processes that run either on-demand or on a scheduled basis. JAMS is used to manage and run those jobs.

We have realized significant savings in manpower. There's no need for operators to be submitting jobs manually, as it is automated. And the ability to chain a whole bunch of sequences or steps, again, results in labor savings.

It gives us a single pane of glass that allows us to see what is going on and that centralizes the management of jobs on all our platforms. We use it both in a production and non-production environment. We're certainly getting a lot of benefits from that.

And data is ready to go when our users need it, due to the fact that it's scheduling jobs and running them as quickly as the backend systems allow.

Another advantage is that the monitor interface gives very good information, good visuals that are color-coded so that you can quickly jump to where an issue is. That helps save time when troubleshooting jobs. In terms of our IT staff's time, JAMS is probably saving us a few hours a day.

One of the things I like the most, as a SQL DBA, is the fact that we can manipulate tables in the background. Also, the fact that you can have your own views and work with the product the way it fits best is a very helpful feature.

There are alerts if things fail, and we do have that functionality in place. For critical jobs, we also have notification that the job has run successfully. And JAMS is very good at handling exceptions. You can do retries.

In the version that we are using, it does validations when you try to delete an object and if there are any dependencies in place, the deletion process will not proceed for obvious reasons. However, there is no information provided as to what it was that caused the validation to fail. Where is that dependency? Right now, it's quite a tedious process to find which object is getting in the way. Getting information with details of the failure would be very helpful.

Also, sometimes the interface is slow. It will lock up the application for no apparent reason.

I've been using Fortra's JAMS for five-plus years.

It's a stable product. We've rarely experienced bugs or glitches.

It's also a scalable solution.

We have it in extensive use. We have hundreds of jobs that run on a daily basis, both in production and non-production environments. There are no plans at this point to expand our use. There simply is no need to have more jobs running. That said, we are in the process of doing an upgrade from 6.5 to 7, but there is no increase in the number of jobs planned.

I was not at the organization when the initial setup happened. 

In terms of training, we do not have formal training for JAMS. For the operators, it is really a handoff. It is quite intuitive for them. For admins, there is obviously a lot more to the product.

We have definitely seen ROI. It's a great labor-saving tool. The hours that would be required to manually submit and monitor these jobs would be quite significant if we did not have an automation solution in place.

The way that we have it licensed is by the number of jobs. We have two installations and there probably could be a little bit more flexibility in terms of moving licenses between one and the other. However, our situation is that we have one that is a production license and another that is a non-production license, so that may be the issue.

We have five hands-on users of JAMS including two admins and three operators who monitor and release jobs on an as-needed basis. The admins are the ones involved in maintenance, not that they're necessarily needed for maintenance, but they are the ones capable of doing whatever needs to be done.

I would definitely recommend it. Note that there is a learning curve, so you should go in with a plan. But it is highly flexible and very valuable.

It is our enterprise job scheduler. Every batch job that runs in the company runs on JAMS. 

It helps save time when troubleshooting stalled jobs. It has full logging. You go into your single pane of glass, you see all your failed jobs, you click on the job, go straight to the log, and you see what has gone wrong. And if something fails in the middle of the night, with the targeted alerting it sends an email or an SMS and does all your on-call for you. We've been using it for so long that it's hard to say how much time it saves us. But it's probably fair to say it quite easily saved us a day a week, and even more. The time saved could easily be the equivalent of one FTE. And that, of course, allows that FTE to do other work that's beneficial to the company.

One of the most valuable features is the natural language selection. That means that when you are scheduling a job, you've got more flexibility than anything else I've ever come across in the industry. You can not only tell it to run something daily or on a specify a day of the week, but you can specify "the first Monday of the month," or "the second workday of the month," or "the second business day of the month," or "the last business day of the month," or "every other Tuesday." The flexibility in the scheduling is because of JAMS' natural language selection. It's better than anything else on the market that I've seen.

The ability to change jobs is the stock standard for a job scheduler, but JAMS has the ability to allocate resources. We mainly use that at a global level. If we are doing scheduled maintenance, for example, we can halt all jobs. We can set the resource level to zero and no jobs will run. That way, we don't have to go through turning off schedules. For maintenance windows, it makes life an absolute breeze.

The alerting in it is really targeted. You can set a hierarchy of jobs if you like. There is a global level, obviously. But underneath that, you can have folders. We set up those folders at a functional level within the business. For instance, we have a folder for our finance jobs, another for our compliance jobs, and another folder for our equities jobs. At that folder level, you can set specific alerting so that if jobs in a given folder fail, certain people are alerted. You can also set security at the folder level, so that only people in those areas can go set them. That means that the alerting and security can be set at a very granular level.

Another great feature is the full auditing capability. If anyone makes a change to a job, you can see who's changed it and when. That full auditing capability is huge for compliance. And you've got version control, as well. If you make a change to a job and it fails, all you have to do is revert back to the previous version and you're back in business.

In addition, it's built on .NET. If you're a Microsoft shop, PowerShell is exposed natively and seamlessly integrates with it, which is brilliant. We use an awful lot of PowerShell in our organization because we're a Microsoft shop.

But it can run agents on any operating system and it can run all types of jobs. The execution methods it has are amazing. It can run stored procedures, SQL Agent jobs, SSIS packages, batch jobs, Linux jobs, and Oracle. The number of execution methods is huge and it runs just about any type of job you would want to run, and on any platform, which is also huge.

JAMS is also very intuitive and easy to use. It doesn't take a lot of work to set up and get started with it. It integrates natively with Windows Workflow Foundation, so you can build quite complex workflows, with if-then-else structures, and you can run things in parallel or in sequence. It really is a very feature-rich product but it's also very easy to use.

In addition, it helps centralize the management of all jobs and all your platforms and applications. You have a single pane of glass where you're looking at everything. If your organization is big, you might have multiple administrators. In that case, you set security at whatever level you like and certain people can only look at certain jobs. In my case, because I'm effectively the administrator of it in our organization, I see everything. But that one pane of glass for a whole organization is its great strength.

The only thing that they could improve on is the fact that they don't have a browser version of JAMS. They've got all the bits and pieces there if you want to build your own web version of it. It does come with a web client, but it's pretty clunky. They could improve on that.

I have been using JAMS since 2009. I was the first in the Australasian region to implement it. We're currently using version 6.5, but we're in the process of upgrading to 7.3.

The stability is really good. They do have a failover solution, which we're not using. We are just using the standalone, with a single server, but with no problems at all. We have never missed a beat.

We haven't had a problem scaling up. We have over 2,000 individual jobs, and we run 25,000 instances of those jobs every day. We plan to increase our usage as this is the only solution that runs jobs in our company.

All of IT uses it to schedule our jobs. And because of the security aspects, we make ad hoc jobs available to end-users as well. They can go in and all they're able to see, and run, only their ad hoc job. So about 50 out of the 350 people in our organization are using it.

The support is terrific. I've been working with these guys for 12 years and, as often as not, they've come across every problem that I've come across. I'll say, "Oh, listen, I've got this problem," and they'll say, "Here's a piece of code you can run. Here's an example where one of our other clients has done it before and we helped them do it." The support is brilliant; really good.

Positive

When I started with this company, they didn't have JAMS. Because I'd used it at a different company, the first thing I did when I got here was to say, "We're putting this in," and they did. They were running jobs via SQL Agent, as well as Windows Tasks Scheduler, SQL Server Reporting Services schedule, via Linux cron, and someone had even built an in-house job scheduler. Back then, when a job failed, remediating it was an absolute nightmare because nothing was synchronized. There were no dependencies on any of the jobs.

All the monitoring was done manually before, in our organization. Any company of a certain size should have an enterprise job scheduler. If you don't, you're just kidding yourself. You are making a rod for your own back, because someone has to monitor things, whether it's SQL Agent or Window Task Scheduler, to make sure the jobs are all working properly. Because it was manual, things would get missed and it was a nightmare.

The initial setup of JAMS was very straightforward. It was really good and their support staff was terrific in helping with that as well.

You get it up and running in a day, if you've got your servers built. It's a matter of provisioning a server, making sure you've got your service account set up, database ready to go or your database server provisioned. As long as you've got all the bits and pieces, you could be up and running in an hour, really.

ROI is hard to quantify. But whereas in the past we might have had one or more people monitoring batches and remediating failed batches, JAMS does all that now. It frees up one or two people. It's been an absolute no-brainer for us. It's worth its weight in gold and we cannot get rid of it now.

There was a price hike recently, which makes it a lot more expensive than what we are currently paying for it. You can do an enterprise license, which is probably the best value. But it's certainly a lot cheaper than Tivoli and Control-M. In comparison to them, you get a lot more bang for your buck. You get pretty much the whole functionality and more, in some cases, when compared to Control-M, but at a fraction of the price.

Before coming across JAMS, I had worked in bigger organizations that used Tivoli and Control-M. They are what I would call your "Tier One" solutions. Very big companies use them, although I don't know why they do, given that they're super expensive. Both of them are very feature-rich products, but in addition to being very expensive, they're very complex to set up. They also require a very heavy touch to maintain and administer. JAMS is easier to set up, much cheaper, and much easier to administer. 

There's another product called ActiveBatch, which is what I would call "Tier Two," because it's not as expensive as Tivoli and Control-M. ActiveBatch is in the same category as JAMS, price-wise. It has a nice drag-and-drop interface, which is something that JAMS doesn't have, but it's a lot more complex to use and not as intuitive.

Give it a go. Compare it to everything else on the market and, in terms of bang for your buck and the features you get, I would be very surprised if anything even comes close to JAMS.

You put an agent on every box that you want to run a job on. It's not agentless. But, as I said, you can put an agent on a Linux box or a Windows box or whatever other type of box you have and run jobs on any type of OS.

JAMS stays well ahead of the curve. I've been using it for 12 years and I still love it. I've recommended it at every company I've worked for.

We use JAMS to run various tasks, such as nightly claims processing jobs. It's also helpful for moving files around and interfacing between the cloud and our on-prem systems. 

The company has 50 to 100 users, including admins, developers, and on-call maintenance staff. We also have reporting staff who monitor jobs to see if they are succeeding. 

JAMS enables us to formalize simple tasks, reducing the amount of manual work. We can package all the access needed for those tasks, so a non-expert can deal with a problem without disturbing people. It automated 100 percent of the functions that can be automated. It's the only scheduler we have. 

It's hard to quantify how much labor it replaced. It's more than 10 days annually but probably less than 100. It saves staff maybe a day every four weeks. JAMS has centralized management. It is a critical way we deal with multiple systems that interface.  

We have eliminated some tools. For example, we can use JAMS as a monitoring tool and use it in place of Enterprise Manager. Regarding time saved, JAMS saved about 15 to 20 percent compared to our previous scheduler. JAMS also costs less than our last system, significantly reducing operational overhead. 

JAMS handles complex schedules well enough. That's one of the main reasons we use it. We use JAMS to populate our data warehouse every night, ensuring the updated data is available every morning. Troubleshooting failed jobs in JAMS is straightforward. You can navigate the logs quickly, and it sends you an email pointing to the source of the problem. 

JAMS is easier to use and cheaper than our previous solution. The installation is more straightforward, and JAMS has a graphical user interface, so it's more accessible. The interactive processes are helpful. We don't use them often, but it's a nice feature to have.

It sends notifications to the person on-call when a job fails, but the failures rarely have anything to do with JAMS. It allows jobs to restart several times, which often resolves exceptions. I'm satisfied with how it handles exceptions. 

JAMS lacks source control features. Our previous solution had job control language, but JAMS doesn't. When migrating between versions, JAMS doesn't migrate all the data, like job change history, etc. Also, the scheduler doesn't have a way to make jobs invisible, so you can temporarily turn a job off if you decide not to run it today.

We have used JAMS since 2014.

The current version of JAMS is stable. It's more stable than the previous version.

I rate Fortra's customer service a nine out of ten. 

Positive

Deploying JAMS is straightforward. During the initial deployment and migration from the old system, we had to request servers and plan to deploy the client. There were three stages: installation, migrating jobs from our old system, and testing. 

The migration wasn't automatic. We had to reenter most of the jobs from the previous system manually. We took the opportunity to redesign the tasks a little. It wasn't that difficult, and we had no problems replicating the functionality or anything like that. The migration took about six months.

There isn't much maintenance after deployment. We can upgrade to the latest version in two or three hours. 

JAMS is cheaper than our previous solution, and we can run it on any server. The license for our old solution was limited to two servers. JAMS reduced our expenditures by about half compared to the other solution. 

JAMS is much cheaper than our previous solution.

I rate Fortra's JAMS an eight out of ten. 

We have a lot of automation between picking up files and pushing them to our dealer portal and to vendors in the cloud. We also use it so that vendors can place files in folders. In addition, we automatically email statements and inventory reports.

We have some jobs that run once a day at a certain time, but we have many jobs that are set to auto-run if a file shows up. When the time changes or a batch job on another server fails and we restart it, we don’t have to follow the job to the end. JAMS just grabs the file when it shows up and sends it. I love that.

We have over 50 jobs running daily to manage all the integration of our systems and we don’t have to monitor these jobs. They just run. In addition, JAMS centralizes the management of jobs in our environment and this has streamlined our monitoring.

The solution saves us about four hours a week in troubleshooting time and has helped free up about eight hours a week of IT staff time.

Among the most valuable features are

• the ability to define autorun jobs to pick up files and push them when they show up
• the scripting 
• PHP
• the timing.

All of these are perfect.

We also use the solution’s Interactive Agents. If we need to push something to our dealer portal, we can just drop a file in a folder and it goes. Running interactive tasks helps me users focus on business processes since I don’t have to take care of running the jobs manually.

Another useful feature is the solution’s ability to handle exceptions. If there are errors, we get notifications. 

The code-driven automation for handling complex scheduling works great. We have reports that come out and we have programs that will bust them and email them to our dealers by dealer number. JAMS helps with automation.

If there were a softcover book on how to really take advantage of all of JAMS' tools, I would buy it. I do better with training books than online searching, so a book would be helpful. I would read the whole thing and learn as much as possible about the product.

I have been using JAMS since February of 2019.

It is very stable. The only time it stops is when the server is rebooted and then the services are restarted.

It is very scalable and we really use a lot of what JAMS offers.

Technical support has been very helpful and that was particularly true when I hired a new programmer.

We used Freebyte and we needed to move off of that product.

I didn’t do the initial setup, but I didn’t hear any complaints from my programmer about it.

Initially, it took a couple of weeks to get all the jobs set up. But we have added so many more because the software has so many great features. We didn't do a migration from our old solution, we just keyed in all the definitions.

We have two people using and maintaining JAMS, but you don’t need everyone in the company setting up automated jobs, just the programmers and integrators.

This is a good product at a fair price. In addition to the standard licensing fees, there is an annual maintenance cost.

We looked at other options, but this was the best.

Consider how much integration and automation you require. This product is very robust.

Overall, the product is excellent.

We have many batch jobs. JAMS really helps us schedule all the jobs and execute them one by one, or sometimes in parallel, on a daily basis.

We have two schedulers, a primary and a secondary, and we also have a few agent servers. All the jobs are scheduled on them to run.

JAMS helps save time when troubleshooting stalled jobs. Also, in the past, we tried different schedulers. We used to have agent jobs on SQL Server, and we used Windows Task Scheduler, but now we have just one tool. For troubleshooting and maintainability, I don't need to go to different places to find the answer. I just go to JAMS.

The scheduling and execution of jobs are the most valuable features. The scheduling is important because if there is a task we want to execute at 4:00 AM, there's no way we will have someone who can manually run the job. In addition, we execute 100 to 200 jobs per day, and manual intervention is not an option.

I can also set up a workflow that repeats, which is quite good. And if there's something wrong, it will send an email notification so that we can look into it.

Most of the jobs are very critical to our internal business operations. On one hand, they need to be executed, and on the other, they need to be completed within a certain timeframe. JAMS helps split jobs out to our different agents to complete. That's really helpful.

The solution is good, it's reliable. But sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain.

I've been using JAMS for about three years.

In general, it's quite stable. I don't need to worry about it 99 percent of the time. And because we have an HA setup, it's quite reliable. 

The scalability is good. If I have, say, two agents at the moment but I think that's not enough, I can just purchase more licenses and it will support more agents. We currently have six agents.

When I have an issue that I don't know how to fix, I just send an email to them. They are very responsive and knowledgeable. They always fix the problem for me.

Positive

Before using JAMS we used Windows Task Scheduler, but it's not a high-availability setup. If that server is down, jobs won't get executed. With JAMS in place, if the primary scheduler is down, the secondary will pick up all the scheduling responsibility, so we don't need to worry. Even if it is an agent, the job will be executed on other agents.

We had a consultant onsite to help us set up, so it was okay. We migrated jobs from Windows Task Scheduler, or agent jobs, to JAMS. It was not time-consuming, but because we have a lot of jobs it's not like the migration happened within 30 minutes. It took some time, but the process was simple and straightforward.

There is a bit of a learning curve to JAMS. It's not like you install it and it will be up and running for you. You need to learn to use it properly. Otherwise, you may run into issues. We engaged a JAMS consultant who gave us some training. It was expensive, but it was quite useful.

It's expensive, it's not free, but it takes care of my concerns. That is a form of ROI.

It's expensive, to be honest, but it does the job.

I haven't used another scheduler in several years, but compared to the one I last used, JAMS is better. It's more reliable, and that is actually the most important thing.

JAMS' ability to handle exceptions is not the best, but it's good. Don't expect any tool to be perfect. You need to make sure your internal program works together with JAMS to deliver the best solution.

What my team needs are tools to reliably execute all the jobs, minimize the risks, and support high-availability. JAMS does the job.

We use it to schedule batch jobs. Batch jobs are a combination of SSIS jobs, which is actually our group's main use case. I brought it in mostly to schedule our SSIS batch jobs. Then, there are other groups who are using it for SQL Server stored procedures. We also have another group using it for a few Python scripts and FME, which is a different type of ETL tool. So, we are using JAMS to schedule those four types of jobs as well as a bunch of FTP jobs.

The application developers have been doing a combination of migrating some of their older jobs, like Python scripts and SQL stored procedures, and FME jobs over to JAMS. Any new batch jobs that they are creating default to using JAMS. They mostly do interactive online type applications. However, on occasions where they do need batch processes, they just use JAMS.

The fact that we no longer need to use Excel spreadsheets is huge. Before JAMS, every group was keeping track of their own batch jobs. Nobody really knew what the other jobs were. So, if jobs failed, other groups wouldn't necessarily know. With JAMS, everything is done through a single scheduler. You can choose who to notify. 

The ability to work out dependencies between jobs is the most valuable feature, which is actually the main reason why we went with JAMS. We went from everybody trying to keep track of stuff on Excel spreadsheets to being able to see things graphically, and say, "This job should not continue or start unless another job begins." That is very useful. Plus, we have a bunch of jobs that are using File Watchers. So, the job doesn't start up until a file is put on a shared drive, which is the automation that JAMS provides that the old SQL Server agent did not do at all.

It provides notifications. 

The fact that JAMS provides metrics is actually nice, although this feature is not really used that much. Before it was a lot harder to get metrics, whereas there are now metrics if we want them.

The client needs a complete revamp as it is not the most intuitive of methods of setting up jobs.    We have encountered situations like options disappearing and with no obvious way of getting it back, we have had to open up a Support ticket just to figure out how to get the missing options back

I have been using it for around three years.

We are about two versions behind. Our upgrades are done by our infrastructure team. We decided that to reduce the amount of work for them that we were going to limit upgrades to approximately every six months, because JAMS does frequently update their software. For the most part, it is fairly stable. We have basically worked out with our infrastructure team to not update every time a new version is released. So, it is done around twice a year.

The product is quite stable and we haven't run into any major issues.

Our infrastructure is pretty straightforward. It is just SQL Server jobs. It works fine on all our Windows machines. We might be exploring a Linux machine for scheduling a SQL Database job, but we haven't done that yet. 

The plan is to have all our batch jobs managed by JAMS. For various reasons, mostly related to strange quirks, they weren't able to just migrate every single thing to JAMS, but that is the end goal. We want to have a single scheduling tool that manages all our batch jobs.

We haven't really encountered any scalability issues. Most of our jobs run at night. We have a bunch of daily jobs that run every half an hour. Therefore, it has not been a huge strain on the JAM server.

There are not that many users of JAMS, probably five or six. We have one administrator who is part of our infrastructure team who can configure JAMS etc., but acts in more of an implementer role. He was the one who installed the software. Setting up jobs and things like that is left up to my group. There are two people in my group who have permission to create and submit jobs. Then, we have about three or four inquirers who look at the output of the jobs, but don't have the permissions to submit jobs.

Reach out to their support, because they're support is really good.

I would give HelpSystems IT support a nine out of 10, which is really good. I have been very impressed with their support. The only reason for a nine out of 10 is sometimes it takes at least a day for them to get back to me, which isn't really that big a deal. However, for the most part, if we do it within U.S.A. working hours, then I get a response pretty quickly. Also, after hours, I think I have sometimes gotten their London support.

We have had situations where we would hide things and could never figure out how to actually get things back. We would inadvertently just hide things without even knowing that we hid them, then we literally have to reach out to JAMS support. As far as kudos, JAMS support is excellent. They are very responsive. There have been little things like, "We lost a window. How do we get that back?" The fact that you had to hover over a specific area of the UI, then depending on where you hovered, you could get that particular window pane back. That was the first thing that we ran into, because it was like, "We lost this. How do we get this back?" 

I actually was the one who brought the product in. My group was looking for a scheduling tool. Until I arrived, everybody was just using the built-in scheduler, which was fine, but it was impossible to look at things practically or even determine dependencies. So, everybody was just using spreadsheets, but I hadn't. The place I came from, which was the private sector, had money. They were using a full-fledged scheduling software, Control-M, which was really expensive. When I came to San Francisco Public Works, they didn't have it. Therefore, I started looking around to see what was available. 

Previously, we were using SQL Server Agent. Migrating these has been going well. One of the great advantages of JAMS is it can just convert SQL Server Agent jobs directly, which is not ideal because you are still running SQL Server Agent. This is one reason why we are doing things slowly. We are decomposing the SQL Server Agent jobs into steps and scheduling those, rather than running SQL Server Agent jobs.

The initial setup was pretty straightforward. We just followed the instructions that were on the webpage. So, on the actual JAMS site, there are steps you need to follow if you are installing JAMS. We just followed them and pretty much everything worked. 

The deployment took less than an hour. It was pretty quick.

We went from nothing. We just deployed all the new tasks first. So, all of the SSIS jobs that my group had built. These were all new. We didn't really have anything to convert because it was already there. That was the initial phase. That is why it was pretty quick. Once we were comfortable using it, we started to expand the use of JAMS to start converting some of the SQL Server agent jobs into JAMS.

We migrated from an on-prem JAMS to an Azure VM JAMS. So, we actually did a migration, which also involved an upgrade in the process. There was a time when we hadn't upgraded JAMS for over a year, so we were way behind. What we were told by JAMS support is to upgrade our JAMS first, then redeploy it on an Azure VM, and that went without a hitch. I was quite surprised and impressed by how easy it was. Support also said, "If you need us, we can be on the line." We scheduled some time with them, but we never really used them.

We installed the Interactive Agents once. There was an odd case where we were trying to automate a Microsoft Access script or something, which required the Interactive Agent to be installed. This took awhile because of permissions and things like that. Once it was working, it just worked like any other JAMS job. The only hassle was setting it up. We were a bit confused by the documentation. This was at least six months back, but it had something to do with the instructions not being entirely clear as to what types of authentication we had to set up. We reached out to JAMS support, and they said, "Do this." Once we did that, it worked. That was really our only exposure to the Interactive Agents.

We did it all ourselves.

It has been a while since we installed it, but we might have had someone on the line. They actually said, "If you want, we can be on the line." We might have used that, but I don't think we really needed them because it was just click, click, click, and follow the instructions.

We have an infrastructure group, but deployment for JAMS usually defaults to a single person, since he was the one who installed it in the first place. So, he has the most "knowledge" for upgrading patches.

We haven't had the requirement to go beyond our number of licenses. The way that the license is set up, we are allowed a certain number of jobs a day. That is the license that we have, which is more than enough. 

It was $10,000 for the first year. Then, there is a maintenance cost for licensing every year that we get billed $5,000 for every year.

The way that the license is set up = it will allow you to 350 jobs a day. You can install the agent on as many machines as you want, but you can only run 350 jobs a day. Then, if you want more, you pay for more.

I looked at VisualCron. The reason why I picked JAMS over VisualCron was that JAMS got back to me very quickly. VisualCron took two days. They are a much smaller company and took a couple of days before they got back to me. Because the main thing is really the type of support that I could get, JAMS won out over VisualCron, even though VisualCron ironically looks prettier. 

The JAMS client is ugly, but I got support. With VisualCron, which I think is based in Sweden, the time difference would have been difficult, whereas JAMS is somewhere within the U.S.A. In hindsight, it is probably a lot easier to use JAMS because we are the government, so it probably looked better than if I was dealing with someone from overseas. 

Before they were bought over by HelpSystems, they were just JAMS. I spent time on quite a few phone calls with their sales rep, who won me over with their level of support. 

Biggest lesson learnt: It is critical having a scheduling tool that will show you where all the jobs are and what their dependencies have been when you are doing batch jobs. In the past, SQL Server Agent jobs allowed you to do it, but you really needed the ability to look at interdependencies between jobs. That is what JAMS gives you.

The reason why I am giving it a seven is because of the UI. If they fix the UI, I would give a higher grade than seven.

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. 

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.

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. 

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.

We used it for almost two years. 

It's very stable.

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.

Positive

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.

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.

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.