Edge Documentation

The filesexport command allows the system administrator to export the current configuration of the enPortal/AppBoard system into a JAR archive.

Purpose

The system administrator may choose to run the filesexport command for the following reasons:

1. To create a backup of the current state of an enPortal/AppBoard system (in conjunction with an export of the database using the XMLexport command)
2. To migrate an enPortal/AppBoard system from one server to another
3. To replicate an instance of an enPortal/AppBoard system for the purpose of implementing Clustering And Failover

Execution

Perform the following steps to execute the filesexport command:

1. In a console, go to the ${TomcatHome}/bin directory
   1. Note: In AppBoard versions prior to 2.1.5, on non-Windows operating systems the command must be run from the /server/webapps/enPortal/WEB-INF/bin/ directory
2. Enter the following command:

[java,N] > portal filesexport -jar JAR_FILE_NAME A JAR file will be created, containing the customization files. By default, it will be created under ${TomcatHome}/bin, unless a full path s specified as part of the JAR_FILE_NAME.

Configuration

The configuration of the filesexport command is managed by the file: ${TomcatHome}/webapps/enportal/WEB-INF/config/export.properties. This file also includes "export-1.properties", "export-appboard.properties", and "custom.properties" files.

To add or remove files or directories to the generated archive, add the settings in "custom.properties" file based on the syntax in "export.properties" file.