Yet Another Tridion Blog

One of the microservices I was describing in my post  Content Delivery Microservices  is the Discovery Service. This post describes what the service does and provide a step-by-step installation guide. The Discovery service is a new addition to the set of functionality in Tridion. It is a REST service that provides information about the capabilities of a given content delivery environment. A capability represents a Content Delivery module that is exposed itself as a REST service (i.e. the other CD Microservices of SDL Web 8). The Discovery service knows about each capability in a given environment and exposes this information in its methods. For example, if a content delivery environment has capabilities Deployer and Dynamic Content , the Discovery service will provide the calling client the information about their endpoints, such that other systems discover what capabilities are available in a given environment, and what are their endpoints, so that they can communicate with the

Among the new features in SDL Web 8 there are the Content Delivery Microservices, namely: Audience Manager Content Deployer Contextual Image Delivery Discovery Service Dynamic Content Dynamic Linking Profiling and Personalization Metadata Query Taxonomy User Generated Content These microservices make up the Content Interaction Services and they expose the existing Content Delivery in-process APIs as RESTful services. They provide the server-side component in a Services-Oriented Architecture and act as data layer between the the web client and the Content Delivery Storage Layer. According to the SDL marketing, these microservices: Simplify upgrades, thus offering shorter time to value Modernize architecture, offering better separation between the web application and Tridion APIs Offer more flexibility with less downtime and improved scalability Improve quality, being self-running, contained and having less dependencies In technical words, these microservices

Following up on a previous post AJAX Component Controller , I’m going to present in this blog entry a way of rendering not only a Dynamic Component Presentation (DCP) to display its entire view, but also a way to render only a PartialView  in this DCP. The premise of the post is that sometimes we need to request minor updates to a page. These updates can be in the form of just a DCP on the page to be rendered in some AJAX architecture. However, sometimes, even rendering an entire DCP is too much. We then need the granularity to only display/update part of the DCP output. Enter the PartialView rendering. Typically an MVC .net application uses views that in turn include other smaller views, called PartialViews in order to abstract commonly used layout structures and facilitate reuse. In my situation, I had to show a section of dynamically retrieved items as part of my Device view. Since my Component view contains several such sections, it would not make sense to render the entire DCP

As a follow-up on the previous post  Move Items Between Publications , I created a simple command line utility that promotes or demotes an item using Core Service. The program is available in this blog's GitHub repository  BluePrint Move Item . Usage parameters: promote | demote -- the action to perform itemTcmUri -- the item to move destinationPublicationTcmUri -- the Publication to move item to The .config file specifies the Core Service endpoint and basicHttp user/password. Note the new endpoint for SDL Web 8:     http://cem.tridion.com/ webservices/CoreService201501.svc The following example promotes (moves up) an item to a parent Publication: Mitza.MoveItem.exe promote tcm:3-37 tcm:0-2-1 Connect to CoreService http://cme.tridion.com/webservices/CoreService201501.svc/basicHttp Connected as Administrator (IP-AC150874\Administrator) Original item:  tcm:3-37 | Publication: "020 Content" Moved item:     tcm:2-37 | Publication: "010 Schem

One of the new features in SDL Web 8 (scheduled to be released in early November, 2015) is "re-locating items in the BluePrint hierarchy". This long awaited functionality gives the possibility of moving items "up" and "down" between child-parent Publications. Of course, the user must have permissions to perform the action. This means read, create, delete permissions on the old and new Publications, so that the items can be successfully relocated. The operation checks first that all dependencies are available before performing the actual move. If there are any errors, they will be all  shown. This is a change in the approach how errors are displayed. So, rather than showing one error at a time, all errors will be shown. The walkthrough below shows a Component being promoted from Publication " 010 Schema " to Publication " 020 Content ". Initially, "My Article" resides in Publication "010 Schema" In its or

In the previous post, I was mentioning that a Component controller can be reused in both cases when the Component Presentation is embedded on the Page, as well as when it is published as Dynamic Component Presentation (DCP). In this post I will elaborate this topic. The Component controller consists of the following sample code:      public class DeviceController : MyControllerBase     {         public ActionResult Index( int ? publication, int ? component, string view)         {             Device device;              string viewName;             ResolveModelAndView< Device >(publication, component, view, out device, out viewName);             return View(viewName, device);         }     } Two things to note here: DeviceController is a specialization of MyControllerBase ; Method ResolveModelAndView is defined in a parent class and is in charge with figuring out both the strongly-typed model for the Component an