ActiveBatch Workload Automation

Job Scheduling was something which used to take alot of time and also need an resource everytime to monitor them with the help of ActiveBatch Workload Automation we can schedule the jobs automatically to a particular time and we do not require any resource to run them. Active Batch also restarts itself when there is failure of jobs. Alerting, Monitoring has also become easy with ActiveBatch. it also provides the option of triggers we can eliminate or reduce the use of Boiler Plate code and we can automate triggers based on event/action. This was helping me alot.

The pre built job function in ActiveBatch Workload Automation helped the team in accelerate the automation process by facilitating us to skip the steps required to create a job function, such as identifying the need, analyzing the requirements, optimizing the process, preparing the script and monitoring the automation progress. <br><br>The team also had a swift experience in learning to use the tool as it is super user friendly and has an easy user interface. Example the drag and drop function.<br><br>The ActiveBatch job scheduler is another feature to vouch for, which helped us create a agile environment for our automation process. This feature helped us allocate tasks to the teammates and sends regular reminder to complete the task within the said timelines, this at the same time helped us project any delays we may encounter. In case of deviation the tool also helps in change management.

Active Batch handles all of our nightly batch jobs including but not limited to file transfers between SFTP sites, SSRS report generation, file encryption/decryption and much more. We have several use cases for using Active Batch but one of the main drivers was having a solution to house all of our Windows Task Scheduler jobs, while task scheduler is great, it was a pain to manage and support. With Active Batch, we now have a single solution where we can see which jobs are running, how long they are running for, if they failed, and when they would run next, etc. We currently have about 1000 jobs in different Active Batch environments.

ActiveBatch Workload Automation is used for multiple purposes such as SAP jobs, File transfer systems (FTP), and data warehouse loads. There are numerous functionalities the supports various types of workflows, including batch calls and service calls. The format of job scheduling is well organized and very similar to what we use in day-to-day life making it easier to use. It is able to control all the jobs (FTP, data warehouse) for multiple environments over and across different servers.

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.