Installing the UGC Moderation service
Install the Moderation service as a microservice or as a Java/JSP Web application. Note that the Moderation service and Community service are almost identical and use the same database; the only difference is the configuration of the Cartridge. If you have already set up the Community service, you can make a copy of its resources (including configurations) and only modify the UGC Ambient Data Framework Cartridge configuration file ugc_ambient_cartridge.xml.
About this task
- Copying resources for the UGC Moderation service
Copy the microservice resources. - Setting a log location for your microservice
By default, Content Delivery microservices write their log files to a folder called c:/SDLWeb/log/. Set a proper location in the Logback configuration file for your microservice, logback.xml. - Configuring UGC
To configure User Generated Content, edit your User Generated Content configuration file, cd_ugc_conf.xml to set a scoring threshold and a whitelist for comments. - Configuring UGC database access for UGC
UGC uses uses the Storage Layer to access the UGC database, where User Generated Content comments, ratings user data and item statistics are stored. To configure storage of this kind of data in the UGC database, add aStorageelement to the Storage Layer configuration file. - Enabling processing of UGC TCDL tags
You need to add a tag bundle to your dynamic configuration file, cd_dynamic_conf.xml to enable UGC to process User Generated Content TCDL tags at runtime. - Configuring the UGC cartridge for the Moderation Web service
The User Generated Content cartridge for the Ambient Data Framework (included in the Moderation Web service resources) takes care of, amongst others, the Content Delivery side of a User Generated Content Audience Manager integration. The Community Web Service requires two Claim Processors. - Installing the UGC Moderation service as a microservice
Run the appropriate microservice installation PowerShell or Unix script to install and run the standalone microservice. - Securing the microservice with SSL
You may wish to secure your microservice using Secure Socket Layer (SSL), so that an HTTPS connection is required to interact with the service. If you do, you require a certificate signed and issued by a Certificate Authority (CA), a private key, and a keystore containing both of these. You then configure the keystore in the application.properties file of your microservice. You can reuse the same certificate, key and keystore for multiple microservices, so long as they are all running on the same machine. This section assumes that you have no certificate, key or keystore yet. If you do, you can skip the topics that do not apply. - Registering the UGC Moderation Web service microservice as a Capability
If you already used theauto-registerswitch to register this Server Role as a Capability when you installed it as a standalone microservice, you can skip this task. If you did not, you can make this microservice discoverable through the Discovery Endpoint by hand by adding it as a Capability to the Discovery Service's Storage Layer configuration file and update the Capability registry by rerunning the Discovery Service registration tool. - Upgrading the SDL Tridion 2013 SP1 HR1 UGC Moderation Web service
Before SDL Web 8, the UGC Moderation Web service (now called the UGC Moderation service) could only exist as (part of) a Web application. As of SDL Web 8, it can also be a standalone microservice. How you upgrade the Role depends on how you have it installed now: as a Java/JSP Web application or as a .NET Web application.
Related tasks