This Scheduler can surely help get you out of JAMS
Overall Satisfaction with JAMS
At WADOR in the Location Services and GIS Program, we use JAMS is used in 2 main types of flows;
- 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.
- 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.
Pros
- Running jobs/application in multiple languages, Python, Powershell etc..
- Smooth UI to create and manage jobs
- Flexible options for scheduling jobs and setting triggers
Cons
- Inclusion of a better coding interface such as Visual Studio Code to improve the script development process and more easily debug jobs.
- Improvement of the Authentication layer; to better integrate with Active-Directory/Azure-AD across the Desktop and Web-Interface to simplify access to managed groups.
- JAMS was not the most cost-effective solution to the original program we were implementing at my Agency; but we were able to expand on the services we do provide using it's power and flexibility to enhance other program areas.
- The cost-model from MVPSI has been great in allowing us to deploy a DEVELOPMENT, STAGING, then PRODUCTION scheduler integrating the platform into our SDLC.
Not Applicable to our Agency/Division.
Do you think JAMS delivers good value for the price?
Not sure
Are you happy with JAMS's feature set?
Yes
Did JAMS live up to sales and marketing promises?
Yes
Did implementation of JAMS go as expected?
Yes
Would you buy JAMS again?
Yes
Comments
Please log in to join the conversation