Use this page to configure a replicator instance.
To view this administrative console page, click Environment > Internal Replication Domains > replication_domain_name.
An application server connected to replicator within a domain can access the same set of data sent out by any application server connected to any other replicator (including the same replicator). Data is not shared across replicator domains.
Configuration tab
Data type | String |
Data type | Integer |
Units | Seconds |
Default | 5 |
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 |
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 |
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 |
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 Web application class path to the system class path.
Data type | String |
Default | BYTES |
Range | Valid values are OBJECT or BYTES. |
Pooling replication resources can enhance the performance of the WebSphere internal data replication service.
Data type | Integer |
Default | 10 |
Range | 1 to 50 |
The default is not to include replicator connections in the pool.
Data type | Boolean |
Default | false |