What users are saying about
22 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 7.7 out of 100
166 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.5 out of 100

Feature Set Ratings

    Workload Automation

    7.0

    ActiveBatch Workload Automation

    70%

    Ansible

    Feature Set Not Supported
    N/A
    ActiveBatch Workload Automation ranks higher in 6/6 features

    Multi-platform scheduling

    5.9
    59%
    9 Ratings
    N/A
    0 Ratings

    Central monitoring

    6.7
    67%
    11 Ratings
    N/A
    0 Ratings

    Logging

    7.9
    79%
    10 Ratings
    N/A
    0 Ratings

    Alerts and notifications

    6.7
    67%
    11 Ratings
    N/A
    0 Ratings

    Analysis and visualization

    8.9
    89%
    10 Ratings
    N/A
    0 Ratings

    Application integration

    5.9
    59%
    10 Ratings
    N/A
    0 Ratings

    Attribute Ratings

    • Red Hat Ansible Automation Platform is rated higher in 2 areas: Likelihood to Recommend, Support Rating

    Likelihood to Recommend

    6.6

    ActiveBatch Workload Automation

    66%
    11 Ratings
    9.7

    Ansible

    97%
    29 Ratings

    Usability

    7.9

    ActiveBatch Workload Automation

    79%
    3 Ratings

    Ansible

    N/A
    0 Ratings

    Performance

    ActiveBatch Workload Automation

    N/A
    0 Ratings
    8.7

    Ansible

    87%
    10 Ratings

    Support Rating

    4.0

    ActiveBatch Workload Automation

    40%
    2 Ratings
    7.8

    Ansible

    78%
    4 Ratings

    Ease of integration

    ActiveBatch Workload Automation

    N/A
    0 Ratings
    8.6

    Ansible

    86%
    5 Ratings

    Likelihood to Recommend

    Redwood Software

    I can only speak for our environment, but it has allowed us to get away from the unfriendly Informatica PowerCenter workflow schedule. And coordination of Informatica/Tableau/ICEDQ has been a BIG help to us. We have not tried to drill down to the Informatica session-level of detail, just stayed with running workflows. The session-level logic seemed complicated.
    Read full review

    Red Hat

    That is a big task for all the functionality now in Ansible Collections - Ethernet Networking, Fibre Channel Networking, Wireless networking, LB/ADC configuration & changes. Storage config and changes, VMware provisioning and changes, Windows Desktop provision when paired w/ a tool like Zuul, Workflow integration w/ ServiceNow (SNOW), Testing framework such as Molecule really all you to ensure what you have in your playbooks is solid...prior to deployment not when released to your consumers; Critical. Consistent runbooks instead of managing tons of scripts allows for cross-team training and functionality in a true disaster scenario. Additionally, conversion tools from other IT automation offerings Puppet and Chef, integration into Cloud environments. The list grows daily so jump in the water is just right!
    Read full review

    Pros

    Redwood Software

    • File management - moving, archiving, and folder cleanup are a drag-and-drop breeze. The visual representation of file management steps includes date/time filtering, file/folder/both specification, and recursion all in an easy and intuitive unit.
    • FTP/SFTP/FTPS - while one must still write the FTP scripts, the interface simplifies much of the infrastructure, allowing the developer to encapsulate the script text in a graphical package that is easy and intuitive.
    • PowerShell integration - for anything that isn't easy in ActiveBatch's GUI, simply drop in a PowerShell step and write the task in PoSh - anything returned from PoSh can then be used by the following steps.
    Read full review

    Red Hat

    • Agentless. For our implementation, this is the single biggest factor. If we have to touch the machine and install an agent before we can start managing it, that's already too much effort and slows us down.
    • Re-entrant. This is not unique to Ansible, but certainly a huge improvement over custom scripts and such. Because it's such a huge effort to make scripts re-entrant, most of our scripts did not allow an elegant way to recover on failure. Manually cleaning up the half-attempt and re-trying is still too cumbersome, and being able to just re-run Ansible is a great improvement!
    • Infrastructure as code. This is new to Ansible, and there are still a few minor bugs with their AWS modules, but it's been a huge help being able to define our infrastructure in an Ansible playbook, commit it to source control, and use one tool for all our DevOps tasks.
    Read full review

    Cons

    Redwood Software

    • While I like being able to reuse scheduling objects and the like, more work needs to be done to help one not reinvent the same scheduling object without realizing it and to then find scheduling objects that have similar schedules even if they are worded slightly differently than what I'm expecting. It needs to be "smarter". It was easy to accumulate a pool of scheduling objects that while named differently, had exactly the same schedule. It was also hard to sift through to find the little differences between similarly named scheduling objects.
    • The logger had a clean enough interface but it could be more legible and offer contextual help to describe the messages one is reading. I remember trying to read black text on a medium gray background with Courier size 10-11 font. Not so easy to read quickly and to parse through the relevant parts. I think some selective color coding would be good and links to message definitions or any form of further information would be nice. Maybe the ability to export the log file to various formats would also be helpful.
    • I don't remember a dashboard that at a glance on the top level would highlight what jobs failed completely and which jobs might have warnings or non-critical errors. I got emails because I defined to get them. Maybe again if there was a way to color-code the type of error would be good nice-to-have.
    Read full review

    Red Hat

    • Ansible Tower is a paid service, which can be annoying at times. But that is understandable, as it requires an additional level of support from the Ansible team to develop.
    • There is a decently large learning curve for someone not familiar with setting up Unix environments. However, there is a very large support community with tons of documentation, so it's not a dealbreaker.
    Read full review

    Pricing Details

    ActiveBatch Workload Automation

    Starting Price

    Editions & Modules

    ActiveBatch Workload Automation editions and modules pricing
    EditionModules

    Footnotes

      Offerings

      Free Trial
      Free/Freemium Version
      Premium Consulting/Integration Services

      Entry-level set up fee?

      Optional

      Additional Details

      Ansible

      Starting Price

      $5,000 per year

      Editions & Modules

      Ansible editions and modules pricing
      EditionModules
      Basic Tower5,0001
      Enterprise Tower10,0002
      Premium Tower14,0003

      Offerings

      Free Trial
      Free/Freemium Version
      Premium Consulting/Integration Services

      Entry-level set up fee?

      No setup fee

      Additional Details

      Usability

      Redwood Software

      ActiveBatch's usability is where it shines. It is pretty straight-forward to learn and administer. Our engineers like it because you can use a GUI to manage it or leverage the command line & api's. You can also create templates or clone existing "jobs" so you don't have to recreate the wheel. It is easy to chain jobs together to make them run in a specific sequence as well.
      Read full review

      Red Hat

      No answers on this topic

      Performance

      Redwood Software

      No answers on this topic

      Red Hat

      Ansible is very friendly to start with. With just a few configurations, you have full management to your servers. You can configure it and implement it in seconds. You can also set up a cron job to make sure it gets implemented. It suits our need perfectly. Support can be a bit hard.
      Read full review

      Support Rating

      Redwood Software

      We have been pretty happy with ActiveBatch support so far. Luckily, we have not had any major issues with it - so we haven't logged a lot of support tickets. The response time to tickets is about average and the level of expertise of the support engineers seems about average as well. Our sales team has been helpful in getting faster responses when necessary as well.
      Read full review

      Red Hat

      There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
      Read full review

      Alternatives Considered

      Redwood Software

      We looked at several other workload automation solutions and hands down we all looked at each other after seeing the demo and we all understood the genius of the application. To be honest we were all stunned and talked about it for weeks afterward. It didn't even compare to the other platforms we had demos of. We knew instinctively that this was the one.
      Read full review

      Red Hat

      Ansible is a great product, which we really love as it is compatible running along side and with other DevOps tool. The integration features allows other teams to participate in our shared objective. Ansible is easy to use as many programmers are familiar with Python and RHEL. We selected Ansible because its easy barrier to entry and pricing model for new users with not many nodes to manage. We will continue to develop and on-board teams and monitor the scaling abilities of Ansible.
      Read full review

      Return on Investment

      Redwood Software

      • ActiveBatch [Workload Automation] has increased our nightly processing stability exponentially. Our prior automation software was unreliable and often failed without explanation. Since moving to ActiveBatch [Workload Automation] we have had incredible stability, and any nightly processing errors that happen now are attributed to a cause other than automation. It's the most reliable software we currently use at our company.
      Read full review

      Red Hat

      • We have been able to deploy solutions to client issues without impacting uptime.
      • Most system administration tasks have been automated so I am now free to work on architectural improvements or customer support.
      • Our customer support has improved thanks to Ansible as it has allowed me more time away from repetitive system activities so I may assist with customer questions and application testing.
      Read full review

      Add comparison