The default deployment for ExtraView is as an exploded directory. However, like many other web applications, ExtraView can be deployed as a .war file. When deploying ExtraView as a .war file, there are configuration parameters that must be modified from the default values, in order to allow the application to write log files and temporary files to locations outside of the application subdirectories that are the default paths.<\/p>\n
Prior to building the .war file, you will modify the WEB-INF\/configuration\/Configuration.properties<\/span> file to set the database connection information, as well as all other configuration settings for your installation.<\/p>\n You will also need to modify the following settings within the Configuration.properties file:<\/p>\n These settings should be commented, and the following parameters and appropriate values should be used instead:<\/p>\n The selected paths must already exist on the file system, and must be writeable by the user that will start up the application server process. Obviously, you should alter the path names to suit your server.<\/p>\n If you will be deploying the .war file to multiple nodes (i.e. you have a clustered system), and each node is on a different machine, please ensure that each node has the same path.<\/p>\n\n
\n
WAR File Deployment in Clustered Systems<\/h3>\n