![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Seeders play an active role in maintaining the space by providing CPU and RAM.
• Leeches play a passive role. They have access to space data but provide no resources.Figure 1 Client-Server DeploymentFor more information on deploying seeders and leeches in the ActiveSpaces network, see When to Join the Space as a Seeder or a Leech in the TIBCO ActiveSpaces Developer’s Guide.ActiveSpaces allows you to persist data to disk storage and recover it if data loss occurs or there is a problem with cluster startup. For detailed information on persistence, see Persistence in the TIBCO ActiveSpaces Developer’s Guide.Figure 2, Deployment with Shared-All Persistence shows all of the seeder nodes in an ActiveSpaces sharing a single database for persistence and data recovery.Figure 3, Deployment with Shared-Nothing Persistence shows a group of seeder nodes that persist data to local hard disk.where group_name can be any name which helps you to identify the grouping of seeder members. For example, the group_name can be the name of the machine on which the seeders are running or some other arbitrary name that logically identifies the group of seeders.
Host-aware replication is purely based on the group_name part of the member name of the seeder, and not on the IP address of the physical host the process is running on.Figure 4, Sample Deployment with Host-Aware Replication shows a topology for host-aware replication in which each host is running four seeders and a seeder grouping is defined for each host.The first host is named Host1, and runs four seeders, Seeder1, Seeder2, Seeder3, and Seeder4. The second host is named Host2, and the third host is named Host3. Each of these hosts also runs four seeders.
1. By using the TIBCO ActiveSpaces API programs in an application program that implements <group_name>.<member_name> member names.For information on the API functions to implement host-aware replication, see Using the ActiveSpaces API Set to Implement Host-Aware Replication in the TIBCO ActiveSpaces Developer’s Guide.
2. For example, you might use as-agent with the -name parameter to start four seeders on each host. For example, on host 1, run as-agent as follows:Then run two additional instances, with the -name parameter specifying Host1.Seeder2, and Host1.Seeder3.
3. By using as-admin to connect to a metaspace. The member name is specified using the membername option of the connect command.Figure 5 Remote Client DeploymentFigure 6, Concurrency with Remote Clients, shows remote clients updating to a seeder (Member 1). The seeders in the metaspace ensure that the data replicated on Member 2 synchronized with the data on Member 1.Figure 6 Concurrency with Remote Clients
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |