What's new

To meet your business needs, IBM® Sterling Control Center Monitor introduces important new features and enhancements.

What's new for V6.3.1

IBM Sterling Control Center Monitor v6.3.1 includes the following enhancements. To install this software, first check the Fix Central for latest update of this product. If an update of this version is available, download the updated version. If no update is found, you should go to the Passport Advantage website and follow the instructions described to complete the download.

  • Log in to Sterling Control Center using single sign on (SSO):

    Support has been added for single sign-on (SSO) using the SAML protocol through Sterling Secure Proxy and the Sterling External Authentication Server. For more information, see IBM Sterling Control Center SSO Configuration.

    Note:
    The following are the prerequisites:
    • SSP version 6.1.0.0 iFix01 or later
    • SEAS version 6.1.0.0 iFix01 or later
  • TLS 1.3 enabled for internal and external connections in Sterling Control Center:

    TLS 1.3, a crucial internet security protocol, introduces enhancements in security, performance, and privacy. For more information, see Securing the IBM Sterling Control Center Monitor using Transport Layer Security 1.3.

  • Failed login attempts recorded in audit logs:

    Enhanced logging now captures details of failed login attempts. When users access the Sterling Control Center console, both successful and unsuccessful login attempts are documented in the audit logs. This feature empowers administrators to track system access, providing insights into user activity and identifying failed login attempts resulting from improper access. For more information, see Displaying the Audit Log.

  • Support for picture IDs enhances logged in user identification:

    Users now have the capability to upload picture IDs to their user profiles in Sterling Control Center, allowing for a personalized user experience. For more information, see Setting the Profile Picture for the IBM Sterling Control Center Monitor Web Console.

  • Removal of escalated permissions for running containers:

    The need for root access when running containers has been eliminated.

  • Control Center FTP Agent:

    The FTP Agent uses OSA approach to monitor FTP logs and post events to Control Center Monitor.

  • Customizable dashboard widgets:

    The enhanced dashboard functionality enables users to have multiple widgets of the same type with distinct filters. Users can conveniently rearrange, resize, and export data from these widgets. For more information, see Overview of Dashboard.

  • New reports added to Sterling Control Center Monitor:
    New standard, built-in reports are available directly in the web console:
    Report Report definition
    File Transfer Metrics Overview

    This report features key file transfer metrics including the largest file size, average file size, and average and max time taken to transfer a set of files.

    Partners File Transfer Summary

    This report provides the file transfer count between Connect:Direct servers and partner servers.

    Event Summary Report

    This report provides the count of event types per server for the given date range. This can be used to indicate the types and amount of activity monitored by Control Center. For example you can see how many processes run on a server by filtering the report.

    Highwater Mark Report The High Watermark report provides information to help manage Sterling Connect:Direct node usage. The High Watermark Report can also be used to see how many times sessions would be queued if the number of concurrent sessions allowed were reduced.

    For more information, see Reporting.

Stack Updates

New security fixes and the following stack upgrades are introduced in this release:
  • Control Center is bundled with Java 17 JRE
  • Support for Microsoft SQL Server 2022 for Control Center database
  • Jetty 11
  • Red Hat OpenShift Container Platform:
    • 4.11.0 or later fixes
    • 4.12.0 or later fixes
    • 4.13.0 or later fixes
  • Kubernetes >= 1.24 and <= 1.27
  • Helm >= 3.10 and <= 3.13.x
  • RedHat - UBI 9.2.x

For more information, see https://www.ibm.com/software/reports/compatibility/clarity/osForProduct.html