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 How to test whether JBoss or Tomcat is able to communicate with a https (secure) website.
When the SBM JBoss/Tomcat server needs to use a secure url using SSL (HTTPS), it is crucial that the Java Runtime Engine (JRE) used by SBM can verify the SSL certificate. This is not a problem when the certificate is a public one, obtained from the commercial Certificate Authorities (CA) Java knows about, but it can become problematic when the SSL certificate is either self-signed or signed by a non-public Certificate Authority.
CMS-XML KM-DIM2009R2: How to configure Tomcat to use SSL with a self-signed certificate
port="8443" scheme="https" secure ="true" sslProtocol="TLS" strategy="ms" truststoreFile="C:\Temp\.keystore" truststorePass="serena"/>
CMS-XML Using SourceBridge from the VM I-Net Web Client when the connection to the SBM server uses HTTPS (Secure Sockets Layer - SSL)
When using self-signed certificates, or when the JRE does not know the Certificate Authority that was used to sign the certificate, attempts to associate an issue (module association) from VM I-Net during checkout or checkin will yield errors similar to the following in the Tomcat logs (std*.log on Windows, catalina.out on UNIX):
CMS-XML OE database fails to upgrade: Tomcat server startup timed out
Tomcat server startup timed out. ---> ConfigurationUtility.Core.Network.HttpException: URL: https://sbmp02/, Method: GET, Error message: The request was aborted: Could not create SSL /TLS secure channel.
PDF How To: Import SSL certificates into the Java keystore used by DA Agent
Import the missing Certificates The next steps describe the how to import the certificate(s) into the Java certificate trust store (cacerts) file so Serena Common Tomcat can communicate via SSL / HTTPS to secure sites and URL's. To determine the location of the Java Runtime Environment (JRE) and the Keystore that is used by the Agent, use these steps:
MS-WORD Integrating SDA with third party tools that use SSL.docx
The next steps describe the how to import the certificate(s) into the Java certificate trust store (cacerts) file so Serena Common Tomcat can communicate via SSL / HTTPS to secure sites and URL's. Let's assume that from step one you have a file called MyCert.cer located in the root of the C: drive Open a command prompt and navigate to the following location:
CMS-XML KM-Dim9: MS Internet Explorer Error: Cannot download.DialogPropertyMgr=28&vmfo=tru from Internet Explorer was not able to open this Internet site. The requested site cannot be found. Please try again later. Check that TOMCAT IIS non SSL works
works. If it does, then refer user to http://jakarta.apache.org/ tomcat / tomcat -3.2-doc/ tomcat -iis-howto.html#troubleshoot
CMS-XML Dim9: IIS 6, redirection to Tomcat, on Windows 2003 Server, using SSL. for Dimensions Web Clients returns a failed to redirect screen.
Dim9: IIS 6, redirection to Tomcat , on Windows 2003 Server, using SSL . for Dimensions Web Clients returns a failed to redirect screen.
CMS-XML How to acquire the SSL certificates for your mail server when setting up the Mail Client ( EOF on Socket ) error in ns.log
The attached video shows how to get a copy of the SSL certificates being used by your mail server in order for them to be imported into the JBoss/ Tomcat keystore.
CMS-XML Deploy stays in waiting when TLS 1.0 is removed from server.xml - Invoking import callback failed: Error observed by underlying SSL/TLS BIO: No such file or directory
As of SBM 11.3, it doesn't look possible to remove TLS 1.0 from both the Server.xml ( Tomcat ) and the SChannel Registry key ( IIS ) and have deploys reach the "Completed" status. The deploy itself will succeed and your changes will get deployed. It is just the callback from the Application Engine to the Repository telling the system the deploy completed that fails so the status stays in "Waiting" forever.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs