Restoring Web Application server file system

The Web Application server file system contains certain files and directories that should persist in a disaster recovery situation.

You should prepare for a disaster situation by configuring the web application servers for high-availability, as described in Configuring Web Application servers for high-availability. If you don't have a warm standby data center, you should copy the following files and directories found in /usr/local/jive to the same location in your new web application servers:

  • applications/*/home/search
  • applications/*/home/themes
  • applications/*/home/attachments/cache
  • applications/*/home/images/cache
  • applications/*/home/documents/cache
  • applications/*/home/cache/jiveSBS
  • applications/*/home/jms
  • applications/*/home/jive_startup.xml
  • applications/*/home/attachments/*.txt
  • applications/*/home/images/*.bin
  • *.pid
  • applications/saasagent
  • tomcat/lib/postgresql*.jar
  • etc/httpd/sites/proxies/maint.con
Tip: If you have a text extraction location set up for search, as described in Configuring text extraction location, you should copy that directory over to the new system to save time while reindexing.