ActiveBatch from Advanced Systems Concepts in New Jersey is IT workload automation software.
N/A
AppFog (discontinued)
Score 6.6 out of 10
N/A
AppFog was a cloud-agnostic application and infrastructure management platform used to manage workloads across on-premises and third-party cloud environments. It has been discontinued.
$0
Pricing
ActiveBatch Workload Automation
AppFog (discontinued)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
ActiveBatch Workload Automation
AppFog (discontinued)
Free Trial
Yes
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
ActiveBatch Workload Automation
AppFog (discontinued)
Features
ActiveBatch Workload Automation
AppFog (discontinued)
Workload Automation
Comparison of Workload Automation features of Product A and Product B
ActiveBatch Workload Automation
9.6
22 Ratings
15% above category average
AppFog (discontinued)
-
Ratings
Multi-platform scheduling
9.620 Ratings
00 Ratings
Central monitoring
9.622 Ratings
00 Ratings
Logging
9.621 Ratings
00 Ratings
Alerts and notifications
9.622 Ratings
00 Ratings
Analysis and visualization
9.621 Ratings
00 Ratings
Application integration
9.621 Ratings
00 Ratings
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
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.
It was very good to use in small scale projects. Considering the high end projects with many instances and multi-platform architectures, it is better to test before the application is deployed. I think few of the questions can be general - who are the system users and what size is the application focussing on? How much resources are required? Will the application require any additional services?
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.
Primarily because it used to have a good free tier earlier, which it does not anymore. It's simple, and things are available to use. Compared to it's competitors, it does has less features, but that kind of acts in its favor. That adds to the simplicity, and ease of use for a new user.
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.)