Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Include a certificate in the trusted keystore
keytool -export -alias test1 -file test1.crt -keystore "C:\Program Files (x86)\Serena\Dimensions 12.5\Common Tools 1.7. 1.0 \ tomcat \8.0\conf\sample-ssl.jks" -storepass serena
CMS-XML Expiration screens appear not to be using SSO Login
The solution / workaround:when running RM 12.4 or later: In Common Tools 1.7. 1.0 \ tomcat \8.0\alfssogatekeeper\conf\gatekeeper-services-config.xml comment (or delete) the following from the unprotected list: <!-- <URIMatcher requestURI="/rtmBrowser/RestServices/*"/> -->
CMS-XML Dimensions RM 12.6.1.0A Patch
To install the patch, perform the following steps: 1 Stop the Micro Focus Common Tomcat (SCT) Service, the Micro Focus Dimensions RM Pool Manager, Micro Focus ALF Event Emitter service and all other Dimensions RM applications.
CMS-XML Dimensions RM 12.5.1.0b hotfix
To install the patch, perform the following steps: 1 Stop the Serena Common Tomcat (SCT) Service, the Serena Dimensions RM Pool Manager, Serena ALF Event Emitter service and all other Dimensions RM applications.
CMS-XML Dimensions RM 12.5.0.0a hotfix
6 Copy files from created "rtmBrowser" directory to existing "rtmBrowser" folder in Serena Common Tomcat installation, e.g. "C:\Program Files\Serena\Dimensions 12.5\Common Tools 1.7. 1.0 \ tomcat \8.0\webapps\rtmBrowser". 7 Delete "rtmBrowser" directory created in Dimensions RM folder.
CMS-XML Dim CM/RM: SSO Gatekeeper error has occurred: Authentication processing error.
Dimensions CM 12.2.2.4 and RM 11.2.4 were installed on the same machine and working with no problems in a non-SSO environment, sharing the same Serena Common Tomcat installation. RM was upgraded to version 12.1.0->12.1.0.3 without error but then the following message was received when attempting to launch either RM or the CM Web Client tools:
CMS-XML DIM RM: How to change the SSO provider hostname
Edit SSO_URL parameter in ...\Serena\Dimensions\Common Tools\ tomcat \6.0\alfssogatekeeper\conf\gatekeeper-core-config.xml. Also, navigate to one of the following, depending upon whether your Windows installation is 32-bit or 64-bit: 32-bit:
CMS-XML VM Installation error: Could not reserve enough space
The error appears to be connected to the start of the tomcat service. The server does start, using only a small percentage of available RAM (e.g., 2 of 12GB)
CMS-XML DIM CM: Using Dimensions CM 2009 R2 - 12.2.1 after upgrading suite version to 4.0.1 or installing RM 12.1
After upgrading suite version to 4.0.1 (Development Manager, Requirement Manager or Release Manager) or installing RM 12.1 you will need to reinstate your Dimensions CM 2009 R2 - 12.2.1 web applications into the new Tomcat . If you are already using Dimensions CM 12.2.2 then no additional steps are necessary.
CMS-XML File attachments fail to attach and crash rmAppServer
The attached zip file contains a corrected rmAppserver RM 12.4. If this issue is encountered with 12.4, stop the pool manager and tomcat , copy the ...RM\bin\rmAppserver to a backup and replace it with the attached.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs