Users may encounter errors in the test data source for SRM-RIB.
Investigation of the srmribservice.log file revealed certificate errors occurring after changing the Java path for SRM-RIB, which caused the application to use a different Java keystore (cacerts) that lacked the necessary certificates.
The issue was caused by a configuration change where SRM-RIB was directed to use a new Java location.
This resulted in the application attempting to authenticate using a new, empty Java keystore instead of the established one containing the required certificates.
To resolve this, merge the certificates from the old Java keystore into the new one by following these steps:
Locate the cacerts files: The default path is usually $JAVA_HOME/jre/lib/security/cacerts.
Back up the new keystore: This command will make changes to your system. Review it carefully before running.
Merge the old keystore into the new one: Navigate to the bin directory of your new Java installation (e.g., /usr/jvm/jre/jre17.0.10/java/bin) and run the following command, replacing the paths with your specific old and new locations: Review this command before running it.
Note: When prompted for a password, the default is usually changeit unless it was previously altered.
Update SRM Java configuration: Once the merge is complete, follow the instructions in the following KB to finalize the Java update for SRM: KB 434094 - Update Java for SRM