Infinispan Installation: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
=Procedure= | =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 <tt>JDG_HOME</tt> environment variable. | 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 <tt>JDG_HOME</tt> environment variable. | ||
In order to run a local instance: | |||
<pre> | |||
$JDG_HOME/bin/standalone.sh | |||
</pre> | |||
In order to run a clustered instance: | |||
<pre> | |||
$JDG_HOME/bin/clustered.sh | |||
</pre> | |||
Revision as of 23:53, 26 May 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