Administer collectives and zones
- Create a collective
- Create and modify zones
- Configure replication between collectives
Create a collectiveFor availability, scalability and management purposes we group multiple appliances into collective. To create a collective, add all the host names and secret keys for all the appliances to group into a collective to the configuration of the one of the appliances. The appliance can communicate all configuration information to other appliances, including...
- Select a single appliance to which you are adding the host names and secret keys for the other appliances in the collective.
Open a new browser window and run...
Collective | Members
A list of the appliances in the collective displays.
The appliance that you are logged in to is marked with the console icon (). Note the Host name and Secret key for this appliance.
Icon Definition Indicates the appliance that you are logged into, and that the appliance is running. Indicates that the appliance is started and is available for configuration and use. Indicates that the appliance is stopped and is not available.
- Add the host name and secret keys for each of the appliances to one of the appliances in the group.
- In the user interface, click...
Collective | Members
- Click the add icon ( ).
- Enter the Host name and Secret key for the appliance to add to the collective.
- Monitor the progress of the addition of the appliances to the collective with the Tasks view. In the user interface, click Tasks.
The appliances are grouped into a collective for scalability and management purposes.
Create and modify zones
Use zones to specify a physical location of your appliance. This physical location might be two different areas of a power grid within the same data center, or appliances that are in completely different data centers, perhaps in different parts of the country.
Before you create and configure zones, install, configure, and assemble your appliances into a collective. You can then select the appliances in your collective to be in particular zones. If you add an additional appliance to the collective after zones have been created, you can specify the zone when you add the appliance.
By specifying zones to physically demarcate the location of your appliances, the data that is stored in your data grids can be placed in a proper location. The DataPower XC10 appliance uses zones to determine where to place primary and replica information for the cache. For example, if a primary data grid is in zone 1, then the replica for that data grid would be in zone 2. If you only have one zone, then no replicas are created.
When an appliance is first initialized, it is added to the default zone, which is called DefaultZone. When you add your appliances to zones that you create, they are removed from the DefaultZone zone. You cannot add appliances back to the DefaultZone zone after they have been removed.
- In the user interface, click Collective > Zones.
- Add zones. Click Add Zones. Specify a name for the zone to add. The zone name displays on the console page. You can repeat these steps if you are creating multiple zones.
- Add appliances to the zone. Expand the zone name and select appliances to add to the zone. Repeat these steps until all your appliances in the collective have been added to zones. Each appliance must be in a zone. A single zone cannot contain appliances from different collectives.
- Apply the zone changes. Your zone changes are not effective until after you click Activate Zone Changes. To change your zone information, you can click the delete icon () to remove a zone or click Reset Zone Changes to reset the zones to the last configuration that you activated.
DataPower XC10 appliance can create primary and replica data caches based on the physical locations, or zones, that you defined. You can view or change the topology of your zones at any time by clicking Collective > Zones in the user interface.
Create and configure the applications and data grids.
Configure replication between collectives
By establishing collective links between the catalog servers in your collectives, you can asynchronously replicate data between data grids in two different collectives.
- You must have at least two collectives configured. For data to replicate between the collectives, create identical data grid configurations in each collective.
- Decide which type of multiple collective topology you want to define.
A single collective does not span an unreliable network because false positive failure detections might occur. However, you might still want to replicate data grid data across appliances that have unreliable network connectivity. Some common scenarios where you might want to use this type of topology follow:
- Disaster recovery between data centers where one collective is active and the other is used for backup.
- Geographically distributed data centers where all collectives are active for geographically close clients.
After you connect two collectives, any data grids that have the same names are asynchronously replicated between the collectives. These data grids must have the same number of replicas in each collective, and must have the same dynamic map configurations.
- Establish a link between the collectives.
- Establishing collective links with the xscmd utility:
- Get the catalog server IP address and port for the catalog servers in each collective. In the user interface, click Collective > Members > collective_member_name. A list of catalog servers and port numbers is displayed. Repeat this step for each collective to connect.
- Connect the xscmd utility to one of the collectives.xscmd.sh -ts xsatruststore.jks -tst jks -ssl -tsp xc10pass -user xcadmin -tsp xcadmin -cep myxc10.mycompany.com:2809 [additional_xscmd_parameters]
- From the collective to which you are currently connected...xscmd -c establishLink -cep myxc10.mycompany.com:2809 -fd dname -fe myxc102.mycompany.com:2809,myxc103.mycompany.com:2809
In the previous example, the parameter...
...gives a name to the remote collective.
...lists the catalog servers within the foreign collective to which you want to connect.
When the link is established, the catalog servers in the collectives begin to replicate with each other. You do not need to establish the link in both directions.
- To dismiss links between collectives....