To return expected results, you can:
Reduce the number of search terms.
Each term you use focuses the search further.
Check your spelling.
A single misspelled or incorrectly typed term can change your result.
Try substituting synonyms for your original terms.
For example, instead of searching for "java classes", try "java training"
Did you search for an IBM acquired or sold product ?
If so, follow the appropriate link below to find the content you need.
The following are the errors that will show up in the rm.log and the rrdg.log file when the problem occurs.
rm.log
2016-01-28 13:37:54,112 [ WebContainer : 8] ERROR ibm.rdm.fronting.server.rrs.publish.PublishService - com.ibm.rational.rpe.common.template.api.TemplateException: Could not load template https://SERVER:PORT/rm/publish/templateLibrary/printModuleBook. Error is: <Invalid keystore format>
at com.ibm.rational.rpe.engine.core.CoreUtils.loadTemplateImpl(CoreUtils.java:108)
rrdg.log
2016-01-28 13:37:54,112 [ WebContainer : 8] DEBUG com.ibm.rational.rrdg - CRRPE3005E The template could not be loaded.
Cannot initialize SSL.
com.ibm.rational.rpe.common.utils.conn.ConnectionException: Cannot initialize SSL
The cacerts file in the WebSphere installation is using the wrong format or is corrupted.
<WAS_HOME>\AppServer\java\jre\lib\security\cacerts
The Rational Reporting for Document Generation (RRDG) feature in RDNG uses Rational Publishing Engine (RPE) for the features to generate reports and print PDF/Word documents. RPE expects a cacerts file in JKS format under the java lib\security directory.
Use the keytool command to determine the keystore format. The following is an example that pipes the output to a text file.
C:\IBM\WebSphere\AppServer\java\jre\bin>
keytool -list -v -keystore C:\IBM\WebSphere\AppServer\java\jre\lib\security\cacerts >> keystoreOutput.txt
There will be a prompt for the password for the keystore. The default password is 'changeit', but may be changed.
The expected output should show:
Keystore type: jks
An output like the following error, or a different keystore type will cause the problem.
java.io.IOException: Invalid keystore format
[{"Product":{"code":"SSUVLZ","label":"IBM Engineering Requirements Management DOORS Next"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"General information","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.0.5;4.0.6;4.0.7;5.0;5.0.1;5.0.2;6.0;6.0.1","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
