4 Replies Latest reply on May 17, 2018 3:46 PM by Sam_P

    How to find out where SQL DEVELOPER folder is installed at?




      Now that Oracle SQL Developer is being released frequently every 3 months, we're trying to see if we can package and automate the deployment of this tool through to several Windows workstations (~ 100) in our organization.


      I wish there was an easy way to deploy such that it would take care of detecting where SQL Developer zip contents were extracted to which folder and where is it actively running from and infact, be able to seamlessly upgrade it in silent/quiet mode on Windows. Having to manually perform this task for 100 PCs is taking a lot from our resources.


      If a user already installed an older version of Oracle SQL Developer by manually downloading the ZIP file and then extracting its contents to some folder path, how can we read the path to this active folder? Because it is not anywhere in Windows Registry, so we're having an issue with automating a package for quick deployment.


      Plus, after we find a way to auto-detect the installation folder, we need to do more steps to ensure the pre-reqs like JDK is installed or not; disable the older version of SQL Developer by renaming the folder perhaps, before deploying the newer version of SQL Developer.


      Any guidance to automate all this would be appreciated.



        • 1. Re: How to find out where SQL DEVELOPER folder is installed at?

          Build an msi and pkg it yourself...and maybe grab an update every 6 or 12 mos

          • 2. Re: How to find out where SQL DEVELOPER folder is installed at?

            That's what we're trying to do Jeff, however, pushing the package and automating it with all the "smarts" of (1) detecting where the previous version is installed, (2) remove the older version, (3) push the newer version along with its pre-reqs (JDK) is not that obvious.


            Suppose the package is developed such that it would always extract the contents of a given new version to folder C:\sqldeveloper folder. What happens if there's already a folder like that existing. What if the user had manually installed the previous version of SQL Developer at C:\Downloads\sqldeveloper folder? How do we know where the user actually installed it previously, so that we can remove it and always stick with C:\sqldeveloper folder?


            Your help would be appreciated. It would be nice if Oracle SQL Developer team would provide us with an MSI such that it would take care of (1) detecting the presence of the appropriate JDK pre-req and if not found, it would install it quietly, (2) detecting the presence of older SQL Developer version and if found, it would un-install it quietly and seamlessly and install the newer version quietly and seamlessly. This will become an important part of keeping the versions up-to-date in the organizations, now that you guys have increased the frequency of releases.

            • 3. Re: How to find out where SQL DEVELOPER folder is installed at?

              If you're going to go the MSI route, i think you start at ground Zero - previous sqldev installs, ignore them. Person gets a FRESH install.


              Then going forward, you know where the previous installs are and how to treat them.


              if someone goes rogue or if after initial deployment they want to get their connections/preferences moved over, it's fairly simple for them to do that on their own.


              Otherwise your'e left to doing a brute force search of their machine looking for sqldeveloper.exe - unless you have desktop auditing software that already has a record of that.


              We don't write to the registry, so there's no easy way to ask.

              • 4. Re: How to find out where SQL DEVELOPER folder is installed at?



                I thought of doing a search on sqldeveloper.exe, however, this exe also shows up inside Oracle Client folder at C:\oracle\product\11.2.0\client_1\sqldeveloper\sqldeveloper.exe, which will certainly confuse and mislead the IT Service Desk personnel to then follow the removal instructions, which would cause more damage. We have packaged and pushed Oracle Client (32-Bit) onto every user's PC at C:\oracle folder.


                Hope you see the need for a feature request to make an MSI or some other form to make our lives easier when deploying the tool (along with checking the pre-reqs). It is not an easy task on our side.