You can now use the getlogs script to package relevant logs if you need technical support. Run this script in a command shell where you have sourced the Oware environment (in Windows Start > Run cmd, then run oware, and then the getlogs script). This script creates a logs.jar file in the root installation directory, and moves any existing copy of logs.jar to oware\temp. This jar compresses all logs necessary for troubleshooting. Read the jar yourself, or forward this jar to Dorado Software technical support to help troubleshoot.
Server logs are in oware\jboss-x.x.x\server\oware\log. Also: If you install Oracle, because the installation is manual, this application does not create db_setup.log.
The getlogs script also gathers the tomcat web server logs for the web portal.
Increasing Startup Logging
For applications based on Oware 6.2.1 and later (see your versions.txt file for your version), you can add the following line to oware\lib\pmstartup.dat. If you do all output from the startappserver script is logged to a file:
The destination you specify can be any valid path and file name. This helps when the server never starts or errors occur during deployment that would not be in our usual server.log.
Tuning Log Retention
The following properties are in appserver.properties and redcell.properties file for purging log files. As with all other properties, best practice is to override them in owareapps/installprops/installed.properties.
# This property defines how many days to retain server log files. All log files
# older than the specified retention days are purged. Back up older log files if
# you want to retain them. Set the property to -1 to disable this option. The
# default is 7.
# This property defines where redcell client log files are stored The
# following is also the default:
# This property defines how many days to retain the client's
# log files. Files older than the specified age are purged.
# Setting the property to a negative value disables log file deletion.
# The default is 7.