Overall Satisfaction with JAMS
We use JAMS to automate a variety of different processes- SSIS packages, SQL stored procedures, PowerShell scripts, FTP processes and more. These all facilitate our non production and production environments. We work with different state governments and JAMS helps us automation the jobs we use daily to provide the solutions we offer.
- Easy to use- on an basic level JAMS is very easy for users. Running, scheduling and viewing jobs is easy to do and access.
- JAMS provides powerful PowerShell snap-ins that allow developers more flexibility. I commonly use Submit-JAMS entry to run jobs within scripts when needed. For those not comfortable with scripting, JAMS offers Workflows which have powerful drag and drop logic blocks that can achieve the same results.
- JAMS has plenty of additional features for job automation. Resources are extremely useful- they can be used to limit if a job can run based on the available pool. Schedules can incorporate calendars to stop jobs from running on holidays.
- Being able to use parameters/variables in job paths when adding jobs in Sequences would be amazing.
- The built-in reporting tool is very difficult to use.
- I wish there was an easier way to do certain batch operations. Exporting jobs has to be done one at a time for example. Also, if I want to rename a job in seven different environments, I have to manually go to each job and rename them one by one.
- Increased reliability on operations
- Provides a central platform for all users to find, run, and review jobs
- Automation through JAMS has allowed us to focus resources on other responsibilities
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?
I wasn't involved with the selection/purchase process
Did implementation of JAMS go as expected?
I wasn't involved with the implementation phase
Would you buy JAMS again?
Yes