ActiveBatch Workload Automation

We use ActiveBatch Workload Automation for our IT processes and systems. Before we needed to make different complex scripts, eg powershell. Now thanks to ActiveBatch Workload Automation it is centralized in one software application.

ActiveBatch Workload Automation runs all of our nightly processes, creates server reports, verifies services are up and restarts them if not. Monitors mission critical servers and SAN units for space issues, encrypts and FTP's files to clients, sends out strategic notifications to clients and monitors SLA's. We use ActiveBatch Workload Automation for almost everything we do. It's an incredible piece of software.

We use ActiveBatch to run our DW Informatica workflows, daily tableau reports, analytics jobs, and ICEDQ rules. This allows us to minimize downtime/errors when coordinating data loads, reporting, data quality, and analysis jobs. We can also easily scheduled prod to test data refreshes which helps our team and others with development and testing priorities.

ActiveBatch [Workload Automation] jobs are developed by two departments, but those jobs are for (or affect) many departments across the whole organization.

We are consistently looking for repetitive tasks that are currently taking up employees time, but which can be automated. By building automation scripts, significant time savings are achieved, and employees are freed to work on tasks which are not repetitive - and thus scriptable.

ActiveBatch has been an excellent tool for this type of automation, as the job scripts are easy to develop quickly, and logging and alerting are strongly incorporated for when things don't go as expected.

ActiveBatch [Workload Automation] is used by our department to fulfill company wide needs. The main use is to control and monitor overnight processing to ensure that all processes are run successfully without need of manual intervention. We also use ActiveBatch [Workload Automation] for internal system maintenance tasks and any other processes that originally required frequent, repetitive manual intervention.

We used ActiveBatch to manage many of our automated database reports. It was used system-wide, but for our department only my colleague and I used it. It was supposed to be a replacement for Windows task scheduler, but it barely worked as intended. We had to hack many of our scheduled jobs to use batch scripts since the built-in Powershell or command line options did not work.

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.

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.

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.

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.