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 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.
CMS-XML Things to Consider when disabling TLSv1.0 and TLSv1.1 for SBM
for Client TLS in IIS and Tomcat , you may prevent SBM from talking to other servers / programs. for Server TLS in IIS and Tomcat, you may prevent other programs from talking to SBM. Here is how we should proceed to verify on the test server.
CMS-XML KM-DIM2009R2: How to configure Tomcat to use SSL with a self-signed certificate
... genkey -alias tomcat -keyalg RSA ... ... genkey -alias tomcat -keyalg RSA ... Stop the Tomcat server, go ... directory>\ tomcat \6. ... ... Web Server/ 1.0 "/> ... keyAlias=" tomcat " keystoreFile= ... ... sslProtocol=" TLS " strategy= ... redirectPort="8443" server="Unknown Web Server/ 1.0 "/> ... delete the log files under <common tools directory>\ tomcat \6.0\logs and start Tomcat back up.
CMS-XML Dim12: IIS: When using IIS and Tomcat with Dimensions, how do we enable logging?
This can be enabled within the registry on the Dimensions CM Server, under the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Jakarta Isapi Redirector\ 1.0 The two entries to review are:
CMS-XML DM913 - Tomcat not responding, Error - Exception looking up UserDatabase under key UserDatabase
<?xml version=' 1.0 ' encoding='utf-8'?>
CMS-XML How to resolve Tomcat port conflicts when VM I-Net and/or Dimensions I-Net and/or Collage and/or Mover are installed on the same server
General Information Mover 1.0 is pre-configured to use these ports:
CMS-XML DimCM: Tomcat: org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header error shows in the Catalina logfile.
<Connector port="443" socket.txBufSize="262144" server="Unknown Web Server/ 1.0 " sendReasonPhrase="true" relaxedQueryChars="[,]" redirectPort="8443" protocol="HTTP/1.1" connectionTimeout="20000"/>
CMS-XML How to configure the Cipher Strength for SBM Tomcat
To ensure a port uses strong ciphers, a list of desired ciphers can be added to the port definition as follows. The cipher suites available for use depend on the exact version of SBM, the version of Windows server and whether TLSv 1.0 , TLSv1.1, TLSv1.2 or TLSv1.3 are allowed. The following list should work in most cases.
CMS-XML KM-Dim10:Tomcat server.xml definitions
The maximum number of HTTP requests which can be pipelined until the connection is closed by the server. Setting this attribute to 1 will disable HTTP/ 1.0 keep-alive, as well as HTTP/1.1 keep-alive and pipelining. Setting this to -1 will allow an unlimited amount of pipelined or keep-alive HTTP requests.
CMS-XML Meritage -Meritage fails when Tomcat is configured to accept SSL connections only.
The underlying connection was closed: Could not establish trust relationship for the SSL/ TLS secure channel. Additionally, in .\Documents and Settings\<User_ID>\Application Data\Serena\Meritage\meritage.log the following will be found: 2005-07-12 11:54:18,777 [3908] INFO Merant.DocShare.UI.Forms.ServerSetupForm - The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs