Adding the legacy Experience Manager Web site extension to a legacy Java/JSP Web site
To add Experience Manager to your existing legacy in-process staging Web site in IIS, install the Experience Manager Web site extension to the staging Web site.
Procedure
- Ensure that all the prerequisites for a Content Delivery Server Role are met on your target system.
- Access the SDL Web installation media.
- Navigate to the Content Delivery\roles\ folder.
- Access the session\extension-web\in-process\java\lib\ subfolder and add the files in this location to the WEB-INF/lib/ folder of the Java/JSP Web application that represents your staging Web site.
- Navigate to the folder \Content Delivery\roles\session\extension-web\in-process\config\.
- Merge all files in this folder (but not the schemas\ subfolder or its files) with those in the WEB-INF/classes/ folder of your Web application. Any files not already present in WEB-INF/classes/ can be copied over.
- Open cd_dynamic_conf.xml for editing.
- Insert the following structure as the first child element inside the root element. This section may already exist, in which case you can use the mappings you see, and add new ones if needed.
<URLMappings> <StaticMappings> <Publications> <Publication Id="23"> <Host Domain="example.com" Port="91" Protocol="http" Path="/local-fr" /> </Publication> </Publications> </StaticMappings> <StorageMapping IdentifyPublicationByProperty="publicationUrl" /> </URLMappings>This example makes it possible to retrieve metadata for a Web page located in the http://example.com:91/local-fr/ by checking the corresponding Page in the Publication with ID 23 in the Content Manager. - Save and close cd_dynamic_conf.xml.
- Copy cd_licenses.xml, your Content Delivery license file available from SDL Customer Support, to the bin\config directory of your Web application.
If you want to name the file differently or put it in a different location, you need to update the
Licenseelement in your configuration files. - Optional: Configure logging.
- Configure the Storage Layer and optionally encrypt sensitive strings.
- If your Web application server is JBoss, do the following:
- Locate the following files in the WEB-INF/lib/ subdirectory and remove them:
- stax-api.jar
- serializer.jar
- xalan.jar
- Access the SDL Web installation media, navigate to Content Delivery\resources\web\ and from that location, copy the file jboss-deployment-structure.xml to the WEB-INF/ directory.
- Open WEB-INF/web.xml, add the following section and save the file:
<context-param> <param-name>resteasy.scan</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>resteasy.scan.resources</param-name> <param-value>false</param-value> </context-param> <context-param> <param-name>resteasy.scan.providers</param-name> <param-value>false</param-value> </context-param>
- Locate the following files in the WEB-INF/lib/ subdirectory and remove them:
- If your Web application server is WebLogic, do the following:
- In the file web.xml in your WEB-INF/ subdirectory, in the
web-appelement, add the attribute-value pairmetadata-complete="true". - Remove the file stax-api.jar from your WEB-INF/lib/ subdirectory.
- Access the SDL Web installation media, navigate to Content Delivery\resources\web\ and from that location, copy the file weblogic.xml to the WEB-INF/ directory.
- In the file web.xml in your WEB-INF/ subdirectory, in the
- Access the root of your legacy in-process staging Web site and open web.xml for editing.
- Ensure the presence of the following in this file:
<listener> <listener-class>com.tridion.storage.persistence.session.SessionManagementContextListener</listener-class> </listener> <filter> <filter-name>webPageContentFilter</filter-name> <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class> </filter> <filter-mapping> <filter-name>webPageContentFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> <filter> <filter-name>webBinaryContentFilter</filter-name> <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class> </filter> <filter-mapping> <filter-name>webBinaryContentFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>This applies session preview filtering to your entire Web site . If your entire staging Web site is located in a subdirectory, change the value ofurl-pattern. - Enable the Ambient Data Framework by adding the following to your web.xml:
<filter> <filter-name>Ambient Data Framework</filter-name> <filter-class>com.tridion.ambientdata.web.AmbientDataServletFilter</filter-class> </filter> <filter-mapping> <filter-name>Ambient Data Framework</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> - Save and close web.xml and restart your Java/JSP Web site.
- Restart the Web application.