Why is the original JDK uninstalled during the installation of Enterprise Distributed Application Service (EDAS) Agent?
During the installation of EDAS Agent, not only EDAS Agent is installed, but also
its dependencies are installed, such as
JDK. EDAS supports JDK 1.7 and JDK 1.8. Therefore, command-line parameters are provided
for selection during the installation of EDAS Agent. If
-java 7 is selected, JDK 1.7 is installed. If
-java 8 is selected, JDK 1.8 is installed. By default, JDK 1.7 is installed.
During initial installation, both JDKs are downloaded and initialized. If the corresponding version of JDK has been installed on EDAS Agent, the JDK will not be reinstalled. Otherwise, the system will uninstall the previous version and then download the corresponding version to install.
In the subsequent update process, when the install.sh script is run for the second
time, two cases may occur:
- If the execution parameters contain the
-forceoption, all the components including the JDK will be uninstalled and reinstalled.
- If the execution parameters do not contain the
-forceoption, only EDAS Agent is reinstalled by default. The
-javaoption is processed in the following ways:
- If the specified JDK version is the same as the previous JDK version, no operation is performed.
- If the specified JDK version is different from the previous JDK version, the system uninstalls the JDK and then installs the corresponding version of JDK.