Replicate data with a multi-broker replication domain


 

+

Search Tips   |   Advanced Search

 

Use this task to mange replication domains that you migrated from a V5.x product environment.

For transitioning users: Multi-broker replication domains are not created in V7.0 product environments. However they can be migrated from existing V5.x product environments. If we migrate V5.x multi-broker replication domains, we can use the Multi-broker domain panel in the V7.0 admin console to managed these domains.trns

Although we can manage migrated multi-broker domains with the current version of the product, after you upgrade the dmgr, we can create only data replication domains in the admin console. Consider migrating any existing multi-broker domains to the new data replication domains.

If performing this task, it is assumed that you configured replication with a previous version of WAS ND, and defined replication domains that list connected replicator entries, residing in managed servers in the cell,) that can exchange data. We can manage these existing replication domains and replicator entries, but we cannot create new multi-broker replication domains or new replicator entries in the admin console.

A replicator does not need to run in the same process as the appserver that uses it. However, it might be easier to manage replicators and replication domains if a one-to-one relationship exists between replicators and appservers. During configuration, we can select the local replicator as the default replicator.

  1. Manage multi-broker replication domain settings. In the admin console, click...

    Environment | Replication domains | Multi-broker domain | multi-broker domain_name

    ...and update the values for that particular multi-broker replication domain. The default values are generally sufficient, especially for the pooling and timeout properties.

    1. Name the replication domain.

    2. Specify the timeout interval.

    3. Specify the encryption type. The DES and TRIPLE_DES options encrypt data sent between appserver processes and better secure the network joining the processes.

    4. Partition the replication domain to filter the number of processes to which data is sent. Partitioning the replication domain is most often done if we are replicating data to support retrieval of an HTTP session if the process maintaining the HTTP session fails. Partitioning is not supported for sharing of cached data that is maintained by Web container dynamic caching.

    5. Specify whether you want a single replication of data to be made. Enable the option if we are replicating data to support retrieval of an HTTP session if the process maintaining the HTTP session fails.

    6. Specify whether processes should receive data in objects or bytes. Processes receiving data in objects receive the data and class definitions. Processes receiving data in bytes receive the data only.

    7. Set a pool of replication resources. Pooling replication resources can enhance the performance of the replication service.

  2. Maintain the replicators that we have already defined. We cannot create any new replicators. The default convention is to define a replicator in each appserver that uses replication. However, we can define a pool of replicators, separate from the servers hosting applications.

    1. In the admin console, click...

      Environment | Replication domains | replication_domain_name | Replicator entries | replicator_entry_name

    2. Specify a replicator name and select a server available within the cell to which we can assign a replicator. Also specify a host name and ports. Note that a replicator has two ports (replicator and client ports) that use the same host name but have different ports.

  3. Click OK to save your changes.

 

Next steps

If we use the DES or TRIPLE_DES encryption type for a replicator, at regular intervals, such as monthly, you should click Regenerate encryption key on the Replication domains settings page. Periodically changing the encryption key enhances security.

 

Related tasks

Multi-broker replication domains
Multi-broker replication domain settings
Migrate servers from multi-broker replication domains to data replication domains
Replicating data across appservers in a cluster
Set cache replication