Chapter 8. Run a Red Hat JBoss Data Grid as a Node without Endpoints
8.1. Run a Red Hat JBoss Data Grid as a Node without Endpoints
Services send messages using channels to communicate with each other. An endpoint is a communications point for these services and is used to send and receive the messages sent through the channels. As a result, a node with no endpoints can communicate with other nodes in the same cluster, but not with clients.
8.2. Benefits of a Node Without Endpoints
The primary benefit for creating a node without endpoints in Red Hat JBoss Data Grid involves data replication.
A node without any endpoints cannot be accessed by the client directly. As a result, they are primarily used to replicate data from other nodes that can communicate with clients. The result is a node with a backup copy of the data that cannot be accessed by the client, which protects it from failure via an error sent by the client.
8.3. Sample Configuration for a Node without Endpoints
Red Hat JBoss Data Grid provides a sample configuration to configure a node without an endpoint:
Find the JBoss Data Grid Sample Configuration for a Node Without Endpoints
Extract the JBoss Data Grid ZIP
Extract the ZIP file for JBoss Data Grid Remote Client-Server mode. This is named jboss-datagrid-server-${version} . Add the relevant version to the file name.
Navigate to the Appropriate Folder
In the extracted folder, navigate to the $JDG_HOME/docs/examples/configs folder.
Find the Configuration File Sample
View the clustered-storage-only.xml file, which contains the configuration for a node with no endpoints.
8.4. Configure a Node with No Endpoints
A standard configuration, such as a standalone high availability configuration, can be changed into a configuration for a node with no endpoints by removing the endpoints subsystem from the configuration file.
Remove the XML element that begins with the following:
<subsystem xmlns="urn:infinispan:server:endpoint:8.0">
Removing the endpoints subsystem ensures endpoints are removed from the configuration and that clustering is not possible.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.