JAMS

JAMS is a life saver. We use it to automate our account creation processes and maintain data integrations across many systems. JAMS is like another team member who makes sure repeating tasks get taken care of. We pull HR data from one system and automatically load it to our Active Directory keeping our Mail Address book up to date with Job Titles and Work Locations.

We use JAMS to run jobs to extract data from source systems like SAP, Salesforce, flat files, and other DBS like Postgre and MySQL and bring them into the Azure data warehouse. Then, we run jobs to transform the data via SQL and Azure adf pipelines and refresh Tableau data sources via JAMS jobs for the end users to consume data.

We use JAMS to automate data transfers, quality checks and loading raw data from multiple sources into our data warehouse. JAMS allows us to automate this entire process, which uses multiple programming languages and statistical programs. We work with about 50 different data providers using different transfer processes, and JAMS lets us be compatible with all of these.

We mostly use Jams for reboot scripts and simple scripts like checking if certificates are out of date.

We use Jams for the Job Automation and Processing. The File processing and Data ingestion into our Database is very critical for the success of our business and some of these files we receive from Vendors is nightly and has to be processed in a Sequential order and has to be processed both On-prem and in the cloud. We have automated these processes using Jams Tool

I researched, recommended, installed, configured, administer, and support JAMS.

We use JAMS as a centralized scheduler to manage the scheduling of tasks, jobs, and processes for our Oracle and Microsoft databases and Windows server tasks. Having the schedules in JAMS allowed us to provide better visibility of the details of the processes to different teams and departments while still maintaining complete control of security and access to the individual jobs.

We have been using JAMS for the last few years. We have hundreds of job schedules, mainly running scripts for Sftp file transfer. JAMS is used here for SFTP file transfer internally and externally.

We use JAMS to automate PowerShell scripting and manage active directory and other applications.

We started using JAMS in 2012 to supplement a scheduling ability that was missing in our Order Management system at that time. In 2020, we left that platform for a new OMS that had an internal scheduler. We use JAMS to pick up and transfer files when they become available - File Watches. We use JAMS to run Power Shell scripts to scrub Data, concatenate and de-dupe data files for Sales. We also use JAMS to sequence files that go to our OMS that need to be completed before feeding the next file - combination of File Watches and Network copy commands.

We're a small firm based on staff (~20), but we manage a lot of money as a hedge fund (>$1B). We need sophisticated & reliable tools to manage our systems but require that they can be managed by one person (me). JAMS fits the bill perfectly for us.

We use JAMS as our primary scheduler. All of our ssis package are scheduled via JAMS. Our daily reporting is schedule via JAMS. Most recently working with JAMS support have been able to leverage powershell integration with an sftp solution. Support was able to provide me with a very quick response to an issue that i was having and now i'm writing a best practices document for the entire company to leverage JAMS with a standard approach to SFTP jobs.

We use JAMS for a variety of things. We use it to automate: Scheduling for SAS Data Integration & SAS EDW Triggers within our environment. Scheduling of server tasks such as cleanup and maintenance tasks w/ PowerShell. Movement, SFTP, and Archival Tasks associated w/ a variety of different files throughout our organization. Email tasks to end users about job statuses. We're constantly learning new ways in which we can use the JAMS Scheduler and making process improvements within our organization on a daily basis.

We had been using an old job batch processor for our organisation's batch job scheduling and data processing needs. When we upgraded our Window's Server to 2019, the old program was no longer compatible with the server. When we transitioned to find a job batch processor software that would be compatible with the new server and allow us to have multiple users submit jobs in a much better manner. We looked at a couple of software companies and Fortra JAMS is the closest thing we have found that met our needs, and in some ways, it is better with a more robust system and user-friendly interface. The automated job submission capabilities from within simple applications using JAMS allow us to modernise our data processing methods and job scheduling ques on the new Windows Server.

JAMS is an intelligent scheduler, it helped to harmonize different and scattered jobs schedulers into one platform. JAMS features has helped our organization in multi fold. Be it data availability to Sales Analytics or to exchange data to Vendors, JAMS features like event based scheduling, several integration capabilities and the User friendly UI are helping us to boost the productivity.

We use JAMS as central scheduler and monitor to schedule almost all different application server jobs, SQL Server Jobs. It is a solution not just a tool, to set up and run simple to complex tasks cross the different platforms.

We schedule various jobs to run based on all sorts of dependencies and sequences using JAMS, mostly automation of extracts, data imports, and data manipulation jobs.

JAMS is used to schedule JAMS setups that run Talend Jobs to generate extract files (in .csv, .txt, .xlsx format) from databases in the Hadoop cluster.
The Talend Jobs are used to convert existing output files (from other sources) to extractions from the Hadoop databases, as well as create new client requests for output
I use JAMS to schedule these Talend processes to run on a daily, weekly, particular days of the week, quarterly, specific calendar days of the week, and annual basis.

We use JAMS very extensively to run automated jobs across our environment. This allows us to devote resources elsewhere and also to reduce errors and human mistakes. Our JAMS jobs perform a very wide range of automated tasks across our software applications.

We have about 20k plus job which we schedule at various frequency and time, each with its own duration of execution. We needed an enterprise wide solution which would be able to handle the load of such big setup. JAMS has a big plus of having a customer support which helps us assist the optimal use of the tool.

JAMS is the primary SAS report scheduling tool used by my team, and also used by other teams in our company. We switched from a prior software to JAMS because it allowed us better control in handling failed reports and our prior software was limited in what kind of jobs could be scheduled. In particular, its ability to inherit multiple variables gave us a lot of flexibility for unifying reports.

We currently use JAMS as part of our Automation as an alternative to Windows Task Scheduler or other internal Job Processing software.
In general it it used as a scheduling tool for processes we need to run at regular intervals along with executing Jobs or processes that are conditional based for example file watch trigger or specific time/date triggers etc

We determine and pay workers' compensation claims for government employees. JAMS is used to schedule the nightly claims processing tasks and refresh the Data Warehouse.

At WADOR in the Location Services and GIS Program, we use JAMS is used in 2 main types of flows;

1. Scheduled jobs that run single or multi-step sequences that check folders for uploads and if there is content found executes executables to process data in a managed space.
2. We have WebApps/WebServices that submit a job that kicks off another process that is a managed workflow that then submits other jobs that then submit the next job in the sequence at the right time.

So in this instance we are not only using the Scheduler to schedule and run known/pre-planned jobs but also for job orchestration based on complex workflows.

Right now we are just demoing JAMS, but we would use it to schedule roughly 5,000 unique jobs a day. Anywhere from sending files via FTP, creating files, processing shipping files. We also run SQL jobs that keep our databases clean. The JAMS client seems very user friendly and support has been great in trying to help us learn how to use it. It's not overly complicated to use, just different from what we are used to.