Troubleshooting Experience Manager problems
This task presents steps to check if your Experience Manager setup is not working properly.
Procedure
- Check your cd_preview.log for the following:
Request for path 'RELATIVEPATH' was found to match the configured excludedPath: 'EXCLUDEDPATH'.where RELATIVEPATH is the path to a webpage that does not work with Experience Manager, and EXCLUDEDPATH is some string.
- If you find the above message, check your cd_ambient_conf.xml for the
ExcludedPathssection, and comment out anyPathelements that match the URL of a webpage you want to make editable. - In your Session-enabled Content Service location on the server, check the following (your log level is assumed to be set to
DEBUG):- In cd_storage_conf.xml, verify that
SessionWrapperis listed among the wrappers. - In cd_storage_conf.xml, verify that Preview_dao_bundle.xml is listed among the storage bindings.
- In cd_ambient_conf.xml, verify that
WhiteListis enabled and that the IP address that is making requests is within the configured IP range. To allow any IP, set the range to<Ip>0.0.0.0-255.255.255.255</Ip> - In cd_ambient_conf.xml, verify that in the
<GloballyAcceptedClaims>section, there's aClaimwith itsUriattribute set totaf:session:preview:preview_session. - In cd_ambient_conf.xml, verify the presence of the two Preview Cartridges:
<Cartridge File="cd_webservice_preview_cartridge.xml" Category="SYSTEM"/>and<Cartridge File="cd_webservice_preview_cartridge.xml"/> - In cd_core.log, ensure the presence of the line:
DEBUG AbstractAmbientDataServletFilter - Cookie forwarding is enabled: true - In cd_core.log, ensure the presence of the line:
DEBUG AbstractAmbientDataServletFilter - Cookie forwardingforcurrent request is allowed: true - In cd_core.log, ensure the presence of the line:
DEBUG ClaimCookieDeserializer - Found NUMBER claims cookies.where NUMBER is some number. You should not see the line:DEBUG ClaimCookieDeserializer - The list of ClaimsCookies sent to be deserialized is empty!
- In cd_storage_conf.xml, verify that
- In your Preview Service location on the server, check the following:
- In cd_storage_conf.xml, verify that
SessionWrapperis listed among the wrappers. - In cd_storage_conf.xml, verify that Preview_dao_bundle.xml is listed among the storage bindings.
- In cd_ambient_conf.xml, verify the presence of the two Preview Cartridges:
<Cartridge File="cd_webservice_preview_cartridge.xml" Category="SYSTEM"/>and<Cartridge File="cd_webservice_preview_cartridge.xml"/>
- In cd_storage_conf.xml, verify that
- In the Session Preview database, verify that when you select Update Preview in Experience Manager, there is data in the
PREVIEW_SESSIONSorPREVIEW_SESSION_ITEMStable. - If your staging website runs as a Java web application, also check the following:
- In cd_client_conf.xml, verify that your cache is disabled.
- In cd_client_conf.xml, verify the presence of a
PreviewServiceelement with theMachineName,FileLocationandDefaultFileSystemattributes set. - In cd_ambient_conf.xml, verify that the
<ForwardedClaims>section is enabled and contains aClaimwith itsUriattribute set totaf:session:preview:preview_session. - Verify that there is a web.xml file at the same level as the classes/ directory.
- In this web.xml file, ensure that
PageContentFilteris enabled and set to com.sdl.web.preview.client.filter.ClientPageContentFilter. - In this web.xml file, ensure that
BinaryContentFilteris enabled and set to com.sdl.web.preview.client.filter.ClientBinaryContentFilter. - The logs contain the following line:
ForwardedClaims is configured. Will forward following claims: LISTOFCLAIMS, where LISTOFCLAIMS containstaf:session:preview:preview_session.