Advanced Scheduling for Scripts
ActiveBatch is a workload automation and enterprise job scheduling solution that supports no-code workflows and integrates custom scripts of any language, including PowerShell, Python, Java, VBSscripts, and shell scripts.
ActiveBatch supports advanced methods for triggering both scripts and cross-platform workflows. For basic scheduling requirements, ActiveBatch supports both interval-based, or date/time schedules with custom holidays, fiscal calendars, and custom business rules.
For more advanced scheduling requirements, ActiveBatch supports dozens of custom event types including FTP file triggers, database modifications, emails, tweets, web service triggers, and more. Plus, dynamic support for constraint-based scheduling and job constraints ensure that custom constraint criteria are met before a script is executed. This allows users to run scripts as soon as possible with zero slack time or false starts.
Seamless, End-to-End Orchestration
Custom scripts often depend on other processes. Manual handoffs and executions can delay those processes, increase the risk of human error, and cause bottlenecks.
In order to simplify IT’s automation environments, ActiveBatch provides seamless, end-to-end orchestration for any process. This can include tying together multiple scripts to run in parallel or in sequence, or integrating script-based and no-code actions into a single workflow.
Workflows can also be routed based on the outcome of scripts. For example, one set of actions can be taken if a script produces a particular exit code, or another set of actions can be taken if a certain string value exists in another script’s log. No matter the use case, ActiveBatch improves the efficiency of script-based workflows.
Protect Your Script Investments
Most organizations have libraries of custom scripts that were written for specific tasks, products, applications, or services. IT teams shouldn’t have to replace or discard those scripts just because they’ve implemented a new automation tool.
ActiveBatch helps organizations protect their existing scripts with vaulting and lifecycle management capabilities, providing the tools IT teams need to simplify and enhance their existing scripts –while reducing the need for new custom scripts. These tools include auditing, versioning, and a central repository for storing and securing all scripts, regardless of the scripting language used.
Reuse Rather Than Rewrite
Maintaining hundreds of jobs is time-intensive. In order to accelerate and streamline script management, ActiveBatch allows developers to create Template Jobs and Reference Jobs. Whenever a change needs to be made to the related job payloads or script contents, the user simply needs to update the Template and ActiveBatch will automatically pass down the changes to its child Reference Jobs. This removes the need for cut-and-paste and improves overall maintainability.
References become even more useful when paired with the power and flexibility of ActiveBatch Active Variables. While static variables are a core function of ActiveBatch, Active Variables update in real time based on a selected data source, so their possibilities are endless. An Active Variable can be a custom date calculation, database values, or even the return value of a PowerShell script. This makes for infinite reusability of the same core script logic while encompassing any dynamic or ad-hoc requirement.
Check-Out | Check-In
With ActiveBatch Check-Out | Check-In functionality, multiple developers can simultaneously work on the same object or objects for faster development and resolve any changes with ActiveBatch’s built-in conflict resolution tool. Since every script is stored in a unique object, the same principles apply.
ActiveBatch Service Library
The ActiveBatch Service Library is a dynamic framework that extends ActiveBatch’s integration capabilities. The Service Library enables users to load and execute APIs (WSDLs and SOAP Web Services, RESTful services, .Net assemblies, stored procedures, and command lines) without the need for custom coding. Individual actions and would-be API calls can be turned into reusable Job Steps within the Integrated Jobs Library. This drastically reduces the need for custom scripts for common integration tasks.