Installing CQ5 with an Application Server

This section tells you how to install CQ with an application server. Consult the Supported Platforms section to see the specific support levels provided for the individual application servers.

The generic procedure details the actions common to the installation procedures for:

After installation you can install further content packages if required.

Consult the appropriate application server documentation for more information on installing web applications.

Note

The naming convention used here for the CQ quickstart file is:
    cq-wcm-quickstart-<version>.jar.

For example, cq-wcm-quickstart-5.4.jar, where 5.4 would be the <version>.

Be sure to substitute the version of your edition of CQ wherever appropriate.

Generic Procedures

Generic Procedure for Installing CQ with an Application Server

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

The procedure (with minor deviations) is used for all web servers and is referenced from the instructions provided for the individual web servers.

After having installed the application server, install CQ as follows:

  1. Open the directory where you want to install CQ. This will be known as <cq-installation-dir>. Copy the installation jar file into this directory.

  2. Unpack the quickstart jar file without starting the installation (or server).

    To do this start the CQ Quickstart jar with the option -unpack by typing, for example:

    java -jar cq-wcm-quickstart-<version>.jar -unpack

    This creates a folder <cq-installation-dir>/crx-quickstart containing the files and folders used for installation.

    Note

    You must start CQ from the command line.

    If you open the jar file directly, you activate the Quickstart installation and start the server.

  3. Stop your web application server (if running).

  4. Copy the following jar files:

    • <cq-install-dir>/crx-quickstart/server/lib/common/cq-shared-libs-<version>.jar
    • <cq-install-dir>/crx-quickstart/server/lib/common/jcr-2.0.jar
    • <cq-install-dir>/crx-quickstart/server/lib/common/crx-shared.jar

    to the application server folder that holds the shared libraries (shared by all applications deployed to the server).

  5. Restart your web application server.

  6. Note

    Perform the additonal installation steps that are required for JBoss.

  7. Deploy the following web applications:

    • CRX webapp: crx-explorer_crx.war
      It is recommended to deploy this with the context path /crx
    • Launchpad webapp: crx-launchpad.war
      It is recommended to deploy this with the context path /

    These can be found in:

       <cq-installation-dir>/crx-quickstart/server/webapps

    Note

    If you decided to deploy any of the applications with a non-recommended context path, you need to follow these additional configuration steps.

    Note

    JBoss:

    • After deploying, copy the two war files to:
          <JBoss-installation-dir>/server/default/deploy
    • Supports Hot Deployment, if hot deployment is enabled then you can simply copy the two war files to:
          <JBoss-installation-dir>/server/default/deploy 
      If hot deployment is disabled then you will need to restart JBoss after copying the files to the deploy directory.

  8. Note

    Websphere - see the additional step of Configuring the Default JDK.

  9. Start the web applications.

  10. Register your CRX license:

    1. Access your CRX installation:
          http://<server>:<port>/crx/index.jsp
    2. Enter the serial number.
  11. Edit the workspace configuration file to prepare for package installation:

    • Open the following file for edit:
      <cq-installation-dir>/crx-quickstart/repository/workspaces/workspace.xml
    • Locate the <SearchIndex> parameter section.
    • Add:
          <param name="indexingConfiguration" value=""/>
      to the <SearchIndex> parameter section.
  12. Follow the Generic Procedure for Installing Content Packages to install the:

    • CQ initial content package:
      <cq-install-dir>/crx-quickstart/repository/install/cq-content-<version>.zip
    • CQ documentation package (optional):
      <cq-install-dir>/crx-quickstart/repository/install/cq-documentation-<version>.zip

    using the CRX Package Manager to Upload, then Install the packages.

You can now configure CQ according to your requirements.

Generic Procedure for Installing Content Packages

After you have installed CQ, you should install the CQ initial content and documentation packages before proceeding to other tasks. The content package ensures that your CQ instance is fully functional (welcome page, example applications, support for CRX IDEs, etc). The documentation package is optional. The packages are available in the following location:

  • <cq-install-dir>/crx-quickstart/repository/install/
    • cq-content-<version>.zip
    • cq-documentation-<version>.zip

After installing these, you can install any additional content packages that you may have; for example, your Sling application, project content and many others.

To install the packages follow the procedure below:

Note

Starting and stopping web applications is specific to your application server.

Please refer to the documentation of the specific application server.

  1. Stop the following web application in your application server:

    • /       (the CRX launchpad web application)
  2. Navigate to the Package Manager in CRX:

    • http://<server>:<port>/crx/packmgr/index.jsp
  3. Log in to the appropriate workspace (usually the default workspace, crx.default).

  4. Use the CRX Package Manager to Upload, then Install the CQ package(s).

    Alternatively, you can use Package Share to access and download packages to your local instance and then install them.

  5. Start the following web application in your application server:

    • /       (the CRX launchpad web application)
  6. Confirm the operation of CQ.

    Note

    If you experience any problems, please restart both web applications to ensure that all bundles are correctly started.

Generic Procedure to Define the Run Mode for an Instance

You must configure your instance to start in the required run mode. This steers functionality such as replication from an author instance of CQ5.

  1. Stop the crx launchpad (/) web application.

  2. Open the file:
        <cq-installation-dir>/crx-quickstart/launchpad/sling.properties

  3. Add the following properties, appropriate to your instance:

    • for an Author environment:
    sling.jcrinstall.folder.name.regexp=.*/(install|config)(.author)?$
    sling.run.modes=author
    • for a Publish Environment
    sling.jcrinstall.folder.name.regexp=.*/(install|config)(.publish)?$
    sling.run.modes=publish

    Note

    For JBoss also add:

    sling.bootdelegation.org.apache.xerces=org.apache.xerces.*

  4. Restart the crx launchpad (/) web application.

WebSphere v6.1

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

  1. Install WebSphere and disable basic authentication.
  2. Install and configure CQ.

The installation process differs slightly according whether you want to:

  • install the author and publish instances under separate web application servers (standard practice)
  • install the author and publish instances under the same web application server (often required for a test or demo environment)

The differences are highlighted below.

Install WebSphere v6.1 and disable basic authentication

To install WebSphere and disable basic authentication:

  1. Install WebSphere v6.1.

  2. Login to the IBM web console at:

       http://<server>:<port>/ibm/console

    For example, http://localhost:9060/ibm/console, where port 9060 is the default port number.

  3. Click Application Servers, then server1, then Web services: Default bindings for Web services security, then Login mappings.

  4. Select the BasicAuth checkbox and then click Delete.

  5. Save your changes.

WebSphere - One CQ Instance with One Web Application Server

Install CQ5

Install CQ, using content packages, according to the generic procedures.

Note

Before registering your CRX license perform the additional step of Configuring the default JDK according to the procedure.

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:

  1. Stop WebSphere.

  2. Open ibm-web-ext.xmi for edit.

    This is found in:

    <WebSphere-installation-dir>/profiles/<profilename>/config/cells/<cellname>/applications/crxauthor_war.ear/deployments/crxauthor_war/crxauthor.war/WEB-INF

  3. Add the following configuration parameter to specify the JSP engine:

    <jspAttributes xmi:id="JSPAttribute_1225281520121" name="jdkSourceLevel" value="15"/> 
  4. Repeat for crx-launchpad.war

    Note

    The default configuration directory for the web module is:
    <WebSphere-installation-dir>/profiles/<profilename>/config/cells/<cellname>/applications/<enterpriseappname>/deployments/<deployedname>/<webmodulename>/

    If you have already checked the option Use Binary Configuration the files are extracted to the following directory, where they can be edited:

    <WebSphere-installation-dir>/profiles/profilename/installedApps/nodename/enterpriseappname/webmodulename/

    Where <WebSphere-installation-dir> is the root directory of the web application server installation.

  5. Start WebSphere.

Websphere - Author and Publish under One Web Application Server

Unpack CQ

To unpack CQ, create the correct folders and deploy the shared libraries:

  1. Open the directory where you want to install CQ. This will be known as <cq-installation-dir>. Copy the installation jar file into this directory.

  2. Unpack the quickstart jar file without starting the installation (or server).

    To do this start the CQ Quickstart jar with the option -unpack by typing, for example:

        java -jar cq-wcm-quickstart-<version>.jar -unpack

    This creates a folder <cq-installation-dir>/crx-quickstart containing the files and folders used for installation.

    Note

    You must start CQ from the command line.

    If you open the jar file directly, you activate the Quickstart installation and start the server.

  3. Rename the newly created folder to crx-quickstart-author.

  4. Copy this folder and name the new instance crx-quickstart-publish.

    You should now have two folders, crx-quickstart-author and crx-quickstart-publish.

  5. Copy the following jar files:

    • <cq-install-dir>/crx-quickstart/server/lib/common/cq-shared-libs-<version>.jar
    • <cq-install-dir>/crx-quickstart/server/lib/common/jcr-2.0.jar
    • <cq-install-dir>/crx-quickstart/server/lib/common/crx-shared.jar

    to the application server folder that holds the shared libraries (shared by all applications deployed to the server).

Install the Author Instance

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

  1. Adjust JNDI and home paths of the web applications.
  2. Configure the default JDK.
  3. Define the run mode.
  4. Adjust the JNDI name for the CRX sling client repository.
  5. Install the content packages.

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:

  1. Unpack <cq-installation-dir>/crx-quickstart-author/server/webapps/crx-explorer_crx.war.

    Windows:

    1. Move to <cq-installation-dir>/crx-quickstart-author/server/webapps.
    2. Rename the crx-explorer_crx.war to crx-explorer_crx.zip.
    3. Extract crx-explorer_crx.zip to a directory named crx-explorer_crx.

    Linux (command line):

    1. cd <cq-installation-dir>/crx-quickstart-author/server/webapps
    2. mkdir crx-explorer_crx
    3. cd crx-explorer_crx
    4. jar -xvf ../crx-explorer_crx.war
  2. Repeat for
        <cq-installation-dir>/crx-quickstart-author/server/webapps/crx-launchpad.war.

  3. In the WEB-INF directory of the unpacked crx-explorer_crx.war, edit web.xml:

    • Change repository-home from crx-quickstart/repository to crx-quickstart-author/repository (Repository Servlet).
    • Change repository-name from crx to crx-author (Repository Servlet).
    • Change repository-name from virtual-crx to virtual-crx-author (JCR Explorer Servlet).
    • Change 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).
  4. In the same directory, edit the repository-template.xml:

    • 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" />
    ...
    </Module>
  5. Again in the same directory, edit log4j.xml to change the File parameter of the error and transaction log from crx-quickstart/... to crx-quickstart-author/....

  6. In the WEB-INF directory of the unpacked crx-launchpad.war, edit web.xml:

    • Change repositoryName from crx to crx-author.
    • Change sling.home from crx-quickstart/launchpad to crx-quickstart-author/launchpad.
  7. Repackage the crx-explorer_crx.war file:

    Windows:

    1. Select all files in the crx-explorer_crx directory.
    2. Select Send To -> Compress (zipped) Folder
      You have now created a zip file in the crx-explorer_crx directory. 
    3. Rename the generated zip file to crx-explorer_crx.war.  

    Linux (command line):

    1. jar -cvf crx-explorer_crx.war -C crx-explorer_crx/ .
  8. Repeat accordingly to repackage crx-launchpad.war.

  9. Rename crx-explorer_crx.war to crx-author.war.

  10. Rename crx-launchpad.war to author.war.

  11. Deploy both war applications inside the WebSphere console at:

        http://<server>:<port>/ibm/console

    For example, http://localhost:9060/ibm/console, where 9060 is the default port.

Configure the Default JDK

Configuring the Default JDK is done with the same procedure as for the standard installation of one CQ instance under one web application server (using crx-quickstart-author as appropriate).

Define the Run Mode

Adjust the JNDI name for the CRX sling client

To adjust the JNDI name for the CRX sling client:

  1. Open the Apache Felix Configuration console:

      http://<server>:<port>/author/system/console/configMgr

    For example, http://localhost:9080/author/system/console/configMgr, where 9080 is the default port.

  2. 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:

  1. Open
        http://<server>:<port>/crx-author/
    Or the location of your CRX installation; for example, http://localhost:9080/crx-author/, where 9080 is the default port.

  2. Enter your license key.

  3. Stop the following web application in your application server:

    • /       (the CRX launchpad web application)
  4. Open the CRX Package Manager.

  5. Upload and install:
        cq-content-<version>.jar 

    from:
        <cq-installation-dir>/crx-quickstart-author/repository/install/

  6. Open the CRX Content Explorer and change the virtual repository from virtual-crx to virtual-crx-author below /etc/virtual-repository.

  7. Start the following web application in your application server:

    • /       (the CRX launchpad web application)
  8. Confirm the operation of CQ.

    Note

    If you experience any problems, please restart both web applications to ensure that all bundles are correctly started.

Install the Publish Instance

To install the publish instance, repeat all the steps described in Installing the Author Instance, replacing author with publish.

WebLogic v10.3

Note

CQ 5.4 deployment on an Oracle WebLogic application server requires version 10.3.0 or version 10.3.3 or later. A CQ 5.4 deployment in WebLogic versions 10.3.1 or 10.3.2 does not work.

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

  1. Install the WebLogic server and create a domain.
  2. Prepare the WebLogic server by:
    • configuring the server locale
    • enabling basic authentication headers
  3. Unpack, install and configure CQ.
  4. Deploy CRXDE Lite.
  5. Modify WebLogic optimization so CQ login succeeds.
  6. Define the Run Mode for your instance.
  7. Additional Configuration for WebLogic.

Install WebLogic Server

To install the WebLogic server and create a domain:

  1. Download and install the WebLogic server software. 

    Note

    The installation folder is referred to as <WebLogic-installation-dir>.

  2. If you do not want to use the default domain, then create a new domain; for example, <myDomain>:

    • navigate to Oracle Weblogic - WebLogic Server - Tools - Configuration Wizard.
    • The domain is created in:
      <WebLogic-installation-dir>/user_projects/domains/<myDomain>

    Note

    This directory is referred to as <myDomain-dir> in the following sections.

Configure the Server Locale

After installing WebLogic v10.3 (for use with CQ5), you must set the server locale to en_US to avoid errors such as:

java.lang.IllegalArgumentException: Bad date header: 'We 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:

  1. Open the Control Panel.

  2. Open Regional and Languages Options.

  3. In the Regional Options tab, for Standards and formats select English (United States).

To configure the server locale on Linux or Unix:

  1. Set the environment variable LANG to en_US.

Enable Basic Authentication Headers

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

  1. Open:
    <WebLogic-installation-dir>/user_projects/domains/<myDomain>/config/config.xml.

  2. Locate the element <security-configuration>.

  3. Add the following as the child element:

    <enforce-valid-basic-auth-credentials>
        false 
    </enforce-valid-basic-auth-credentials>
    

    Note that in many cases placing the above sub-element as the last sub-element within <security-configuration> will work, but in some cases the correct placement depends on which other sub-elements are already present. For full details, consult the weblogic schema documentation found at http://xmlns.oracle.com/weblogic/domain/1.0/domain.xsd.

  4. If you had already started WebLogic then you will need to restart it.

Create folders for holding the web applications deployment plans:

This is recommended if you want to change the context paths of the web applications:

  1. Create the directories (the names are suggestions):

    • <myDomain-dir>/packages/crx-explorer
    • <myDomain-dir>/packages/crx-launchpad
    • <myDomain-dir>/packages/crxde 

    to hold the war files and the deployment plan files.

  2. Copy the files:

    • crx-explorer_crx.war to <myDomain-dir>/packages/crx-explorer
    • crx-launchpad.jar to <myDomain-dir>/packages/crx-launchpad
    • crxde.war file to <myDomain-dir>/packages/crxde

Install CQ5

Install CQ, using content packages, according to the generic procedures.

Deploy CRXDE Lite

If you have changed the context paths of either web application, then to use CRXDE Lite with WebLogic v10, you need to adapt the context path of crx-launchpad and crx-explorer_crx.

To do this, edit the web.xml file of the CRXDE Lite web application and insert these paths into the <context-param> section:

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

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

Note

If you have upgraded the CRX (within CQ) to 2.1 this step is not needed as CRXDE Lite is embedded in the CRX web application.

Modify WebLogic optimization

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

To modify the WebLogic optimization so that CQ login succeeds:

  1. Open <myDomain-dir>/packages/crx-launchpad/plan/WEB-INF/weblogic.xml.

  2. Add the following line as a child entry of <container-description>:
      <optimistic-serialization>true</optimistic-serialization>

  3. Perform the same change for crx-explorer
    (<myDomain-dir>/packages/crx-explorer/plan/WEB-INF/weblogic.xml).

  4. Restart both web applications.

  5. Log into CQ and access the Websites page to ensure that everything operates as expected.

Additional Configuration for WebLogic

WebLogic requires some additional configurations:

  1. Stop the CRX launchpad web application.

  2. Open <myDomain-dir>/crx-quickstart/launchpad/sling.properties and add this line:

    sling.bootdelegation.weblogic.xml=weblogic.xml.*
  3. Start the CRX launchpad web application.

Proxy Configuration for WebLogic

In some cases it may be necessary to comment-out the proxy configuration section of the WEB-INF/web.xml inside crx-explorer_crx.war. If you encounter errors related to proxy configuration, comment out the following section:

<!-- BEGIN Proxy Configuration -->
<context-param>
...
</context-param>
<!-- END Proxy Configuration -->

as follows:

<!-- BEGIN Proxy Configuration -->
<!-- <context-param>
...
</context-param> -->
<!-- END Proxy Configuration -->

Tomcat v6

To install Tomcat v6, you need to perform the following tasks:

  1. Install the Tomcat server.
  2. Configure the Tomcat access accounts.
  3. Unpack, install and configure CQ.

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:

  1. Navigate to the Tomcat configuration folder.

  2. 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

Install CQ, using content packages, according to the generic procedures.

JBoss v5.1

To install JBoss, you need to perform the following tasks:

  1. Follow the JBoss documentation on how to install a default instance of JBoss v5.1 Application Server.
  2. Unpack, install and configure CQ.
  3. Configure the JBoss Server Login Module.

Install CQ5

Install CQ, using content packages, according to the generic procedures. and the additional steps required for JBoss.

Note

The data directories of your installation now can be found under the working directory of your JBoss Application Server:

(usually the working directory is <JBoss-installation-dir>/bin/crx-quickstart)

 

  • CRX Repository Data: crx-quickstart/repository
  • Launchpad / Apache Felix Data: crx-quickstart/launchpad
  • Logs: crx-quickstart/logs, crx-quickstart/launchpad/logs

Additional Installation Steps required for JBoss

  1. Unpack <cq-installation-dir>/crx-quickstart/server/webapps/crx-explorer_crx.war.

    Windows:

    1. Move to <cq-installation-dir>/crx-quickstart/server/webapps.
    2. Rename the crx-explorer_crx.war to crx-explorer_crx.zip.
    3. Extract crx-explorer_crx.zip to a directory named crx-explorer_crx.

    Linux (command line):

    1. cd <cq-installation-dir>/crx-quickstart/server/webapps
    2. mkdir crx-explorer_crx
    3. cd crx-explorer_crx
    4. jar -xvf ../crx-explorer_crx.war

     

  2. In the WEB-INF directory, open log4j.xml.

  3. Disable console logging in the CRX web application:

    1. Remove or comment out the line
          <appender-ref ref="console"/>
      from the Loggers section of the file.
    2. Save your changes and exit the file.
  4. Delete the following files from the WEB-INF/lib folder:

    • log4j-1.2.14.jar
    • slf4j-api-1.5.11.jar
    • slf4j-log4j12-1.5.11.jar
  5. Repackage the crx-explorer_crx.war file:

    Windows:

    1. Select all files in the crx-explorer_crx directory.
    2. Select Send To -> Compress (zipped) Folder
      You have now created a zip file in the crx-explorer_crx directory. 
    3. Rename the generated zip file to crx-explorer_crx.war.  

    Linux (command line):

    1. cd <cq-installation-dir>/crx-quickstart/server/webapps
    2. jar -cvf crx-explorer_crx.war -C crx-explorer_crx/ .

Redefining where the Web Applications Store their Data

The procedure above uses the default configuration for the crx and launchpad web application data directories.  This means that the data directory crx-quickstart will be created under the JBoss working directory (usually <Jboss-installation-dir>/bin). 

Optionally, you can reconfigure where crx-explorer_crx.war and crx-launchpad.war store their data:

  1. Configure the launchpad web application:

    1. Unpack crx-launchpad.war.
    2. Edit WEB-INF/web.xml.
    3. Change sling.home from crx-quickstart/launchpad to the required path (where you would like to store the Apache Felix data).
    4. Repack crx-launchpad.war.
  2. Configure the crx-explorer web application:

    1. Unpack crx-explorer_crx.war.
    2. Edit WEB-INF/web.xml.
    3. Change repository-home from crx-quickstart/repository to the required path (where you want to store the CRX repository data - Repository Servlet).
    4. Change explorer-home from crx-quickstart/repository to the required path (JCR Explorer Servlet).
    5. Change the home parameter from crx-quickstart to the required path (WebDav Server Servlet).
    6. Repack crx-explorer_crx.war.

    Caution

    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 refer to the CRX clustering documentation for information about how you can configure the CRX shared data paths (the clustering documentation also applies to single crx instances).

Configure the JBoss Server Login Module

The default login configuration of JBoss attempts to authenticate users against a list of users in the users.properties file.

You must configure JBoss to allow login attempts by unknown users to pass to the web application (CRX Explorer). The web application will then process authentication.

The configuration is made as follows:

  1. Open for editing:
      <JBoss-installation-dir>/server/default/conf/login-config.xml

     

  2. 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>

Configuration Required when not using Default Contexts

Day recommends installing the product web applications under the default contexts (/ and /crx). If there are reasons why this is not possible (operations, deployment, etc), you can also deploy the web applications under other contexts.

You will need the following additional configuration step(s) if you do not use the default contexts (/ and /crx) for the webapps. The description below assumes that crx-launchpad.war is deployed into /launchpad, and crx-explorer_crx.war into /daycrx).

  1. The action to be taken depends on whether you will be using CRXDE or CRXDE Lite:

    • CRXDE Lite:
      Edit the configuration file WEB-INF/web.xml, of the CRX web application deployed to your application server. Configure the required launchpad context in the JCRExplorer servlet section:
    <init-param>
    <param-name>launchpad.ctx.path</param-name>
    <param-value>/launchpad</param-value>
    <description>Context path of the launchpad</description>
    </init-param>

    The location of the WEB-INF/web.xml configuration file is specific to the application server and its configuration, please consult the relevant third-party documentation.

    • CRXDE:
      Reconfigure the URL for the CRX server endpoint. See Changing the CRX Server Endpoint for instructions.
      You have to log in to CRXDE with the URL appropriate to your launchpad web application; for example, http://<server>:<port>/launchpad
  2. If you are using a Dispatcher Flush Agent and have installed CQ in a context other than the recommended default context, then you need to configure the HTTP Headers in the Extended tab.

Verifying the Installation

The following links can be used to verify that your installation is operational (all examples are on the basis that the instance is running on port 8080 of the localhost, that CRX is installed under /crx and Launchpad under /):

  • http://localhost:8080/libs/cq/core/content/welcome.html
    The CQ Welcome screen.
  • http://localhost:8080/crx/
    The CRX administration Console.
  • http://localhost:8080/crx/de/
    The CRXDE Lite console.
  • http://localhost:8080/system/console
    The Apache Felix Web Console.