Installing the legacy API (in-process) Server Role for a Java/JSP Web application

Only install the legacy API (in-process) Server Role if you have a pressing reason to do so (for example, because you have legacy code that you are unqilling to migrate). Otherwise, install the API (RESTful) Server Role. Installing the legacy API (in-process) Server Role involves registering .NET Server Controls, configuring Profiling & Personalization, and setting up the Ambient Data Framework. The API (in-process) Server Role is typically installed on the staging or live Web site, and takes care of resolving dynamic links between content items.

Procedure

  1. Ensure that all the prerequisites for a Content Delivery Server Role are met on your target system.
  2. Ensure that the .NET Framework has the WCF Services feature "HTTP Activation" switched on.
  3. 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/.
  4. Access the SDL Web installation media.
  5. Navigate to the Content Delivery\roles\ folder.
  6. On the installation media, navigate to the Content Delivery\roles\api\in-process\java\lib\ folder.
  7. Copy all the JAR files from this folder to the WEB-INF/lib/ folder of your Web application.
  8. Copy the contents of the Content Delivery\roles\api\in-process\config\ folder on the installation media to the WEB-INF/classes/ folder of your Web application.
  9. Copy cd_licenses.xml, your Content Delivery license file available from SDL 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.
  10. Optional: Configure logging.
  11. Configure the Storage Layer and optionally encrypt sensitive strings.
  12. 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. 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.
    3. 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>
  13. If your Web application server is WebLogic, do the following:
    1. In the file web.xml in your WEB-INF/ subdirectory, in the web-app element, add the attribute-value pair metadata-complete="true".
    2. Remove the file stax-api.jar from your WEB-INF/lib/ subdirectory.
    3. 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.
  14. Restart the Web application.