Magnolia has been designed for heavy-load enterprise websites. It has a low memory footprint, a smart cache, built-in clustering capabilities and a distributed deployment architecture that decouples authoring from publishing. Public servers can be load-balanced to provide more throughput and availability.
Easy to integrate
Magnolia is open-source software and runs on the Java platform. Any standard integration practice is supported. This allows you to tie sites created with Magnolia to a variety of legacy applications such as user authentication and authorization and data sources such as digital photo repositories.
- User management. You can deploy Magnolia in large-scale intranet environments where an enterprise-grade user management infrastructure already exists. Magnolia Enterprise Edition implements the Java Authentication and Authorization Service (JAAS) standard to meet single sign-on (SSO) requirements or to connect to your existing LDAP/ADS directory servers such as Microsoft Active Directory.
- Web applications. Magnolia can manage multiple sites within a single installation. Sites can be independent or share content, templates or any other data between each other. The RSS Aggregator module can aggregate external feeds and render them for inclusion in any web page. REST based web services will be available in Magnolia 5.0. This will enable content to be aggregated from separate, independent repositories.
- File systems. Magnolia includes an implementation of the WebDAV interface. This provides a way for users to create, edit and manage templates on the Magnolia server as if they resided on the local file system, and eliminates the need for any Java or system-specific knowledge when creating templates.
You can manage multiple sites from the same author instance. The public instances can serve geo-specific content for example
Magnolia is distributed as two web-applications, one acting as authoring and the other as public environment. This allows for better security by having one application inside your firewall and the other outside.
The integrated publish & subscribe mechanism allows you to mirror your website to as many physically distributed servers as you want.
Basic four-eye editorial workflow that is configured in Magnolia by default. Authoring and editorial review happen on the Author instance. Content is published to Public instance only when the workflow is completed.
Magnolia has integrated cross-platform OpenWFE workflow engine, which allows for extensive customization of workflows and the integration of Magnolia as part of a business process managed architecture.
Users will come across a pre-defined workflow for the first time when they activate content. A workflow named activation is started and a workitem arrives to the responsible user's inbox. This basic editorial four-eye workflow is included by default.
You can create your own workflows to match the needs for editorial review and publishing procedures.
Magnolia has its own caching mechanism to increase speed and minimize CPU load. The cache is written to the file system and is automatically updated whenever needed. The cache is configurable by tree or by page.
The caching API allows for highly customizable caching strategies. Magnolia Enterprise Edition comes with a set of default strategies that provide superior caching behaviour.
At a certain amount of traffic, or a certain need on availability, multiple public instances provide an advantage. In a typical load-balanced system one server acts as the load-balancer, using Apache to split requests, for example, while other servers host Magnolia public instances.
A sticky session ensures that a particular visitor will be handled by the same server over the lifetime of a session.
This Enterprise-only feature ensures that activated content is either published in its entirety to all Magnolia instances in a staging environment, or - should anything go wrong - no changes are performed at all. It ensures the integrity of the published content.
The Magnolia user interface for content authors is available in over 15 languages, including English, Russian, Chinese, French, German and Spanish.
Magnolia CMS can manage multiple language within a single site structure or use independent site-trees per language. Read more...
Magnolia can manage multiple sites within a single installation. Sites can be completely independend or share content, templates or any other data between each other, depending on your needs. Read more...