Workload Automation Software Resources

All jobs have properties that determine how job log files are managed. The factory default setting is Centrally Managed Logging. This means that the location and name of the log file is completely left to ActiveBatch. You can specify how long to keep these log files using a custom retention period – once it has been met, they can either be deleted or archived. The properties in question can be found on the job's Execution tab. With the Centrally Managed Log File radio button selected, you can then specify a log retention period. The retention period cannot exceed how long you keep the job instances (found in Completion properties) since logs are associated with instances. If the factory default log retention period is not suited for your organization, we would recommend you create a default job policy to modify the default value for this property. This way, ActiveBatch job authors don’t have to set or override the factory default values themselves. This is a great time saver, reduces errors, and sets company standards. You can also use the default policy feature to "push down" a policy to existing child objects with the container, overriding whatever existing value exists. A default job policy can be set on any ActiveBatch folder or plan, or the root-level Job Scheduler object by right-clicking it in the Object Navigation Pane and selecting Policy > Defaults.

Control-M is used to automate, schedule, and monitor backend jobs and workflows, while DevOps is used to build, test, deploy, and operate software quickly and reliably.

Hi Werner. The answer is yes. We already have a few Kafka integrations available on the Stonebranch Integration Hub. Here is the link: https://www.stonebranch.com/integration-hub/search?search=kafka