IBM WebSphere DataPower XC10 appliance overview

  1. Introduction
  2. Topologies for multiple collectives
  3. What's new
  4. Release notes
  5. Notices


Introduction

The DataPower XC10 appliance contains a 240 GB data grid used for caching of WebSphere application data. To add more memory to the data grid, add additional appliances to the configuration to create a collective.

WebSphere Application Server drop-in scenarios:

The appliance sits between the appserver and backend tiers. In the appserver tier, WebSphere eXtreme Scale Client is installed on each node, including the dmgr. The WXS client enables the appserver tier to communicate with the appliance tier.

Data grids store application objects. Collectives group appliances together for scalability management. Zones define physical locations for appliances, and are used to determine placement of data in the cache. Each appliance can be a member of one collective and one zone. Each appliance hosts multiple data grids.

Two appliances are required to make the data grid highly available.

When we define a collective, the following information is shared among the appliances in the collective:

When information is updated, changes are persisted to all of the other appliances in the collective. The catalog service, a group of catalog servers, enables communication between appliances. Each appliance in the collective runs a catalog server, with a max of three catalog servers used per collective. If there are more than three appliances in a collective, the catalog service runs on the first three appliances that were added to the collective. If an appliance with a catalog server is removed from the collective, or an appliance with a catalog server becomes unavailable, the next appliance added to the collective runs a catalog server. The catalog server does not fail over to other appliances.

Appliances can only be in one collective. You cannot add an appliance one collective to a different collective. You also cannot join two collectives into a single collective. To join appliances from separate collectives, remove each appliance from its respective collective, making each appliance stand alone. Then create a new collective that includes all of the appliances.

To add an appliance to a collective, we add the host name and secret key for the appliance to the collective configuration panel in another appliance. Because membership information is persisted among the members, configuration changes can be done from any appliance in the collective.

To make a change, log in to any appliance in the collective, and go to...


Zones

Zones are associated with a physical location of the appliance, such as a city or rack location in a lab. Zones help the catalog service to define where the data in the data grids is stored. For example, if the primary information for the data grid is stored in a given zone, then the replica data is stored in an appliance that is in a different zone. With this configuration, failover can occur from the primary to a replica if the appliance that holds the data grid primary fails.


Data grids

Data grids hold the cached objects for the applications. There are three types of data grids:


Data grid replicas

Replicas are created when there are at least two appliances in the collective. If there is only one appliance, no replicas are created. The maximum number of replicas is n-1, because one appliance hosts the primary data grid. Editing replica settings requires that data grids be cleared, set intial values carefully. As new appliances join the collective, additional replicas are created. Primary and replica data grids are evenly distributed, or striped, across all of the appliances in the collective. As new appliances join the collective, rebalancing occurs to distribute the primary and replica data grids.

Replicas can be synchronous or asynchronous. Synchronous replicas receive updates as part of the transaction on the primary data grid. Asynchronous replicas are updated after the transaction on the primary data grid is committed. Synchronous replicas guarantee data consistency, but can increase the response time of a request when compared with an asynchronous replica. Asynchronous replicas do not have the same guarantee in data consistency, but can make your transactions complete faster. A data grid has one asynchronous replica by default. A placement algorithm controls where the replicas are located.


Maps

Contain data for the grid in key-value pairs. A single data grid has multiple maps. Client apps can connect to a specifically-named map, or dynamic maps, which are automatically created, can be used..


Collective links

A single collective should 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:

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.


Topologies for multiple collectives


New in Version 2.0

WebSphere DataPower XC10 appliance Version 2.0 includes enhanced appliance hardware, the ability to enable capacity limits on data grids, SNMP support, and integration with WebSphere Portal.


Multimaster replication support

Replicate data grid data across appliances that have unreliable network connectivity.


xscmd utility

New supported version of the old xsadmin utility, which was included as an unsupported sample in previous releases.


xsloganalyzer tool

Generate reports from log files to analyze the performance and troubleshoot issues.


HTTP command interface

Run operations with HTTP POST JSON statements that you can combine into scripted operations to configure appliance settings and administer data grids, collectives and zones.


IPv6 support

Internet Protocol Version 6 (IPv6), which is the next evolution in Internet Protocol beyond the IPv4 standard. The key IPv6 enhancement is the expansion of the IP address space from 32 bits to 128 bits, enabling virtually unlimited IP addresses.


Least recently used (LRU) policy support

When setting the maximum capacity on a simple grid, you can choose to specify an LRU policy.


Eviction policy support

With Simple Grids, a default map and a set of dynamic maps are created. By default, a time-to-live (TTL) eviction policy is required when you create a dynamic map with one of the provided templates, where you can choose an eviction policy of creation time, last-update-time, or last-access-time. You can now change this behavior so that an eviction policy is set on both a dynamic map and default map on a simple grid.


Appliance Type 7199-92x

New with Version 2.0. Includes faster processors, more network ports, and more cache capacity.


Data grid capacity limits

Define a maximum capacity for each data grid in a collective. Configuring a maximum capacity limits the amount of data storage that a particular data grid can use. The capacity limit ensures that the available storage capacity for the collective is used in a predictable manner.


Simple Network Monitoring Protocol (SNMP) support

Use SNMP to monitor the status of an appliance as a part of a larger group of systems in a data center.


WebSphere Portal integration

Persist HTTP sessions from WebSphere Portal into a data grid on the appliance.


Data grid inserts are rejected when physical data storage reaches full capacity

When the included 240 GB cache is full, the physical data storage is at its maximum capacity. Any insert or operations on the data grid are rejected, but read and delete operations can continue. To prevent the physical data storage from reaching full capacity, you can configure capacity limits on the data grids in the collective.


Firmware performance improvements

The Version 2.0 firmware includes throughput performance improvements that apply to both Type 9235-92X and Type 7199-92X appliances. Performance varies depending on the workload and environment.


WebSphere Commerce integration

WebSphere Commerce Version 7.0.0.1 now supports the use of WXS client Version 7.1. Use the WebSphere DataPower XC10 appliance to cache dynamic cache data from WebSphere Commerce.


Release notes and technotes

  1. WebSphere DataPower XC10 appliance Support Web page
  2. Search the Support Web page
  3. Library page