This topic is intended for administrators and developers with administration access rights in Episerver.
Content channels is an APIApplication programming interface. The API specifies how some software components should interact with each other, such as accessing a database or computer hardware, or easing the work of programming graphical user interface components. APIs often are in the form of a library that includes specifications for routines, data structures, object classes, and variables. to allow external systems to push content to Episerver CMS. Each channel consists of a number of settings that define the content, content types and properties to be retrieved.
Create a content channel as follows:
- On the Admin tab, select Content Channels.
- Click Add.
- In Channel name, name the channel. Note that the name you enter here is used when configuring the external system.
- In Page root, select where in the tree structure you want the pages from the external system to be displayed.
- In Block root, enter the path to the tree structure where you want the block library from the external system to be displayed.
- In Virtual root for files, enter the path in the tree structure where you want the media library from the external system to be displayed.
- In Save action, select one of the following options to define which status the content receives when transported to Episerver CMS:
- None. Set the save action to None if you do not want any content to be retrieved from the external system. This can be seen as a way of switching the channel off.
- Save. The content is imported so that it has status Not ready.
- Check in. The content is imported so that it has status Ready to publish.
- Publish. The content is imported and published.
- In Default content type, state which content type you want to be used as default when retrieving content from the external system.
- Map the content type properties according to the instructions below and click Add.
All content type properties in Episerver CMS have a corresponding property in the external system. It is necessary to map these properties so that Episerver CMS knows which content should be transported to which property in the content types.
Select the unmapped content type from the Unmapped content types drop-down list. Change the property names in the Mapped Property column so that they correspond to the properties in the external system and click Add Property Mapping for Content Type. The content type with the mapped properties now appears in the Mapped content types drop-down list.
Select the content type from the Mapped content type drop-down list, change the properties and click Update Property Mapping for Content Type.
Select the content type from the Mapped content type drop-down list, change the properties and click Remove Property Mapping for Content Type.