Post installation

After successful installation there are some things worth knowning before starting the server. This article describes the key items.  

Start the PhenixID server

Windows

  • Make sure there is a license file in the license folder. If not please read these instructions
  • The PhenixID Server can be started as a Windows service or as an application
  • Locate the Windows service PhenixID Server and select Start, in order to start the service
  • Start [installation path]\PhenixID\Server\bin\phenixidserver.exe to startup the PhenixID server as an application
  • The startup sequence can be verified in the server.log and/or events.log

Linux

  • Make sure there is a license file in the license folder. If not please read these instructions
  • Start [installation path]/PhenixID/Server/bin/start-PhenixID.sh
  • The startup sequence can be verified in the server.log and/or events.log.

Login into the PhenixID Configuration Manager

NOTE: Modules are deployed the first time the server is started which might take 30-300 seconds. The configuration interface won’t be available until this is complete!

Folder structure

The folder structure after a installation should look like shown below. Base of this folder is referenced as phenixid server root.

 

Key folders and their purpose are:

  • bin – contains startup scripts and configuration files for tuning custom performance. By changing settings in the *.vmoptions files custom boot behavior achieved. Please consult PhenixID support before changing anything in any file
  • config – contains configuration files. The most important file is the boot.json file, the main bootstrap file. It contains the bare minimum to get the server started. The phenix-store.json contains most PhenixID Server settings. The log4j.xml file regulates the level of logging in the server. How logging works and is configured is described in detail in separate document which can be found here.
  • license – This the location of the license. How to replace the license is described here
  • logs – Contains log files. A more deep documentation for logging can be found here. server.log – contains system information used for troubleshooting. event.log – contains server events like startup, deployment and more
  • mods – contains temporary data. Please do not add or remove anything from this directory if not instructed to do so by PhenixID support.
  • webroot – the location of HTML templates, images and scripts used when serving HTML content. Changes to any files in this directory will be overwritten on upgrade.
  • data - holds the reporting data and additional "non system configuration".

Bootstrap configuration

PhenixID server relies on a bootstrap file, boot.json.  It contains initial configuration data used to start the server. File location must be <phenixid server root>/config and may not be changed . Changes to this file should only be done advised by PhenixID support or PhenixID documentation.

Configuration interface

After successful login four main headings are available.

Start page

The start page is a dashboard for the PhenixID Server which will contain information about the local installation, connections and most recent events.

Reports page

The Reports page provides a number of default reports on system events. It is possible to create custom reports.  

Scenarios page

PhenixID Server ships with several guides to choose from. With these guides you will be able to create what we call a scenario. There are several guides mapping the most common authentication scenarios, e.g. an SSL-VPN authentication using Username/Password and OTP.

All configured scenarios are located on the scenarios page. There is also a button to configure new scenarios.

Configuration page

The Configuration page is a powerful module used when needing to move outside the capabilities of a Scenario. It gives a total control over the system configuration.

Backup / Restore

PhenixID server relies on files and folders created during the installation process. Maintain backup of the installation root directory. A recovery simply means replacing the current files and folders with the data from last backup. Replacing single files or directories should only be done if advised by PhenixID support.