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. Currently, EDAS supports JDK 1.7 and JDK 1.8, and therefore command-line parameters are provided for selection during the installation of EDAS Agent. If -java 7 is selected, JDK 1.7 is installed, or if -java 8 is selected, JDK 1.8 is installed. JDK 1.7 is installed by default.

During initial installation, both JDKs are downloaded and initialized. If the corresponding version of JDK has already been installed on the target 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 upgrade process, when the install.sh script is run for the second time, two cases may occur:

  • If the execution parameters contain the -force option, all the components including the JDK will be uninstalled and reinstalled.
  • If the execution parameters do not contain the -force option, by default, only EDAS Agent is reinstalled. The -java option is processed as follows:
    • If the specified JDK version is the same as the previous JDK version, no action 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.