Installing the Content Service
The Content Service is a core Content Delivery Server Role. The Content Service must be installed in order for SDL Tridion Docs to work.
- Copying resources for the Content Service installation
Copy microservice resources to your target machine. - Configuring Content Data Store database access for your microservice
Your microservice uses the Storage Layer to access the Content Data Store, where all content is stored. To configure content storage in one or more databases, addStorageelements to the Storage Layer configuration file. In this file, you can specify configuration strings as hardcoded values or as parameters. - Installing the Content Service as a standalone microservice
Run the appropriate microservice installation PowerShell or Unix script to install and run the standalone microservice. - Adding the ISH cartridge to the Content Service
To enable a content mashup, that is, to enable an upgrade between SDL Tridion Sites and SDL Tridion Docs, copy Ambient Data Framework Cartridge resources to your Content Service. To use REL, some additional configuration is needed. - Adding the UGC Cartridge to the Content Service
To add the UGC Cartridge to the Content Service, load an Add-on. - 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. - Connecting to an HTTPS-secured Discovery Service
If you secured your Discovery Service with HTTPS, you imported your certificate into a keystore which you passed to the Discovery Service. To connect to the Discovery Service, import the same certificate into your local Java keystore. - Registering the Content 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.