How to install CQ5 with an Application Server

The following sections detail how to install CQ5 in conjunction with various application servers:

A generic overview is also given for general usage and information:

Generic Procedures

Note

This documentation explains how to install CQ 5.3 on a 3rd party application server, if you would like to install CQ5.2.X on an application server then please go here

WebSphere v6.1

To install CQ5 with the WebSphere 6.1 server, you need to complete the following tasks:

Install WebSphere and disable basic authentication.
Configure the server local on WebSphere.
Unpack CQ.
Install the author instance.
Install the publish instance.
Set up replication.

Install WebSphere 6.1 and disable basic authentication

To install WebSphere and disable basic authentication:

Install WebSphere 6.1.
Login to the IBM web console at http://localhost:9060/ibm/console. (Port number 9060 is the default port number.)
Click Application Servers, then server1, then Web services: Default bindings for Web services security, and then Login mappings.
Select the BasicAuth checkbox and then click Delete.
Save your changes.

Configure the Server Locale

When you deploy CQ5 with WebSphere v6.1 and your system locale is using a UTF-8 encoding, some SDK tools may throw a sun.io.MalformedInputException. You will know whether your system uses UTF-8 encoding if locale-specific environment variables like LANG and LC_ALL end with .UTF-8.

To workaround this issue, you must set the server locale to en_US before installing CQ.

To configure the server locale on Microsoft Windows:

Open the Control Panel.
Open Regional and Languages Options.
In the Regional Options tab, for Standards and formats select English(United States).

To configure the server locale on Linux or Unix:

Set the environment variable LANG to en_US.

Unpack CQ

To unpack CQ and create the correct folders:

Start the CQ Quickstart jar with the option -unpack by typing, for example: java -jar quickstart.jar -unpack. This creates a folder <cq-installation-dir>crx quickstart containing the files and folders used for installation, without starting the installation.
Rename the newly created folder to crx-quickstart-author.
Copy this folder and rename it again to crx-quickstart-publish (you should now have two folders: crx-quickstart-author and crx-quickstart-publish).
Copy the cq-shared-libs-5.3.0.jar file from quickstart-author/server/lib/common to the shared library folder of WebSphere.

Note

Unpacking must be performed from the command line. If you open the jar file directly, you activate the Quickstart installation and activate the server.

Install the Author Instance

To install the author instance, we must do the following:

Adjust JNDI and home paths of the web applications.
Set the jdkSourceLevel.
Add sling properties.
Adjust the JNDI name for the CRX sling client repository.
Install the content package.

Detailed instructions are provided in the following sections.

Adjust JNDI and home paths of the web applications

To adjust JNDI and home paths of the web applications:

Unpack the crx-launchpad.war and crx-explorer_crx.war files located in the <cq-installation-dir>/crx-quickstart-author/server/webapps folder.
- In Windows, change the .war extensions to .zip and extract all files to directories: crx-launchpad.zip to crx-launchpad and crx-explorer_crx.zip to crx-explorer_crx
- In Linux, type the following commands in a terminal from the directory containing the war files:
  mkdir crx-explorer_crx
  cd crx-explorer_crx
  jar -xvf ../crx-explorer_crx.war
  mkdir crx-launchpad
  cd crx-launchpad
  jar -xvf ../crx-launchpad.war
Edit the web.xml file from the unpacked crx-launchpad.war's WEB-INF subdirectory. In web.xml:
1. Change repositoryName from crx to crx-author.
2. Change sling.home from crx-quickstart/launchpad to crx-quickstart-author/launchpad.
Edit the web.xml from the unpacked crx-explorer_crx.war's WEB-INF subdirectory. In web.xml:
1. Change the repository-home from crx-quickstart/repository to crx-quickstart-author/repository (Repository Servlet).
2. Change the repository-name from crx to crx-author (Repository Servlet).
3. Change the repository-name from virtual-crx to virtual-crx-author (JCR Explorer Servlet).
4. Change the explorer-home from crx-quickstart/repository to crx-quickstart-author/repository (JCR Explorer Servlet).
5. Change the home parameter from crx-quickstart to crx-quickstart-author (WebDav Server Servlet).
In the same directory, edit the repository-template.xml file:
1. Add the defaultVirtualRepository parameter (shown below) to the VirtualRepositoryModule configuration:
  <Module class="com.day.crx.mount.virtual.VirtualRepositoryModule">
  <param name="defaultVirtualRepository" value="virtual-crx-author" />
  <param name="configWspName" value="crx.default"/>
  <param name="configPath" value="/etc/virtual-repositories"/>
  <param name
  </Module>
In the same directory, edit the log4j.xml by changing the File parameter of the error and transaction log from crx-quickstart/.... to crx-quickstart-author/....
Repackage the crx-explorer_crx.war and crx-launchpad.war files.
- In Windows, open the crx-explorer_crx directory, select all contained files then select Send To -> Compress (zipped) Folder. Now you have created a zip file in the crx-explorer_crx directory. Rename the generated zip file to crx-explorer_crx.war. Repeat the same process for the crx-launchpad directory.
- In Linux, type the following in a terminal from the directory containing the war files:
  jar -cvf crx-launchpad.war -C crx-launchpad/ .
  jar -cvf crx-explorer_crx.war -C crx-explorer_crx/ .
Rename crx-explorer_crx.war to crx-author.war
Rename crx-launchpad.war to author.war
Deploy both war applications inside the WebSphere console at http://localhost:9060/ibm/console.

Configure the Default JDK

WebSphere v6.1 uses JDK 1.5. By default the SAMLv2 JSP JDK source level uses JDK 1.3. As the SAMLv2 sample configuration uses the JDK 1.5 syntax, running it with the default source level will not work. The following steps should be used to configure the source level as 1.5:

Stop WebSphere.
Within the deployed crx-explorer_crx.war, edit ibm-web-ext.xmi and add the following configuration parameter to specify the JSP engine:
<jspAttributes xmi:id="JSPAttribute_1225281520121" name="jdkSourceLevel" value="15"/>
Repeat for crx-launchpad.war. The default configuration directory for the web module is as follows:
<WAS_ROOT>\profiles\profilename\config\cells\cellname\applications\enterpriseappname\ deployments\deployedname\webmodulename\WEB-INF\
Start WebSphere.

Add sling properties

To add sling properties:

Stop the author web application.
Edit the <cq-installation-dir>/crx-quickstart-author/launchpad/sling.properties and set the following two properties:
- sling.jcrinstall.folder.name.regexp=.*/(install|config)(.author)?$
- sling.run.modes = author
Start the author web application.

Adjust the JNDI name for the CRX sling client

To adjust the JNDI name for the CRX sling client:

Open the felix console: http://localhost:9080/author/system/console/configMgr.
Select the CRX sling client repository and change the repository name from virtual-crx to virtual-crx-author.

Install the content package

To install the content package:

Open http://localhost:9080/crx-author/ or the location of your CRX installation.
Enter the license key.
Open the package manager.
Upload and install the cq-content-5.3.jar file from the <cq-installation-dir>/quickstart-author/repository/install/ folder
Open the content explorer and edit the virtual repository from virtual-crx to virtual-crx-author below /etc/virtual-repository.

Install the Publish Instance

To install the publish instance, follow all the steps described in Installing the Author Instance except replace author with publish.

Enable Replication for Author instances of CQ5

For an author instance of CQ5 you must configure it to start in author run mode so that you can perform replications. To enable replication:

Edit the default agent on the author at point to http://localhost:9080/publish/bin/receive.

WebLogic v10.3

To install WebLogic v10.3, you need to perform the following steps:

Install the WebLogic server and create a domain.
Prepare the WebLogic server by configuring the server locale, enabling basic authentication headers, and optionally increasing the max heap size.
Unpack CQ and install it.
Install your content packages.
Deploy CRXDE Lite.
Modify WebLogic optimization so CQ login succeeds.
Enable replication for author instances in CQ.

Install WebLogic Server

To install the WebLogic server and create a domain:

Download the WebLogic server software and install it (Installation folder is referred to as $WebLogicInstallDir).
Create a domain, for example, MyDomain. To create the domain, go to Oracle Weblogic, then WebLogic Server, then Tools, then Configuration Wizard. The domain is created in the $WebLogicInstallDir/user_projects/domains/myDomain folder (referred to as $MyDomain in the following sections).

Prepare the WebLogic Server

You need to perform several steps to prepare the WebLogic server for CQ Deployment including setting the server locale, enabling basic authentication headers, and optionally increasing the max heap size.

Configure the Server Locale

When you deploy CQ5 with WebLogic 10.3 you must have the server locale set to en_US to avoid errors such as:

java.lang.IllegalArgumentException: Bad date header: 'Wed, 12 Nov 2008 16:34:28 GMT'

These can occur when, for example, requesting a resource such as /libs/widgets/0.gif.

To configure the server locale on Microsoft Windows:

Open the Control Panel.
Open Regional and Languages Options.
In the Regional Options tab, for Standards and formats select English(United States).

To configure the server locale on Linux or Unix:

Set the environment variable LANG to en_US.

Enable Basic Authentication Headers

To enable out-of-the-box authentication of users in CQ5, authentication by the application server must be switched off:

Open $WebLogicInstallDir/user_projects/domains/$MyDomain/config/config.xml.
Locate the element <security-configuration>.
Add the following child element to the end of it: <enforce-valid-basic-auth-credentials> false </enforce-valid-basic-auth-credentials>
If you had already started WebLogic then you need to restart it.

Create folders for holding the web applications deployment plans:

Useful if you want to change the context paths of the web applications:

Create directories $MyDomain/packages/crx-explorer and $MyDomain/packages/crx-launchpad and $MyDomain/packages/crxde to hold the war files and the deployment plan files.
Copy the file crx-launchpad.jar to $MyDomain/packages/crx-launchpad and crx-explorer_crx.war to $MyDomain/packags/crx-explorer and the crxde.war file to $MyDomain/packages/crxde.

Increasing max heap size

To increase the max heap size (optional):

Navigate to the $WebLogicInstallDir/user_projects/domains/MyDomain/bin folder
Open and edit setDomainEnv.cmd (setDomainEnv.sh on Linux).
Search for MEM_ARGS (and MEM_MAX_PERM_SIZE, if needed) and set the desired values.
Restart the server.

Install CQ5

Unpack the installation files of the CQ5 Quickstart into a directory (without starting the server); the installation directory will be referred to as <cq-installation-dir>:
1. Start the CQ5 Quickstart jar with the option -unpack; for example:
  
  java -jar cq-wcm-quickstart-5.3.jar -unpack
  
  This will create a folder <cq-installation-dir>\crx-quickstart containing the files and folders used for installation, without actually starting the installation.
This must be done from the command line. If you open the jar file directly you will activate the Quickstart installation and start the server.
Copy the cq-shared-libs-5.3.X.jar file from <cq-installation-dir>\crx-quickstarts/server/lib/commons to the application server shared libraries directory
Restart WebLogic.
Deploy the following web applications; they can be found in <cq-installation-dir>\crx-quickstart\server\webapps or in the $MyDomain\packages\ folder:
1. CRX webapp; crx-explorer_crx.war.
  
  For example, deploy with the context path /crx.
2. Launchpad webapp; crx-launchpad.war.
  
  For example, deploy with the context path /launchpad.
Start the two applications.
Register your CRX license:
1. Access your CRX installation:
  
  http://<server>:<port>/<context-path>
  
  for example: http://<server>:<port>/crx
2. Click the red warning message - Click here... (the message is a link).
3. Enter your license key.

Install your Content Packages

Go to /console and stop the crx-launchpad web application and wait until it is stopped.
Log in to /crx-explorer_crx, navigate to the Package Manager and upload and install the cq-content-5.3.X.jar file residing in <cq-installation-dir>/crx-quickstart/repository/install folder of the CQ5.3 unpack folder.
Configure run mode by doing the following:
1. Stop the crx-launchpad web application in the WebLogic web console.
2. Edit the sling.properties file residing in $MyDomain/crx-quickstart/launchpad folder and add the following properties:For Author Runmode: sling.jcrinstall.folder.name.regexp=.*/(install|config)(.author)?$ sling.run.modes = authorFor Publish Runmode: sling.jcrinstall.folder.name.regexp=.*/(install|config)(.publish)?$sling.run.modes = publish
Start crx-launchpad web application.

Deploy CRXDE Lite

To use CRXDE Lite with WebLogic 10, you need to adapt the context path of crx-launchpad and crx-explorer_crx by editing the web.xml file of the CRXDE Lite web application as follows:

<context-param>
        <param-name>repository.ctx.path</param-name>
        <param-value>/crx-explorer_crx</param-value>
    </context-param>
    
    <context-param>
        <param-name>launchpad.ctx.path</param-name>
        <param-value>/crx-launchpad</param-value>
    </context-param>

Note

If you have changed the context paths of the two other web applications, insert those into the context-param section. Default paths are /crx-explorer_crx and /launchpad.

Modify WebLogic optimization

By default WebLogic optimization is enabled, which does not allow you to log into the CQ Websites page and returns a ClassNotFoundException error although the class can be found in the stacktrace.

To modify the WebLogic optimization so CQ login succeeds:

Open $MyDomain/packages/crx-launchpad/plan/WEB-INF/weblogic.xml.
Add the following line as child to <container-description>: <optimistic-serialization>true</optimistic-serialization>
Perform the same change for crx-explorer.
Restart both web applications.
Log into the CQ Websites page to ensure everything works.

Tomcat v6

After installing Tomcat v6 you:

Configure Tomcat access accounts

Tomcat enables neither admin nor manager access at installation.

Therefore you have to manually edit tomcat-users.xml to allow access for these accounts:

Navigate to the Tomcat configuration folder.
Edit tomcat-users.xml to include access for admin and manager. The configuration should look similar to the following example:

<?xml version='1.0' encoding='utf-8'?> <tomcat-users> <role rolename="manager"/> <role rolename="tomcat"/> <role rolename="admin"/> <role rolename="role1"/> <user username="both" password="tomcat" roles="tomcat,role1"/> <user username="tomcat" password="tomcat" roles="tomcat"/> <user username="admin" password="admin" roles="admin,manager"/> <user username="role1" password="tomcat" roles="role1"/> </tomcat-users>

Install CQ5

Unpack the installation files of the CQ5 Quickstart into a directory (without starting the server); the installation directory will be referred to as <cq-installation-dir>:
1. Start the CQ5 Quickstart jar with the option -unpack; for example:
  
  java -jar cq-wcm-quickstart-5.3.jar -unpack
  
  This will create a folder <cq-installation-dir>/crx-quickstart containing the files and folders used for installation, without actually starting the installation.
This must be done from the command line. If you open the jar file directly you will activate the Quickstart installation and start the server.
Copy the following jar files to the application server folder holding shared libraries:
1. <cq-installation-dir>/crx-quickstart/server/common/cq-shared-5.3.X.jar
Restart Tomcat.
Deploy the following web applications; they can be found in <cq-installation-dir>/crx-quickstart/server/webapps (see here for info on tomcat application deployment):
1. CRX webapp; crx-explorer_crx.war.
  
  For example, deploy with the context path /crx by renaming the crx-explorer_crx.war file to crx.war then copying it to $CATALINA_HOME/webapps
2. Launchpad webapp; crx-launchpad.war.
  
  For example, deploy with the context path /launchpad by renaming the crx-launchpad.war file to launchpad.war then copying it to $CATALINA_HOME/webapps.
Start the two applications.
Register your CRX license:
1. Access your CRX installation:
  
  http://<server>:<port>/<context-path>/index.jsp
  
  for example: http://<server>:<port>/crx/index.jsp
2. Click the red warning message - Click here... (the message is a link).
3. Enter your license key.

Install your Content Packages

Stop CQ5.
Edit the workspace configuration file:
1. Open the following file for edit:
  
  <cq-installation-dir>/crx-quickstart/repository/workspaces/workspace.xml
2. Scroll down to the <SearchIndex> parameter section.
3. Add <param name="indexingConfiguration" value=""/> to the <SearchIndex> parameter section.
Start CQ5.
Access the CRX main console.
Log in to the crx.default workspace as admin.
Upload and install the CQ5 package from <cq-installation-dir>/crx-quickstart/repository/install:

1. CQ5 Content Package: cq-content-5.3.jar

2. CQ5 Documentation Package (optional): cq-documentation-5.3.zip

Enable Replication for Author instances of CQ5

For an author instance of CQ5 you must configure it to start in author run mode so that you can perform replications.

Open the file: <cq-installation-dir>\crx-quickstart\launchpad\sling.properties for edit.
Add the following two properties to the file:
sling.jcrinstall.folder.name.regexp = .*/(install|config)(.author)?$ sling.run.modes = author
Restart the crx-launchpad web application.

JBoss v4

Install JBoss

Follow the JBoss documentation on how to install a default instance of JBoss v4 Application Server

Install CQ5

Unpack the installation files of the CQ5 Quickstart into a directory (without starting the server); the installation directory is referred to as <cq-installation-dir>:
1. Start the CQ5 Quickstart jar with the option -unpack; for example:
  
  java -jar cq-wcm-quickstart-5.3.jar -unpack
  
  This creates a folder <cq-installation-dir>/crx-quickstart containing the files and folders used for installation, without actually starting the installation.
This must be done from the command line. If you open the jar file directly you will activate the Quickstart installation and start the server.
Copy the following jar files to the application server folder shared libraries directory ($JBOSS_HOME/server/default/lib):
1. <cq-installation-dir>/crx-quickstart/server/lib/common/cq-shared-5.3.X.jar
Restart JBoss.
Unpack the crx-launchpad.war file located in the <cq-installation-dir>/crx-quickstart-author/server/webapps folder.
- In Windows, rename the .war extension to .zip and extract all files to directory. Extract crx-explorer_crx.zip to a directory named crx-explorer_crx
- In Linux, type the following commands in a terminal from the directory containing the war file:
  mkdir crx-explorer_crx
  cd crx-explorer_crx
  jar -xvf ../crx-explorer_crx.war
In the WEB-INF directory, open log4j.xml.
Remove or comment the line <appender-ref ref="console"/> which is in the Loggers section of the file and save your changes and exit the file. This disables console logging in the CRX web application.
In the WEB-INF folder, navigate to the lib folder and delete the following files:
- jcr-2.0.jar
- jackrabbit-api-2.0.0.jar
- day-commons-naming-1.1.2.jar
- crx-api-2.0.0.jar
- log4j-1.2.14.jar
- xml-apis-1.3.04.jar
- xercesImpl-2.9.0.jar
Repackage the crx-explorer_crx.war file.
- In Windows, open the crx-explorer_crx directory, select all files in the crx-explorer_crx directory then select Send To -> Compress (zipped) Folder. Now you have created a zip file in the crx-explorer_crx directory. Rename the generated zip file to crx-explorer_crx.war.
- In Linux, type the following in a terminal from the directory containing the war files:
  jar -cvf crx-launchpad.war -C crx-launchpad/ .
Deploy the following web applications; they can be found in <cq-installation-dir>/crx-quickstart/server/webapps:
1. CRX webapp; crx-explorer_crx.war.
  
  For example, deploy with the context path /crx by renaming the crx-explorer_crx.war file to crx.war then copying it to
  $JBOSS_HOME/server/default/deploy
2. Launchpad webapp; crx-launchpad.war.
  
  For example, deploy with the context path /launchpad by renaming the crx-launchpad.war file to launchpad.war then copying it to $JBOSS_HOME/server/default/deploy

JBoss supports Hot Deployment, if hot deployment is enabled then you can simply copy the two war files to $JBOSS_HOME/server/default/deploy. If hot deployment is disabled then you will need to restart JBoss after copying the files to the deploy directory.

Start the two applications.
Register your CRX license:
1. Access your CRX installation:
  
  http://<server>:<port>/<crx-context-path>/index.jsp
  
  for example if crx-explorer_crx.war was deployed as crx.war: http://<server>:<port>/crx/index.jsp
2. Click the red warning message - Click here... (the message is a link).
3. Enter your license key.

Note

The procedure above uses the default configuration for the crx and launchpad web application data directories. This means that your data directory "crx-quickstart" will be created under the JBoss working directory (usually $JBOSS_HOME/bin). Optionally, you can reconfigure the paths of where crx-explorer_crx.war and crx-launchpad.war store their data.

You can do so by editing the paths in the following files (to do so you will have to unpackage edit and repackage both the crx-explorer_crx.war and the crx-launchpad.war):

Edit the web.xml file from the unpacked crx-launchpad.war's WEB-INF subdirectory.

In web.xml:

Change sling.home from crx-quickstart/launchpad to the path you would like to store the Apache Felix data.

Edit the web.xml from the unpacked crx-explorer_crx.war's WEB-INF subdirectory.

In web.xml:

Change the repository-home from crx-quickstart/repository to the path where you want to store the CRX repository data (Repository Servlet).
Change the explorer-home from crx-quickstart/repository to crx-quickstart-author/repository (JCR Explorer Servlet).
Change the home parameter from crx-quickstart to crx-quickstart-author (WebDav Server Servlet).

Caution

Regarding the note above, it is not recommended to configure these data paths to point to a network share directory such as an NFS or Windows Share (CIFS). If you would like to store data on a network share then please see the CRX clustering documentation for how you can configure the CRX shared data paths (the clustering documentation also applies to single crx instances).

Configure the JBoss Server Login Module

By default JBoss' default login configuration attempts to authenticate users against a list of users in the users.properties file. You must configure JBoss as follows to let login attempts by unknown users to pass to the web application (CRX Explorer). The web application will then process authentication by itself.

Open the file for editing:

$JBOSS_HOME\server\default\conf\login-config.xml
Find the and delete the application-policy name="other" section (it can be found at the bottom of the login-config.xml file):
<application-policy name="other">
...
</application-policy>

Install your Content Packages

Once you have installed CQ5 you will want to install content packages.

Stop CQ5.
Edit the workspace configuration file:
1. Open the following file for edit:
  
  <cq-installation-dir>/crx-quickstart/repository/workspaces/workspace.xml
2. Scroll down to the <SearchIndex> parameter section.
3. Add <param name="indexingConfiguration" value=""/> to the <SearchIndex> parameter section.
Start CQ5.
Access the CRX main console:

http://<server>:<port>/crx/index.jsp
Navigate to the Package Manager in CRX.
Upload and install the CQ5 package from <cq-installation-dir>/crx-quickstart/repository/install:

1. CQ5 Content Package: cq-content-5.3.jar

2. CQ5 Documentation Package (optional): cq-documentation-5.3.zip
Restart JBoss.

Note

The data directories of your installation now can be found under the working directory of your JBoss Application Server (Usually this directory is $JBOSS_HOME/bin/crx-quickstart):
CRX Repository Data: crx-quickstart/repository
Launchpad / Apache Felix Data: crx-quickstart/launchpad
Logs: crx-quickstart/logs, crx-quickstart/launchpad/logs

Enable Replication for Author instances of CQ5

For an author instance of CQ5 you must configure it to start in author run mode so that you can perform replications.

Open the file: <cq-installation-dir>\crx-quickstart\launchpad\sling.properties for edit.
Add the following two properties to the file:
sling.jcrinstall.folder.name.regexp = .*/(install|config)(.author)?$ sling.run.modes = author
Restart the crx-launchpad web application.

Generic Procedures

After installing the appropriate web application server you:

Generic Installation Procedure

This section provides generic information about installing CQ5 with an application server.

Unpack the installation files of the CQ5 Quickstart into a directory (without starting the server); the installation directory will be referred to as <cq-installation-dir>:
1. Start the CQ5 Quickstart jar with the option -unpack; for example:
  
  java -jar cq-wcm-quickstart-5.3.jar -unpack
  
  This will create a folder <cq-installation-dir>/crx-quickstart containing the files and folders used for installation, without actually starting the installation.
This must be done from the command line. If you open the jar file directly you will activate the Quickstart installation and start the server.
Copy the following jar files to the application server folder holding shared libraries:
1. <cq-installation-dir>c/rx-quickstart/server/lib/common/cq-shared-5.3.X.jar
Restart your web application server.
Deploy the following web applications; they can be found in <cq-installation-dir>/crx-quickstart/server/webapps:
1. CRX webapp; crx-explorer_crx.war.
  
  For example, deploy with the context path /crx.
2. Launchpad webapp; crx-launchpad.war.
  
  For example, deploy with the context path /launchpad.
Start the two applications.
Register your CRX license:
1. Access your CRX installation:
  
  http://<server>:<port>/<context-path>/index.jsp
  
  for example if the crx-explorer_crx.war was deployed with the context /crx: http://<server>:<port>/crx/index.jsp
2. Click the red warning message - Click here... (the message is a link).
3. Enter your license key.

Install Content Packages

Once you have installed CQ5 you will want to install content packages.

Stop CQ5.
Edit the workspace configuration file:
1. Open the following file for edit:
  
  <cq-installation-dir>\crx-quickstart\repository\workspaces\workspace.xml
2. Scroll down to the <SearchIndex> parameter section.
3. Add <param name="indexingConfiguration" value=""/> to the <SearchIndex> parameter section.
Start CQ5.
Access the CRX main console.

http://<server>:<port>/crx/index.jsp
Log in to the crx.default workspace as admin.
Navigate to the Package Manager in CRX.
Upload and install the CQ5 package from <cq-installation-dir>/crx-quickstart/repository/install:

1. CQ5 Content Package: cq-content-5.3.jar

2. CQ5 Documentation Package (optional): cq-documentation-5.3.zip

Enable Replication for Author instances of CQ5

For an author instance of CQ5 you must configure it to start in author run mode so that you can perform replications.

Open the file: <cq-installation-dir>\crx-quickstart\launchpad\sling.properties for edit.
Add the following two properties to the file:
sling.jcrinstall.folder.name.regexp = .*/(install|config)(.author)?$ sling.run.modes = author
Restart the crx-launchpad web application.

Your comments are welcome!

Did you notice a way we could improve the documentation on this page? Is something unclear or insufficiently explained? Please leave your comments below and we will make the appropriate changes. Comments that have been addressed, by improving the documentation accordingly, will then be removed.

No comments yet

In order to post a comment, you need to sign-in.

Email address *

Do you have a day.com password?

Yes, I have a day.com password:

No, help me create an account:

First Name *

Last Name *

Job Title

Company *

Phone Number *

Password *

Confirm Password

Forgotten your password? Reset the password here.

Note: Customers with DayCare user accounts need to create a new account for use on day.com.