Release Notes 6.5.0

Enhancements

Renaming AAI

The product name has been changed to Automation Analytics & Intelligence, AAI for short, to convey the value it provides. The product reflects the new name across all the product components, server, classic client, existing web user interface and the new, next generation Web UI.

The landing page reflects the new name, new icon and graphics showing the value.

Web UI v2

This AAI version includes the following next generation Web UI enhancements for AAI users:

• View jobstream details

  You can view jobstream details such as basic information, alert settings, jobs in the jobstream, jobstream run details with respect to SLA, trend, and so on. You can also view alerts generated for the jobstream.

• Jobstream life cycle management

  You can perform the following tasks from the Web UI:

  • Create/Add jobstream

    Allows you to identify a job as a target job to create a jobstream from the Jobstream Definitions view.

  • Edit jobstream

    You can edit jobstream associations with business areas, SLA, alert criteria, setting one or more jobs as start jobs of the jobstream in addition to adjusting other jobstream properties.

    Note:

    Trimming one or more jobs from the jobstream would be available in future releases.

  • Delete jobstream

    You can delete a jobstream when no longer needed.

  • View jobstream

    You can see the list of job streams defined in AAI and can filter by business area, scheduler, target job, parent job, and so on.

• Monitor jobstreams

  You can monitor the jobstreams associated with their respective business areas and investigate the jobstream run data to understand the jobstream performance.

  The Timeline View provides a top level glance of the jobstreams with completed runs including the run status (early or late, running and forecasted runs) in relation to the defined SLA as well as the status of jobstream runs like early, late, not predicted to finish (NPTF), and others.

  It also allows you to drill down to subordinate business areas then finally to jobstreams.

  The Grid View gives you a tabular view of the filtered set of runs displayed in the Timeline View.

• Analyze the jobstream run with the help of Gantt chart

  The Gantt chart allows you to analyze a jobstream run to determine possible reasons for delayed or early completion compared to its SLA. Additionally, the Gantt chart has a tabular view to show only critical path jobs, jobs running longer than their average duration, and so on.

  You can also export the job details in the table for further analysis.

For more information, see:

• Adding and Editing Jobstreams

• Viewing Jobstream Definitions

• Monitoring Jobstream Runs

• The Gantt View for a Jobstream Run (Web Interface)

Schedulers

• Universal custom conditions service supports time conditions

  AAI identifies time based custom conditions for jobs of universal schedulers (Automic, Control-M, ESP) and where possible, makes recommendations which you can review and/or accept or for which you can define times based on the available information. The capability already exists for AutoSys and CA7 schedulers and is now available for universal schedulers, too.

  For more information, see Custom Start Time Conditions.

• AAI prediction model enhanced to consider workflow end states for universal schedulers

  Universal schedulers (Automic, Control-M, ESP) have workflows that end with different states, for example, termination, skip, abort or execute another object depending on the completion state of jobs in the workflow. As of this version, AAI also considers these end conditions in the prediction model.

• Next generation prediction model now default for AutoSys scheduler

  The AutoSys scheduler now uses the next generation prediction model by default. This model can provide predictions and run simulations on jobstreams that have cross-scheduler dependencies with not only other AutoSys instances but also compatible native schedulers (CA7 and IWS).

General Improvements

Improvements to existing features, capabilities, and components include the following: 

• Added an Oracle JDBC driver (bundle version 21.4.0.0.1) back to the AAI jboss/standalone/deployments folder.

  Important!

  Please note that upgrading an existing AAI installation will overwrite any existing ojdbc8.jar file. Therefore, before upgrading make sure you save a copy of any site-specific version of the Oracle driver so that you can replace the file after the upgrade.

• Updated the tool tip for the Previous/Next Hours fields of the Daily Batch Report to be more descriptive for users.

Bug Fixes

General

• Implemented changes to the way AAI DB queries are used to gather scheduler data (such as runs, parents, predecessors) to significantly reduce the time required to initialize AAI memory after an application restart.

  Associated ticket: DE572755

• Updated the content of the Status column in the System Monitoring panel of the Web UI v2 to increase accuracy of the Behind status, which points to one or more of the following issues:

  • Job Definitions have not been updated in the interval that was configured

  • The event processing process (Jammer) has not run in the configured interval

  • 15 minutes or more have elapsed since the last scheduler job event was received or processed

• Resolved an issue in the Web UI v1 that sometimes prevented users from navigating to a specific page number of a report. A resource.not.found message was displayed in a pop-up window on the web page.

  Associated ticket: DE559695

• Fixed an issue that prevented Insight reports from loading in the Web UI v1 when using a TLS/SSL connection.

• Fixed an issue that prevented an Insight report from successfully being exported to a file a few minutes after running the report.

  Associated ticket: DE560881

• Resolved an issue with the Simulation feature where some conditions were not being propagated correctly through the forecast and associated simulation. This issue caused some simulated job runs to have start times before their predecessor completed or caused simulated jobs to have simulated start times despite a predecessor failing which resulted either in one or more job runs being discarded from the simulation or in a missing forecast or simulation.

  Associated ticket: DE564652

• Fixed an issue that prevented saving the proper time zone for Job Definition Refresh times for universal schedulers (Automic, Control-M, ESP). The default UTC time zone was used instead. Now, the time zone is saved correctly when you Add or Update a schedulder.

  Associated ticket: DE572507

• Resolved an issue where a job run END event for universal schedulers (Automic, Control-M, ESP) was received with no corresponding starting events and resulted in a missed job run.

• Updated the DB commits for statistics updates by the Statistics Generator to be done in smaller batches to prevent long blocking of event processing (Jammer).

  Associated ticket: DE569834

• Upgraded the embedded json-smart package from version 2.4.8 to 2.4.11 to resolve the following Black Duck Security vulnerabilities:

  • CVE-2023-1370

• Upgraded the embedded Woodstox package from version 5.0.3 to 5.4.0 to resolve the following security vulnerabilities:

  • CVE-2022-40152

• Upgraded the embedded XStream package from version 1.4.19 to 1.4.20 to resolve the following security vulnerabilities:

  • CVE-2022-41966

  • CVE-2022-40151

  • CVE-2022-40152

AutoSys

Fixed an issue with support for AutoSys job renaming that prevented the job definitions update (Converter) to fail in AAI when a new job was added with the original job name.

Associated ticket: DE548977

Automic

Fixed an issue with missing forecast runs of Automic jobstreams within AAI when there were additional runs still scheduled for the current day. Once all runs for the current day completed, the remaining forecast runs were correct. Now, all forecast runs should properly be shown in the Monitoring tab.

Associated ticket: DE558483

CA7

The following server parameters are now available in the Params tab of the Configuration Tool. These can be modified to suppress individual CA7 dataset conditions. By default, all dataset conditions are enabled.

• ca7.suppressDataSetCreatorConditions - Suppress the dataset creator conditions.

• ca7.suppressDataSetTriggerConditions - Suppress the dataset predecessor conditions.

• ca7.suppressDataSetPredecessorConditions - Suppress the dataset Trigger conditions.

Associated ticket: DE573698

Database Schema Upgrade Summary from 6.4.6-3

The following new tables have been added:

• ReportColumn

• ReportFilter

• SchedulerAuditHistory

• ReportSettings

 

Table Name	Change Type	Column(s) Affected
Report	Add	reportSettingId

Automic Connector 3.2.0

This version of the Automic Connector includes the following enhancements and bug fixes.

Enhancements

• The Automic Connector has been enhanced to display the Scheduler's name on the log file. The Name is the same as defined on the Add/Edit Scheduler pane.

• As of this version, the OriginatorID is set and passed on to AAI, thus allowing it to predict when another object is started using the Automic Automation ACTIVATE_UC_OBJECT script function. For more information, please refer to the Automic Automation documentation.

• As of this version, the Automic Connector also considers Calendar conditions for tasks in workflows thus increasing the accuracy of the parent's workflow runtime prediction.

• The Automic Connector uses the Connector Framework version 6.4.6.

Bug Fixes

• Resolved an issue that caused the Automic Connector to send the calendar (JSCH) settings for child tasks/workflows using an incorrect data structure.

• Resolved an issue that prevented proper logging of Automic REST API payloads even if the Debug Log Automic REST API Payloads function was selected on the Add/Edit Scheduler window.

• Resolved an issue with some Automic Automation Workflow (JOBP) types being passed on to AAI. Only STANDARD workflows are supported. JOBP IF (IF statements) and JOBP FOREACH (loops) are not supported.