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.
W…
Verified User
Administrator
Chose ActiveBatch Workload Automation
Control-M seems to be a more mature product with a cleaner user interface, however, ActiveBatch has the same functionality.
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 …
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.
Businesses can use ActiveBatch to plan tasks based on parameters like frequency, dependencies, and the time of day. By automating typical actions like backups and data transfers, businesses can make sure that crucial operations go off without a hitch.
Multiple systems and apps can be used in complicated workflows that ActiveBatch can automate. For instance, it can automate a workflow for processing orders from beginning to end, from the customer order through inventory control and delivery through the processing of invoices and payments.
Files can be sent between many platforms and systems safely with ActiveBatch. Transfers to cloud-based storage systems like Amazon S3 and Microsoft Azure are also included in this. SFTP and FTP transfers are also included.
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.
I have not run numbers to determine hard impact, but a quick estimate is that at least one job is running for a average of about 6 hours per day - that 6 hours, if done by hand, would equate to about 30 - 40 hours per day (and in some cases, could not be duplicated manually, as the job repeats faster than a person could accomplish one cycle.)