> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/10.2-install/multidimensional-data-modeling-in-pentaho/mondrian-cache-control/modify-the-jgroups-configuration.md).

# Modify the JGroups configuration

The default Infinispan configuration uses JGroups to distribute the cache across all Mondrian instances it finds on the local network. If you want to modify how those communications are done, you must edit the JGroups configuration file.

**Note:** The segment cache features explained in this section are for very large OLAP deployments.

Each node might require a different configuration; the default configuration is highly portable.

If you are deploying this plugin on Amazon EC2, JGroups has a special configuration file that you copied to your `/WEB-INF/classes/` directory when you installed the Analysis Enterprise Edition package. Additionally, default JGroups configuration files are inside of the JAR archive.

**Note:** Fine-grained JGroups configuration is covered in the [JGroups documentation](http://www.jgroups.org/ug.html); you should read through it before making changes.

To switch implementations, edit `infinispan-config.xml` and make the modification appropriate to your communication method:

<table data-header-hidden><thead><tr><th></th><th></th></tr></thead><tbody><tr><td>Communication Type</td><td>Configuration Entry</td></tr><tr><td>UDP communication</td><td><pre><code>&#x3C;property name="configurationFile" value="jgroups-udp.xml"/>
</code></pre></td></tr><tr><td>TCP communication</td><td><pre><code>&#x3C;property name="configurationFile" value="jgroups-tcp.xml"/>
</code></pre></td></tr><tr><td>Amazon EC2</td><td><pre><code>&#x3C;property name="configurationFile" value="jgroups-ec2.xml"/>
</code></pre></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/install/10.2-install/multidimensional-data-modeling-in-pentaho/mondrian-cache-control/modify-the-jgroups-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
