Configuring the Content Engine

You now need to configure a Content Engine link header plug-in component that can access the CCI Newsgate web server you configured in the previous step. For general information about link header plug-ins and how to configure them, see the Escenic Content Engine Advanced Developer Guide.

You can base your component on the default link header plug-in supplied with the Content Engine. To do this you must create a .properties file in one of your configuration layers. You can call it anything you like, and put it anywhere you like in the configuration layer. You might, for example, call it configuration-root/com/escenic/newsgate/publication/NewsgateInfo.properties, and give it the following contents:

$class=com.escenic.webservice.spi.DefaultLinkHeaderPlugin
vendor=myCompany.com
version=1.0-1
description=Retrieves CCI Newsgate info for display in Content Studio

relation=CCI-Newsgate
mimeType=text/html
title=CCI Newsgate sample
uriTemplate=http://newsgate.myCompany.com/{content-type}/{source}/{sourceid}
objectLoader=/io/api/ObjectLoader

All the properties shown in the above listing must be specified, but the values are just examples. For a description of the properties and advice on how to set them, see the Escenic Content Engine Advanced Developer Guide.

When you have done this, you must also add a configuration-root/com/escenic/service/LinkHeaderManager.properties file to the same configuration layer, and define a service property for your new component. For example:

$class=com.escenic.webservice.manager.LinkHeaderPluginManager

service.myProvider-1=/com/escenic/newsgate/publication/NewsgateInfo

For additional information about this, see the Escenic Content Engine Advanced Developer Guide.