ActiveBatch from Advanced Systems Concepts in New Jersey is IT workload automation software.
N/A
Camunda
Score 7.9 out of 10
N/A
Camunda is a process orchestration tool designed to help organizations design, automate, and improve any process. Built for business and IT collaboration using BPMN and DMN standards, Camunda aims to enable seamless integration across endpoints to transform mission-critical processes.
In our organization we need to schedule job quite frequently and it was difficult to manage as we were doing it manually, thanks to ActiveBatch Workload Automation this feature has been automated and no manual intervention is required, which has resulted in less errors.With the …
The workload automation solution is based on the specific needs of an organization, as well as the features, capabilities, and costs of various solutions. A thorough evaluation process and consideration of these factors can help ensure the selection of a solution that aligns …
It almost works everything good compares to other software, in terms of set up, in terms of cost, in terms of end number of options which is required for any organization you workuseful in planning your daily activities, providing the purchase order for raw materials, track the …
A well-known and established workload automation system with a solid track record for scalability and dependability is Control-M. However, many users note that Control-M is more sophisticated and takes longer to develop than ActiveBatch, which is frequently commended for its …
Users may manage and automate IT activities across many systems and applications using the complete task scheduling and automation platform known as ActiveBatch Workload Automation. It supports several different technologies, such as Windows, UNIX/Linux, Oracle, SAP, and many …
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 …
I was not involved in the evaluation/purchase decision of ActiveBatch as that decision was made at our VP level. So I cannot comment on other product comparison.
During initial selection, we compared ActiveBatch with simple schedulers like Task Manager and cron, as well as VisualCron and JAMS. ActiveBatch had the widest range of triggers and the best scheduler/calendar system, and the most comprehensive list of easily-available actions.
N/A - It was already in place when I was on the scene, but like I said earlier it is much more powerful than SQL Server Agent and probably anything we would've come up with from scratch using .Net. However if your needs are small and traffic is light, then maybe SQL Server …
They're just different products with different target audiences. In different ways, IBM and Pega have offerings that are meant to serve processes in a platform-centric approach to their customers. An emphasis on unified development environments, including forms building, …
Lacks good documentation. Training and documentation is geared towards those who are already technically adept. Does not have as many data integrations as other full fledged products. Paid version of Camunda is not as fully fledged as other products.
Any large business or organisation that wants to manage their workload effectively and with the least amount of room for error might choose the ActiveBatch Automation tool. Being a consultant I feel that It aids in task automation and has the flexibility to change in response to varying company requirements. It helps to save huge time by doing all the repetitive tasks on daily basis. During the patching activity the schedulers can be stopped. It also help by alerting us if any system/job is down so that SLA can be saved. Overall ActiveBatch Automation stands as a dependable cornerstone for ensuring the seamless operation of our tasks.
Camunda Platform is well suited for scenarios where there are different stages in a business flow and the flow is driven by user action at each stage. For example placing of an order on an ecommerce platform. Depending on whether user was able to make the payment or not the workflow would go to dispatch or retry stage. Now the retry stage would trigger further actions like sending follow up emails etc. Likewise, dispatch stage would have a different set of actions. Since every order is important and we need to know where it stands, using Camunda Platform is imperative. Camunda Platform might not be a right choice where just a one off thing needs to be done. For example, uploading of product information by user or periodic processing of heavy images by a worker. These are all either one step processes or periodic automated processes where we can track the status without using a business modeler like Camunda Platform.
String handling / parsing. I find myself using PowerShell to do a fair amount of text parsing (particularly if manipulations are needed) - not necessarily a bad thing, but certainly a place where ActiveBatch could be improved.
Debugging - or lack of it! With no stepping debugger, it can be a longer process than many other programming / scripting environments: rather than simply stepping through and observing state changes, I find myself inserting logging steps to excess, then having to clean them up once the error is found.
The perennial - Documentation! While a near-universal complaint for *any* software, ActiveBatch's developer documentation is somewhat spotty - just where I need detail, I find summary-level info. There is lots of documentation (as there should be for a tool with such a wide range of applications), but it is in mixed formats (some PDF, some CHM), and the descriptions of specific fields within job steps is often little more than I can get in a tool-tip in the GUI. Allowable ranges, expected formats for string data, and similar helpful details are inconsistent.
The KnowledgeBase at ASCI's web site often has examples which answer the questions I have, but not always - and not always under the search terms one would think to use.
Documentation - It is usually daunting for beginners because of lack of good documentation
Simplified setup on local machine for Camunda Server would help developers test changes quickly
Easier migration from one deployment version of a Camunda process to another deployment version would help in making changes and deploying them faster.
Heap memory management becomes issue at times resulting in stuck processes. This needs to be resolved.
We can easily add new plans/jobs in our batch schedules. Also, coordination with reporting and QA jobs is simple to do. Building schedules, restarting jobs, triggering dependencies is easy to understand. The system is very stable and allows us to easily see overall processing times.
The workload automation solution is based on the specific needs of an organization, as well as the features, capabilities, and costs of various solutions. A thorough evaluation process and consideration of these factors can help ensure the selection of a solution that aligns with overall business objectives and meets the specific needs of the organization.
ActiveBatch can automate intricate procedures and minimise manual involvement, which can boost an organization's production and efficiency.
Organisations can save money by using ActiveBatch to automate operations, which lowers the expenses of manual labour and potential mistakes.
Implementing ActiveBatch could come with hefty up-front expenses including licencing, instruction, and consultancy fees, which could have a short-term negative impact on ROI.