JAMS

It's suited for a vast number of scenarios. They have delivered a solution for every use case we have devised in the last six years.

JAMS is great at automating processes that need to send information and variables across multiple platforms and programs. The scheduling functions and file watch triggers are pretty user-friendly and function well.

Jams needs much more documentation when creating jobs and clearer feedback when running jobs that it didn't like the parameters/settings of. I've had times when I clicked from one tab to another and the script block was empty when I came back. That was infuriating. Otherwise, it schedules things, does what it was tested to do, and sends notifications, so there's utility in it.

Its been well suited where Automation is used. Soem older legacy modules/companies used in built or Nightly Ops people to ensure processing happened in a timely and correct order, Jams does it best without a need for a fulltime FTE doing that.

The application overall is pretty good and does what we need, but there a room for improvement with fewer steps to conduct activities. The web URL is unusual but the console works well. There is no graceful failover. Jobs fail when failover to HA pair. Upgrades and patches are easy to perform.

JAMS is well suited for centralizing schedules. We have hundreds of databases, and JAMS has allowed us to centralize the scheduling of all of the individual jobs related to each individual database. This allows certain teams to follow the activity of specific jobs without having to access the individual servers on which the databases reside.

simple interface and easy configuration with robust application great technical support

JAMS is a great place to store source code for scripts and run them automatically. In its current state it is used well as a tool rather than an all encompassing solution. It works great to run scripts as different users and in different environments but lacks in its ability to be the development ide and be a one stop shop containing all the information you would want to know about a specific job. The documentation of this product is lacking but the support is good making it time consuming when getting started and coming up to speed when trying to use the product.

Being able to create your own execution methods for running SQL Scripts against a DB. Set up a method to run an API call to another program and pass in parameters, like interfacing to Go Anywhere / MFT to call a project to run with or without parameters. Interfacing to an AS400 / IBMi for remote submitting jobs after sending the files to be processed to the AS400. Running API calls to outside systems for picking up orders and processing them into another API call to internal systems using Powershell on an automated schedule starting at 3:00 AM until 11:00 PM at 1/2 hour intervals.

For my small environment I haven't really come across any examples where JAMS wasn't a fit. It's a huge improvement from the "free" option of Windows Task Scheduler (obviously not even close).

As mentioned previously, I use JAMS for a variety of tasks. Automate executing powershell scripts, sql queries, sql agent jobs, reporting etc. There seems to be no limitation in the variety of jobs JAMS can handle.

I use a lot of PowerShell scripting with JAMS. There isn't much, considering, that I have yet found that has limited me with JAMS with regards to file manipulation, file movement in our local environment as well as SFTP jobs. The more we learn, the more heavily we rely on JAMS to perform tasks within our organization.

Our team found JAMS to be reliable and an ideal tool for handling our automation, queue, and scheduling needs. We valued proactive and clear communication, and our dedicated JAMS account manager made it a priority to keep us informed at every step of the way. We had a very stringent and aggressive timeline to implement a new job batch processor to keep the project moving forward and our account manager was very accommodating and responsive. Whether it’s updates on ongoing issues or proactive tips to enhance our experience, their team has your best interest in mind.

Several types of jobs, accommodating different OS and event based triggering has helped us a lot. Especially, in the Sales Analytics area, whenever there is a change in external or internal data and events, JAMS jobs were triggered as per the nature of the events to perform different Commercial operations.

It is a powerful tool, support many sources, easy to setup for different tasks.

The automation of jobs with JAMS is great.

I am very pleased with what JAMS offers for basic scheduling of processes (great flexibility on 'Scheduled Date' / required frequencies.

I am not too experienced with the triggering functionality of JAMS (did have a bad experience with my setup of one ..didn't work), but the dependencies processing is excellent.

It's well suited for any task you want to automate in your IT environment. I see issues with JAMS for our larger clients where the JAMS jobs have to run for an extended amount of time and they end up failing often.

Best appropriate when you have thousands of jobs to schedule and need an Enterprise level solution which has a good customer support. They need to better the license subscription model and need cloud support to be suited for scenarios which need cloud support too.

JAMS is at its best when you already have a solid framework for reporting and just need scheduling software that works. Once it is set up, it is far better to manage than any similar tool. However, if you intend to fiddle with the jobs frequently, and want to set up and then iterate on jobs, you will see more of its weaknesses.

JAMS is well suited for Operational Tasks and Jobs or Processes that need to be run on a schedule. It works well and has plenty of opportunity to add as much or little detail in terms of Job Task, Method, Error Catching, Inputs/Outputs etc. For Example I could be a one-line cmd or a 2000 line PowerShell scripts filled with functions/Switches parameters. Great log files, multiple notification options.

My one con for the system is the Job numbers, although that is not a JAMS restriction rather the license we have purchased.

Support are worth mentioning as they are fast and accurate when I have a question relating to jobs and tweaking setups.

JAMS has a small footprint, is quick and easy to install, populate with jobs and deploy to users, and includes a (working) Web Interface. This licensing is SME-friendly (good value) based on a very practical metric, jobs run per day. It can allow unlimited agents machines which give huge flexibility.

The best way to determine if/when you need service layer like this is; if you are in a place where you have to manage multiple job-streams that need to be both scheduled on various regiments as well as triggered ad-hoc then JAMS is a magnificent solution. The flexibility to run Command-Line apps, PowerShell Scripts, Python Scripts; in such a powerful way is really a driving factor towards this.

If all you need is to trigger a job every hour, or once a day; then Windows Scheduler would be much more cost-effective.

In the limited time I have had to work with JAMS, it has been very easy to schedule SQL jobs and the types of jobs we run as a company. We do use a product called Ecometry that's very old. I have a support ticket open to make sure JAMS will work with it, but from what I have found it actually integrates better than our current software.

the source tab is well suited to handle many execution methods from windows, unix, to file transfers.