Oracle Java - Oracle lacking detail on java.settings.cfg - is it required for more than MSI Enterprise?


I have found in the vast unknown (a.k.a. Oracle Docs forest) some information pertaining to java.settings.cfg (or in some instances java_settings.cfg - https://docs.oracle.com/javacomponents/doc/install-guide/use-installer-configuration-file-install-jre.htm ) in which Oracle politely informs you that "After installing the JRE, the installer creates the system runtime configuration file." or, in this particular instance "java_settings.cfg". They do not mention (typical) which machine this file gets created on... only that the file is created. Does anyone have knowledge of this file or process?

In other instances in Oracle Docs where the file java.settings.cfg is found, the document lends one to believe that by providing the path to this file (really?) JRE can be installed silently. Oh joy... As I said, lacking in detail. If anyone has knowledge of MSI Enterprise or java.settings.cfg... could you answer these questions:

  1. If your organization uses the MSI, does the java*settings.cfg file get created on each endpoint? Or, does it only reside on the central MSI server?
  2. Is there ever a situation where there would not be a java*settings.cfg when the MSI is used?

    An unrelated question:
  3. Is there ever a time where Java Mission Control can be used without Java Flight Recorder files? 
  4. If Java Mission Control (or jmc.exe) is present, but Java Flight Recorder files (*.jfr) are not... would this be obvious that Mission Control was never used?

Much appreciated!


0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ