Preparing for Content Distribution
Preparing a server for distribution requires a special license token and some special logging configuration.
Procedure
- The distribution server requires a
lcpackagelicense token. Contact SDL to obtain the proper license.Note: Thelcpackagelicense token is not required for content delivery servers. - On your distribution server, enable logging for the distribution center in your log4j.xml configuration file. This file is located at LiveContent_home/tools/wrapper/conf folder on a Bundled Web Application Server Install. This file is located at LiveContent_home/WEB-INF folder on a Third-Party Web Application Server Install. Un-comment the following block to enable distribution center logging:
<category name="livecontent.distribution" additivity="false"> <priority value="real-info"/> <appender-ref ref="livecontent.distribution"/> </category>Note: Enabling livecontent.distribution logging is not required for content delivery servers.CAUTION:When specifying directory paths in the log4j.xml configuration file, use only forward slashes (/). Backward slashes (\), such as those used in typical Windows directory paths, are ignored. - Restart the application or service.
- If you are using a third-party web application server, restart the application server's service. For example, if you are using Apache Tomcat, restart the Apache Tomcat service
- If you are using the bundled web application server, restart the SDL LiveContent Reach database.
- On Windows, restart the LiveContent XML Database service.
- On Linux, log in as the root user, and type the following at a command prompt:
/etc/init.d/SDL_LiveContent restart
- Ensure that all of your content delivery servers and the distro server have been configured into the same secure content distribution group. See Securing Content Distribution.
- Before you can add content delivery servers, you must ensure that your distro server has the content delivery server's machine cert by exporting it from each content delivery server and importing it into the distro server's Tomcat keystore. See Enabling Secure Socket Layer (SSL) protocol for the Apache Tomcat web application server
The distro server now trusts the content delivery servers.