We performed a comparison between ActiveBatch by Redwood and Oracle BPEL based on real PeerSpot user reviews.
Find out in this report how the two Process Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"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."
"Error Handling is one of the best standout features of ActiveBatch."
"It has helped with scheduling complex jobs with simple scripts."
"It can connect to a number of third-party/legacy systems."
"Using this tool, if there are any huge failures, we immediately get an email notification, and the proper team will be informed, at which time they can act accordingly."
"The most valuable feature is its stability. We've only had very minor issues and generally they have happened because someone has applied a patch on a Windows operating system and it has caused some grief. We've actually been able to resolve those issues quite quickly with ActiveBatch. In all the time that I've had use of ActiveBatch, it hasn't failed completely once. Uptime is almost 100 percent."
"The REST API adapters and native integrations for integrating and orchestrating the software stack are very flexible."
"The product has everything we need."
"What I find the most valuable about Oracle BPEL is that it saves me time."
"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."
"I have faced struggles to understand, set up the tool, and implement it in my early days as a new user."
"They have some crucial design flaws within the console that still need to be worked out because it is not working exactly how we hoped to see it, e.g., just some minor things where when you hit the save button, then all of a sudden all your job's library items collapse. Then, in order to continue on with your testing, you have to open those back up. I have taken that to them, and they are like, "Yep. We know about it. We know we have some enhancements that need to be taken care of. We have more developers now." They are working towards taking the minor things that annoy us, resolving them, and getting them fixed."
"Whenever there is an overload, we are seeing crashes happening."
"ActiveBatch UI could use a little more help, and video tutorials would be greatly appreciated for user guides."
"The monitoring dashboard could have been more user-friendly so that in the monitoring dashboard itself we can see the total number of jobs created in the system and how many were currently active/scheduled/chained."
"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."
"The user interface can be improved so that it is more appealing and accessible to new users."
"In the next release, I would like to see REST improved and new technologies for microservices. I'd like to see more containers for separating containers."
"Some user-defined functions for transformation must be added to the next release of the solution."
ActiveBatch by Redwood is ranked 6th in Process Automation with 35 reviews while Oracle BPEL is ranked 18th in Process Automation with 2 reviews. ActiveBatch by Redwood is rated 9.2, while Oracle BPEL is rated 9.0. The top reviewer of ActiveBatch by Redwood writes "Flexible, easy to use, and offers good automation". On the other hand, the top reviewer of Oracle BPEL writes "A highly scalable solution that provides various features for the execution of business processes". ActiveBatch by Redwood is most compared with Control-M, AutoSys Workload Automation, Tidal by Redwood, Redwood RunMyJobs and VisualCron, whereas Oracle BPEL is most compared with Camunda and BizTalk Server. See our ActiveBatch by Redwood vs. Oracle BPEL report.
See our list of best Process Automation vendors.
We monitor all Process Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
