IBM FileNet P8, Version 5.2.1            

Replication site settings override

A storage device has a replication synchronization type of primary, secondary, or asynchronous, depending on how it is configured in the storage device connection of an advanced storage area. However, you can override the replication synchronization type of the device with site-specific settings, also set on the storage device connection of the advanced storage area. As a result, the replication synchronization type of the device can vary, depending on the site of the Content Platform Engine server instance that is uploading content to the device.

Conceptual example

Consider an example where you have two sites, one in New York, the other in London. You want users in New York and London to create content as efficiently as possible. So you create an advanced storage area with two file system storage devices. One file system device is physically located in New York, so you assign it's site as "New York". The other file system device is physically located in London, so you assign its site as "London".

For the New York site, you set the New York file system storage device as a primary replica and the London file system device as an asynchronous replica.

For the London site, you create a site setting override so that you can assign the London file system device replica as primary and the New York file system device replica as asynchronous.

As a result of this configuration, users in New York, accessing Content Platform Engine servers in New York, will create documents that are synchronously written to the New York file system storage device first. These documents will eventually be replicated asynchronously to the London site.

Likewise, users in London, accessing Content Platform Engine servers in London, will create documents that are synchronously written to the London site first. Then these documents will eventually be replicated to the New York site.

Diagrammatic representation

The following diagram shows how the replication synchronization type can be set on both the storage device and on sites that access that device. Replication synchronization type is set on a storage device connection, which associates a storage device replica to an advanced storage area.

The replication synchronization type set on the connection applies to the storage device set on the connection. A storage device is site-specific in that it is physically located in a site, and its site cannot be changed.

The replication site settings are also set on the connection. Each replication site setting specifies a site of a Content Platform Engine server instance and the replication synchronization type for that site.

Replication synchronization type set on the storage device and on sites.

The next diagram shows an example of how replication site settings override the synchronization type for a device. The storage device is in site 1, and replication site settings are defined for site 2 (there is no replication site setting for site 1). The server instance that is running in site 1 sees the device as being in site 1, and obtains the synchronization type from the storage device connection. The server instance that is running in site 2 also sees the device as being in site 1, but it obtains the synchronization from the replication site settings (instead of from the storage device connection).

Example of how replication site settings override the synchronization type for a device.



Last updated: October 2015
p8pcc227.htm

© Copyright IBM Corporation 2015.