Data360 Analyze

Hi Data360 Analyze Team,

I enabled SSL on my Data360 Analyze with port 8443 via instruction here , it worked.

Now, the normal port 8080 is not working which is good, however, i checked the server.xml and the string is still active ( <Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1" redirectPort="8443" compress ...).

Can I comment this string out to disable 8080 altogether ?

Once port 8080 is disabled, how do we stop/start services in SSL ports?

Data360 Analyze Tomcat Server: Start: 8080 Stop: 8089

Do you have instruction on how to perform step #2 and #4 ?

Resources used: 

Enable SSL:

https://support.infogix.com/hc/en-us/articles/360040883974-Setting-up-SSL-with-a-CA-certificate?source=search 

Port 8080

https://support.infogix.com/hc/en-us/articles/360053322513-Data360-Analyze-required-ports

https://support.infogix.com/hc/en-us/articles/360043057473-How-to-change-the-webapp-port-in-Data360-Analyze

2. change `ls.brain.webapp.port` in cust.prop to the port you need
3. change the tomcat server port in this file: <Install Dir>/tomcat/conf/server.xml
4. check the site.prop in <installDirectory>\Data3SixtyAnalyzeServer\web-conf\ to make sure no other properties need to be changed

Thanks

The Connector in the <install directory>/tomcat/conf/server.xml redirects incoming connections on port 8080 to port 8443. Given the other SSL-related changes you have made to configure the application to listen on 8443, the application itself is no longer using 8080. If all your clients have changed their browser bookmarks to use 8443 then it could be commentd out but there are no negative impacts to keeping it in.

Your end users connect to the service on port 8443. The service is already started on the server. The Stop port is used internally by the application and is only needs to be accessible on the loopback adaptor and not from external machines. The services are stopped using the shutdown script (Linux) or via the Services panel (windows server).

The resource in the third link is for Desktop instances, not Server instances and was intended to explain how the Desktop application could be modified post-install to use a different port if another application on the user's machine needs to run locally on port 8080 - it does not relate to configuring SSL. The article will be updated to clarify the use case.