Configuring a User-Generated Content Server to interact with Legacy Content Delivery servers
In a content distribution model using Legacy Content Delivery servers, you should configure one server (either an existing Collaborative Review or Legacy Content Delivery server, or a separate server) to be the user-generated content server.
Before you begin
Each Legacy Content Delivery server needs to be configured to use a user-generated content server. Once configured, each server will read their user-generated content from this single user-generated content server, and write all of their new user-generated content to this server as well, instead of storing it locally. This allows a group of Legacy Content Delivery servers to present a single, consistent set of user-generated content to your user community. The best way to share this configuration amongst your delivery servers is to include it in a configuration package to be pushed by your content distribution profile.
Your load balancer settings may be combined with your user-generated content server settings into a single configuration package.
Procedure
- Define and export a new configuration package specifically to distribute your user-generated content server settings. Do not include any skins, publications, or configuration items in this configuration package. See Defining a Configuration Package.
- Create a new content distribution profile. See Creating a Content Distribution Profile.
- When this configuration package is pushed to your Legacy Content Delivery servers, they will immediately start to use the user-generated content server as the central repository for all user-generated content.