This behavior is noted in the TSCO 20.02.01 Release Notes in the "Known and Corrected Problems" section:
https://docs.bmc.com/docs/display/btco2002/Known+and+corrected+issues
Important Note: This KA has two sections. The first section describes how to fix the problem in the running environment to bring the web server back up. The second section describes how to fix the problem in the extracted installation image so that a future run of the setup.sh Reconfigure workflow won't cause the problem again.
Fixing the problem after a TSCO setup.sh reconfigure has been run against TSCO
The solution is to manually edit the server.xml file in the 3 different directories ($CPITBASE/datahub/tomcat/logs, $CPITBASE/web/tomcat/logs, and $CPITBASE/servicecontainer/tomcat/logs) to add the required parameter to the Connector definition and restart these TSCO components.
Datahub component
- Log in as the cpit user (owner of the installation)
- Edit the $CPITBASE/datahub/tomcat/conf/server.xml file
- Look for the following entry. The port number may be different.
- <Connector port="8209" address="localhost" protocol="AJP/1.3" redirectPort="8443" xpoweredBy="false" />
- Change it to look like this. Note the additional secretRequired="false" parameter.
- <Connector port="8209" address="localhost" protocol="AJP/1.3" secretRequired="false" redirectPort="8443" xpoweredBy="false" />
- Save the server.xml file
- Restart the Datahub component.
- cd $CPITBASE
- ./cpit restart datahub
Web component
- Log in as the cpit user (owner of the installation)
- Edit the $CPITBASE/web/tomcat/conf/server.xml file
- Look for the following entry. The port number may be different.
- <Connector port="8009" address="localhost" protocol="AJP/1.3" redirectPort="8443" xpoweredBy="false" />
- Change it to look like this. Note the additional secretRequired="false" parameter.
- <Connector port="8009" address="localhost" protocol="AJP/1.3" secretRequired="false" redirectPort="8443" xpoweredBy="false" />
- Save the server.xml file
- Restart the Web component.
- cd $CPITBASE
- ./cpit restart web
Service Container component (if enabled)
- Log in as the cpit user (owner of the installation)
- Edit the $CPITBASE/servicecontainer/tomcat/conf/server.xml file
- Look for the following entry. The port number may be different.
- <Connector port="8309" address="localhost" protocol="AJP/1.3" redirectPort="8443" xpoweredBy="false" />
- Change it to look like this. Note the additional secretRequired="false" parameter.
- <Connector port="8309" address="localhost" protocol="AJP/1.3" secretRequired="false" redirectPort="8443" xpoweredBy="false" />
- Save the server.xml file
- Restart the Service Container component.
- cd $CPITBASE
- ./cpit restart servicecontainer
Fixing the TSCO installation image template files to avoid the problem in the future
Uncompress the installer image (or locate where you already have it)
To prevent the setup.sh program in your TSCO 20.02 installation files from creating this issue, one can edit the following 3 files and set the Connector definition to the correct version for 20.02.01 and later as shown in the steps above.
- /[TSCO Installation Image]/BCO/Disk1/templates/servicecontainer/server.xml.def
- /[TSCO Installation Image]/BCO/Disk1/templates/as/web#server.xml.def
- /[TSCO Installation Image]/BCO/Disk1/templates/datahub/server.xml.def
This will update the template files that are used by the setup.sh reconfigure to re-create the configuration files during the reconfiguration process. Updating the template files will allow the setup.sh reconfigure workflow to properly reconfigure the TSCO 20.02.01 product and avoid the service startup problem.