The steps described in this page will walk you through the process of deploying DPOD's software on the appliance created in the Appliance Installation phase.
- 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:
installApp
- Adjust Date, Time and TimeZone if required
- Update NTP services and servers
- Read the End User License Agreement (EULA) and if you accept the term please 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
t
Option 1 - AIO_Developer_appliance.arch.properties is found only in Light Edition ISO file.
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 option that fits your requirements (you may consult the information found in the Hardware and Software Requirements page).
- Note that the list might change, and the options available to you may not 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 /app/scripts
./montier_env_uninstall.shRerun installation from step 3 but this time run command :
installApp --clean
Wait for the installation to finish.
After displaying the messages "Stopping/Starting ...", the installation will work in silent mode - without any further messages for ~ 5 minutes, this is a normal behavior.
When the install is completed, you should see the following output:
r in screenshotAny errors will be logged to the installation log file, displayed at the end of the installation process.
The /installs/logs directory contains detailed install logs for each component.
Login again as root or just use the "su -" command
su -
continue to Installation Verification.
Light Edition Only
Minimize Resource Consumption - In this version, NO special steps required to install Light Edition as was in previous versions