Appboard/old/backup and restore 2.0.x
AppBoard/enPortal provides utilities for backing up and restoring system data and configuration settings. This page details the commands and procedures for managing this aspect of the system.
Backup
There are several reasons that the AppBoard/enPortal administrator may need to create a backup of the system:
- Migrating a system from development to production, or from one physical location to another
- Upgrading the system to a newer version
- Creating a regular backup to have available in case the system ceases to function properly
In order to perform a backup, it is first helpful to understand the relevant file locations and commands.
Backup File Locations
| Directory | Description |
|---|---|
| /server/webapps/enportal/WEB-INF/xmlroot/server/content/ | XML files representing all of the stock (original) content that was installed into the AppBoard/enPortal database to provide the base system definitions and content. Includes stock content for any Product Integration Modules (PIMs) that you have loaded into the system. |
| /server/webapps/enportal/WEB-INF/xmlroot/server/backup/ | The /backup/ directory is identical to the /content/ directory, except it also includes all of the changes you have made in the system. |
| /server/webapps/enportal/WEB-INF/xmlroot/appboard/ | Contains XML definitions for AppBoard data adapters and data sources. |
| /server/webapps/enportal/WEB-INF/appboard-archive.jar | The AppBoard archive file, created by the Backup button in AppBoard Builder. |
Backup Commands
| Command | How To Run | Result |
|---|---|---|
| XMLExport | Log in to enPortal as administrator and select the Advanced / XMLExport menu item and then click "Start" - OR - |
Creates the directory /server/webapps/enportal/WEB-INF/xmlroot/server/backup/ containing XML definitions for all data in the system database. |
| FilesExport | Go to /server/webapps/enportal/WEB-INF/bin/ and run: > portal FilesExport -jar yourJarFileName.jar |
Creates the enPortal archive file yourJarFileName.jar, containing backup copies of system license and configuration files. Note, you can customize what files are included in this archive by editing the file /server/webapps/enportal/WEB-INF/config/export.properties. |
| Backup | Log in to AppBoard Builder as administrator, select Settings, and click "Backup" | Creates the AppBoard archive file /server/webapps/enportal/WEB-INF/appboard-archive.jar. This is a compressed file containing the following directories of files:
|
How To Create a Backup
Perform the following steps to create a full backup of AppBoard/enPortal:
- Execute the enPortal XMLExport
- Execute the enPortal FilesExport
- Execute the AppBoard Backup
After completing the above commands, copy the entire file system to the backup server.
Restore
The restore process enables you to install a new version of AppBoard/enPortal and restore your previous data and configurations.
Restore File Locations
| Directory | Description |
|---|---|
| /server/webapps/enportal/WEB-INF/xmlroot/server/ | Files in this directory are invoked whenever the AppBoard/enPortal application is started (by the startup command). Any file in this directory that begins with "load" identifies sets of XML content to be loaded into the system database, which will be executed unless the file contains the ".disabled" or ".completed" extension. When restoring the system, you must edit these filenames to control what content will get loaded into the database. |
| /server/webapps/enportal/WEB-INF/xmlroot/server/backup/ | This is the full system backup directory, which will be loaded at system startup if the load file "load_restore.txt" is not disabled. |
| /server/webapps/enportal/WEB-INF/xmlroot/appboard/ | Contains AppBoard configuration files, including the stacks.xml file with all of the Appboard visualization configurations. XML files in the /adapters/ directory will load data adapters and data sources, unless the file contains the ".disabled" or ".completed" extension. |
Restore Commands
| Command | How To Run | Result |
|---|---|---|
| DBReset | Shut down the system, then go to /server/webapps/enportal/WEB-INF/bin/ and run: > portal DBreset. Enter "y" to reset the load files so the backup content will be loaded upon system startup. |
Clears all configuration data from the system database, so that the backup data can be re-loaded into the system. |
| LoadFileReset | Go to /server/webapps/enportal/WEB-INF/bin/ and run: > portal LoadFileReset |
Renames load files under /server/webapps/enportal/WEB-INF/xmlroot/server/backup/, to remove the completed extension. |
| FilesImport | Go to /server/webapps/enportal/WEB-INF/bin/ and run: > portal filesImport -jar YourJarFileName |
Extracts saved configuration files from a jar file to the proper location in the current system. |
How To Restore AppBoard/enPortal
- On the previous system, run all of the backup commands
- XMLExport
- FilesExport
- Backup
- Stop AppBoard/enPortal.
- Steps needed for a new installation only:
- Install the new version of AppBoard/enPortal.
- Copy the directory /server/webapps/enportal/WEB-INF/xmlroot/server/backup/ into the file system from the backup.
- Copy the enPortal archive jar file to the new file system and run FilesImport to import the enPortal configuration and license files on to the new installation.
- Copy the AppBoard archive jar file to the new file system and run FilesImport to import the AppBoard configuration files on to the new installation.
- Ensure that the file /server/webapps/enportal/WEB-INF/xmlroot/server/load_restore.txt does not have the ".disabled" extension.
- Copy all files from /server/webapps/enportal/WEB-INF/xmlroot/appboard/adapters-bk/ to /server/webapps/enportal/WEB-INF/xmlroot/appboard/adapters/
- Run the DBReset command to clear out the system database (not needed for a new installation).
- Start AppBoard/enPortal
