Use this task to manage replication domains that you migrated from a Version 6.x or
earlier product environment.
Before you begin
For transitioning users: Multi-broker replication domains are not created in Version 7.0 product
environments. However they can be migrated from existing Version 6.x product environments. If you
migrate Version 6.x multi-broker replication domains, you can use the Multi-broker domain panel in
the Version 7.0 administrative console to manage these domains.
Although you can manage migrated multi-broker domains with the current version of the product,
after you upgrade your deployment manager, you can create only data replication domains in the
administrative console. Consider migrating any existing multi-broker domains to the new data
replication domains.
About this task
If you are performing this task, it is assumed that you configured replication with a
previous version of the product, and defined replication domains that list connected replicator
entries, residing in managed servers in the cell that can exchange data. You can manage these
existing replication domains and replicator entries, but you cannot create new multi-broker
replication domains or new replicator entries in the administrative console.A replicator does not
need to run in the same process as the application server that uses it. However, it might be easier
to manage replicators and replication domains if a one-to-one relationship exists between
replicators and application servers. During configuration, you can select the local replicator as
the default replicator.
Procedure
-
Manage multi-broker replication domain configuration settings.
In the administrative console, click .
-
Click 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.
-
Name the replication domain.
-
Specify the timeout interval.
-
Specify the encryption type. The DES and TRIPLE_DES options encrypt data sent between
application server processes and better secure the network joining the processes.
-
Partition the replication domain to filter the number of processes to which data is sent.
Partitioning the replication domain is most often done if you 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.
-
Specify whether you want a single replication of data to be made. Enable the option if you are
replicating data to support retrieval of an HTTP session if the process maintaining the HTTP session
fails.
-
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.
-
Configure a pool of replication resources. Pooling replication resources can enhance the
performance of the replication service.
-
Maintain the replicators that you have already defined. You cannot create any replicators. The
default convention is to define a replicator in each application server that uses replication.
However, you can define a pool of replicators, separate from the servers hosting applications.
-
In the administrative console, click
replication_domain_namereplicator_entry_name.
-
Specify a replicator name and select a server available within the cell to which you 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.
-
Click to save your changes.