Fortra's JAMS (BYOL)
Fortra | 7.7.0Windows, Windows Server 2022 Base 2024.02.14 - 64-bit Amazon Machine Image (AMI)
Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
JAMS Enterprise Job Scheduler
What do you like best about the product?
I like having one access point to all of our servers and batch queues.
What do you dislike about the product?
Interactive Services that could be viewed on Server 2012 no longer can be viewed on Server 2016. I understand that this is a Windows Issue, but it would be helpful if there was an alternative.
What problems is the product solving and how is that benefiting you?
One access point to all of our servers and batch queues.
- Leave a Comment |
- Mark review as helpful
Enterprise Scheduling
What do you like best about the product?
Task Automation that can be distributed across the enterprise.
A number of self help articles provided by the vendor.
A number of self help articles provided by the vendor.
What do you dislike about the product?
I have yet to find a problem or dislike for this software.
What problems is the product solving and how is that benefiting you?
Currently using the software to schedule jobs to make sure that they are accomplished and track the issues they are not completed. I have found that it saves time by automating processes
Recommendations to others considering the product:
JAMS provides a number of resources for implementation like converters and tutorials.
JAMS also has a number of different connectors to allow the schedule to connect to multiple systems on one server.
JAMS also has a number of different connectors to allow the schedule to connect to multiple systems on one server.
Installation and training was on target.
What do you like best about the product?
The options to schedule a wide variety of different job types.
What do you dislike about the product?
The only dislike was FTP options but they are much better in v 7.
What problems is the product solving and how is that benefiting you?
We are solving the problem of multiple schedulers like cron and SQL now use just one scheduler JAMS.
JAMS Scheduler is an great solution to scheduling/creating/managing batch jobs on a single platform
What do you like best about the product?
- JAMS Documentation and User Manual
- Vendor Assistance and Support
- User Friendly Platform
- Vendor Assistance and Support
- User Friendly Platform
What do you dislike about the product?
- Platform Stability
- Troubleshooting Performance Issues
- Troubleshooting Performance Issues
What problems is the product solving and how is that benefiting you?
- Time Saved
- Managing Batch Jobs
- Meeting Business Requirements
- Managing Batch Jobs
- Meeting Business Requirements
Recommendations to others considering the product:
- Provide training for end users
- Require knowledge in Powershell
- Require knowledge in Powershell
JAMS Review
What do you like best about the product?
Ease of complete automation using underlying coding for any module that you need to create. Plus the workflows are pretty cool if you're not a coder. Also, if you are a coder, you can automate almost anything. Gennaro at MVP is a stellar employee and always ready to help.
What do you dislike about the product?
It is pretty heavy IO based, so it can take some time loading.
What problems is the product solving and how is that benefiting you?
Installing the new v7 app along with the v6 app. Having an errorpop-up when I login to v6 app.
JAMS Enterprise Job Scheduler Is a Great Enterprise Tool for Manage Different Tasks
What do you like best about the product?
JAMS Scheduler is a great central place for our all DBA related automation tasks, integrated with application servers. It simplifies the maintenance and monitoring, reduces the operation cost.
What do you dislike about the product?
JAMS has many functions and we only used part of them.
What problems is the product solving and how is that benefiting you?
Central place to schedule and monitor multi tasks from different platform.
Exceptional Job Scheduler Tool
What do you like best about the product?
The most useful feature we found is scheduling of job(s) based on workflow. In which critical business jobs are scheduled and executes in sequence. Without workflow feature we may have to create no of independent jobs.
What do you dislike about the product?
There's none downside of JAMS scheduler. Though with any software/suite there's always room for new features.
Eg: JAMS web client is not as good as desktop client to create complex jobs.
Eg: JAMS web client is not as good as desktop client to create complex jobs.
What problems is the product solving and how is that benefiting you?
Some business critical processes are now handled by JAMS. Eg: Moving, copying, ftping files around internal and external servers for printing and then to ship to customers.
We moved hundreds of windows based scheduled job to JAMS and eliminated some manual intervention by integrating jobs in a workflow. That freed up some man hours which can now be used somewhere else.
We moved hundreds of windows based scheduled job to JAMS and eliminated some manual intervention by integrating jobs in a workflow. That freed up some man hours which can now be used somewhere else.
Recommendations to others considering the product:
One word, exceptional scheduling tool.
JAMS support is amazing. There's always someone available to answer your question and if need be for Gotomeeting or webex. You can bet all your money on their tech support team.
JAMS support is amazing. There's always someone available to answer your question and if need be for Gotomeeting or webex. You can bet all your money on their tech support team.
Very useful tool with excellent customer support
What do you like best about the product?
The ability to use import custom DLLs. Our company has a lot of very specific scheduled tasks, so we found the integration with our own code to be very useful. Also, very knowledgeable Customer Support. JAMS has a lot of different execution methods and different ways to accomplish tasks, so it's hard at first to understand its full power, but Customer Support and the online support knowledge base always has a good answer
What do you dislike about the product?
There are a few limitations in version 6 that we've found, but there is usually a simple workaround available. For example, custom scheduling (which I know is available in version 7).
What problems is the product solving and how is that benefiting you?
Most of our jobs are file transfers, especially across our corporate domain and SCADA domain. Also, we created a lot of custom jobs that integrate with some of our enterprise applications.
JAMS is a nice place to centralize all these scheduled tasks so that certain users can keep tabs on jobs.
JAMS is a nice place to centralize all these scheduled tasks so that certain users can keep tabs on jobs.
Recommendations to others considering the product:
Learn all of what it can do, because you will likely find a solution for your job. Lean on customer support, they are incredibly helpful.
One Ring to Rule Them All!
What do you like best about the product?
We had a myriad of Windows Scheduled Tasks and SQL Agent Jobs spread about on multiple servers. Just keeping track of what jobs, lived where was a job unto itself. There was also risk associated with these jobs running as the SQL Agent or System account when often that was not the best choice. JAMS delivered as advertised by giving us a single place to create, manage, and monitor all of our scheduled processes!
In many cases we were able to leave the functional code in place (i.e. SSIS packages, custom PowerShell scripts, custom executables.) We simply eliminated the SQL jobs and scheduled tasks and replaced them with entries in JAMS. This approach allowed for a quick conversion with greater control over security and an immediate improvement in our ability to monitor jobs execution. Now we're finding many of our new jobs are more easily implemented directly through JAMS using the numerous templates for things like (s)ftp transfers, database maintenance, emailing daily reports, etc.
In many cases we were able to leave the functional code in place (i.e. SSIS packages, custom PowerShell scripts, custom executables.) We simply eliminated the SQL jobs and scheduled tasks and replaced them with entries in JAMS. This approach allowed for a quick conversion with greater control over security and an immediate improvement in our ability to monitor jobs execution. Now we're finding many of our new jobs are more easily implemented directly through JAMS using the numerous templates for things like (s)ftp transfers, database maintenance, emailing daily reports, etc.
What do you dislike about the product?
This may be an odd "dislike", but I did find JAMS to be too "all-inclusive" in one regard......
We have a non-prod and prod instance of JAMS. The former is used as our develop and test environment. JAMS provides it's own version control for every job and an interface that makes it easy for an authorized user to copy a job from non-prod to prod as a means of deploying to production.
So what's not to like about all of that?
Once you get used to using the same tools for all of your development, source control, builds, and deployments, it can be a hard habit to break when something like JAMS includes all of that functionality. And while we have tried to make JAMS work using our regular toolset (i.e. Visual Studio, Git, TeamCity, and Octopus Deploy) thus far it has proven more trouble than its worth. Instead we've been working on ways tailor our change control process and continue to use JAMS as designed.
We have a non-prod and prod instance of JAMS. The former is used as our develop and test environment. JAMS provides it's own version control for every job and an interface that makes it easy for an authorized user to copy a job from non-prod to prod as a means of deploying to production.
So what's not to like about all of that?
Once you get used to using the same tools for all of your development, source control, builds, and deployments, it can be a hard habit to break when something like JAMS includes all of that functionality. And while we have tried to make JAMS work using our regular toolset (i.e. Visual Studio, Git, TeamCity, and Octopus Deploy) thus far it has proven more trouble than its worth. Instead we've been working on ways tailor our change control process and continue to use JAMS as designed.
What problems is the product solving and how is that benefiting you?
Consolidation of scheduled jobs and tasks to a single server and a common interface.
Recommendations to others considering the product:
If you have scheduled tasks and jobs running on more than one server using more than one solution, you should give JAMS a try!
Great support with JAMS helped us running on daily ETL process on time
What do you like best about the product?
Support is helpful to setup the jobs with new features.
What do you dislike about the product?
Nothing as specific, all are very good..
What problems is the product solving and how is that benefiting you?
All of our scheduling jobs is done through JAMS at enterprise level
Recommendations to others considering the product:
Yes strongly recommend
showing 91 - 100