Digital Experience Manager's official and nightly builds are distributed as installation packages, which contain the entire software suite (Digital Experience Manager, Jahia Core Content Platform, Studio) as well as the ACME-Space demo, several template sets and dozens of composite modules.
java -jar <your-downloaded-digital-experience-manager-jar>
java -jar <your-downloaded-digital-experience-manager-jar> -console
./start.sh” (on Linux/MacOSX) or “start.bat” (on Windows).There shouldn’t be any spaces in your folder naming. For example C:\DigitalExperienceManager-7.1\ is OK while C:\Digital Experience Manager 7.1\ is not.
This option allows to discover Digital Experience Manager without specific configuration thanks to the installation of an Apache Tomcat 8 server & Sun Java DB / Apache Derby DBMS bundle. This installation also provides and deploys all interesting and available modules, applications and templates.
The default Digital Experience Manager v7.1.2 is distributed with an Apache Tomcat 8.0.23 application server. No manual configuration of the server is required, as it will be directly setup during the Digital Experience Manager installation. By default Tomcat will use standard ports (8080, 8009 and 8005). Please ensure that you do not have any other servers/services running and using those ports. Optionally, you can change Tomcat ports during the "Custom install" installation type (see "3.2.3 Installation type – Custom install").
Digital Experience Manager v7.1.2 is installed with the embedded Sun Java DB / Apache Derby database engine with the “Discovery install” option. If you wish to get started rapidly, you can use the provided database as is. With the “Custom Install” option you can choose to install Digital Experience Manager to another more robust standalone database during the configuration wizard of Digital Experience Manager. Please note that you cannot simply switch the database at a later stage on the same installation. You will have to export the content and import it into a new Digital Experience Manager installation configured with the different database.
If you want to install Digital Experience Manager on a custom environment (application server, database, mail server configuration, different port numbers), choose particular operating mode (development, production, distant publication server), configure clustering or LDAP providers, you need to choose the “Custom Install” option.
Digital Experience Manager v7.1.2 Enterprise Distribution can be installed with an Apache Tomcat 8.0.23 application server. If you want to install into your own server, you need to deselect the “Apache Tomcat” checkbox on Step 5 of the installation wizard and click Next. On the next page you will be able to choose whether the installation is targeted into one of these application servers: - Apache Tomcat 8.0.x (in case you want to deploy Digital Experience Manager yourself into an existing Tomcat server other than the one bundled by default) - IBM WebSphere 8.5.5 - Red Hat JBoss EAP 6.x
The installed Digital Experience Manager will then include some specific configurations, which are needed to make it run smoothly in the targeted application server. See the next chapter “3.7 Application server specific installations” for further information.
The embedded Sun Java DB / Apache Derby database engine, which is used with “Discovery install” option is not suited for production. During installation you can choose between:
Please note, that you cannot simply switch the database at a later stage on the same installation. You will have to export the content and import it into a new Digital Experience Manager installation configured with the different database.
During installation you will be asked to provide the connection URL (see chapter "2.3 Database" for details) and the user/password for accessing the database.
Furthermore, you also will be able to set whether binary data should be stored in the database or directly on a file system (for clustered Digital Experience Manager setup the file system need to be shared by all cluster nodes). By default, the binary files are stored on the file system, which in most cases results in a better performance as the file content can be directly streamed from the file system (utilizing low level OS mechanism) and a higher level of concurrency can be achieved. There is also an option present to define if the Digital Experience Manager DB structure (tables, indexes, sequences) has to be created first (this option needs to be unchecked e.g. when running the installation wizard for installing second, third, etc. cluster nodes).
This section is available only if you have chosen to use the bundled Tomcat application server.
Here you have the possibility to configure the different ports used by Tomcat.
Here you have the possibility to specify the context path for Digital Experience Manager Web application. If you want to deploy it into the root context (“/”), just leave the field blank.
You also need to specify a login and password that will be required to access the Tools Area: monitoring and debugging tools embedded in Digital Experience Manager.
Here you have to choose in which mode you want to install Digital Experience Manager.
Just take care that even if you can switch later between the modes (you can reconfigure it in jahia.properties), some modules will be packaged only when you perform the installation in “Development + Modules/JahiApps/Demos” Mode. Installing in Production Mode, and then switching to Development Mode will activate the development dedicated features (like the Studio), but will not deploy the additional modules. You will have to deploy them using Module Management Panel in Digital Server Administration. Please refer to the “3.8 Modules” section for more information.
Here we will list the differences in terms of available features and Digital Experience Manager behavior between the Development and Productions modes. From the packaged modules point of view, there are no differences between plain Development (not the second option, which is “Development + Modules/JahiApps/Demos”) and Production mode.
| Development mode | Production mode | |
|---|---|---|
| Studio | Yes | Not accessible |
| Cache | Display extra information directly in the rendered page by passing request parameter “cacheinfo=true” in the page URL | n/a |
| Rendering | Display extra view/area rendering information by passing request parameter “moduleinfo=true” in the page URL | n/a |
| Error handling | Exception stacktraces are rendered in the error page. Additional (more verbose) error reporting using ErrorFileDumper in the rendering of views. | n/a |
| Rules | Watch for changes in rule files under <digital-experience-manager-web-app-dir>/WEB-INF/etc/repository/rules and automatically rebuild the rule base | n/a |
| Job scheduling (from Spring) | If a background job is scheduled from a Spring definition file, the job is recreated (all the job data is deleted) and rescheduled on each Digital Experience Manager restart. | Spring-based configured jobs are never deleted. If the change is detected in the trigger configuration the job is re-scheduled on Digital Experience Manager startup. |
| URL rewriting rules | Scanned for changes each 5 seconds. The rule base is reloaded if changes are detected. | No implicit scanning for changes. |
| Groovy patcher | Scans for new patches each 5 seconds and executes them. | Scan interval is configurable at is set to 5 minutes by default. Scanning can be disabled completely. |
In case you will use LDAP directory as a provider for application users or/and groups, you can choose to configure LDAP provider settings during installation. If you check this option, you will then access an additional screen, where you can setup your configuration for user and group providers.
If you do not configure them during the installation process, you will still be able to do it later from the configuration files. Please refer to the “4.5 LDAP ” section for more information.
You can also configure Digital Experience Manager to be run in cluster mode. If you check this option, you will then access an additional screen where you can setup your cluster configuration.
Here, you will have to specify if the node you are installing is the processing server. Remember that only one node of this type is allowed in the same cluster. Please refer to the “4.4 Clustering” section for more information.
You will also have to specify a unique server identifier (or leave the <auto> value for it to be auto-generated) and declare the IP and listening port.
You need to at least provide the password for the root user, who, like a super-user, always has all of the privileges in Digital Experience Manager. So you should choose a strong password and keep it secret.
Mail server: this field contains the SMTP host name, with advanced options.
Digital Experience Manager uses the Apache Camel framework for messaging, and the format of the mail endpoint should conform to the one, required by the Camel Mail Component (http://camel.apache.org/mail.html), i.e.:
[smtp|smtps]://[username@]host[:port][?options]
All parts except the host are optional. See use cases below. Mail administrator: the field contains a single e-mail address or multiple addresses (separated by a comma) of users who will receive system-level notifications (e.g. about errors, if this option is enabled).
Mail from: the default sender e-mail address for an e-mail message.
Here are several use cases for "Mail server" field values:
smtp.acme.com
smtp.acme.com:11019?username=myuser&password=secretpassword
smtps://smtp.gmail.com?username=acme@gmail.com&password=mypassword
or
smtp.gmail.com:587?username=acme@gmail.com&password=mypassword&mail.smtp.starttls.enable=true
smtp.acme.com?mail.debug=true
Note, please, that since Digital Experience Manager 7.0.0.2, the runtime data and main configuration files are by default located outside of the Digital Experience Manager Web application (the feature, known previously as “externalization”). This allows for more clear separation of artifacts, better customization, production deployment and maintainability throughout the project lifecycle, including hotfixes and upgrades. We will reference further in this document the runtime data folder as digital-factory-data and the configuration folder as digital-factory-config. Here is a brief overview of the folders structure in Digital Experience Manager along with the important files that will be used throughout this guide. The files and folders in the Web application (here under tomcat/webapps/ROOT) should be the same as what is on the other application servers.
<INSTALL_PATH>
|-- digital-factory-data
| |-- db
| | `-- sql
| | `-- schema
| |-- dbdata
| |-- modules
| |-- prepackagedSites
| |-- repository
| | |-- datastore
| | |-- workspaces
| | |-- indexing_configuration.xml
| | |-- indexing_configuration_version.xml
| |-- scripts
| | `-- groovy
|-- digital-factory-config
| |-- jahia
| | |-- applicationcontext-custom.xml
| | |-- jahia.properties
| | |-- jahia.node.properties
| | `-- license.xml
|-- docs
|-- icons
|-- licences
|-- logs
|-- tomcat
| |-- bin
| | |-- catalina.bat
| | |-- catalina.sh
| | |-- setenv.bat
| | |-- setenv.sh
| | |-- shutdown.bat
| | |-- shutdown.sh
| | |-- startup.bat
| | `-- startup.sh
| |-- conf
| | |-- catalina.properties
| | |-- server.xml
| | `-- web.xml
| |-- lib
| |-- logs
| | |-- jahia-errors
| | |-- jahia-threads
| | |-- jahia.log
| | |-- jahia_access.log
| | `-- jahia_profiler.log
| |-- temp
| | |-- jahia-caches
| | `-- jahia-jsps
| |-- webapps
| | `-- ROOT
| | |-- css
| | |-- engines
| | |-- errors
| | |-- gwt
| | |-- icons
| | |-- iphone
| | |-- javascript
| | |-- META-INF
| | | `-- context.xml
| | |-- tools
| | `-- WEB-INF
| | |-- classes
| | |-- etc
| | | |-- config
| | | | |-- log4j.xml
| | | | `-- urlrewrite.xml
| | | |-- repository
| | | | |-- export
| | | | |-- jackrabbit
| | | | | |-- repository.xml
| | | | |-- nodetypes
| | | | |-- rules
| | | | |-- root.xml
| | | | |-- root-mail-server.xml
| | | | |-- root-permissions.xml
| | | | |-- root-roles.xml
| | | | |-- root-user.xml
| | | | |-- site.xml
| | | | |-- template-root-mail-server.xml
| | | | |-- template-root-user.xml
| | | | `-- user.xml
| | | `-- spring
| | |-- lib
| | |-- notifications
| | `-- web.xml
| |-- work
|-- uninstaller
|-- OpenAdministration.URL
|-- OpenHome.URL
|-- start.bat
|-- start.sh
|-- stop.bat
`-- stop.sh
Here is a brief overview of the important folders:
digital-factory-config/: Contains Digital Experience Manager configuration and license file under jahia sub-folderdigital-factory-data/: Runtime Digital Experience Manager data, including database creation scripts, modules and prepackaged sites to be deployed, JCR repository folder etcdigital-factory-data/db: The database scripts to create the DB schema of Jahia and to connect to the corresponding database can be found here.digital-factory-data/repository: The Jackrabbit repository home, where the workspace configuration, and version storage is located as well as search indexes.digital-factory-data/repository/datastore: The Jackrabbit datastore folder where the binary resources will be stored.digital-factory-data/repository/index and digital-factory-data/repository/workspaces/*/index: The search indexes will be stored in these directories.digital-factory-data/modules: Modules and template-sets located in that directory will be deployed to the server on startup or whenever a file changes during runtime. Template-sets will be available in the drop-down list when you create a new virtual site, and modules will be seen in the left panel of the Studio or in the Edit mode.tomcat/: Contains pre-configured Apache Tomcat servertomcat/logs/jahia-erros: Folder where Digital Experience Manager error dumper service writes error reports into.tomcat/logs/jahia-threads: Folder where Digital Experience Manager thread dumper service writes thread dump files into.tomcat/temp/jahia-jsps: This directory will contain complied JSPs of the Digital Experience Manager modules. It will include both compiled class and Java file for each JSP. This can prove helpful in case you have an error in a template showing in the Tomcat logs, for instance: sitemap_jsp.java:984: illegal start of expression. If you want to make sure that all JSP files of the templates are recompiled after a change, you may want to delete the jahia-jsps directory and also the Standalone directory in work. Next time you access a page, Tomcat will recompile all JSP files used by the page.tomcat/webapps/ROOT/engines: This directory contains all the JSP, images and JavaScript files of Digital Experience Manager engines (Content Manager, Content Picker, Live Content Picker etc.).tomcat/webapps/ROOT/META-INF/context.xml: Database connection information. This configuration is applicable only for Apache Tomcat server.tomcat/webapps/ROOT/WEB-INF/classes: Besides some configuration files, here you will find mainly resource bundle files used to translate the Digital Experience Manager interface in other languages. There are normally at least 2 files for each language: JahiaInternalResources.properties and JahiaTypesResources.properties.tomcat/webapps/ROOT/WEB-INF/etc: The etc directory contains most of the configuration files of Jahia. The config sub-directory contains several configuration files (log4j.xml, seo-urlrewrite.xml, etc.). The repository directory contains the configuration files for Jackrabbit repository. The spring directory may contain custom Spring bean definition files, but is empty by default. The internal Spring files are located inside jahia-impl-*.jar file.start.*/stop.*: The Digital Experience Manager start and stop scripts.This applies only if you want to discover Digital Experience Manager 7.1, using the prepackaged demonstration site. It assumes that you have installed Digital Experience Manager using “Discovery install” or selecting “Development + Modules/JahiApps/Demos” Mode, so that the example templates and the modules they require have been automatically deployed.
This applies when you install your production server, and assumes that you have installed Digital Experience Manager in Production Mode.
Before being able to create your first website, you will have to deploy your custom set of templates and modules. But during the development process, you may have used some Digital Experience Manager standard modules, automatically available on your installation. Notice that most of those modules were available because you installed your development server using the development mode. As your production server uses the production mode, only the core modules will be available. So, you also need to deploy yourself the standard modules you want to use.
During the life-cycle of a project you will need different types of environments:
Development environment - each of your developers will have their own environment. Those developer environments are normally much lighter than the one needed for production. Your developers can either use the integrated DBMS (Apache Derby) or use another DBMS (MySQL, Microsoft SQL Server, PostgreSQL or Oracle).Integration environment - this environment will help you integrate the work of all your developers on the same platform and prepare the site(s) you are going to deploy in production.Production environment - this one is the last step in the development life-cycle of your project.In order to deploy Digital Experience Manager into an existing Apache Tomcat 8.0.x installation a number of required steps has to be completed.
Next subsections describe all those steps, which are all mandatory.
The installation procedure for an existing Apache Tomcat 8 is as follows:
- Launch the Installer.
Custom Install (advanced) installation type.Digital Experience Manager + Jahia Core Content Platform pack, unselecting the Add Apache Tomcat oneApache Tomcat 8.0.x as the target application serverOnce the Installer is finished in your installation directory you should find among others the tomcat folder and, if the locations of runtime data and configuration folders were not changed during the installation, the digital-factory-config and digital-factory-data folders.
Further, it is assumed that your target Apache Tomcat server is installed in the <tomcat> folder and <install-dir> will reference the folder, where you’ve installed Digital Experience Manager into using the installer.
common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar","/opt/DigitalExperienceManager-7/digital-factory-config"
If your digital-factory-config folder is inside the installation folder, you could use the path, relative to catalina.home, i.e.:
common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar","${catalina.home}/../digital-factory-config"
5. Please, note, if you decide to move the digital-factory-data folder to other location, the jahiaVarDiskPath value in the digital-factory-config/jahia/jahia.properties file should be adjusted to reflect its new path.
6. Adjust the JVM and connector options appropriately (see next sections).
The default JVM options of the Apache Tomcat have to be adjusted to reflect the Digital Experience Manager requirements. We recommend creating a setenv.bat (Windows) or setenv.sh (non-Windows OS) script in the <tomcat>/bin folder to put those options. An example of the <tomcat>/bin/setenv.bat for Windows OS could be:
rem ------------------------------------------------------------------
rem Digital Experience Manager settings
rem ------------------------------------------------------------------
set CATALINA_OPTS=%CATALINA_OPTS% -server -Dsun.io.useCanonCaches=false -verbose:gc -XX:+HeapDumpOnOutOfMemoryError -XX:+PrintConcurrentLocks -Djava.net.preferIPv4Stack=true -Xms2048m -Xmx2048m -XX:MaxPermSize=384m
set CATALINA_OPTS=%CATALINA_OPTS% -Dderby.system.home="%CATALINA_HOME%\..\digital-factory-data\dbdata"
In a similar way, the <tomcat>/bin/setenv.sh script for a non-Windows OS can look like:
#!/bin/sh
# --------------------------------------------------------------------
# Digital Experience Manager settings
# --------------------------------------------------------------------
CATALINA_OPTS="$CATALINA_OPTS -server -Djava.awt.headless=true -verbose:gc -XX:+HeapDumpOnOutOfMemoryError -XX:+PrintConcurrentLocks -Djava.net.preferIPv4Stack=true -Xms2048m -Xmx2048m -XX:MaxPermSize=384m"
CATALINA_OPTS="$CATALINA_OPTS -Dderby.system.home=$CATALINA_HOME/../digital-factory-data/dbdata"
export CATALINA_OPTS
export CATALINA_PID=$CATALINA_HOME/temp/tomcat.pid
The JVM heap sizes (-Xms and -Xmx) as well as the permanent generation space size (-XX:MaxPermSize) should be adjusted according to your needs. Note that the minimal value of the -Xmx value, required by Digital Experience Manager is 2048m. If you have chosen Apache Derby as the target DBMS server during the installation, the value of the -Dderby.system.home in the setenv.bat/setenv.sh script should point to your digital-factory-data/dbdata folder.
The following configuration for the HTTP and AJP connectors (configured in the <tomcat>/conf/server.xml file) is recommended[1], which includes maximum threads and accept count configuration, compression of the response content etc.:
<Connector port="8080"
protocol="HTTP/1.1"
redirectPort="8443"
maxThreads="300" acceptCount="100"
compression="on"
compressableMimeType="text/plain,text/html,text/xml,text/css,text/javascript,application/x-javascript,application/javascript" />
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
connectionTimeout="20000" keepAliveTimeout="300000" maxThreads="300" />
The installation and configuration steps for IBM WebSphere are covered in a separate “WebSphere 8.5.5 Installation Guide” which can be found on our documentation Web page: https://www.jahia.com/extranet/digital-experience-manager/previous-version-7-releases/digital-factory-70/digital-factory-70-documentation
In order to deploy Digital Experience Manager into an existing Red Hat JBoss EAP 6.x installation a number of required steps has to be completed. Note, please, here we assume the deployment into a JBoss EAP instance, running in a standalone mode with a default configuration profile. Next subsections describe all those steps, which are all mandatory.
The installation procedure for an existing JBoss server is as follows:
Custom Install (advanced) installation type.Digital Experience Manager + Jahia Core Content Platform pack, unselecting the Add Apache Tomcat oneRed Hat JBoss EAP 6.x as the target application serverOnce the Installer is finished in your installation directory you should find among others the jboss folder and, if the location of runtime data folder was not changed during the installation, the digital-factory-data folder.
Further, it is assumed that your target Red Hat JBoss server is installed in the <jboss> folder and <install-dir> will reference the folder, where you’ve installed Digital Experience Manager into using the installer.
The default JVM options in the JBoss’ startup script (<jboss>/bin/standalone.conf.bat or <jboss>/bin/standalone.conf) should be adjusted to use server JVM ("-server" option), have at least 1280 MB heap size (-Xms1280m) and at least 256 MB as a limit for the permanent generation heap size (-XX:MaxPermSize=256M), if applicable, also adding other tuning options.
This can be done by adjusting the corresponding line in your <jboss>/bin/standalone.conf.bat file (Windows OS):
set "JAVA_OPTS=-server –Xms2G –Xmx2G -XX:MaxPermSize=384M"
or in the <jboss>/bin/standalone.conf file (non-Windows OS) – here we use larger values as an example:
JAVA_OPTS="-server –Xms4G –Xmx4G -XX:MaxPermSize=512M"
The following lines needs to be added to:
set "JAVA_OPTS=%JAVA_OPTS% -Djava.io.tmpdir=%JBOSS_HOME%\standalone\tmp"
set "JAVA_OPTS=%JAVA_OPTS% -Dderby.system.home=c:\DigitalExperienceManager-7\digital-factory-data\dbdata"
set "JAVA_OPTS=%JAVA_OPTS% -verbose:gc -XX:+HeapDumpOnOutOfMemoryError -XX:+PrintConcurrentLocks"
And for non-Windows OS:
JAVA_OPTS="$JAVA_OPTS -Djava.io.tmpdir=$JBOSS_HOME/standalone/tmp"
JAVA_OPTS="$JAVA_OPTS -Dderby.system.home=/opt/DigitalExperienceManager-7/digital-factory-data/dbdata"
JAVA_OPTS="$JAVA_OPTS -verbose:gc -XX:+HeapDumpOnOutOfMemoryError -XX:+PrintConcurrentLocks"
The next steps have to be performed on a started JBoss server instance. Please, start your JBoss server instance from <jboss>/bin folder by using: On Windows OS:
standalone.bat -b 0.0.0.0
On non-Windows OS:
./standalone.sh -b 0.0.0.0
The 0.0.0.0 value after -b switch means that JBoss will be bound to all available network interfaces. You could use particular one instead, e.g. 192.168.1.101. When omitted the JBoss will bind to the loopback address (127.0.0.1) only. After the JBoss instance is started continue with the next steps.
When JBoss is running you could create a server management user (for accessing JBoss Management UI) by using <jboss>\bin\add-user.bat (Windows platform) or <jboss>/bin/add-user.sh (non-Windows platform). Provide the required information to add the user. Alternatively you could add a user in a non-interactive mode: On Windows OS:
add-user.bat -u manager -p manager_123
On non-Windows OS:
./add-user.sh -u manager -p manager_123
For configuring JDBC driver, DB datasource and also deactivating default JBoss ROOT application (in case Digital Experience Manager will use ROOT Web application context), the following script has to be executed against running JBoss server instance from <jboss>/bin folder: Windows OS:
jboss-cli.bat --file=jahia-config.cli
Non-Windows OS:
./jboss-cli.sh --file=jahia-config.cli
The configuration is ready now and we can deploy and start the Digital Experience Manager. To trigger the deployment, you need to delete the marker file:
<jboss>/standalone/deployments/digitalexperiencemanager.ear.skipdeploy
This will trigger the deployment and startup of the Digital Experience Manager Web application.
Modules are extensions to Digital Experience Manager, which are packaged as JAR files and can be deployed on a server. A module can contain different kinds of resources: JSPs, definitions in CND files, CSS and images, resource bundles, XML or ZIP import files, rules definitions, libraries, Spring files etc. Modules are deployed by using the built-in module management screen in Server Settings or by dropping them into the digital-factory-data/modules folder.
In cluster environments, we must differentiate between cold deployment and hot deployment of modules.
Cold deployment means that modules are being deployed when the cluster is completely shut down. Simply copy the jar file of the module on each cluster node in the digital-factory-data/modules folder.
For hot deployments of modules (when the cluster is up and running), installation on different cluster nodes should be done in sequence. Modules will be available only when they have been deployed on the processing server. The main difference with previous versions is that, thanks to OSGi, the servers do not need to be restarted anymore even if the module(s) contains classes or libraries.
To cold undeploy modules, just remove them from the digital-factory-data/modules folder while all cluster nodes are stopped.
You can hot undeploy your modules by removing them from digital-factory-data/modules folder of all your nodes. Alternatively, you can undeploy the modules from the Administration > Server settings > System components > Modules screen. The advantage of doing so over the manual approach of removing the module jar is that Digital Experience Manager will inform you of any modules that might depend on the one you're trying to undeploy and will first ask you to disable the module from all the sites that might be using it. Either way, this procedure only affects the current cluster node and does not propagate the changes to the other nodes. This means that you will need to repeat the procedure for every node of your cluster. This also means that some nodes will still be able to use the modules while they may be unavailable on the nodes where they have already been undeployed using the administration screen.
Once the JAR file has been deployed, modules become available. They can then be deployed to Web projects via module management screen in Server Settings or via Studio. If a new version of the module is uploaded on the server, it will be automatically deployed on all sites that are currently using it. All updates will be immediately available in the site.