Developing applications to write to multi-partition transactions for WebSphere eXtreme Scale in a stand-alone environment
You can write an application for a distributed data grid with multiple partitions in your stand-alone WebSphere® eXtreme Scale environment.
Before you begin
Enable the eXtremeIO protocol. For more information, see Configuring IBM eXtremeIO (XIO).
Restriction: You should note the following restrictions before developing
applications to write to multi-partition transactions.
- You cannot use multi-partitions in a WebSphere eXtreme Scale Client in a .NET environment.
- BackingMaps that are configured with a Loader plug-in can read but cannot write to the map in a multi-partition transaction.
- BackingMaps that are using locking strategy as NONE cannot participate in multi-partition transactions.
About this task
- TxCommitProtocol.ONEPHASE: A transaction commit protocol constant that indicates that the transaction must be committed with the default one-phase commit. With this option, a transaction can read from multiple partitions but can write to a single partition only. A TransactionException exception occurs if the transaction writes to multiple partitions.
- TxCommitProtocol.TWOPHASE: A transaction commit protocol constant that indicates that the transaction must be committed either with the one-phase commit or two-phase commit. If the transaction writes to a single partition then the one-phase commit protocol is used. Otherwise, the two-phase protocol is used to commit the transaction, involving write operations to multiple partitions.