Documentation Center

Content Delivery functionality introduced in Tridion Docs 15

The Tridion Docs 15 release introduces several functional changes to Content Delivery.

New caching mechanism
As from Tridion Docs 15, Content Delivery offers a new implementation of caching on the server, based on the JCache (JSR107) specification, as implemented in Apache Ignite. This new implementation, called embedded caching, replaces the old implementation using the Cache Channel Service and/or Java Messaging Service (JMS). Embedded caching is configurable in terms of caching nodes and clients.
For more information, refer to these topics:
Recommendations
As from Tridion Docs 15, the search query contains a recommend argument to find recommended content. The query can be written to make recommendations on the basis of an existing item ("Find me more content like this"), on the basis of a set of concepts ("Find me content with these properties"), or a combination of both.
For more information, refer to these topics:
Simplified microservice packaging
A number of improvements were made to package our microservices in line with Java Spring-based packaging best practices. Specifically:
  • The use of services\ folders is discontinued. Instead, all your custom items go in a new custom\ folder.
  • A number of settings that were, for example, only configurable on the command line, are now set in the application.properties file of the microservice.
  • The springprofilesactive placeholder, which was used by both the Content Service and the Content Deployer, is discontinued in favor of separate contentspringprofilesactive and deployerspringprofilesactive placeholders, so that both services can run in the same environment, each with their own spring.profiles.active setting.
  • The new cache feature is enabled or disabled in application.properties.
  • Semantic Content Model configuration is in application.properties.
  • OpenSearch configuration properties have been moved from the properties file search.properties into application.properties.
  • Similarly, properties from the properties file endpoint.properties have been moved into application.properties.
IQ Combined Service
Instead of the IQ Index Service and IQ Query Service , which existed prior to Tridion Docs 15, there is now an IQ Combined Service instead, which combines indexing and querying functionality.
Additionally, the IQ Combined Service is a microservice that is only intended for internal use by the product itself, specifically by the Content Deployer. As an implementer, you cannot use the new IQ Combined Service to query. Use the Public Content API instead.
Note that the latest version of the Dynamic Delivery web application (with DXA with the latest hotfix applied) also no longer uses an IQ microservice to query, but uses the Public Content API instead.
Improved performance for Content Delivery database upgrades
As of Tridion Docs 15, the performance of upgrading a relational database for Content Delivery is much improved.
More robust security
A number of security issues revealed by a Veracode analysis led to significant security improvements. Also, a Tomcat Attack Vector was closed.
GraphQL queries specific to Tridion Docs
As from Tridion Docs 15, the Public Content API contains a number of new root queries that are specific to Tridion Docs. Use these new root queries to explore the Tridion Docs content model by fetching publications or topics, or by exploring the table of contents of a publication.
Persistent topic identifier in Dynamic Delivery URL across versions
When you publish a publication to Dynamic Delivery, each webpage has a URL in the following kind of format: https://internaldocs.example.com/986917/139451. The two numbers are generated in the following way:
  • The first number identifies the specific version of the publication you published, in the specific language in which you published it.
  • The second number, until now, identified the specific version of the topic you published, in the specific language in which you published it.
This meant that if you changed a topic in a publication that was already published, and then republished that publication, the second number would change, and so the URL would change as well (say, to https://internaldocs.example.com/986917/233435). Even worse, if you didn't unpublish your publication first, the original URL would continue to exist, showing the wrong, uncorrected topic.
As from Tridion Docs 15, a numerical ID for a topic is generated based only on its GUID, its unique identifier in Content Manager. That way, creating a new version of the topic won't result in a different URL.
Library Topics no longer published to Dynamic Delivery
Prior to Tridion Docs 15, when you published a publication to Dynamic Delivery, not only topics and images, but also Library Topics would be published. While these Library Topics did not appear in the table of contents panel, they could still show up as a search result to a user who had entered a search string contained in a Library Topic. Library Topics are not supposed to be seen by the reader.
As from Tridion Docs 15, Library Topics are no longer included during publishing, and so they are no longer present or findable in the published publication on the Dynamic Delivery website.