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
PDF RLM HTTP Server Overview:
<Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol=" TLS " keystoreFile="/u/ tomcat /TomcatCertificate.cer" keystorePass="TomcatPassword" />
CMS-XML SRA: Tomcat: How can we change the Tomcat port for Serena Release Automation?
SRA: Tomcat : How can we change the Tomcat port for Serena Release Automation?
CMS-XML How to install an SSL certificate into the RLC 5.x/RLM 4.x/ALM 3.x JRE keystore for Serena Common Tomcat
How to install an SSL certificate into the RLC 5.x/RLM 4.x/ALM 3.x JRE keystore for Serena Common Tomcat
CMS-XML Dm2009R2: CM Build jobs fail during submit if tomcat is running HTTPS on IBM AIX
Dm2009R2: CM Build jobs fail during submit if tomcat is running HTTPS on IBM AIX
CMS-XML How to configure Release Manager or Development Manager to use a non-default port number
Configuring Release Manager to Use a Different Port Serena Release Manager runs using the Serena Common Web server, which is an Apache Tomcat Web server. The Serena Release Manager installer automatically installs and configures the Serena Common Web server to run on the default port of 8080. If this port is already in use by another application on your server, or if you already have an instance of the Serena Common Web server running on a different port on this server, you will need to decide how you want to proceed.
CMS-XML DMCM: Web Client does not correctly report connection problems
If connectivity between Tomcat and Dimensions Server is lost, or the Dimensions Server goes down, then during a login attempt, the user will get the following error message: "It was not possible to log you in at this time. The error message has been recorded (in stderr.log in default configurations)." However, if a user has an active session then no errors are reported wehn the connection is lost.
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 DVM: Unable launch Build from Dev Package. "Must specify an object or a list of objects"
The problem is caused by enabling the option to collect build outputs, not updating the file C:\Program Files\Serena\Dimensions 12.2\Common Tools\ tomcat \6.0\webapps\alm\WEB-INF\classes\dm-client.xml, and/or not completing the setup in the Adminconsole to create Requests of the relevant Type. The file C:\Program Files\Serena\Dimensions 12.2\Common Tools\tomcat\6.0\logs\alm.log
CMS-XML ALM 4.0.1: Check almopd.log for the source of problems when using the OPD section of ALM
If you run into problems when using the new OPD capabilities of ALM 4.0.1, Products and Components, make sure you check almopd.log which is located in C:\Program Files\Serena\Dimensions 12.2\Common Tools\ tomcat \6.0\logs. For example when using the "Get Products" option to select a Dimensions CM product the following message was generated:
MS-WORD New Serena Common Tools.docx
When using the suite installer your CM web applications will need to be reinstated into the tomcat webapps folder. To do this you simply stop Tomcat and copy all *.war files from <SERENA INSTALL FOLDER >\Serena\<version>\Common Tools\tomcat\6.0.pre4.0.1\webapps\ to the webapps folder of the new Tomcat. Then start Tomcat and all *.war files will be expanded.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs