Initializing PadoGrid - padogrid/padogrid GitHub Wiki

◀️ Root Workspaces Environments (RWEs) 🔗 Bash Auto-Completion ▶️


The first RWE you create initializes PadoGrid for all the subsequent RWEs you create thereafter. If you installed PadoGrid using install_padogrid, then you have already created your first RWE; otherwise, if you have manually installed PadoGrid, then you can run the create_rwe command to create your first RWE. When you execute the create_rwe command, it interactively displays step-by-step instructions.

✏️ If you installed PadoGrid using install_padogrid, then skip this section.

  1. Initialize PadoGrid environment. This is an interactive command. Enter valid values for all prompts.
~/Padogrid/products/padogrid_0.9.32/bin_sh/create_rwe \
-path ~/Padogrid/workspaces -rwe myrwe -cluster myhz
  1. If you installed Hazelcast Enterprise and/or Jet Enterprise, then enter their license keys in the ~/Padogrid/workspaces/myrwe/.hazelcastenv.sh file as shown below (Others do not require license keys).
vi ~/Padogrid/workspaces/myrwe/.hazelcastenv.sh

# Enter license keys
IMDG_LICENSE_KEY=***
JET_LICENSE_KEY=***
MC_LICENSE_KEY=***

Each product has their own environment file named, .<product>env.sh, in the RWE directory. You may enter any product specific initialization routine and variables in these files. The following is a complete of product environment files.

  • .coherenceenv.sh
  • .geodeenv.sh (Geode and GemFire)
  • .hadoopenv.sh
  • .hazelcastenv.sh (Hazelcast IMDG and Jet)
  • .kafkaenv.sh
  • .mosquittoenv.sh
  • .redisenv.sh
  • .snappydataenv.sh (SnappyData and ComputeDB)
  • .sparkenv.sh
  1. Source in the generated initenv.sh file. initenv.sh sets the required environment variables including PATH.
. ~/Padogrid/workspaces/myrwe/initenv.sh
  1. Add the above line to .bashrc (.bash_profile, etc) so that the required environment variables are automatically set when you login next time. By sourcing in initenv.sh, you are setting the default RWE. If you create additional RWEs under the same directory as myrwe, i.e., ~/Padogrid/workspaces, then you only need to source in one of the RWE's initenv.sh file. The one that you source in becomes the default reference to all other RWEs. All PadoGrid operations are performed relative to the default RWE.

❗️ It is important to include the -quiet option if you are sourcing in initenv.sh from the login startup file (.bashrc, .bash_profile, .profile, etc.) Without the -quiet option, the PadoGrid VM (ssh) commands may not work properly due to the console outputs generated by initenv.sh.

# For .bashrc
echo ". ~/Padogrid/workspaces/myrwe/initenv.sh -quiet" >> ~/.bashrc

# For .bash_profile
echo ". ~/Padogrid/workspaces/myrwe/initenv.sh -quiet" >> ~/.bash_profile

◀️ Root Workspaces Environments (RWEs) 🔗 Bash Auto-Completion ▶️

⚠️ **GitHub.com Fallback** ⚠️