ActiveBatch Workload Automation Pros and Cons

ActiveBatch Workload Automation Pros

Shaun Guthrie
Senior Operations Administrator at Illinois Mutual
As far as centralization goes it's nice because we can see all these processes that are tied to this larger process. The commissions, FTP processing, the reporting, the file moves to the business users — all that is right there. It's very easy to read. It's easy to tie it together, visually, and see where each of these steps fits into the bigger picture.
The Jobs Library has been a tremendous asset. For the most, that's what we use. There are some outliers, but we pretty much integrate those Jobs Library steps throughout the process, whether it's REST calls, FTP processes, or file copies and moves... That has helped us to build end-to-end workflows.
View full review »
reviewer1319073
Client Service Manager/Programmer at a tech vendor with 51-200 employees
One of the most valuable features is the job templates. If we need to create an FTP job, we just drag over the FTP template and fill out the requirements using the variables that ActiveBatch uses. And that makes it reusable. We can create a job once but use it for many different clients.
View full review »
Bob Olson
Supervisor IT Operations at a insurance company with 501-1,000 employees
The nice thing about ActiveBatch is once we have created a specific job that can be easily be replicated to another job, then minimal changes will have to be made. This makes things nice. Reduction of coding is substantial in a lot of cases. The replication of one job to another is just doing a few minor tweaks and rolling it into production. This decreases our development costs substantially.
View full review »
Learn what your peers think about ActiveBatch Workload Automation. Get advice and tips from experienced pros sharing their opinions. Updated: August 2020.
442,986 professionals have used our research since 2012.
Peter MacDonald
Senior IT Architect at a pharma/biotech company with 5,001-10,000 employees
What ActiveBatch allows you to do is develop a more efficient process. It gave me visibility into all my jobs so I could choose which jobs to run in parallel. This is much easier than when I have to try to do it through cron for Windows XP, where you really can't do things in parallel and know what is going on.
View full review »
Mike Scocca
Data Warehouse Operations Analyst at a leisure / travel company with 1,001-5,000 employees
One of the valuable features is the ability to trigger workflows, one after another, based on success, without having to worry about overlapping workflows. The ability to integrate our BI, analytics, and our data quality jobs is also valuable
View full review »
Georg Johansen
Operations Manager at Statkraft AS
We use the main job-scheduling feature. It's the only thing we use in the tool. That's the reason we are using the tool: to reduce costs by replacing manual tasks with automated tasks and to perform regular, repetitive tasks in a more reliable way.
View full review »
reviewer1424916
DBA at a venture capital & private equity firm with 11-50 employees
From a scheduling point of view, it is pretty good.
View full review »

ActiveBatch Workload Automation Cons

Shaun Guthrie
Senior Operations Administrator at Illinois Mutual
One thing I've noticed is that navigation can be difficult unless you are familiar with the structure that we have in place. If someone else had to look at our ActiveBatch console and find a job, they might not know where to find it.
View full review »
reviewer1319073
Client Service Manager/Programmer at a tech vendor with 51-200 employees
It does have a little bit of a learning curve because it is fairly complex. You have to learn how it does things. I don't know if it's any worse than any other tool would be, just because of the nature of what it does... the learning curve is the hardest part.
View full review »
Bob Olson
Supervisor IT Operations at a insurance company with 501-1,000 employees
There is this back and forth, where ActiveBatch says, "Your Oracle people should be dealing with this," and Oracle people say, "No, we don't know anything about ActiveBatch." Then, it all falls back on me as to what happens. Nobody is taking responsibility. This is the biggest failing for ActiveBatch.
View full review »
Learn what your peers think about ActiveBatch Workload Automation. Get advice and tips from experienced pros sharing their opinions. Updated: August 2020.
442,986 professionals have used our research since 2012.
Peter MacDonald
Senior IT Architect at a pharma/biotech company with 5,001-10,000 employees
I can't get the cleaning up of logs to work consistently. Right now, we are not setup correctly, and maybe it is something that I have not effectively communicated to them.
View full review »
Mike Scocca
Data Warehouse Operations Analyst at a leisure / travel company with 1,001-5,000 employees
The thing I've noticed the most is the Help function. It's very difficult, at times, to find examples of how to do something. The Help function will explain what the tool does, but we're not a Windows shop at the data warehouse. Our data warehouse jobs actually run on Linux servers. Finding things for Linux-based solutions is not as easy as it is for Windows-based solutions. I would like to see more examples, and more non-Windows examples as well, in the Help.
View full review »
Georg Johansen
Operations Manager at Statkraft AS
It could be easier to provide dashboards on how many jobs are running at the same time; more monitoring.
View full review »
reviewer1424916
DBA at a venture capital & private equity firm with 11-50 employees
The interface is not that user-friendly and is a little tough to navigate.
View full review »
Learn what your peers think about ActiveBatch Workload Automation. Get advice and tips from experienced pros sharing their opinions. Updated: August 2020.
442,986 professionals have used our research since 2012.