Magnolia: Difference between revisions
| Line 2: | Line 2: | ||
Magnolia has a number of concepts: | Magnolia has a number of concepts: | ||
* | * Usually Magnolia is set up in such a way that you have one instance running as the '''authoring system''', one as the '''public system'''. This provides flexibility, scalability and security. | ||
* | * If an instance is author or public is determined by a setting in the Config GUI. Setting isAdmin to true will generally let you edit pages etc. Set it to false for public instances - see Changing an author instance into a public instance | ||
* | * To get content from the authoring instance to the public instance(s), you use a mechanism called '''activation''', which is executed from the GUI. Activation pushes content from the source instance (the one you are using when you click activate) to its subscribers | ||
* | * There can be any number of '''subscribers'''. Subscribers are configured through the GUI. Usually, there is one subscriber only, called the '''public instance''' | ||
* Magnolia is delivered as a single war file which per default is set up as | * Magnolia is delivered as a single war file which per default is set up as '''authoring'''. | ||
* | * You control the public instance from the author environment through means of activating content from the author environment to its subscriber(s) | ||
* Launch Screen shows apps | * '''Launch Screen''' shows apps | ||
* Pages app shows site hierachy as site tree or list view and action bar at the right | * '''Pages''' app shows site hierachy as site tree or list view and action bar at the right | ||
* | * Pages consist of '''areas''' | ||
* | * Areas consist of '''components''' (editables are green) | ||
* Images, documents, videos and other asset files are stored in the '''Assets''' app | |||
==Installation== | ==Installation== | ||
Revision as of 14:10, 14 January 2014
Concept
Magnolia has a number of concepts:
- Usually Magnolia is set up in such a way that you have one instance running as the authoring system, one as the public system. This provides flexibility, scalability and security.
- If an instance is author or public is determined by a setting in the Config GUI. Setting isAdmin to true will generally let you edit pages etc. Set it to false for public instances - see Changing an author instance into a public instance
- To get content from the authoring instance to the public instance(s), you use a mechanism called activation, which is executed from the GUI. Activation pushes content from the source instance (the one you are using when you click activate) to its subscribers
- There can be any number of subscribers. Subscribers are configured through the GUI. Usually, there is one subscriber only, called the public instance
- Magnolia is delivered as a single war file which per default is set up as authoring.
- You control the public instance from the author environment through means of activating content from the author environment to its subscriber(s)
- Launch Screen shows apps
- Pages app shows site hierachy as site tree or list view and action bar at the right
- Pages consist of areas
- Areas consist of components (editables are green)
- Images, documents, videos and other asset files are stored in the Assets app
Installation
Installation according to [1]:
- download magnolia-bundled-webapp-5.2.1.war
- extract to directory magnoliaAuthor.war
- change property magnolia.home in magnoliaAuthor.war\WEB-INF\config\default\magnolia.properties to <JBOSS_DATA_DIR>\magnolia\
- create empty file magnoliaAuthor.war.dodeploy
- copy directory and empty file to <JBOSS_DIR>\standalone\deployments
- call http://localhost:8080/magnoliaAuthor
- click 'start installation'
- saved output to C:\Uwes\Documents\Magnolia\Magnolia Installation.htm
- extract to directory magnoliaPublic.war
- change property magnolia.home in magnoliaAuthor.war\WEB-INF\config\default\magnolia.properties to <JBOSS_DATA_DIR>\magnolia\
- create empty file magnoliaPublic.war.dodeploy
- copy directory and empty file to <JBOSS_DIR>\standalone\deployments
Configuration according to [2] for JBoss 7:
- edit <JBOSS_DIR>\configuration\standalone.xml according for JAAS
- edit <JBOSS_DIR>\bin\standalone.conf to increase java startup parameter for JBoss