Page tree
Skip to end of metadata
Go to start of metadata

Introduction

This article clarifies the replication filter options available when scheduling a replication job.

Definitions

Replication filters control how document instances are replicated during a two-way replication job. They are only supported for "Normal Replication" mode, and cannot be used for refresh from origin or refresh from destination modes.

  • Replicate document templates : this option triggers the replication of any object that is not a document instance (user, folder, security, parent Crystal report, Webi document template, dashboard, ...)
  • Replicate locally run completed instances : this option triggers the replication of document instances from destination to origin only ("Locally run instances" means "Instances run on destination")
  • Replicate remote schedules : this option triggers the replication of document instances from origin to destination as well instances with remote schedule flag from origin to destination

Example 1 : report is refreshed on origin

In this example, we schedule a report on the origin site and make it so there is a mix of failed, successful and pending instances.

We then create a replication list containing that report and one user group.

We will now create and execute a replication job for that replication list, and observe the execution result depending on the replication filter settings.

No filter

configuration

result

All options are unchecked

The job fails with the error code (FWM 14003) : "Filter settings exclude everything from replication".

Document templates only

configuration

result

Replicate document templates option is checked

The job succeeds and all objects (parent report, users, users' folders, security) are replicated but the report instances. You can observe from the destination site's CMC that the parent report exists but does not have any child instance.

Locally run instances

configuration

result

Replicate locally run completed instances option is checked

The job succeeds but there is still no instance from the origin replicated on to the destination.

Here, "locally run" means run on destination.

Remote schedule

configuration

result

Replicate remote schedules option is checked

The job succeeds and all completed instances from origin are copied to the destination, whether they are failed or successful instances.

Note that pending instances are not replicated unless they are remote schedule (scheduled from the origin but meant to run on destination).

  • No labels