24.2 enhancements and patches

Review the TrueSight Server Automation 24.2 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.

Version	Fixed issues	Updates and enhancements
24.2.01	Known-and-corrected-issues
24.2.00	Known-and-corrected-issues

For a list of recent updates and enhancements across multiple versions, see Release-notes-and-notices.

24.2

Use Remedy SSO for Multifactor Authentication in the TrueSight Server Automation Console

The TrueSight Server Automation Console offers support for multifactor authentication by using the Remedy SSO authentication system. This feature significantly enhances security measures within the system. The additional layer of protection beyond just a user name and password, reduces the risk of unauthorized access, data breaches, and identity theft.

This increased security safeguards sensitive information, maintains regulatory compliance, and makes the system more reliable.

For more information, see Enabling-Multifactor-Authentication-MFA-support-for-console-users-using-Remedy-SSO.

Set idle timeout for the TrueSight Server Automation Console

Improve your overall system security through re-authenticating inactive users.

Users will be automatically logged out after a specified period of inactivity, enhancing security by protecting sensitive information and preventing unauthorized access.
Users can seamlessly resume work after re-authentication without a lengthy login process. This enhances user experience and minimizes the risk of data loss.
This feature ensures compliance with regulations that mandate security measures for protecting user data.

For more information, see Configuring-the-console-inactivity-timeout.

Get support for additional platforms

The following additional platforms are supported:

Ubuntu Server 24.04 x86_64 (LTS version)
Oracle Linux 8 x86-64 (Guest OS Virtualization)
Oracle Linux 9 x86-64 (Guest OS Virtualization)
AlmaLinux 8 x86-64 (RSCD Agent)
AlmaLinux 9 x86-64 (RSCD Agent)
Oracle Solaris 10 x86 (Smart Agent)
Oracle Solaris 10 x86-64 (Smart Agent)
Oracle Solaris 10 SPARC (Smart Agent)
Oracle Solaris 11 x86 (Smart Agent)
Oracle Solaris 11 x86-64 (Smart Agent)
Oracle Solaris 11 SPARC (Smart Agent)

For a complete list of supported operating systems, see Supported-platforms.

Get support for additional databases

The following additional databases are supported:

Oracle 23c
Oracle 23c RAC

For a complete list of supported databases, see Database support.

Execute jobs against the same targets by using REST APIs and the TrueSight Server Automation Console

You can execute an existing job run against targets that have succeeded or failed without updating the job, even if you do not have the permissions to modify the job.

For example, to re-execute a file-deploy job against same targets, use the PATCH method at this endpoint:

PATCH /api/v1/batch-jobs/{id}/jobruns/{run_id}/: Executes the batch job against failed or same targets.

For information about REST API endpoints, see REST-API-endpoints.

For information about executing jobs against same targets for RCP, see Executing-a-job-against-same-targets.

Configuring load balancer parameter.png

Configure application servers to redirect a session to the next available server during server downtime

If a server goes down, you can have the session redirected to the next available application server based on its availability. This feature reduces failovers as well as the manual effort of reconnecting to another application server. You configure the application server by setting the value of the LoadBalancerHosts parameter in a load balancer environment, so that in case of a server down situation, the tasks will be redirected to the next available server.

You can also configure the load balancing environment through REST API.

For more information, see Recommendations-for-Application-Servers-of-type-Configuration.

Upgrade Z-series, P-Series and ARM-based devices easily using the out-of-the-box Agent Bundle

The following additional platforms are supported in the out-of-the-box agent bundle:

Linux PPC64LE
Linux AArch64
Z-series S390x

You can now execute the Agent Upgrade Job or the Agent Installer Job on the following platforms, without the need to perform manual steps on every upgrade.

Z-series platforms (including RHEL 8 s390x, RHEL 9 s390x, SUSE 15 s390x)
P-Series platform (RHEL 7 PPC64LE, RHEL 8 PPC64LE, SUSE 12 PPC64LE)
ARM-based devices (RHEL 8 AArch64, RHEL 9 AArch64)

These platforms are also available through the File > Unified Agent Installer menu option.

To view a comprehensive list of supported target platforms, see Adding-agent-installer-packages-to-the-Depot.

Utilize additional Compliance Content templates

The following additional Compliance Content templates are supported:

For a complete list of supported templates, see Compliance Content component templates.

What else changed in this release

The following table lists the changes in the product behavior:

Update	Product behavior in versions earlier than 24.2	Product behavior in version 24.2.01
Updated patch vendor access site details for Windows	NA	The patch vendor access site details for Windows is now updated.
Improved security through the digital signing of each individual component installer	Only the Windows installers were digitally signed by using BMC's signer certificate.	All individual component installers, including UNIX installers for TrueSight Server Automation, are digitally signed for enhanced security. For more information, see Digital-signature-for-installers.
Improved performance by adopting table partitioning for deploy_job_run_event cleanup	The table partitioning feature in SQL Server did not include the deploy_job_run_event table. This omission led to performance issues in Offline Cleanup. Specifically, the process followed a non-partitioned table route for addressing table cleanup, resulting in significant delays in determining deletions and processing qualified data.	The scope of table partitioning has been extended to include the deploy_job_run_event table. As a result, the table follows the table partition cleanup route, dropping partitions instead of deleting data rows. This change has led to a significant performance improvement.
Enabled Cross Origin Request Security (CORS)	You could not enable Cross Origin Request Security (CORS).	You can enable Cross Origin Request Security (CORS) by using the access_control_allow_origin property. You must define this property in the existing application.properties file located in the appserver install path\NSH\br\deployments\default\tomcat\webapps\rest\WEB-INF\classes directory. To define this property, add the list of the servers on which you want to enable CORS, separated by a comma. For example, access_control_allow_origin = https://www.myorg.com,http://www.domain1.com
Enabled support for REST API on Rocky Linux	The catalogs APIs and the patching-jobs APIs did not support Rocky Linux.	The catalogs APIs, which contain APIs for retrieving, updating, or running patch catalogs and the patching-jobs APIs, now support Rocky Linux. For more information, see REST-API-endpoints.
Upgraded JRE to version 17.0.10+7	The product supported Java Runtime Environment (JRE) version 17 update 8.	The runtime environment required for running Java applications has been upgraded from JRE 17.0.8+7 to 17.0.10+7. Upgrading to JRE 17.0.10+7 offers enhanced security, stability, performance, and access to new features introduced in the Java Runtime Environment (JRE) version 17 update 10.
Additional properties for the GET /api/v1/servers API	You could not view or download additional details or properties for the GET /api/v1/servers API.	Select the value as true for the additional_details parameter to view additional properties for every server. For more information, see REST API endpoints.
Improved log monitoring through the BLWorkbenchPlugin.log and appserver.log files	The BLWorkbenchPlugin.log and appserver.log files displayed different error messages for the same authentication failure.	The BLWorkbenchPlugin.log and appserver.log files display similar error messages for the same authentication failure, which can be found under the [ AUTH_FAILURE ] Authentication failed keyword. This information correlates the logs between the client and the server.
Adopted systemd for default initialization of modern Linux distributions	The init.d startup scripts were available for managing the RSCD Agent, Application Server, Smart Agent, and the blpxe utilities on various Linux systems that also support systemd.	The init.d startup scripts are not available on Linux systems that support systemd. Use systemd commands instead.
Improved security for RMI interfaces by using SSL to encrypt connections	By default, the connections to the Application Server and PXE server were not encrypted.	By default, the connections to the Application Server and PXE server are encrypted.