Installation on z/OS
Java 8+, tested with IBM J9 VM.
Download the GridGain binary as a zip archive.
Unzip the zip archive into the installation folder in your system.
(Optional) Enable any of the modules you might want to use.
After unpacking the distribution package, make sure that all text files (e.g. xml, .sh, text, properties) are properly tagged as text and have a UTF-8 or ISO 8859-1 encoding. Use the
chtagutility to do that.
The following command adds a
txtflagto all files in the
chtag -t -R -c ISO8859-1 gridgain-community-8.7.17/bin/
Run this command on the configuration file and the license file.
Now you can launch a node.
To verify that installation is successful, go to the distribution directory and run the following command:
gridgain-community-8.7.17/bin/ignite.sh -v config/default-config.xml
If the node starts successfully, you will see the following message in the console:
MEMLIMITparameter. The parameter defines the limit on memory for a single process. Set it to a value that is larger than the RAM memory required for your GridGain nodes, including Heap and Off-Heap data regions.
We recommend to always specify
-Dfile.encoding=UTF-8JVM argument. You do not need to specify it if you start GridGain by running
ignite.sh. However, if you start nodes from custom code, add it to the startup parameters of your application.
If you are going to use the Native Persistence feature, set the
IGNITE_WAL_MMAPsystem property (or environment variable) to
false, for example, by adding
Configure static discovery instead of the default multicast option. Specify the
TcpDiscoverySpi.localAddressproperty and the
IgniteConfiguration.localHostproperty with the preferred IP address for the current host.
If you are going to use log4j for logging, add the following parameter to every appender in the log4j configuration:
<param name="Encoding" value="IBM-1047"/>
sqllineutility is used, it should be invoked as
TERM=dumb bin/sqlline.shto avoid incorrect terminal detection.
For nodes with a persistent storage, increase the
dataStorage.checkpointThreadsvalue. The default value is
4, but we recommend you set it to a value between
32on z/OS nodes for best checkpointing speed.
If your load profile includes intensive network usage, consider the following
usePairedConnections=true, pick the
connectionsPerNodevalue from between
Nodes may benefit from a larger striped pool size, increase it by setting