...
After making any change, restart the up.time Web Server
service (on the correct up.time instance, if applicable) to apply these changes. Then verify that you have correctly configured the proxy by browsing to https://<uptimeMonitoringStation>/api
. The behavior should be identical to browsing to the up.time Controller at https://<uptimeController>/api
.
...
The following list details several common up.time Controller configuration tasks.
Task | Setting | Configuration Location in <uptimeDirectory>\controller\ | Notes |
---|---|---|---|
change Controller port | up.time Contoller port | \etc\jetty-ssl.xml | To change the port, find this line within jetty-ssl.xml : <Set name="Port"><Property name="jetty.port" default="9997"/></Set> Update the |
change Controller DataStore target | database connection settings | \resources\uptime-controller.conf | Example connection fields and options are provided for all supported DataStore back-end platforms. By default, the up.time Controller uses a standard MySQL DataStore connection (unless you updated these values during installation). dbType=MYSQL To change the connection details, update these fields with your database platform information. There are example entries in the configuration file. After you have updated your settings, restart the up.time Controller service. |
indicate where PHP sessions are stored | PHP session directory | \resources\uptime-controller.conf | By default, the
|
change Controller logging level | logging level | \resources\uptime-controller.conf | The Controller automatically logs events in the
By default, the logging level is After you have updated your settings, restart the up.time Controller service. |
install new Controller SSL certificate | SSL communication |
| To install a new key, follow steps 3 and 4 from the jetty How to Configure SSL Page, then restart the up.time Controller service. |