JAMS

We use JAMS to automate all those repetitive processes and tasks that manually would take hours of our admin's time. We also use JAMS in our file processing for things like FTP, internal file moves, data cleanup, etc so it's become vital to getting things done in our business. The more we use it, the most use cases we're able to discover as word gets out through the business.

• Being able to automate routine, repetitive, and mundane tasks has freed our admins up to focus on improving our environment and reduce task fatigue.
• Being able to automate solutions for other departments has greatly enhanced their ability to accomplish their jobs and has eliminated the need to manually input or convert data to a usable format.

ActiveBatch Workload Automation

Veeam Data Platform, PDQ Deploy & Inventory

JAMS brings all jobs under one roof triggering process across 5 different platforms besides doing its own direct calls via scripts and other file share processes.

It solves the business need of having access to near real time data, allowing jobs to be scheduled as often as needed since the business licensing model does not count triggers

• With better error handling, JAMS improved our infrastructure stability by 30% I would say and helping with the performance optimisation
• Faster recovery having the ability to re-trigger jobs after timeouts or connectivity issues providing increased reliability and business continuity

Control-M and ActiveBatch Workload Automation

Azure Databricks, Jupyter Notebook, MongoDB Atlas, Oracle Database, Microsoft SQL Server

We use JAMS primarily to support all our overnight batch processes, whilst it's true that many platforms like SQL or Windows can run their own internal scheduled jobs, they are inflexible and your flow in unreadable. JAMS allows us to keep track of all of these processes as it seamlessly switches between it's agents and inbuilt users. We have found the system itself to be robust with issues only ever arising from misconfiguration on the human end, indeed we're never actually had an issue with the software itself crashing or not doing what it was instructed. We have also found it incredibly easy to integrate it with many of the other services we use and in cases where there isn't an applicable agent type it has never been more complicated than throwing together a batch script. In terms of scope, our overnight processes total around 1,000 separate jobs so likely 50-100,000 lines of code, this fits entirely within a workflow that is itself comprised of other workflows and sequences.

• SOX auditing has been part automated saving days of work for the people involved.
• The ability for jobs to react to different failure values has enabled us to do away with overnight human monitoring ultimately contributing to saving us in the 6 figures.

Microsoft SQL Server, IBM Storage Protect, IBM WebSphere Hybrid Edition

JAMS is used in 2 ways. One as an Enterprise Scheduler for all types of Jobs and the other type Jobs are specifically for Managed File Transfers using SFTP. The scope of standard Enterprise Scheduler Jobs are becoming more and more SAP centric, while standard MFT Jobs are slowly being replaced by other dedicated services.

• Our company depends on the JAMS Scheduler in executing a large number of SAP Jobs. In never having had a true Enterprise Scheduler such as JAMS before now, we are very happy with the results.
• There a number of features in JAMS for setting up schedules and dependencies on other jobs. This helps our company achieve the necessary workflows for Job execution. This optimization saves on system resources and keeps Jobs flowing smoothly.
• We are very happy that JAMS is a robust solution with High Availability. This is necessary for Enterprise products, to reduce downtime, which we have not had as a result. This feature definitely saves our company money by reducing or eliminating unexpected downtime.

IBM B2B Integrator

IBM B2B Integrator

JAMS is now our single platform for scheduling jobs. It replaced Windows Task Scheduler, SQL Agent jobs and a homegrown solution. It reliable runs job on schedule for various .Net executions, PowerShell scripts and SQL scripts. Before JAMS was implemented, there were times when it was unknown if a job actually ran or not.

• Increased reliability
• Centralized system
• Improved reporting

Microsoft SQL Server, Microsoft Visual Studio Code