Installing the Discovery Service when upgrading from SDL Tridion 2013 SP1 HR1
If you are upgrading from SDL Tridion 2013 SP1 HR1, the Discovery Service is a core Content Delivery Role that you must install, regardless of whether you are performing a minimal upgrade or a direct migration.
- Copying resources for a Discovery Service installation in an upgrade scenario
Copy the microservice resources, or for a deprecated Web application-based microservice, copy the contents of a WAR file to a Web application location. - Configuring the Discovery Service
Configure storage, logging and other configuration options for this Server Role. - List of Capabilities
The Discovery Service can expose Capabilities: Content Delivery features that run as microservices and can be accessed through the Discovery Endpoint. You configure these Capabilities in the Storage Layer configuration file of the Discovery Service. SDL Web has a number of Capabilities of its own, some core Capabilities, others optional. As for add-on products, consult the documentation for the specific add-on to learn the name and URL of its Capability or Capabilities. Capabilities can have properties and/or service targets. - Registering the Token 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. - Installing the Discovery Service as a standalone microservice
Run the appropriate microservice installation PowerShell or Unix script to install and run the standalone microservice. - Installing the Discovery Service as a Java/JSP Web application-based microservice (deprecated)
Installing the Discovery Service as a Java Web application-based microservice may require some Web application-server specific configuration before deployment can start. - 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.