AEM Custom Quiz

cq5-author-p4502.jar

cq5-author-4502-1234.jar

cq5-author-p4502-1234.jar

cq5-author-4502.jar

Use the nosamplecontent run mode when installing the cq5 instance

Remove all the geometrix related files manually

Uninstall the packages cq-geometrixx-pkg-x.y.z.zip and cq-geometrixx-outdoors-pkg-x.y.z.zip from the Package manager

Uninstall the packages cq-geometrixx-pkg-x.y.z.zip from the Package manager

Uninstall the package cq-geometrixx-all-pkg-5.6.12.zip

Starts the cq5 service

Creates the cq5 services

Shows the status for the cq5 service

Creates the cq5 service and starts it right away

CQ_INSTANCE

CQ_INTERFACE

CQ_USE_JAAS

CQ_LOGS_DIR

CQ_JAAS_CONFIG

CQ_JARFILE, CQ_RUNMODE

CQ_VERSION

CQ_HOST, CQ_JVM_OPTS

CQ_TEMP_DIR

CQ_PORT

Click Stop in the Services control panel or in the command line

Navigate to the folder and type instsrv.bat -uninstall cq5

Navigate to the folder and type instsrv.bat cq5

Click Stop in the Services control panel or in the command line, navigate to the folder and type instsrv.bat -uninstall cq5

Add the JVM parameter -Djava.io.tmpdir="/<new-tmp-path>" to the server startup command line

Add the JVM parameter -Dcq.tmpdir="/<new-tmp-path>" to the server startup command line

Add the JVM parameter -Djava.io.tmpdir="/<new-tmp-path>" to the CQ_JVM_OPTS environment parameter in the serverctl or start script

Add the JVM parameter -Dcq.tmpdir="/<new-tmp-path>" to the CQ_JVM_OPTS environment parameter in the serverctl or start script

By accessing the file crx-quicqstart/help after unpacking the quickstart jar file

By running the command java -jar cq5-<version>.jar –help

By going to the osgi system/console, Support tab, Help section

The home directory for sling logs

The path to crx-quickstart directory

The directory for sling jar files.

access.log All access requests to AEM WCM and the repository are registered here

audit.log Moderation actions are registered here.

error.log Error messages (of varying levels of severity) are registered here.

request.log Each access request is registered here together with the response.

stderr.log Holds error messages, again of varying levels of severity, generated during startup. By default the log level is set to Warning (WARN)

stdout.log Holds logging messages indicating events during startup

upgrade.log Provides a log of all upgrade operations that runs from the com.day.compat.codeupgrade and com.adobe.cq.upgradesexecutor packages.

cq-installation-dir>/crx-quickstart/repository (only CQ5) revision.log Revision journaling information.

Java 5

Java 6

Java 7

Java 8

A. properties.get("cq:tempate","");

B. page.getTemplate().getPath()

C. page.getTemplate()

resource.getTemplate.getPath();

http.conf.disp<x>

dispatcher.any

mod_dispatcher.so

dispatcher-apache<x.y>-<rel-nr>.so

dispatcher-apache<x.y>-<rel-nr>.so

mod_dispatcher.so

http.conf.disp<x>

dispatcher.any

Dynamic modules support. This can be done by using any of the --enable-shared options or at a minimum include the mod_so module with --enable-module=so

Dispatcher modules support. This can be done by using any of the --enable-dispatcher options. At a minimum include the dispatcher_so module.

Dispatcher modules support. This can be done by using any of the --enable-shared options. At a minimum include the dispatcher_so module.

Dispatcher modules support. This can be done by using any of the --enable-shared options. At a minimum include the mod_so module.

In the dispatcher configuration dispatcher.any, using the parameter DispatcherLog

In the apache configuration apache2.conf, using the parameter DispatcherLog

In the CQ5 installation by adding a Logging Logger Configuration

Defines the Server Header to be used: undefined or 0 - the HTTP server header contains the AEM version. 1 - the Apache server header is used.

Defines the Server Header to be used: undefined or 0 - the Apache server header is used. undefined or 0 - the HTTP server header contains the AEM version.

Defines whether to decline requests to the root "/": 0 - accept requests to / 1 - requests to / are not handled by the dispatcher; use mod_alias for the correct mapping.

Defines whether to decline requests to the root "/": 1 - accept requests to / 0 - requests to / are not handled by the dispatcher; use mod_alias for the correct mapping.

Defines whether to use pre-processed URLs for all further processing by Dispatcher: 0 - use the original URL passed to the web server. 1 - the dispatcher uses the URL already processed by the handlers that precede the dispatcher (i.e. mod_rewrite) instead of the original URL passed to the web server.

Defines whether to use pre-processed URLs for all further processing by Dispatcher: 1 - use the original URL passed to the web server. 0 - the dispatcher uses the URL already processed by the handlers that precede the dispatcher (i.e. mod_rewrite) instead of the original URL passed to the web server.

Defines how to support error codes for ErrorDocument handling: 0 - Dispatcher spools all error responses to the client. 1 - Dispatcher does not spool an error response to the client (where the status code is greater or equal than 400), but passes the status code to Apache, which e.g. allows an ErrorDocument directive to process such a status code.

Defines how to support error codes for ErrorDocument handling: 1 - Dispatcher spools all error responses to the client. 0 - Dispatcher does not spool an error response to the client (where the status code is greater or equal than 400), but passes the status code to Apache, which e.g. allows an ErrorDocument directive to process such a status code.

0,1,2,3

Error,Warning,Info,Debug

Yes

No

Content Updates remove the pages that have changed, as well as files that are directly associated with them.

Auto-Invalidation automatically invalidates those parts of the cache that may be out of date after an update. i.e. it effectively flags relevant pages as being out of date, without deleting anything.

Content Delete remove the pages that have changed, as well as files that are directly associated with them.

Content Update : remove the pages that have changed, as well as files that are directly associated with them.

Content Delete : remove the pages that have changed, as well as files that are directly associated with them.

Dispatcher-Invalidate: automatically invalidates those parts of the cache that may be out of date after an update. i.e. it effectively flags relevant pages as being out of date, without deleting anything.

If the HTTP method is not GET. Other common methods are POST for form data and HEAD for the HTTP header.

If the request URI contains a question mark "?". This usually indicates a dynamic page, such as a search result, which does not need to be cached.

The file extension is missing. The web server needs the extension to determine the document type (the MIME-type).

The authentication header is set (this can be configured)

Increased processing and increased fail-safe coverage

Increased security

Increased data storage