Appboard/old/filesexport - Revision history

imported>Jason.nicholls at 18:15, 17 July 2014

2014-07-17T18:15:15Z

← Older revision		Revision as of 18:15, 17 July 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:Filesexport}}
			[[Category:AppBoard old]]
	The filesexport command allows the system administrator to export the current configuration of the enPortal/AppBoard system into a JAR archive.		The filesexport command allows the system administrator to export the current configuration of the enPortal/AppBoard system into a JAR archive.

imported>Jason.nicholls: moved Filesexport to appboard/old/filesexport

2014-07-17T18:14:26Z

moved Filesexport to appboard/old/filesexport

← Older revision	Revision as of 18:14, 17 July 2014
(No difference)

imported>Jason.nicholls: /* Purpose */

2014-07-17T05:34:22Z

Purpose

← Older revision		Revision as of 05:34, 17 July 2014
Line 8:		Line 8:
	#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)		#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)
	#To migrate an enPortal/AppBoard system from one server to another		#To migrate an enPortal/AppBoard system from one server to another
	#To replicate an instance of an enPortal/AppBoard system for the purpose of implementing [[~~Clustering_And_Failover~~\|Clustering And Failover]]		#To replicate an instance of an enPortal/AppBoard system for the purpose of implementing [[appboard/old/clustering_and_failover\|Clustering And Failover]]


	== Execution ==		== Execution ==

imported>Mike.berman: created page

2012-01-17T20:15:32Z

created page

New page

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:

#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)
#To migrate an enPortal/AppBoard system from one server to another
#To replicate an instance of an enPortal/AppBoard system for the purpose of implementing [[Clustering_And_Failover|Clustering And Failover]]

== Execution ==

Perform the following steps to execute the filesexport command:

#In a console, go to the ${TomcatHome}/bin directory
##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
#Enter the following command:
<code>[java,N]
> portal filesexport -jar JAR_FILE_NAME
</code>
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.