Internal replication domain settings
Configure a replicator instance.
Environment > Internal Replication Domains > replication_domain_name.An appserver connected to replicator within a domain can access the same set of data sent out by any appserver connected to any other replicator (including the same replicator). Data is not shared across replicator domains.
Configuration tab
Name
- Specifies a name for the replication domain.
Data type String
Request Timeout
- Specifies the number of seconds that a replicator waits when requesting information from another replicator before giving up and assuming the information does not exist. The default is 5 seconds.
Data type Integer Units Seconds Default 5
Encryption Type
- Specifies the type of encryption used before transfer. The options include NONE, DES, TRIPLE_DES. The default is NONE. The DES and TRIPLE_DES options encrypt data sent between WebSphere processes and better secure the network joining the processes.
If you specify DES or TRIPLE_DES, a key for global data replication is generated after you click Apply or OK. When you use the DES or TRIPLE_DES encryption type, click RegenerateKey at regular intervals such as monthly because periodically changing the key enhances security.
Data type String Default NONE
DRS Partition Size
- Specifies the number of groups into which a replication domain is partitioned. By default, data sent by a WebSphere Application Server process to a replication domain is transferred to all other WebSphere Application Server processes connected to that replication domain. To filter or reduce the number of destinations for the data being sent, partition the replication domain. The default partition size is 10, and the partition size should be 10 or more to enhance performance.
Partitioning the replication domain is most often done if you are replicating data to support retrieval of an HttpSession if the process maintaining the HttpSession fails. Partitioning is not supported for sharing of cached data maintained by Web container dynamic caching. As to dynamic caching, all partitions or groups are always active and used for data replication.
When you partition a replication domain, you define the total number of groups or partitions. Use this setting to define the number of groups. Then, when you configure a specific session manager under a Web container or as part of an enterprise application or Web module, select the partition to which that session manager instance listens and from which it accepts data. To specify the groups to which an application server listens, change the settings for affected servers on a Session Manager page. In addition, you can set a replicator role for a server. This replicator role affects whether a WebSphere process sends data to the replication domain, receives data, or does both. The default is both to receive and send data.
Data type Integer Default 10
Single Replica
- Specifies that a single replication of data be made. Enable this option if you are replicating data to support retrieval of an HttpSession if the process maintaining the HttpSession fails. This option restricts the recipient of the data to a single instance.
This setting provides filtering beyond grouping or partitioning. Using this setting, you can choose to have data only sent to one other listening instance in the replication domain.
Data type Boolean Default false
Serialization Method
- Specifies the object serialization method to use when replicating data. An administrative concern with replicating Java objects is locating the class definition, especially in a J2EE environment where class definitions might reside only in certain web modules or enterprise applications. Object serialization methods define whether the processes receiving data also need the class definition.
The options for this setting are OBJECT and BYTES. The default is BYTES.
OBJECT instructs a replicator to write the object directly to the stream. With OBJECT, a replicator must reinstantiate the object on the receiving side so must have the class definition.
BYTES instructs a replicator to break down the object into bytes and then send only the bytes across the stream. With BYTES, a replicator does not need to instantiate the object on the receiving side. The BYTES option is useful for failover, where the data is not used at the receiving side and thus the class definitions do not need to be stored there. Or, the option requires that you move class definitions from the Webapp class path to the system class path.
Data type String Default BYTES Range Valid values are OBJECT or BYTES.
DRS Pool Size
- Specifies the maximum number of items allowed in a pool of replication resources. The default is 10.
Pooling replication resources can enhance the performance of the WebSphere internal data replication service.
Data type Integer Default 10 Range 1 to 50
DRS Pool Connections
- Specifies whether the data replication service includes replicator connections in a pool of replication resources. Whether this option is enabled or not, the pool includes replicator sessions, publishers and subscribers.
The default is not to include replicator connections in the pool.
Data type Boolean Default false
Replication domain
Replicating data
Administrative console buttons
Administrative console page features
Internal replication domain collection
Replicator entry collection
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.