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
- Ensure that all the prerequisites for a Content Delivery Server Role are met on your target system.
- Ensure that the .NET Framework has the WCF Services feature "HTTP Activation" switched on.
- Create the following Web application directory structure:
- In the root folder, create a WEB-INF/ directory.
- In the WEB-INF/ directory, create subdirectories classes/ and lib/.
- Access the SDL Web installation media.
- Navigate to the Content Delivery\roles\ folder.
- On the installation media, navigate to the Content Delivery\roles\api\in-process\java\lib\ folder.
- Copy all the JAR files from this folder to the WEB-INF/lib/ folder of your Web application.
- 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.
- 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.
- 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>
- If your Web application server is WebLogic, do the following:
- In the file web.xml in your WEB-INF/ subdirectory, in the
web-app element, add the attribute-value pair metadata-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.
- Restart the Web application.