In the General Settings tab, you can do the following:
...
In cases where more than one XpoLog instance shares the same configuratonconfiguration, you also have the option of specifying that XpoLog run in Cluster mode, so that the XpoLog instances are aware of each other. See XpoLog Cluster Installation for full explanation.
...
The default HTTP port is 30303; default HTTPS port is 30443. You can change the ports used by XpoLog for HTTP/HTTPS.
To change the HTTP/HTTPS port:
- In the XpoLog General Settings General tab, in HTTP port, type the port to be used by XpoLog for HTTP, and/or in HTTPS port, type the port to be used by XpoLog for HTTPS.
- Click Save.
The ports configuration is saved.
Disabling HTTP/HTTPS Access to XpoLog
To disable the HTTP/HTTPS access to XpoLog it is required to edit the servlet container configuration that XpoLog uses (standalone installations only, if XpoLog is deployed on a different application server then it has to be done on the application server level):
- Stop XpoLog
- Go to XPOLOG_INSTALLATION_DIRECTORY/ServletContainer/conf/ and edit the file server.xml
- Follow these:
- To disable HTTP comment the line:
<!--
<Connector protocol="HTTP/1.1" acceptCount="100" connectionTimeout="50000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxPostSize="0" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="30303" redirectPort="30443" xpolog="http"/>
--> - Disable HTTPS:
<!--
<Connector acceptCount="100" clientAuth="false" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" compressableMimeType="text/html,text/xml" compression="on" compressionMinSize="2048" debug="0" disableUploadTimeout="true" enableLookups="false" keystoreFile="${catalina.home}/.keystore" maxHttpHeaderSize="8192" maxPostSize="0" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" noCompressionUserAgents="gozilla, traviata" port="30443" scheme="https" secure="true" sslProtocol="TLS" xpolog="ssl"/>
-->
- To disable HTTP comment the line:
- Save the modification and restart XpoLog.
Note: XpoLog will not be accessible on the disabled protocol and port (also consider modifying XpoLog agents account URLs if required).