One way to serve a TC Server application is to have clients request the application directly from the TC Server.
In this example, the client requests www.example.com:8080/sample direct from TC Server, and then TC Server sends the application to the client.
An HTTPD web server can be configured as a proxy server, so that the clients will request the TC Server application from the HTTPD web server, and then the HTTPD web server will get the application from TC Server, and the HTTPD web server will send the TC Server application to the client.
Enure the proxy modules are loaded. If they are not loaded, add Include conf.modules.d/*.conf to /etc/httpd/conf/httpd.conf.
~]# httpd -M . . . proxy_module (shared) proxy_http_module (shared) . . .
Assuming HTTPD is configured to use virtual hosts, add Proxy and ProxyPass to the /etc/httpd/sites-enabled/vhosts.conf file.
<VirtualHost *:80> ServerName www.example.com DocumentRoot "/var/www/site1" ProxyPass / http://www.example.com:8080/ ProxyPassReverse / http://www.example.com:8080/ </VirtualHost>
Configure SELinux on the HTTPD server to allow httpd network connections.
~]# setsebool httpd_can_network_connect on
~]# systemctl restart httpd
Now, the TC Server application can be produced by navigating to www.example.com/sample.
Proxy Pass can also be used to load balance between two or more TC Servers.
Replace "server1" with whatever unique text you want to use to distinguish and identify your cluster of TC Servers.
<VirtualHost *:80> ServerName www.example.com DocumentRoot "/var/www/site1" <Proxy balancer://server1> BalancerMember http://www.tcserver1.com:8080/ BalancerMember http://www.tcserver2.com:8080/ ProxySet lbmethod=bytraffic </Proxy> ProxyPass / balancer://server1/ </VirtualHost>