Sanity Check
After the installation, the system administrator shall confirm the process was executed correctly. This shall be done by checking three aspects:
Logs Checking
Three different types of logs shall be checked with respect to the initial system setup.
-
Deployment log
-
The installer produces the log file dirxaccess_installer_debug.txt under DirXAccessInstallFolder/logs folder.
-
-
OSGi logs
-
The correct and expected state is that after the DirX Access Services startup, there are no OSGi logs printed. The OSGi logs can be found in log file *.log (named with timestamp corresponding to the startup time) under DirXAccessInstallFolder/Services/instances/instance-name/configuration. If the startup causes any of the OSGi logs to be printed out, these shall be thoroughly investigated and appropriate actions shall be executed. The OSGi logs typically reflect situations, when:
-
System customizations (supplied via custom JAR files) are not implemented/configured properly,
-
Configured network connections are not working correctly.
-
-
-
Run-time logs
-
The logs found under DirXAccessInstallFolder/Services/instances/instance-name/logs shall not contain unsolicited records with log level ERROR.
-
DirX Access Manager Checking
Supposing the installation has been run with the option "Deploy DirX Access Manager" switched on, the fast and easy check of the basic system functioning can give the try to log into the DirX Access Manager. When this action does not proceed correctly, it is a clear indicator the system was not deployed in the right way.