TrustRadius
ActiveBatch from Advanced Systems Concepts in New Jersey is IT workload automation software.https://dudodiprj2sv7.cloudfront.net/product-logos/WV/p8/T7GLG1IIAG0I.PNGAutomate the process and free your timeActiveBatch is used by our organization to automate redundant tasks, both internally and externally. Many of our departments have 'jobs' they've created, to run processes that would normally occur during working hours. With ActiveBatch, these processes can now be set to 'trigger' at scheduled times throughout the day and throughout the night. This saves from having one person being assigned with running and managing the individual tasks. And since the jobs are scheduled, the processes can run during the weekends and holidays, saving employees time and the company money.,Easy to automate mundane tasks. Take all those batch files spread across your environment and put them in one application for management. Good support site and knowledge base. If you run into issues, the support is quick to respond and assist with a resolution or advice. Additional 'extensions' (plug-ins) are available, to aid ActiveBatch with interfacing with other platforms (AWS, Sharepoint, IBM and VMWare).,The manual could provide more examples of how to create certain jobs, otherwise you will need to check the site or call support to aid with creation. Dashboard presentation could be worked on, to help present an overview for management.,9,Saves employees time and sanity, from having to manually run tasks at certain times. Cost is not overly expensive, considering the amount of platforms it integrates with "out of the box." Takes control of sensitive processes, and runs them confidentially. Alerts management when completed.,Microsoft System Center Configuration Manager, HP Operations OrchestrationActiveBatch is a job automation tool that fits our needs wellWe are using ActiveBatch across multiple departments. Our collections team is using it to gather customer payment history from a Microsoft SQL database. Our billing application runs through ActiveBatch and feeds the billing data to the data warehouse. Through ActiveBatch, our business unit's reports are made available, or they receive ActiveBatch alerts indicating an error occurred in the data generation and details about the error.,ActiveBatch does Microsoft SQL jobs well, providing centralized configurations. The scheduling options and flexibility is very good in ActiveBatch. The ability to restrict ActiveBatch users to specific areas of the application is easy to manage.,The Oracle connectivity and error detection is challenging and doesn't always work for us. The UI for administration is overwhelming as first and could be simplified.,8,I have not been involved in the purchase or contract negotiation of our Active Batch purchase, therefore am unable to comment on the ROI.,Control-MA Great Solution For AutomationActiveBatch usage in the company has expended extensively from its v4 days when it hosted just 6 jobs. Now, with over two thousand jobs and dozens of workflows, it touches and does processes for just about every department within the company; claims, sales, I.T., finance, H.R., and now the mainframe. It allowed us to set standards for how users write jobs and security of the systems. With the addition of the web server component, end-users can access the system via the web GUI instead of providing them server console access. In training the users, we set forth policies for how to write/use code/elements of the system so that others, not familiar with the system, can quickly identify where issues are and target their efforts in those jobs. After our security audit, use of the ActiveBatch increased since it hooks into our encryption software....well, it hooks into a lot of applications specific to our needs. With any workflow, comes a different set of requirements, and ActiveBatch has allowed us to meet or exceed every one of them.,Interaction with other third party software. Interacts with encryption software, various 'partner designated' sftp software, file manipulation software, etc. Variety of options for users based on experience in accomplishing the same things as 'coders'. Someone like me wouldn't need to use the Jobs Library too much but users who are not comfortable with code can accomplish the same tasks using the drag/drop functionality of the pre-built jobs library. Security. Allows the admins to secure every single element of the system; plans, jobs, accounts, etc. Easy to use by the end-users.,Lack of continued development for the non-jobs step library items. Updates sometimes 'break' previously working functionality; the email trigger comes to mind. Lack of development of what can trigger jobs/processes.,10,Less errors since taking humans out of the processes. Security tightened on the servers. Standards set.ETL processing you can set up once and forget aboutIt was and still is being managed and integrated into other internal systems by the whole IT DevOps team, but forms a critical layer that services our entire organization in providing automated linkage between my former company's systems and those of their clients. On any given week the company would have literally hundreds of file import/export transactions that need to happen on a single day, every day, every month, or some complex combination of days at different hours of the day and night and consistently ActiveBatch delivered. It allowed for the efficient design and redesign of import/export jobs (such as being able to reuse schedule objects, allow for the partial execution of nodes for a particular job to help with testing, and effortlessly change parameters from testing to development deployments), logging of transaction errors, and ability to work with the wide variety of file processing tools that we would use internally (ETL, SSIS packages, .NET code, etc.) It's relatively intuitive design allows for it to be used and managed by people with even a bare minimum of IT experience, without sacrificing power and reliability.,One good feature I already mentioned is that once you create a configuration object (such as a schedule object), you can reuse it as much as needed. This minimizes errors in scheduling because there's less opportunity to make a configuration error with future similar jobs that would follow the same schedule, makes it more efficient to schedule those new jobs, and makes it efficient to make scheduling changes--change the scheduling object once and all the related jobs' schedules are automatically changed. Partial path execution is a good strength, especially for testing/debugging. I can have a decently sized tree of process nodes for a given job, but I can easily deactivate the nodes I do not want to include in my testing. Being able to define test and production jobs in separate environments and easily change the settings of one without affecting the other is another strength. Often I would have a job set up in a test environment and after testing it, it would get ported to a very similar production environment with only having to change 3-4 parameter settings. And then I could easily deactivate the test job while still keeping it all set up in the event of needing it for future enhancement/troubleshooting.,While I like being able to reuse scheduling objects and the like, more work needs to be done to help one not reinvent the same scheduling object without realizing it and to then find scheduling objects that have similar schedules even if they are worded slightly differently than what I'm expecting. It needs to be "smarter". It was easy to accumulate a pool of scheduling objects that while named differently, had exactly the same schedule. It was also hard to sift through to find the little differences between similarly named scheduling objects. The logger had a clean enough interface but it could be more legible and offer contextual help to describe the messages one is reading. I remember trying to read black text on a medium gray background with Courier size 10-11 font. Not so easy to read quickly and to parse through the relevant parts. I think some selective color coding would be good and links to message definitions or any form of further information would be nice. Maybe the ability to export the log file to various formats would also be helpful. I don't remember a dashboard that at a glance on the top level would highlight what jobs failed completely and which jobs might have warnings or non-critical errors. I got emails because I defined to get them. Maybe again if there was a way to color-code the type of error would be good nice-to-have.,8,Definitely increased ETL tool testing and deployment efficiency for the IT DevOps staff. Troubleshooting and retesting of problems with using ETL tools is enhanced, but there's definitely room for improvement there. Emails and logging helped but didn't really provide any additional help to those provided by GlobalScape and Microsoft. So a positive, but not a strong positive there. For as much data that it manages coming in and out, the errors that came up were certainly important to deal with very quickly and this product could make that aspect better, the errors were few and far between and almost always the errors had nothing to do with ActiveBatch itself (usually with the quality of the data it was handling)--so in that sense, it brought visibility to areas of quality improvement to be made between the company and the clients.,
Windows, Linux, Mac, UNIX, Mac OS, IBM z/OS, Hyper-V, VMware, and more
ActiveBatch IT Automation
7 Ratings
Score 8.6 out of 101
TRScore

ActiveBatch Reviews

ActiveBatch
7 Ratings
Score 8.6 out of 101
Show Filters 
Hide Filters 
Filter 7 vetted ActiveBatch reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Reviews (1-4 of 4)
  Vendors can't alter or remove reviews. Here's why.
April 18, 2017

ActiveBatch Review: "Automate the process and free your time"

Score 9 out of 10
Vetted Review
Verified User
Review Source
ActiveBatch is used by our organization to automate redundant tasks, both internally and externally. Many of our departments have 'jobs' they've created, to run processes that would normally occur during working hours. With ActiveBatch, these processes can now be set to 'trigger' at scheduled times throughout the day and throughout the night. This saves from having one person being assigned with running and managing the individual tasks. And since the jobs are scheduled, the processes can run during the weekends and holidays, saving employees time and the company money.
  • Easy to automate mundane tasks. Take all those batch files spread across your environment and put them in one application for management.
  • Good support site and knowledge base. If you run into issues, the support is quick to respond and assist with a resolution or advice.
  • Additional 'extensions' (plug-ins) are available, to aid ActiveBatch with interfacing with other platforms (AWS, Sharepoint, IBM and VMWare).
  • The manual could provide more examples of how to create certain jobs, otherwise you will need to check the site or call support to aid with creation.
  • Dashboard presentation could be worked on, to help present an overview for management.
It's great for basic tasks or tasks that need to run in a certain sequence. Especially import/export jobs, where the next step can only work when the previous job has completed. It does have some issues where a tasks may run into an error (file location not available) and may not always prevent itself from continuing to run the job.
Read Ron Zermeno's full review
March 24, 2017

Review: "ActiveBatch is a job automation tool that fits our needs well"

Score 8 out of 10
Vetted Review
Verified User
Review Source
We are using ActiveBatch across multiple departments. Our collections team is using it to gather customer payment history from a Microsoft SQL database. Our billing application runs through ActiveBatch and feeds the billing data to the data warehouse. Through ActiveBatch, our business unit's reports are made available, or they receive ActiveBatch alerts indicating an error occurred in the data generation and details about the error.
  • ActiveBatch does Microsoft SQL jobs well, providing centralized configurations.
  • The scheduling options and flexibility is very good in ActiveBatch.
  • The ability to restrict ActiveBatch users to specific areas of the application is easy to manage.
  • The Oracle connectivity and error detection is challenging and doesn't always work for us.
  • The UI for administration is overwhelming as first and could be simplified.
ActiveBatch is an excellent tool to distribute to multiple teams across the organization, allowing developers, application support, business units as well as mangers to create the tasks they need and maintain their configurations, without having to wait on a central point of support.
Read this authenticated review
November 03, 2015

ActiveBatch Review: "A Great Solution For Automation"

Score 10 out of 10
Vetted Review
Verified User
Review Source
ActiveBatch usage in the company has expended extensively from its v4 days when it hosted just 6 jobs. Now, with over two thousand jobs and dozens of workflows, it touches and does processes for just about every department within the company; claims, sales, I.T., finance, H.R., and now the mainframe. It allowed us to set standards for how users write jobs and security of the systems. With the addition of the web server component, end-users can access the system via the web GUI instead of providing them server console access. In training the users, we set forth policies for how to write/use code/elements of the system so that others, not familiar with the system, can quickly identify where issues are and target their efforts in those jobs. After our security audit, use of the ActiveBatch increased since it hooks into our encryption software....well, it hooks into a lot of applications specific to our needs. With any workflow, comes a different set of requirements, and ActiveBatch has allowed us to meet or exceed every one of them.
  • Interaction with other third party software. Interacts with encryption software, various 'partner designated' sftp software, file manipulation software, etc.
  • Variety of options for users based on experience in accomplishing the same things as 'coders'. Someone like me wouldn't need to use the Jobs Library too much but users who are not comfortable with code can accomplish the same tasks using the drag/drop functionality of the pre-built jobs library.
  • Security. Allows the admins to secure every single element of the system; plans, jobs, accounts, etc.
  • Easy to use by the end-users.
  • Lack of continued development for the non-jobs step library items.
  • Updates sometimes 'break' previously working functionality; the email trigger comes to mind.
  • Lack of development of what can trigger jobs/processes.
I found it suited for just about anything. Currently ActiveBatch sits on a Windows environment, but it can hit the Linux servers by calling WinSCP or Putty to perform actions on the Linux servers.
Read Ruben Santiago's full review
November 06, 2015

ActiveBatch Review: "ETL processing you can set up once and forget about"

Score 8 out of 10
Vetted Review
Verified User
Review Source
It was and still is being managed and integrated into other internal systems by the whole IT DevOps team, but forms a critical layer that services our entire organization in providing automated linkage between my former company's systems and those of their clients. On any given week the company would have literally hundreds of file import/export transactions that need to happen on a single day, every day, every month, or some complex combination of days at different hours of the day and night and consistently ActiveBatch delivered. It allowed for the efficient design and redesign of import/export jobs (such as being able to reuse schedule objects, allow for the partial execution of nodes for a particular job to help with testing, and effortlessly change parameters from testing to development deployments), logging of transaction errors, and ability to work with the wide variety of file processing tools that we would use internally (ETL, SSIS packages, .NET code, etc.) It's relatively intuitive design allows for it to be used and managed by people with even a bare minimum of IT experience, without sacrificing power and reliability.
  • One good feature I already mentioned is that once you create a configuration object (such as a schedule object), you can reuse it as much as needed. This minimizes errors in scheduling because there's less opportunity to make a configuration error with future similar jobs that would follow the same schedule, makes it more efficient to schedule those new jobs, and makes it efficient to make scheduling changes--change the scheduling object once and all the related jobs' schedules are automatically changed.
  • Partial path execution is a good strength, especially for testing/debugging. I can have a decently sized tree of process nodes for a given job, but I can easily deactivate the nodes I do not want to include in my testing.
  • Being able to define test and production jobs in separate environments and easily change the settings of one without affecting the other is another strength. Often I would have a job set up in a test environment and after testing it, it would get ported to a very similar production environment with only having to change 3-4 parameter settings. And then I could easily deactivate the test job while still keeping it all set up in the event of needing it for future enhancement/troubleshooting.
  • While I like being able to reuse scheduling objects and the like, more work needs to be done to help one not reinvent the same scheduling object without realizing it and to then find scheduling objects that have similar schedules even if they are worded slightly differently than what I'm expecting. It needs to be "smarter". It was easy to accumulate a pool of scheduling objects that while named differently, had exactly the same schedule. It was also hard to sift through to find the little differences between similarly named scheduling objects.
  • The logger had a clean enough interface but it could be more legible and offer contextual help to describe the messages one is reading. I remember trying to read black text on a medium gray background with Courier size 10-11 font. Not so easy to read quickly and to parse through the relevant parts. I think some selective color coding would be good and links to message definitions or any form of further information would be nice. Maybe the ability to export the log file to various formats would also be helpful.
  • I don't remember a dashboard that at a glance on the top level would highlight what jobs failed completely and which jobs might have warnings or non-critical errors. I got emails because I defined to get them. Maybe again if there was a way to color-code the type of error would be good nice-to-have.
I used to work in a company that only used SQL Server Agent to handle imports and exports of ETL data. ActiveBatch is far more powerful and easy to use, so I definitely would recommend it. I would think of three questions: (1) Do you handle a large volume of exports and imports in a given week? (2) Do you need a lot of configurable options, such as with scheduling? (3) Do you utilize a variety of ETL processing tools (such as GlobalScape EFT and Microsoft SSIS) but want one tool to work with them all? If yes to those questions, then ActiveBatch would well fit the bill for you then.
Read this authenticated review

ActiveBatch Scorecard Summary

Feature Scorecard Summary

Multi-platform scheduling (4)
8.1
Central monitoring (4)
8.5
Logging (4)
5.0
Alerts and notifications (4)
7.0
Analysis and visualization (4)
5.4
Application integration (4)
7.5

About ActiveBatch

Advanced Systems Concepts, Inc. (ASCI) offers its Enterprise IT Automation Solution, ActiveBatch.

ActiveBatch coordinates and consolidates silos of automation within a single framework. The goal is to give businesses the IT agility they need and reduce the time expended on managing and supporting multiple automation tools and silos. ActiveBatch provides users with advanced job scheduling and workload automation capabilities for reliable and adaptable integration with an array of applications, databases, platforms, and technologies. IT organizations can reduce their dependency on custom scripting with the ActiveBatch Integrated Jobs Library, which features hundreds of pre-built, proven, drag-and-drop integrations for commonly-scripted actions and functions in a multitude of different automation areas including workload, business and IT processes, managed file transfer, big data, and more.
Categories:  Workload Automation

ActiveBatch Features

Workload Automation Features
Has featureMulti-platform scheduling
Has featureCentral monitoring
Has featureLogging
Has featureAlerts and notifications
Has featureAnalysis and visualization
Has featureApplication integration

ActiveBatch Integrations

Microsoft Azure, Microsoft Dynamics AX, Microsoft System Center, SAP Crystal, ServiceNow, Amazon EC2, Hadoop Ecosystem, IBM Cognos BI, IBM DataStage, IBM PureData (Netezza), Informatica Cloud, Informatica PowerCenter, Microsoft Active Directory, Microsoft Confiuration Manager, Microsoft Exchange Server, Microsoft Operations Manager, Microsoft Orchestrator, Microsoft Service Manager, Microsoft SharePoint, Microsoft Team Foundation Server, Microsoft Virtual Machine Manager, Oracle EBS, Oracle Job Scheduling, Oracle PeopleSoft, PowerShell, SAP BusinessObjects Data Services, SAP NetWeaver, SQL Server Scheduling, Task Scheduler Automation, Teradata, VMware

ActiveBatch Competitors

CA Workload Automation (AutoSys), Automic (CA) Workload Automation, BMC Control-M, Cisco Workload Automation

Pricing

Has featureFree Trial Available?Yes
Does not have featureFree or Freemium Version Available?No
Has featurePremium Consulting/Integration Services Available?Yes
Entry-level set up fee?Optional

ActiveBatch Technical Details

Deployment Types:On-premise
Operating Systems: Windows, Linux, Mac, UNIX, Mac OS, IBM z/OS, Hyper-V, VMware, and more
Mobile Application:Apple iOS, Android, Windows Phone, Blackberry, Mobile Web