I want to install the latest ODP.Net driver on some new IIS servers we are building using the "OPD.Net Managed Only XCopy" install. I have it installed and working, but want to make sure I am doing it correctly so when a new version comes out we can install it on same machine side-by-side. I currently have the following directory structure for the 12c OPD.Net managed driver.
* This is where our sql.ora and tnsnames.ora file are located and we have the TNS_Admin environmental pointing to this directory.
v121010 (This was original named ODP.Net in the installation zip file)
Ran the configure.bat to setup the managed driver.
Not used at this time.
So everything seems to work correctly with only the one ODP.Net managed drive installed. But when the next version comes out and we want to run it on the servers side-by side, will I be able to do the following.
1) Download the "OPD.Net Managed Only XCopy" install for the new version (ex 220.127.116.11).
2) Copy the ODP.Net\ODP.Net folder in the installation zip to our server under ODP.Net\v131010
3) Run the configuration.bat for the new version (without messing up the other managed drivers installation).
If this is not correct, can someone please tell me how I need to install the 12c Managed Only Drivers on our servers so we can install newer versions side-by-side? The one thing we like about the latest ODP.Net driver is that it connects directly to the Oracle databases and does not require the Oracle Client to be installed. This is perfect for our IIS servers, so we need to make sure we install this correctly so when we want to install newer versions we can do that and still have our application use the older driver until they are migrated over and tested using the new driver.
Any help will be appreciated.
I totally understand that, but is they way I have done it the correct way to install it so we can install future versions side-by-side. The readme.txt just cover installing the single version and there are no instructions on how to install it for side-by-side installation. My biggest concern is the changes the configure.bat makes to the machine.config and the registry.
What you've done is correct.
There are no instructions for side by side installation since there's nothing special you need to do for side by side installation. You just install side by side.
Since configure.bat is a text file, you can see exactly what changes it's making and customize the script as needed. In fact, we expect customers to customize this script as needed. In Chapter 2 of the ODP.NET doc, you can read about ways to further customize your managed ODP.NET deployment.
There's a tutorial to teach you how to use and configure managed ODP.NET