Open Content
Docs homeNaviga web
  • Introduction
  • Overview
  • Key features
  • Meta data standards
  • Architecture
  • Open Content API
  • Headless and end-to-end CMS workflows
  • Use and explore
    • How does it work
    • Open Content Docker
    • OC REST API
    • Event logs
    • Replication
    • Open Content Notifier
    • New JSON API:s - CCA and Duppy
    • Terminology: Other backend services
    • Lab: upload
      • Curl for object upload
      • Environment
      • Lab 0: Configuration
      • Lab 1: Concept upload
      • Lab 2: Image upload
      • Lab 3: Article Upload
      • Lab 4: Search
      • Lab 5: Delete objects
      • Lab 6: Event sourcing using event log
  • Releases
    • Release documentation and admin guides
      • Open Content 2.3
    • New in OC 3.0 (draft)
      • Removed features in OC 3.0
  • XLibris Archive
    • Archive everything you ever created or published
    • Import content to XLibris
Powered by GitBook
On this page
Export as PDF
  1. Use and explore

Replication

Replication is an Open Content Service responsible for copying items between different Open Content instances

Open Content Replicator is a module that allows the Open Content to replicate content to an Open Content Satellite. The OC Satellite works as a "read only" and can store anything from all of the information in the Master to a part of it.

The Replicator can be run automatically in near real time and/or be triggered manually in batches.

For example, a satellite can consist of content with a specific setup of meta data (products, categories etc.) and another satellite can have a different content

Open Content Replicator is in this environment:

http://localhost:8180/replication

The replicator can be used to replicate objects from one Open Content to another Open Content.

Different types of replication exists:

  • Full replication; replicate objects using a query

  • Incremental replication; replicate object on incremental re-indexing event. Uses RabbitMQ Indexer needs to be configured for this.

    • used for replication between editorial and public Open Content.

  • Batch replication; replicate objects on batch re-indexing event. Uses RabbitMQ Indexer needs to be configured for this.

    • almost never used

  • Partial replication; updates target Open Content for filter changes

    • not used

  • Event-log replication; polls event-log or content-log

PreviousEvent logsNextOpen Content Notifier

Last updated 5 years ago