PHENOM Maintenance

Information about PHENOM Installation can be found here.

Application Initialization

As soon as PHENOM is installed (as well as after any machine reboot or update installation), it will begin to be served as a web-application on the default local IP of its host machine, reachable at `localhost` within that machine. The ability of users from outside to reach this service must be configured in the environment in which the machine hosting PHENOM is installed – this is specific to the customer’s IT setup and is therefore a customer responsibility.

Environment Credentials

All user credentials relevant for the operation and use of PHENOM, including those of the Linux users administering the machine hosting the application, the database user managing PHENOM user data, and those of PHENOM application users themselves will be created during the setup or provided alongside it.

If Linux or database user credentials are changed, it is the customer’s responsibility to maintain a record of the new credentials.

Issue Reporting

If users experience issues with PHENOM and reaches out to Skayl, Skayl’s support team may request a portion of the log produced by PHENOM which may aid in issue diagnosis. On Debian installations, these logs can be found in the file `/home/phenomadmin/smlapp.log`, while on RHEL installations they can be found by using the command `journalctl -u smlapp`. When necessary, it is highly recommended that there be an IT professional comfortable with navigating a Linux file system, searching through the above-mentioned outputs, and communicating them (or about them) back to Skayl’s support team.

Domain Name and HTTPS Setup

Customer preferences and setup of the domain name under which their PHENOM application can be reached, whether it is only available internally or can be reached externally over the web, as well as provision, setup, configuration, and maintenance of HTTPS certificates of the Apache2 webserver serving PHENOM is the responsibility of the customer.