Known Restrictions and Known Issues
Control Center Director and its related software have the following known restrictions:
- When moving from the configuration objects' listing page to the details page, the page turns blank. This is caused due to high identity number generated in the database and may cause issues with JavaScript. If the identities in CC_SEQUENCE has high numbers in 16 digits or beyond (Safe limit- link), this is most likely to happen. In such a case, it is advised to track the upcoming FixPack (ifix01).
- Connect:Direct servers can only be restored to a release from which upgrade was planned. For example, if you upgrade from Connect:Direct for UNIX v4.3 to v6.0, then you can only restore to Connect:Direct for UNIX v4.3 but not v4.2.
- Upgrades on target Connect:Direct nodes via Control Center Director Web Console is currently not supported for Connect:Direct servers running on a 32-bit Solaris platform. You must upgrade to Connect:Direct for UNIX v6.0.0 and above to support the upgrade process.
- If the login attempt fails, clearing the browser cache may resolve the issue.
- When you upgrade from Control Center Director version 1.0.0.2 or Control Center Monitor v6.1.3 to Control Center version 6.2 or later, External Auth Server connection parameters change and do not remain the same as in the original version from which you upgraded. You must run configCC.sh/bat and specify the parameters again.
Known Issues
This section outlines the known issues present in the latest version of IBM Sterling Control Center Director. 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 |
|---|---|---|
| Control Center Director | In CCD-Deployments, if an installer is created without specifying the Type Installation location, attempting to override it using the Add Override option renders the Proceed button disabled, hindering further progress. Even if user updates any information on override window, still the button remains disabled. | Alternative is to specify the installation location during installation creation. |
| Secure Connections | As Java 17 by default, support only TLS1.2 and TLS1.3, any existing servers or connections enabled with protocols below TLS1.2 will not be able to establish 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. |