...
- Log in to DPOD's VM Console with the user "root" (Do not use an SSH terminal here. For security reasons, SSH sessions are limited to 300 seconds and your session might time out during installation).
- run "df -h" and make sure the three required disks were mounted and are in the correct order (OS, Install and Data disks, as explained on Hardware and Software Requirements)
Run the installApp command to start the product installation:
Code Block language bash theme RDark installApp
- Read the End User License Agreement (EULA) and press 1 to accept it. You may also press 0 to decline the agreement and abort the installation.
On the following screen, the installation program will prompt you to select an installation configuration file
todo: change diagram to new-namet
Note Option 1 - AIO_Developer_appliance.arch.properties Exists only in Light Edition ISO file !
Note In some special cases, DPOD's support team will send you a custom configuration file. This would be the time to FTP it to the appliance,
following the instructions received from DPOD's support team.- Select the configuration file option that fits your option (you may consult with the information found in the Hardware and Software Requirements page).
- Please be aware that list might change, and the options available to you may not completely match the list shown above
- Unless otherwise instructed by DPOD Software team, use the AIO_medium_resource_appliance.arch.props
If you choose to abort the installation at this stage (e.g. by using CTRL-C) and wish to start the process again at a later time, you will have to run the following command in order to start the installation again:
cd /installs/MonTierInstaller/
./montier_env_install.sh –-clean –r montier-environment-1.0-1.x86_64.rpm
Wait for the installation to finish.
After printing the messages "Stopping/Starting MonTier", the installation will be silent without any further messages for 5 to 10 minutes, this is a normal behavior.
When it is done, you should see the following output:
todo:montier r in screenshotErrors are logged to the installation log file, displayed at the end of the installation process.
The /installs/logs directory contains detailed logs for each component.
Login again as root or just use the su command and continue to Installation Verification.
...