Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
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
If you are prompted or override or trust the certificate, enter yes. Restart Serena Common Tomcat and test the process you were working on. TIP: This KB S140385 article has a tool you can use to test whether the https url you are attempting to use is now considered secure by Java.
CMS-XML How to enable SBM to communicate via SSL with a SQL Server database in SBM 11.x
If your MS SQL Server is setup with the Force Encryption value set to yes then you will have to make the following changes for SBM to communicate with it. If your SQL server is setup this way then the Application Engine components will work fine because they connect via ODBC but the Tomcat components will fail to connect via JDBC and need the following changes made to the JDBC connection string in order to connect to the SQL Server database.
CMS-XML How to get a copy of the certificate chain and copy it to the certificate trust store ("PKIX path building failed" or similar SSL connection errors.)
snap-in. For Java based programs, the certificate keystore is located in the JRE used by JBoss or Tomcat . These are mutually exclusive certificate trust stores.
CMS-XML Dm2009R2: CM Build jobs fail during submit if tomcat is running HTTPS on IBM AIX
Run Build No input items were selected for dependency analysis BCB1901000E Error: SOAP FAULT: SOAP-ENV:Client" SSL _ERROR_ SSL error:140773F2: SSL routines: SSL 23_GET_SERVER_HELLO:sslv3 alert unexpected message". COR0004737E Dimensions Build Server authentication failed FSY0004611E Error: Cannot open file /tmp/pt0009c3.tmp - A file or directory in the path name does not exist. (error=2)
PDF RLM HTTP Server Overview:
2) Tomcat SSL is configured at the port level. A SSL connector port is defined in the Tomcat server.xml file and specifies the SSLEnabled=”true” attribute.
CMS-XML RC 3.3 - unable to do a clean install with SSO & Common Tools
You may then also need to verify that the URL is correct in the gatekeeper-core-config.xml file in the "\ tomcat \6.0\alfssogatekeeper\conf" directory, as for non- SSL installations an invalid space is added after the port number as here :
CMS-XML How to troubleshoot the Rest Grid widget when you get "We did not find any matches for your request" instead of results.
To investigate these errors, look in the rlm.log or alm.log file (by default located in C:\Program Files\Common\ tomcat \6.0\logs) for additional information. ... SSL :
CMS-XML SSO and SSL: Only secure content is displayed and users get error about mixed content
SSO and SSL : Only secure content is displayed and users get error about mixed content
CMS-XML Popup messages about non-SSL content when using SSL
"Do you want to view only the webpage content that was delivered securely? This webpage contains content that will not be delivered using a secure HTTPS connection, which could compromise the security of the entire webpage."
CMS-XML Two-way SSL configuration for Manual Deployment Tasks
, change the Port value from 80 to the secure IIS port (443 by default). Note:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs