Infinispan Installation: Difference between revisions
| Line 29: | Line 29: | ||
=Isolated Self-Contained Standalone Profile= | =Isolated Self-Contained Standalone Profile= | ||
Follow the procedure described here: [[WildFly_Isolated_Self-Contained_Standalone_Profile|WildFly Isolated Self-Contained Standalone Profile]] | Follow the procedure described here: | ||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[WildFly_Isolated_Self-Contained_Standalone_Profile|WildFly Isolated Self-Contained Standalone Profile]] | |||
</blockquote> | |||
Details particular to JDG: | Details particular to JDG: | ||
Revision as of 01:18, 15 July 2016
Internal
Overview
This section applies only if Infinispan is installed as a standalone JBoss Data Grid server or cluster. If used within WildFly, installation is irrelevant, Infinispan comes pre-bundled as a sub-system.
Relevance
JDG 6.6
Procedure
A JDG server instance is a WildFly/EAP server instance, so the installation procedure is similar. The JAR expansion directory should be exported as the JDG_HOME environment variable.
In order to run a local instance:
$JDG_HOME/bin/standalone.sh
In order to run a clustered instance:
$JDG_HOME/bin/clustered.sh
Isolated Self-Contained Standalone Profile
Follow the procedure described here:
Details particular to JDG:
1. The XML configuration file corresponding to a clustered configuration is $JDG_HOME/standalone/configuration/clustered.xml and the one corresponding to a local configuration is $JDG_HOME/standalone/configuration/standalone.xmll. These need to be copied in the profile's configuration directory instead of standalone-ha.xml, etc.
2. The .conf files are $JDG_HOME/bin/clustered.conf, respectively $JDG_HOME/bin/standalone.conf.