During the TrueSight Capacity Optimization (TSCO) Gateway Server installation the option to configure the GeneralManagerServer to be able to communicate over HTTPS was selected and when the Gateway Server was defined in the TSCO Gateway Manager UI the 'Server configured for HTTPS connection' checkbox was selected.  However, after the reboot of the Linux Gateway Server it was shown as Offline in the TSCO Gateway Manager UI and the ETLs were also no longer able to access the Gateway Server.

What is the expected way that the 'httpd' processes used to communicate with the GeneralManagerServer in TLS mode (HTTPS configuration) are to be started on a machine after it has been rebooted? 

Configuring the TSCO Gateway Server HTTPD processes to start on system boot on Linux

Attached to this article is a systemd startup script to trigger the startup of the Apache httpd service to be used to support HTTPS communication with the GeneralManagerServer binary.  This script is designed for RHEL 7.  For a startup script for another TSCO Gateway Server Linux OS contact TSCO Technical Support.

To implement the script:

(1) Edit the tsco-gateway-httpd.service and update the 'User=' and 'Group=' lines to properly represent your TSCO Gateway Server Installation Owner user and group.  Those values should match to owner and group of the $BEST1_HOME/bgs/bin/bgsagent binary.

(2) Copy the tsco-gateway-httpd.service to the /etc/systemd/system directory
  # cp tsco-gateway-httpd.service /etc/systemd/system

(3) As root, run:
  # systemctl daemon-reload

This will reload the daemon configuration and make this new service available for startup/shutdown

(4) Start the service:
  # systemctl start tsco-gateway-httpd

That will start the httpd processes.

(5) Run 'ps -ef | grep httpd' to see that the processes are now running.

(6) Register the service to run on machine boot:
  # systemctl enable tsco-gateway-httpd

This should configure to httpd process listening on port 10130 for the GeneralManagerServer to be restarted automatically on machine reboot.

Improvement DRCOZ-18951: 'TSCO Gateway Server HTTPS config for GeneralManagerServer should register httpd process start on boot' has been logged to request that the ability to register a systemd startups script as part of the TSCO Gateway Server install and configuration process.

Additional Information

The way that HTTPS mode works is that the GeneralManagerServer still runs on port 10129 -- but there is a separate Apache HTTPD server started on the machine listening on port 10130.

So if you have root access if you run 'netstat -anp' as root you and grep for a LISTEN on port 10130 you should see something like this:

> netstat -anp | grep 10130 | grep LISTEN
> tcp6       0      0 :::10130                :::*                    LISTEN      23928/httpd

And if you run a 'ps -ef | grep http' you should see something like this:
 ps -ef | grep httpd
perform  23928     1  0 15:43 ?        00:00:00 /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/bin/httpd -f /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/conf/httpd.conf -k start
perform  23931 23928  0 15:43 ?        00:00:00 /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/bin/httpd -f /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/conf/httpd.conf -k start
perform  23932 23928  0 15:43 ?        00:00:00 /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/bin/httpd -f /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/conf/httpd.conf -k start
perform  23934 23928  0 15:43 ?        00:00:00 /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/bin/httpd -f /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/conf/httpd.conf -k start
perform  25529 23928  0 15:45 ?        00:00:00 /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/bin/httpd -f /opt/bmc/TSCOGatewayServer/Linux-2-6-x86-64/best1/11.3.00/3rd_party_files/apache2/conf/httpd.conf -k start

The problem is that when the TSCO Gateway Server is first installed it starts the Apache Web Server on port 10130 for you -- but the Gateway Manager doesn't have a way to restart it.

To debug further check to see if the httpd service is up and running.   Do either of these commands return output showing it running:
  (1) ps -ef | grep httpd
  (2) netstat -an | grep 10130

If it isn't running you can start it via the following command (run as the TSCO Gateway Server Installation Owner):
  cd /usr/adm/best1_11.3.00/3rd_party_files
  ./startHttpd.sh start

That should make the GeneralManagerServer accessible via TLS on port 10130.