Release Notes 2024.4

Redwood Software, Inc. is pleased to announce the release of ActiveBatch® version 2024.4.

For details on how to upgrade, see the General Information section.

Updated .net Framework Prerequisite

ActiveBatch now requires .net Framework 4.8.

The Prerequisite .net Framework version has been updated to .net Framework 4.8. You must ensure the version of .Net Framework installed on your ActiveBatch systems is updated to match the minimum required.

System Center DLLs

Customers using SCOrch, SCSM, or SCOM should know that ActiveBatch no longer packages System Center DLLs. We recommend special attention to the testing of these.

For an example of obtaining these System Center SDK files, go to Microsoft Learn - Orchestrator SDK.

Enhancements

The following list of enhancements applies to Version 2024.4:

New Extensions Added

Amazon Simple Storage Service (Amazon S3) is a cloud storage service which allows for storage of any type. Amazon S3 stores data as objects within buckets. An object is a file and any metadata that describes the file. A bucket is a container for objects. Each object has a unique key to identify it within the bucket.

 

The Amazon S3 extension implements new job steps to perform the following Amazon S3 operations:

  • List S3 Buckets
  • List S3 Objects
  • Upload S3 Objects
  • Download S3 Objects
  • Delete S3 Objects

Updated CyberArk Integration

CyberArk is a subscription-based Identity and Access Management (IAM) security management tool designed to protect administrative access. It offers comprehensive solutions to store, manage, and share passwords. ActiveBatch supports CyberArk’s access management solution for secure runtime access to credentials required for batch operations.

 

ActiveBatch has now added support for the 2nd generation CyberArk API. This enables you to leverage CyberArk's Privilege Cloud feature.

 

CyberArk support is integrated into the ActiveBatch User Account object via the CyberArk Credential Type and the CyberArk “Get Account Info” job step. This will return credentials such as username and password values, which can be used in other job steps.

Expanded Capabilities for the REST API

The ActiveBatch REST API provides an interface to get information about ActiveBatch Objects and Instances and perform ActiveBatch Operations.

 

ActiveBatch now supports performing Import and Export objects using the REST API.

 

ActiveBatch has also included an operation to get the complete details of an ActiveBatch object. This currently includes the Folder, Schedule, Plan, and User account object types. (More will be added in future releases).

Improved Compatibility with OpenPGP

ActiveBatch PGP Job Steps has improved compatibility with external OpenPGP tools. Previously, you may have experienced situations where the ActiveBatch PGP Job Steps could not decrypt data coming from external sources.

Corrections

The following list of corrections apply to Version 2024.4:

SSH Job Step Error

In some instances, the SSH Job Step would misinterpret some characters, sending incomplete commands to the remote system.

 

A new job variable has been created:

 

#SSH.IsServerWindows set to false (“0”) by default.

 

This default setting will configure prompt and line termination with Linux Server settings. This can be overridden by changing the setting to "1" to connect to a Windows SSH Server.

FTP/MFT Job Steps Error

FTP/MFT job steps on Windows agents. After an upgrade, you may have experienced a generic error message: "SftpException: channel open failure." We identified this issue with the adaptive connect feature in the JSCAPE client. This feature has been disabled by default to prevent these failures. This default setting can be overridden by setting #Sftp.UseAdaptiveConnect to 1.

Backward Compatibility Issues with Informatica Cloud API

Informatica now requires RunID and TaskID for certain API operations. The ActiveBatch Job Steps for Informatica Cloud have been updated to allow you to supply the additional required information.

Issue with Queue Override

This release has fixed the reported issue of jobs being sent to the Template Queue due to the Queue Override failing.

Variable Explorer's Rename Variable Function Not Updating

When using Variable Explorer, the Rename Variable will update all the references. This does not include the REST API Job Step.

Secure Variables Decryption Failure For Script Type Jobs

Secured variables were not properly decrypting when supplied to script-type jobs. These variables are now normally evaluated for script and library-type jobs.

Variables Failing in ScheduleConcurrentRequestSet Job Step

Variables are now resolved properly within the ScheduleConcurrentRequestSet Job Step for .NET and Java implementations.

Self Service Portal

Where an audit policy was defined at a root folder, an issue prevented you from triggering jobs in the folder from the Self Service Portal.

 

 

General Information

See the ActiveBatch Installation and Administrator's Product Compatibility Matrix to make sure your database and operating systems are supported in 2024.4.

 

Before you consider the upgrade process, confirm your ActiveBatch environment is running on a version that has been thoroughly tested to support the upgrade procedure. See more details below.

Note About Version Numbers

 

In the past, ActiveBatch major release version numbers increased by 1 (e.g. Version 11, Version 12). Last year, we released our first major-release using a new calendar-based system. It is based on the year and the quarter within the year (e.g. 2024.4).

 

This current release is numbered 2024.4 since it is being released in the fourth quarter of this year.

 

Currently, the various user interfaces do not display the new version numbering system; rather, you will see version 14 (our internal version number). This will change in a future release, where the UI will match the new numbering scheme. Until then:

  • 2023.3 = 14.0.1
  • 2024.2 = 14.0.2
  • 2024.3 = 14.0.3
  • 2024.4 = 14.0.4

Locating your version information

  • The thick console internal version number is displayed on AbatConsole's Start Page.
  • The Web Console internal version is displayed when clicking the About ActiveBatch icon (located at the top far-right of the UI, second from the left).
  • The Job Scheduler internal version is displayed on the Job Scheduler Information page (see Views > Job Scheduler Information).
  • The Execution Agent internal version is displayed on the Execution Queue object - see Properties > Machine Characteristics > AbatVersionId.

Upgrading from Version 2023.x to 2024.4

You can upgrade from 2023.x, 2024.x to 2024.4. This release should be treated like a service pack upgrade. For more information, refer to ActiveBatch Installation and Administrator. See the Service Packs and Installation Maintenance Operations section.

 

Upgrading from version 12 SP9 to 2024.x

 

You can upgrade from Version 12 SP9 to 2024.x. You do not need to upgrade to 2023.4. To upgrade to 2024.4, your current Scheduler must be running V12 SP9. If you are not running on the latest service pack, review the following KB article: Upgrading ActiveBatch V12 to the Latest Service Pack.

 

Once you are on the latest V12 service pack, see ActiveBatch Installation and Administrator. It provides all the details required to upgrade from V12 SP9 to 2024.3. See the section named Upgrading from V12.

Upgrading from version 11 SP5 to 2024.x

You cannot upgrade from Version 11 to 2024.x directly. You must upgrade from V11 SP5 to V12 SP9 first. From there, you can upgrade to 2024.x. See the ActiveBatch Installation and Administrator's - Upgrading from V11 for more information on this topic.

 

 

ActiveBatch End-of-Life, Release and Support Policy

 

Redwood Software, Inc. is committed to providing the most stable, best version of ActiveBatch possible. Click HERE for more information regarding our release strategy and support policy.

End-of-Maintenance (EOM)

The EOM date is defined as the point at which the software will no longer receive updates or bug fixes, but support will still be available to you. EOM happens 12 months after the release date, and notifications will be sent to you before that date. Updates or patches for software applications that have reached their EOM date will no longer be provided.

End-of-Life (EOL)

The EOL date is defined as the point at which the software will no longer be supported, and no further updates or bug fixes will be provided. EOL happens 18 months after the EOM date, as described in the documentation at the time of the release.

  • EOM for 2024.2 is May 29, 2025.
  • EOL for 2024.2 is October 28, 2026.
  • EOM for 2024.3 is August 29, 2025.
  • EOL for 2024.3 is March 2, 2027.
  • EOM for 2024.4 is Nov 20, 2025.
  • EOL for 2024.4 is May 20, 2027.
  • EOM for 2025.1 is February 21, 2026.
  • EOL for 2025.1 is Sept 1, 2027.

End-of-Life (EOL) for other versions

  • EOL for V11 was June 30, 2024
  • EOL for V12 was Nov 30, 2024

Contact Information

If you encounter any problems with ActiveBatch and are under the Product Warranty or post-warranty maintenance service plan, contact Redwood at support@redwood.com or visit our website at http://www.redwood.com.