Documentation Center

Installing the Moderation Web Service as a Java Web application

User Generated Content requires you to install and configure two Web applications, one of which is used for moderating comments (the Moderation Web Service). Note that this Web application also contains the Content Delivery Web service Server Role.

Procedure

  1. Ensure that all the prerequisites for a Content Delivery Server Role are met on your target system.
  2. Create the following Web application directory structure:
    1. In the root folder, create a WEB-INF/ directory.
    2. In the WEB-INF/ directory, create subdirectories classes/ and lib/.
  3. Navigate to the Content Delivery\roles\ugc\java\ folder.
  4. Copy all the JAR files from the lib\ subfolder, and all the JAR files from the third-party-lib\ subfolder, to the WEB-INF/lib/ folder of your Web application.
  5. If you store published content in a database, download the JDBC driver (JAR file) required for your specific database vendor and copy it into the WEB-INF/lib directory of your Web application:
    VendorJDBC DriverRequired JAR
    Microsoft SQL ServerMicrosoft SQL Server JDBC Driver 4.0

    sqljdbc42.jar for Java 8

    sqljdbc4.jar for Java 6 or Java 7

    OracleOracle JDBC driver 11.2.0.3 (deprecated)

    ojdbc6.jar for Java 6 or Java 7

    OracleOracle JDBC driver 12.1.0.1

    ojdbc7-12.1.0.1.jar for Java 8

    ojdbc7.jar for Java 7

    ojdbc6.jar for Java 6

    IBM DB2IBM Data Server Driver for JDBC and SQLJ (9.7 GA) (deprecated)

    Not supported with Java 8

    db2jcc.jar for Java 6 or Java 7

    You can download JDBC drivers from the following locations:
  6. Navigate to \Content Delivery\resources\configurations\.
  7. Copy logback.xml from that folder to the WEB-INF/classes/ subdirectory of your Web application.
  8. Copy and rename the following configuration files to the WEB-INF/classes/ folder of your Web application:
    Corresponding configuration fileRenamed configuration file
    cd_ambient_conf_sample.xmlcd_ambient_conf.xml
    cd_dynamic_conf_sample.xmlcd_dynamic_conf.xml
    cd_storage_conf_sample.xmlcd_storage_conf.xml
    cd_link_conf_sample.xmlcd_link_conf.xml
    cd_ugc_conf_sample.xmlcd_ugc_conf.xml
    cd_webservice_conf_sample.xmlcd_webservice_conf.xml
  9. Open cd_ambient_conf.xml for editing.
  10. Find the <Security> section and enclose it in comments. This element is only needed if you intend to set up OAuth authentication.
  11. Save and close cd_ambient_conf.xml.
  12. Copy cd_licenses.xml, your Content Delivery license file available from SDL Tridion Customer Support, to the WEB-INF/classes 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 License element in your configuration files.
  13. Optional: Configure logging.
  14. Configure the Storage Layer and optionally encrypt sensitive strings.
  15. If your Web application server is JBoss, do the following:
    1. Locate the following files in the WEB-INF/lib/ subdirectory and remove them:
      • stax-api.jar
      • serializer.jar
      • xalan.jar
    2. If you use JBoss 5.1 or 5.2, add the following JVM property-value pair to the JAVA_OPTS variable: -Dorg.jboss.logging.provider=slf4j
    3. If you use JBoss 6.0 or 6.1, create a file with the following contents called jboss-deployment-structure.xml and save the file in the WEB-INF/ directory:
      <jboss-deployment-structure>
      	<deployment>
      		<exclusions>
      			<module name="org.slf4j" />
      			<module name="org.slf4j.impl" />
      			<module name="com.sun.jersey" />
      			<module name="com.sun.jersey.json" />
      			<module name="com.sun.jersey.core" />   
      		</exclusions>
      	</deployment>
      </jboss-deployment-structure>
    4. If you use JBoss 6.0 or 6.1, 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>
  16. If your Web application server is WebLogic, do the following:
    1. Remove the file stax-api.jar from your WEB-INF/lib/ subdirectory.
    2. Add a weblogic.xml file to the WEB-INF folder of your Web application that forces WebLogic to use the libraries contained in the Web application, rather than its own libraries. The contents of this weblogic.xml file must be as follows:
      <weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      	xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"
      	xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">
      	<container-descriptor>
      		<prefer-application-packages>
      			<package-name>javax.persistence.**</package-name>
      			<package-name>antlr.*</package-name>
      			<package-name>org.slf4j.**</package-name>
      			<package-name>org.apache.log4j.**</package-name>
      			<package-name>org.apache.xml.serializer.**</package-name>
      		</prefer-application-packages>
      	</container-descriptor>
      </weblogic-web-app>
  17. Navigate to Content Delivery\roles\webservice\java\ and copy web.xml to the root of your Java Web application.
  18. Open the web.xml file and uncomment the following sections:
    Sample configuration for the Web service
    OAuth 2.0 security access filter
    Uncomment the following block to apply the filter for the UGC user
  19. Save and close web.xml.
  20. Restart the Web application.