JAMS is a centralized workload automation and job scheduling solution that runs, monitors, and manages jobs and workflows. Reliably orchestrate the critical IT processes that run your business from a single pane of glass.
N/A
Tidal by Redwood
Score 6.4 out of 10
N/A
Tidal Automation, from Redwood Software since the early 2023 acquisition, is an enterprise workload automation platform for automating and orchestrating cross-application, cross-platform workloads – in on-prem, cloud or hybrid environments – from one central point of control. Tidal is used to optimize mission-critical business processes, manage…
It's just different. The views are different, how you set it up is different. It's not good or bad, just different. I think JAMS offers more options when it comes to how jobs run. Like you can use sequence, or setup a job to run based on a number of different dependencies.
Tidal and Tivoli are great solutions for very large organizations with deep pockets. I have worked with them as an end-user but was not in a position to extend the platforms, so I can't speak to their capability to be extended with custom code as JAMS can with custom execution …
JAMS is well suited for centralizing schedules. We have hundreds of databases, and JAMS has allowed us to centralize the scheduling of all of the individual jobs related to each individual database. This allows certain teams to follow the activity of specific jobs without having to access the individual servers on which the databases reside.
On coming to well suited experience while error handling and effortless recovery processes are crucial, Tidal performs exceptionally well. It can identify and fix automated issues, reducing downtime and interruptions. A smaller automation solution may be more cost-effective if a business primarily utilizes a single platform or uses a small number of applications that do not require complex integration.
Being able to interface / run other programs as either dos window, Power shell window, Python window through configurable execution methods
Purging JAMS history by Parameters, like dates and # of copies to keep of a job
Being able to configure a hot backup to take over in the event a Primary JAMS Server goes down, the backup automatically kicks in after 3 minutes. - High Availability mode
Being able to set up variables that can be used in JOBs / Sequences to hold login information (encrypted), date ranges or other Job Parameter values. And be able to programmatically updated by Power shell scripts to track progress between runs of the same job: count of orders processed, API Skip values when retrieving orders, when the API call only returns X amount per call and you need to get all available orders with multiple calls
JOB logs can be put anywhere on network for other users to access - IT allowing of course. With the high availability option, this is Great, since you don't have to check each of the JAMS Servers for a log when a fail over occures
Tidal Automation allows us to automate and schedule/ perform various tasks in a easy and effective manner. It is highly interactive and effective allowing nearly 4k -5k jobs to run a day.
Tidal is designed to be easily shareable and collaborative allowing multiple users to work at a particular time making work effective.
Tidal allows us to ensure that every event which is triggered is exactly when it's supposed to be regardless of other activities which are going as well.
It is user-friendly to generate the reports required of a particular object and allows us to test the codes perfectly well before executing in live environment.
Prior to JAMS I organized various batch job runs with a user friendly naming process (job, machine, date, etc). I had to jump through hoops to get JAMS to replicate by having a post-completion job rename and copy the log.
Natively support JAMS commands in Powershell7.
Failsafe guard to prevent runaway jobs that submit other JAMS jobs that were improperly coded. i.e. A throttle setting for new JOBS. I once had production go down when hundreds of jobs used up our daily license allocation in under a minute.
I have similar (but different) Execution Methods that would benefit from a shared template. Current setup is awkward to change.
I'd love my job Definitions to be natively linked to github for version control.
Still a bit slow when navigating. If you close a job you have to wait a few seconds to open another one. Even when you made no changes.
When viewing a job and make no changes, the "ok" button changes the last modified date as if you made a change. No big deal, but wastes time when troubleshooting a problem and looking into what jobs were changed last.
You can see the parameters column in the "job activity", but not in "Job definitions".
Can't search the parameters field in the filter.
Changing a variable name does not change it on the job. It still works because Tidal Automation uses the ID number. It just causes confusion when you see a variable on a job and can't find the variable under "Variables". On top of that, Tidal Automation does not show the ID column under "Variables" making it even more difficult to find the variable.
JAMS is an essential application within our organization. There is no chance that at any point in the foreseeable future we would migrate off of the platform or stop our maintenance contract. HelpSystems (now rebranded Forta) releases frequent updates which always add value to the product. The system's reliability and extensibility has earned our trust that it will scale with our organization.
We are on the fence. The increased pricing for renewals is staggering. With new automation options like Microsoft's Power Automate and Event Driven Ansible on the field, there are other options now available.
At first its not 100% obvious what each item is meant for. When you look at the list for the first time there are a lot of objects, its taken some time to figure out what each one does. Once you figure out what each one does it makes more sense.
JAMS has been super reliable in our implementation. The only reason it isn't a 10 is the web client isn't fully functional so the availability suffers very mildly there
We had a very aggressive timeline to look for a new batch job processor that is compatible with our new server that could help us maintain and improve our current data processing procedure. The JAMS support team was there to address our inquiries promptly. On average, their response times have been within 24 hours, ensuring that we receive assistance when we need it
I Was not part of the original Implementation, and the persons did that are no longer with the Organization. But I was part of the recent Upgrade process a year ago and I am the JAMS admin and was very pleased
Having provided consulting services for years on Tidal by Redwood, I recommend going with a solutions partner or consultant to deploy it. I believe there are sizing and tuning guidelines that should be followed for environments of scale. I believe they are not critical when first lighting up the product, but if you are not aware of them you will encounter performance degradation after a few thousand job objects are added.
JAMS is easier to use, provides more features and was easier to manage form a central location. simple features in JAMS were missing from VisualCron such as a projected daily schedule. The install setup with a client and agents was better suited for us too
1. Tidal is good at processing large volume pf data and is cost effective. 2. Tidal can automate the scheduling of production objects, ensure that materials are delivered on time 3. Tidal Process large volumes of data which cannot be done everyday by running codes/scripts manually which does it with ease when required.
I can only speak in in regards to scalability in the volume of jobs we have created. Many of our jobs exist in multiple environments, with each environment having its own unique folder names, connection strings, etc. We incorporate parameters on the folder level that contain the unique environment information. The jobs reference these values from the folder they are contained in, so we can easily copy a job from DEV to TEST and the source is the same but the values passed from the parameters are not. This makes it very easy to create many new jobs and copy them across multiple environments and have them work
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.
