Appboard/old/xml persistence: Difference between revisions

imported>Mike.berman
(created page)
 
imported>Jason.nicholls
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:XML Persistence}}
[[Category:AppBoard old]]
You can use XML to save all of your changes in the enPortal interface, without requiring a connection to a database.
You can use XML to save all of your changes in the enPortal interface, without requiring a connection to a database.


Line 7: Line 9:
# In the portal, select Advanced -> XMLExport.  Then select start.  All of the system data will be saved as XML files under the folder [APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/backup/
# In the portal, select Advanced -> XMLExport.  Then select start.  All of the system data will be saved as XML files under the folder [APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/backup/
# Rename [APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/load-restore.txt.disabled to load-restore.txt.  This will instruct AppBoard to load the saved content when it is started.
# Rename [APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/load-restore.txt.disabled to load-restore.txt.  This will instruct AppBoard to load the saved content when it is started.
# Rename the following files to prevent AppBoard from double-loading default content that is now being loaded from the XML backup.:
# Rename the following files to prevent AppBoard from double-loading default content that is now being loaded from the XML backup:
#*[APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/<b>load_defaultContent.txt</b> to <b>load_defaultContent.txt.disabled</b>.   
#*[APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/<b>load_defaultContent.txt</b> to <b>load_defaultContent.txt.disabled</b>.   
#*[APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/<b>load_edge.appboard_pimA.txt</b> to <b>load_edge.appboard_pimA.txt.disabled</b>.
#*[APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/<b>load_edge.appboard_pimA.txt</b> to <b>load_edge.appboard_pimA.txt.disabled</b>.
Line 14: Line 16:


{{Note|Make sure you always run the XMLExport before shutting down AppBoard if you want the current changes to be saved to the XML files}}
{{Note|Make sure you always run the XMLExport before shutting down AppBoard if you want the current changes to be saved to the XML files}}
{{Tip|If you have a "good" portal configuration that you want to save and keep as a restore point, you can simply make a copy of the /backup/ directory and all sub-directories.  For example, you can save a copy called backup_20110324.  You can restore this backup later (by renaming the directory back to "backup"), or use the directory to migrate data to another portal server.}}

Latest revision as of 10:35, 17 July 2014

You can use XML to save all of your changes in the enPortal interface, without requiring a connection to a database.

Perform the following steps to configure XML persistence:

  1. Start AppBoard and make any desired configurations to the system (create users, roles, etc.)
  2. Open the file [APPBOARD_HOME]/webapps/enportal/WEB-INF/config/persist.properties and confirm that the persistence setting reads persisting=false.
  3. In the portal, select Advanced -> XMLExport. Then select start. All of the system data will be saved as XML files under the folder [APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/backup/
  4. Rename [APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/load-restore.txt.disabled to load-restore.txt. This will instruct AppBoard to load the saved content when it is started.
  5. Rename the following files to prevent AppBoard from double-loading default content that is now being loaded from the XML backup:
    • [APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/load_defaultContent.txt to load_defaultContent.txt.disabled.
    • [APPBOARD_HOME]/webapps/enportal/WEB-INF/xmlroot/server/load_edge.appboard_pimA.txt to load_edge.appboard_pimA.txt.disabled.

After completing the above, stop and re-start AppBoard to confirm that the data is persisted.

Template-note.png
Make sure you always run the XMLExport before shutting down AppBoard if you want the current changes to be saved to the XML files
Template-tip.png
If you have a "good" portal configuration that you want to save and keep as a restore point, you can simply make a copy of the /backup/ directory and all sub-directories. For example, you can save a copy called backup_20110324. You can restore this backup later (by renaming the directory back to "backup"), or use the directory to migrate data to another portal server.