Jahia the Java Open Source Web Content Management Community
A
Access control list (ACL)
A list of permissions attached to a content object (page, container list, container or field) or to some Jahia administration tasks. It is a list of users or user groups, which can either have (R)ead, (W)rite or (A)dministration rights on the corresponding objects. On default ACLs are inherited by the child content objects, but you can specify to break inheritance. The ACLs for fields are stored on the container list level, so that the settings apply to the field in all containers of the list.
Action menu
A context menu, which appears when clicking on an icon, which obviously is automatically attached to content objects (container lists, containers) in the EDIT mode. The menu allows to add, update, delete, copy, paste content or set some properties on it. Most of the time engine popups will be opened for the action. The menu is dynamic, considers the rights of the current user or disallows action on currently locked objects. Next to the action menu, there may be some icons showing the workflow or time base publishing state of the content object.
Admin center, administration console
This is a web-based administration interface to manage your Jahia server instance. Users with administration rights will see an Administration link in the toolbar. Alternatively the panels can be accessed with using the URL http://domain/CONTEXT_NAME/administration
AJAX (Asynchronous JavaScript and XML)
A web development technique to create interactive, rich internet applications. There are several known libraries and frameworks available, but it is not recommended to mix or use many of them, as the web pages or attached Javascript files will become too large to load. Jahia has decided to solely use Google Web Toolkit (GWT) and Ext GWT (GXT) , which is an extension library for GWT.
Application programming interface (API)
This acronym is mostly used for the Java based Jahia API, which is exposed by the service classes in Jahia´s service registry. These classes are implementations of a corresponding interface. With Jahia 6 we discourage the usage of these APIs if our tag library can be used instead. The reason is that an API will more probably change in future releases than a tag. Also the usage of the API is less documented in Jahia.
Audit log
A journal, which Jahia writes to the database by logging the last user actions. The log can be limited in size and flushed at any time. It can be viewed in the Admin Center or via the container and page related popup engines. There is also a query tag to show a list of containers based on the information in the aufit log (for instance "last added" or "last edited" containers).
Authoring
Relates to content authoring, which relates to input and mange content, either via the Jahia popip engines or via inline editing.
Authoring server
Refers to one (or more) Jahia server instance(s) dedicated to authoring in a cluster of Jahia servers. This is recommended in large sites under heavy load, so that the browsing nodes can use their caches and CPU resources exclusively for users browsing (reading) the site.
B
Bigtext
One of Jahia's fieldtypes to hold text of unlimited length, which is obviously edited in a Rich text editor (on default: FCK editor). Depending on the Jahia server configuration, these fields are either saved in files on the file system or as blogs in the database.
C
Cache
Temporary storage for frequently accessed data. Jahia uses database level caches managed by Hibernate, service level caches and HTML level caches managed by Jahia. Jahia on default uses an implmentation of the Reference-Cache, which maximizes the usage of memory and relies on the garbage collector. When using Jahia in cluster it is important that cache entries are properly invlidated throughout the cluster, after content objects have changed. Jahia allows to also plug-in different cache providers, like EHCache, JBossCache and experiments with Terracotta and disk serialization.
Category management
Jahia allows a definition of a server-wide category (taxonomy) tree. Each content object has a default category metadata fields to attach one or more categories to it. It is possible to define further custom category fields for content object, either via metadata configration or content definition to support browsing Jahia by different axis.
Clustering
A Jahia cluster is a group of Jahia servers (called nodes) that run on several computers and that work together closely. The most important aspect of a cluster is that all the nodes contained in the cluster can be viewed as though they are a single Jahia machine.
In Jahia we make the distinction between several types of nodes:
- Browsing/editing nodes (used for browsing or editing content)
- Processing node (that will handle background jobs such as content import or publications)
- Indexing nodes (that will handle background content indexing)
Content Management System (CMS)
Acronym for a computer application used to create, edit, manage, search and publish any kinds of digital media and electronic text. Jahia is the leasing provider an Enterprise Content and Portal Management software in the Professional Open Source world.
CND (Compact Namespace and Node Type Definition)
A notation defined in the Java Content Repository (JCR) specification. Jahia uses an extension of this specification to define the structure of its content objects.
CSS (Cascading Style Sheets)
A stylesheet language used to describe the presentation of web pages written in HTML or XHTML. Jahia´s templates makes good use of it to separate the content from the presentation and thus provides more flexibility and allow to easily change the look & feel in custom templates deriving from the ones deployed with Jahia.
Configuration wizard
Since Jahia 6 this is a separate application used to configure and create Jahia server packages to be deployed on specific environments (application server, cluster nodes,...).
D
Document Management System (DMS)
A computer system used to track and store electronic documents. In Jahia the term relates to all documents in our file repository, which is based on the Java Content Repository standard, but can also mount any shared network systems.
Dublin Core
A standard metadata element set developed by the Dublin Core Metadata Initiative to describe digital content. We use it to create standard metadata fields for web pages, container lists, containers and file documents within Jahia.
E
Engines
Jahia provides several graphical user interfaces to help users input and manage content. We call these interfaces "engines" in the Jahia vocabulary. Several actions (add container, update container, set page properties, login/logout) and also each type of content object has its own custom engine. For example a date field will launch a Date Picker interface while a text field will launch a WYSIWYG HTML Editor.
Enterprise Content Management (ECM)
The official definition for this term comes from AIIM (Association for Information and Image Management) International and is:
Enterprise Content Management (ECM) is the strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes.
Jahia offers enterprise workflow capabilities, website factories, multilingual capabilities, site replications and many other enterprise Web Content features.
Ext GWT (GXT)
A Rich Internet Application Framework for GWT providing some out of the box UI controls used by Jahia.
F
FCK Editor
A lightweight Open Source Web richtext editor integrated in Jahia, which is used on default for editing Bigtext fields. You may also plug-in other third party richtext editors.
Filtering
Since Jahia 5.0.4 Jahia uses query object model, which internally use the previously availabe container filters to display a query filtered list of containers. Since that version we also internally started to use Lucene filters if the query property to use backend cache is set to true.
G
Groovy
A scripting language for the Java platform, which Jahia template developers can use for event handlers or to create mails sent by the Jahia server.
Google Web Toolkit (GWT)
A very efficient open source Java software development framework to createa AJAX applications in Java. Jahia uses a GWT based framework to create many content widgets used in the engines or templates.
H
Hibernate
Hibernate is a powerful, high performance Open Source object/relational persistence and query service. Jahia uses it for any database access in favour of the previously used direct JDBC access.
I
Import / export
Jahia allows to import / export content (sites, pages, container lists, containers) to and from XML. It is used internally for site replication purpose, but sometimes it is the means to migrate content between major Jahia releases. It can also be used for regular backups of your content.
In-context editing
Jahia allows to edit content directly in the page for a WYSIWYG user experience. Content can either be edited in a richtext editor opening in a popup, but since Jahia 6 you can also make simple editing directly on the page in EDIT mode, when Inline editing is activated.
Indexing
Indexing is used by the search engine to collect, parse and store data for fast and accurate information retrieval. Jahia uses Apache Lucene to create the index of Jahia content.
Indexing policies
Jahia allows to configure indexing policies in order to define, when content should be indexed. On default content is indexed asynchronously with a small delay, but can also be indexed immediately (synchronized), which is useful if you want to use the Lucene based query tags. Resource intensive indexing can also be delayed to low peak times.
J
Jackrabbit
Apache Jackrabbit is a fully conforming implementation of the Content Repository for Java Technology API (JCR). A content repository is a hierarchical content store with support for structured and unstructured content, full text search, versioning, transactions, observation, and more.
Jahia 6 uses Jackrabbit for the file based documents, but will in future store all content objects within this content repository.
Java Content Repository (JCR)
The Content Repository API for Java Technology specified in JSR-170 and JSR-283.
A Content Repository is a high-level information management system that is a superset of traditional data repositories. A content repository implements "content services" such as: author based versioning, full textual searching, fine grained access control, content categorization and content event monitoring. It is these "content services" that differentiate a Content Repository from a Data Repository.
Java Development Kit (JDK)
The JDK is a superset of the JRE, and contains everything that is in the JRE, plus tools such as the compilers and debuggers necessary for developing applets and applications. Jahia requires a JDK to run, a JRE will NOT be sufficient.
Java Platform, Enterprise Edition (Java EE)
Java Platform, Enterprise Edition (Java EE) builds on the solid foundation of Java Platform, Standard Edition (Java SE) and is the industry standard for implementing enterprise-class service-oriented architecture (SOA) and next-generation web applications.
Jahia will run on any Java EE compliant application servers, itself it uses some Java EE services.
Java Runtime Environment (JRE)
The Java Runtime Environment (JRE) provides the libraries, the Java Virtual Machine, and other components to run applications written in the Java programming language. Jahia is written in Java but needs a Java Development Kit (JDK) to run, a JRE will not be sufficient.
Java Server Pages (JSP)
A JSP page is a page created by the web developer that includes JSP technology-specific and custom tags, in combination with other static (HTML or XML) tags. A JSP page has the extension .jsp or .jspx; this signals to the web server that the JSP engine will process elements on this page.
The exact format of a JSP page is described in the JSP specification. Jahia is based on the JSP 2.0 specification.
Java Server Pages Standard Tag Library (JSTL)
Simple tags providing core functionality common to many Web applications. JSTL has support for common, structural tasks such as iteration and conditionals, tags for manipulating XML documents, internationalization tags, and SQL tags.
Jahia 6 uses the JSTL 1.1 standard.
Java Virtual Machine (JVM)
The Java Virtual Machine is responsible for the hardware- and operating system-independence of the Java SE platform, the small size of compiled code (bytecodes), and platform security.
K
L
Layout manager
A component based on GWT, which can be used to let the Jahia user create a portal page with positioning mashup widgets with drag&drop.
Lightweight Directory Access Protocol (LDAP)
LDAP is an application protocol for querying and modifying directory services running over TCP/IP. Jahia has default connectors to retrieve users/groups from an LDAP server.
Lucene
Lucene is a full-featured open ource text search engine written entirely in Java.
M
Metadata
Data providing information about other data. In Jahia there are standarad metadata fields (based on Dublin Core standard) to describe content objects (page, container list, container., files).
N
Node
An item in a JCR workspace is either a node or a property. Each node may have zero or more child nodes and zero or more child properties. There is a single root node per workspace, which has no parent. All other nodes have one parent. Properties have one parent (a node) and cannot have children; they are the leaves of the tree.
N-step workflow
These workflows may have several steps depending of the manager selection or the inherited workflow fixed on the parent page. This is the default workflow type in Jahia 6.
O
OpenSearch
OpenSearch is a collection of technologies developed by Amazon.com that allow publishing of search results in a format suitable for syndication and aggregation. It is a way for websites and search engines to publish search results in a standard and accessible format.
Jahia can act as producer as well as consumer of OpenSearch enabled search engines.
P
Processing server
Several tasks, like workflow procesing, time based publishing, and others are done asynchronously as background jobs in a processing server. In a cluster it can be defined that just one node is doing the processing.
Q
R
Read-only mode
A Jahia server can operate in read-only mode, meaning that the EDIT tab will never be displayed. This makes only sense in clustered environments, where browsing nodes will repond faster, when no write/admin access checks need to be done.
Resource bundle
Resource bundles contain locale-specific objects. When your program needs a locale-specific resource, a String for example, your program can load it from the resource bundle that is appropriate for the current user's locale.
For labels used in Jahia administration, engines and templates we use resource bundles, which are files with the extension .properties and consist of key/value pairs. When translating Jahia into another language, the values of these files need to be translated and saved in a file, which has the language code appended before the extension.
S
Spring framework
This is an open source Java application framework. The core features of the Spring Framework can be used by any Java application, but there are extensions for building web applications on top of the Java Enterprise platform.
Jahia uses this framework mainly for configuration and startup of service registries, but will use also other functionalities in future.
T
Toolbar
Since Jahia 5 there is a common toolbar used in all Jahia templates, which is displayed on top as soon as a user logs on. In Jahia 6 the toolbar has been completely refactored and now adds many more convenient options and will also allow to easily add custom options in the near future.
