This document is for versions of SBM prior to 11.4. SBM 11.4 lets you set Tomcat memory allocation in the Tomcat Server section of the SBM Configurator.
To work around this problem, you can revert the socket protocol in Tomcat 8 to what was used in Tomcat 7 (which allowed the integration to work). This involves switching the non-blocking Java connector (NIO) used in SBM 11.0 or higher to the blocking connector (BIO) used in versions prior to SBM 11.0.
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 TLSv1.0, TLSv1.1, TLSv1.2 or TLSv1.3 are allowed. The following list should work in most cases.
Version Manager and SBM used to be able to co-exist on the same server. SBM 11 inadvertently introduced a Tomcat port conflict that prevents the secondary Tomcat server from starting, so depending on the startup order either Serena Common Tomcat
This will typically happen when there is another application such as Version Manager occupying Tomcat's SHUTDOWN port 8005. In such a case modify either the SBM Tomcat SHUTDOWN port or the SHUTDOWN port of the other product to something else so that there is no conflict. The SHUTDOWN port is configured in ...\Tomcat 7.0\server\default\conf\server.xml file.
If VM I-Net is installed on a Windows server using IIS 7, enabling access through IIS will break access to SBM (and any other product using .dll in the URL). Attempting to go to http://server/tmtrack/tmtrack.dll? will show an error originating from Version Manager's Tomcat application server.
