VM 8.6.1+: PVCS Version Manager Server Admin utility fails executing "Remote integration from site" to remove legacy Tomcat ISAPI Filter from Microsoft IIS Server
Enter 'jakarta' into the Filter Name field Click 'Browse' and navigate to <VM Server installation directory>\VMINET\ tomcat \bin\win32\i386\ isapi _redirect.dll Stop and restart the WWW Publishing Service
NOTE: This URL will load the file ( Tomcat ) C:\Program Files\Serena\SBM\Common\ tomcat \server\default\webapps\idp\img or (JBoss) C:\Program Files\Serena\SBM\Common\jboss405\server\default\deploy\idp.war\img\logo.png
If you do not need to integrate with a 3rd party web server, meaning end-users directly connect to the Serena VM Web Application Server by specifying :8080 or :8090 in their URLs: Unselect the Enabled box for Microsoft IIS server in the Version Manager Application Server Admin utility (VPADMIN) and remove the ISAPI redirector from IIS (Default Web Site -> Properties -> ISAPI filters : jakarta ), or remove the include directive for httpd_pvcs.conf
TeamTrack used to be delivered with a webserver that you could use, mainly for demos (instead of IIS). This server cannot load the ISAPI filters that are required for SBM to run, including Tomcat redirector, URL rewriter, and ModSecurity. As such, it is generally useless, even for trying to debug problems on customer sites.
In order for Tomcat to see this Reg entry you need to modify the ISAPI filter DLL for the second instance. You will need to use a hex editor to do this, do not use Notepad or any other ASCII editor. Open the following file:
You must change the configuration of the ISAPI redirector that is installed as an ISAPI filter so it will pass through HTTP error messages from Tomcat directly to the client. To configure the ISAPI filter to pass the messages directly to the client:
If you are running Tomcat clustered, then ISAPI Redirect to enforce stickiness with Tomcat must be set. To do this, you would need to set jvmRoute of each Tomcat server (server.xml) to the appropriate worker. Currently this is a done manually and an upgrade removes the changes made to jvmRoute, breaking the Tomcat cluster.
[error] ajp_send_request::jk_ajp_common.c (1630): (worker1) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
