Multiple public instances are useful when you want to:
- Publish one part of a site to a different public instance.
- Manage multiple sites in one author instances and publish each site to a dedicated public instance.
- Add more public instances to cope with high load.
- Add more public instances to ensure high-availability.
Copying a public instance
The simplest way is to create a new public instance is to copy an existing one.
Before you do this, back up the
webapps folder and the database. There is always the risk of corrupting the existing instance.
- Stop the instance.
- Copy a public instance folder such as
magnoliaPublic. If you use an external database such as MySQL, copy the database folder too.
- Rename the copied folder to
- Delete unnecessary subfolders from the copy. The copy is a clone of the source instance. Some folders are essential to the new instance but others can be deleted.
- OK to delete:
cachecontains cached entries of the original instance.
logscontains log entries of the original instance. Empty log files will be recreated during server startup.
subfolders in each
/repositories/magnolia/workspaces/*folder. Deleting the subfolders reindexes the
repositories. The rest of the
repositoriesfolders should remain intact.
tmpis a temporary folder which Tomcat or Jackrabbit uses for its processes during export/import.
- Don't delete:
docrootcontains the Tomcat
templatescontains static resources.
- OK to delete:
Other ways to create a public instance
Other ways to create new public instances:
- Backup module. Use the Restore function. This creates a new public instance for the restored data automatically.
- Backup and restore JSP scripts. The is also useful here.
- reate new public instances without shutting down existing ones.
- Programmatically by writing a
- How to replicate a public instance lists many options to repair a broken public instance using a second instance.
- Jackrabbit DataStore for blobs in special cases.