Page History
...
A subscriber is a public Magnolia instance. Here is an example subscriber from the default installation. The name of the subscriber node is magnoliaPublic8080. You can choose any name, just pick a descriptive name like corporate-website or intranet.
...
| heading | 0 |
|---|---|
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
Node name
...
Value
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
http://localhost:8080/magnoliaPublic
...
| Mgnl p |
|---|
...
true
...
| Mgnl p |
|---|
...
info.magnolia.module.activation.DefaultSubscriber
...
| Mgnl p |
|---|
...
10000
...
| Mgnl p |
|---|
...
600000
Properties:
URL | required Host name (or IP address) and port number of the receiving public instance. You can use either HTTP or HTTPS protocol in the subscriber URL. The syntax of URL is defined by RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax and amended by RFC 2732: Format for Literal IPv6 Addresses in URLs. The Literal IPv6 address format also supports scoped addresses. The syntax and usage of scope_ids is described in Textual representation of IPv6 scoped addresses. The connection to a subscriber (public instance) during publishing is implemented by the |
active | optional, default is Enables or disables the subscriber without deleting the setup. Useful when there are multiple subscribers. |
class | required, default is Java Bean class that holds the subscriber configuration at runtime. |
connectionTimeout | optional, default is Sets a connection timeout in milliseconds. If time runs out before a connection to the subscriber can be established, a |
readTimeout | optional, default is Sets the read timeout in milliseconds. If time runs before the published content is read from the author instance, a |
...
The content to be published is configured in a subscription. By default, there is a subscription for each Magnolia workspace. The subscription node name is up to you. The default naming convention uses the name of the workspace, for example websiteSubscription.
...
| heading | 0 |
|---|---|
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
Node name
...
Value
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
/
...
| Mgnl p |
|---|
...
website
...
| Mgnl p |
|---|
...
/
...
| Mgnl n |
|---|
Properties:
repository | required Name of the workspace. |
fromURI | required Workspace path on the author instance from which content is published. Use root |
toURI | required Workspace path on the public instance to which the content is published. |
enabled | optional, default is Enables and disables the subscription. |
...
Typically each subscriber resides on a separate server. In the example below, productionOne and productionTwo are subscribers. Each has a unique domain name (siteone, sitetwo) so they likely receive different content.
| Info | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Advanced Tables - Table Plus | ||||||||||
| ||||||||||
Node name | Value |
|
|
|
|
| ||||
| http://localhost:8080/magnoliaPublic | |||||||||
| true | |||||||||
| info.magnolia.module.activation.DefaultSubscriber |
|
| |||||||
| http://www.siteone.com:8080/productionOne | |||||||||
| true | |||||||||
| info.magnolia.module.activation.DefaultSubscriber |
|
| |||||||
| http://www.sitetwo.com:8080/productionTwo | |||||||||
| false | |||||||||
| info.magnolia.module.activation.DefaultSubscriber | |||||||||
| Info | ||||||||||
Once you have your production environment established, it is recommended that you delete the default |
...
This kind of configuration simplifies the security setup. You don't need to segregate anonymous visitors from authenticated intranet visitors since no intranet content is ever published to the magnoliaPublic instance. Intranet content is published only to magnoliaIntranet which is a completely different instance.
...
| heading | 0 |
|---|---|
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
Node name
...
Value
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
/public
...
| Mgnl p |
|---|
...
website
...
| Mgnl p |
|---|
...
/public
...
| Mgnl p |
|---|
...
http://localhost:8080/magnoliaPublic
...
| Mgnl p |
|---|
...
true
...
| Mgnl p |
|---|
...
info.magnolia.module.activation.DefaultSubscriber
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
/extranet
...
| Mgnl p |
|---|
...
website
...
| Mgnl p |
|---|
...
/extranet
...
| Mgnl p |
|---|
...
http://localhost:8080/magnoliaExtranet
...
| Mgnl p |
|---|
...
true
...
| Mgnl p |
|---|
...
info.magnolia.module.activation.DefaultSubscriber
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
/intranet
...
| Mgnl p |
|---|
...
website
...
| Mgnl p |
|---|
...
/intranet
...
| Mgnl p |
|---|
...
http://localhost:8080/magnoliaIntranet
...
| Mgnl p |
|---|
...
true
...
| Mgnl p |
|---|
...
info.magnolia.module.activation.DefaultSubscriber
Flat authoring
Subscriber configuration can turn a hierarchical site structure to a flat one or vice versa. Editors may prefer a flat hierarchy on the author instance. For example, a busy site section such as news is edited several times a day. If that section resides deep in the site hierarchy it takes editors too much time to navigate the tree. Make an editor's life easier by moving the news section to the root level on the author instance. Adding news is now quicker. The subscription publishes the news pages to their intended deeper location on the public instance.
...
| heading | 0 |
|---|---|
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
Node name
...
Value
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
website
...
| Mgnl p |
|---|
...
/news
...
| Mgnl p |
|---|
...
/usa/politics/2015
Flat public site
An opposite example is a flat public site. Search engines prefer a shallow site structure. As a rule of thumb, the flatter the public structure the better. The higher a page appears in the site structure the more likely it will be ranked high by a crawler.
In this example, news pages are published from a deep authoring location /usa/politics/2015 to a more SEO favorable /news.
...
| heading | 0 |
|---|---|
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
Node name
...
Value
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
website
...
| Mgnl p |
|---|
...
/usa/politics/2015
...
| Mgnl p |
|---|
...
/news
Publishing multiple sites to the same public instance
The demo websites /travel and /sportstation that ship with the Magnolia bundle are an example of publishing two different sites to the same public instance. Subscriber magnoliaPublic8080 subscribes to the root node / in the website workspace so it receives content from both sites.
...
| heading | 0 |
|---|---|
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
Node name
...
Value
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
website
...
| Mgnl p |
|---|
...
/
...
| Mgnl p |
|---|
...
/
Publishing the same content to multiple public instances
...
Suppose that the corporation stores branding material such as logos in the dam workspace in a /branding folder. In this subscription example the brand material is published to Asia and Europe affiliate sites. While the content is the same, you can publish it to different location on the target sites depending on how those sites are organized.
...
| heading | 0 |
|---|---|
| enableHeadingAttributes | false |
| enableSorting | false |
| class | m5-configuration-tree |
| enableHighlighting | false |
...
Node name
...
Value
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl f |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
dam
...
| Mgnl p |
|---|
...
/branding
...
| Mgnl p |
|---|
...
/corporate/branding
...
| Mgnl p |
|---|
...
http://acme-asia.com:8080/magnoliaPublic
...
| Mgnl p |
|---|
...
true
...
| Mgnl p |
|---|
...
info.magnolia.module.activation.DefaultSubscriber
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl n |
|---|
...
| Mgnl p |
|---|
...
dam
...
| Mgnl p |
|---|
...
/branding
...
| Mgnl p |
|---|
...
/global-assets/branding
...
| Mgnl p |
|---|
...
http://acme-europe.com:8080/magnoliaPublic
...
| Mgnl p |
|---|
...
true
...
| Mgnl p |
|---|
...
Publishing content from multiple author instances
...
Overview
Content Tools