Known Limitations and Known Issues

IBM Control Center Monitor has the following limitations:
  • While configuring JDBC driver for MS SQL database, even though the prompt mentions about using JDBC driver files ending with jre8.jar, the JDBC driver files ending with jre11.jar is allowed.
  • In a containerized environment, the following certificate management features are not supported:
    • Keystore certificate management
    • Truststore certificate management
    • Certificate management using Venafi

  • For an upgraded setup where IBM Control Center Monitor 6.4.0 GA is installed, follow the steps below manually since the encrypted password has already been generated and stored in the EP2 configuration folder. Replace it manually with the correct encryption keys.

    Step 1: Take a backup of the following files:

    • conf/SCCRootPass.enc
    • conf/SCCRootPass.digest
    • conf/KeyStoreTrustStoreConfig.xml
    • conf/services/system/JDBCService.xml
    • conf/services/system/JDBCStagingService.xml
    Step 2: (Assuming it is configured with the same keystore and truststore files)
    • Replace conf/SCCRootPass.enc and conf/SCCRootPass.digest with the files from EP1.
    • Replace conf/KeyStoreTrustStoreConfig.xml with the file from EP1.
    • Replace conf/services/system/JDBCService.xml with the file from EP1.
    • Replace conf/services/system/JDBCStagingService.xml with the file from EP1.
    Step 3:
    • Run ConfigCC for EP2.
    • Re-enter database details and web application configuration. Other configurations can be skipped.
    Step 4:
    • Start EP2.

Known Issues

This section outlines the known issues present in the latest version of IBM Sterling Control Center. It is crucial to familiarize yourself with these issues to facilitate a smoother experience. Additionally, you may need to follow specific workarounds to address these issues effectively.

List of known issues:
Functionality Known Issue Workaround
Secure Connections Given that Java 17 supports TLS 1.2 and TLS 1.3 by default, any existing servers or connections that are enabled with protocols below TLS 1.2 will be unable to establish a connection with CC 6310 by default. In order to make sure to those connections to work, we need to enable the required protocols in CC_java.security file or at JRE level.
Control Center Monitor In B2Bi monitor settings, when switched from Monitored to Not Monitored, in the BP list popup, “Not Monitored” selection is not correct. Manually select the appropriate business processes not to be monitored.
Control Center FTP Agent Since FTP Agent that is provided with CC 6.4.0 uses OSA approach, existing FTP Agent cannot be upgraded with the newer FTP Agent If existing FTP Agent needs to be upgraded, install the newer FTP Agent in a different location on the same server where existing FTP Agent is running and configure osaFtpAgent.properties file.