updated README's with more instructions to download and setup jdbc drivers

Author: vlkong

README.DB2.md

@@ -2,9 +2,12 @@
 
 ## Build the sample
 
-Before you build the sample, you must edit `build.properties` for the appropriate path locations:
+Samples [advanced_queries](examples/advanced_queries), [embedded_in_dat](examples/embedded_in_dat) and
+[studio_integration](examples/studio_integration) do not need to be compiled, so you can skip this
+section.
+
+Before you build the [oil](examples/oil) sample, you must edit `build.properties` for the appropriate path locations:
 
-* If you want to run the sample with MySQL, `mysql.jdbc.connector.path` should point to your JDBC driver location.
 * If you want to run the sample with IBM DB2, `db2.jdbc.connector.path` should point to your JDBC driver location.
 * `opl.home` should point to your OPL home, unless you have a `CPLEX_STUDIO_DIR128` set. (this variable should exists if you installed on a Windows machine).
 
@@ -38,19 +41,41 @@ Run the following SQL script to create and populate the example database:
 db2 -tvmf data/oil_db2.sql
 ```
 
-Before you run the sample, you need to edit `build.properties` to make `db2.jdbc.connector.path` point
-to your DB2 jdbc driver.
 
 You can download the DB2 jdbc driver [here](http://www-01.ibm.com/support/docview.wss?uid=swg21363866).
 Note that if you installed DB2 Express-C, your JDBC driver is `db2jcc4.jar`
 in `<DB2 installdir>/SQLLIB/java`.
 
-Edit `data\db_db2.xml` for your JDBC connection string and credentials.
+Depending on the sample you run, you need to edit, `build.properties` to make `db2.jdbc.connector.path` point
+to your DB2 jdbc driver.
+
+Depending on the sample you run, you need to edit `build.properties` to make
+`db2.jdbc.connector.path` point to your DB2 jdbc driver (i.e. db2jcc4.jar).
+
+On samples like [advanced_queries](examples/advanced_queries), [embedded_in_dat](examples/embedded_in_dat),
+you will need to edit your `.dat` so that the following line points to where your jdbc driver resides:
+
+```
+	IloOplImportJava("../../external_libs/db2jcc4.jar")
+```
+
+In sample [studio_integration](examples/studio_integration), you will need to edit `jdbc.js` to point
+to your jdbc driver, *or* add an `OPL_JDBC_DRIVER` environment variable pointing to it:
+
+```
+	var jdbc_driver = IloOplGetEnv("OPL_JDBC_DRIVER");
+	if (! jdbc_driver ) {
+		jdbc_driver = "../../external_libs/db2jcc4.jar";  // default for this project
+	}
+```
+
+For sample [oil](examples/oil), edit `data\db_db2.xml` for your JDBC connection string and credentials.
 Your connection string looks like `db2://localhost:<port>/<database_name>`
 where `port` is the DB2 port (default is 50000), `<database_name>` is the name
 of your database (default is `CUSTOMDB`).
 
-## Run the sample
+## Run the oil sample
+
 Compile and run the sample for IBM DB2:
 
 ```
@@ -61,4 +86,12 @@ $ ant run_db2
 * Uses data/oil.dat as a data file
 * Uses data/db_db2.xml to customize the JDBC custom data source.
 
+## Other samples
+
+The other samples do not need to be compiled, and will use `oplrun` executable. Each sample directory
+contains a convenience `run.bat` command line to run the sample. Otherwise you run them using the `run` target:
+
+```
+$ ant run
+```
 

README.MySQL.md

@@ -2,10 +2,13 @@
 
 ## Build the sample
 
-Before you build the sample, you must edit `build.properties` for the appropriate path locations:
+Samples [advanced_queries](examples/advanced_queries), [embedded_in_dat](examples/embedded_in_dat) and
+[studio_integration](examples/studio_integration) do not need to be compiled, so you can skip this
+section.
+
+Before you build the [oil](examples/oil) sample, you must edit `build.properties` for the appropriate path locations:
 
 * If you want to run the sample with MySQL, `mysql.jdbc.connector.path` should point to your JDBC driver location.
-* If you want to run the sample with IBM DB2, `db2.jdbc.connector.path` should point to your JDBC driver location.
 * `opl.home` should point to your OPL home, unless you have a `CPLEX_STUDIO_DIR128` set. (this variable should exists if you installed on a Windows machine).
 
 The build file, `build.xml`, imports the build file from the OPL samples,
@@ -57,7 +60,29 @@ Once the driver is download and extracted, edit property `jdbc.connector.path` i
 to include the MySQL Connector/J `.jar` (should look like `mysql-connector-java-5.1.40-bin.jar`
 in your MySQL Connector/J extracted diretory)
 
-Edit `data\db_mysql.xml` for your JDBC connection string and credentials.
+
+Depending on the sample you run, you need to edit `build.properties` to make
+`mysql.jdbc.connector.path` point to your MySQL jdbc driver (i.e. mysql-connector-java-5.1.40-bin.jar).
+
+On samples like [advanced_queries](examples/advanced_queries), [embedded_in_dat](examples/embedded_in_dat),
+you will need to edit your `.dat` so that the following line points to where your jdbc driver resides:
+
+```
+	IloOplImportJava("../../external_libs/mysql-connector-java-5.1.40-bin.jar")
+```
+
+In sample [studio_integration](examples/studio_integration), you will need to edit `jdbc.js` to point
+to your jdbc driver, *or* add an `OPL_JDBC_DRIVER` environment variable pointing to it:
+
+```
+	var jdbc_driver = IloOplGetEnv("OPL_JDBC_DRIVER");
+	if (! jdbc_driver ) {
+		jdbc_driver = "../../external_libs/mysql-connector-java-5.1.40-bin.jar";  // default for this project
+	}
+```
+
+
+For sample [oil](examples/oil), edit `data\db_mysql.xml` for your JDBC connection string and credentials.
 Your connection string looks like `jdbc:mysql://localhost:3306/<database_name>?useSSL=false`
 where `<database_name>` is the name of your database (default is `custom_data_source`).
 

README.SQLServer.md

@@ -2,10 +2,13 @@
 
 ## Build the sample
 
-Before you build the sample, you must edit `build.properties` for the appropriate path locations:
+Samples [advanced_queries](examples/advanced_queries), [embedded_in_dat](examples/embedded_in_dat) and
+[studio_integration](examples/studio_integration) do not need to be compiled, so you can skip this
+section.
 
-* If you want to run the sample with MySQL, `mysql.jdbc.connector.path` should point to your JDBC driver location.
-* If you want to run the sample with IBM DB2, `db2.jdbc.connector.path` should point to your JDBC driver location.
+Before you build the [oil](examples/oil) sample, you must edit `build.properties` for the appropriate path locations:
+
+* `sqlserver.jdbc.connector.path` should point to your JDBC driver location.
 * `opl.home` should point to your OPL home, unless you have a `CPLEX_STUDIO_DIR128` set. (this variable should exists if you installed on a Windows machine).
 
 The build file, `build.xml`, imports the build file from the OPL samples,
@@ -20,26 +23,50 @@ The example is automatically compiled with the run Ant targets is invoked.
 
 ## Setup the sample database
 
-To run the sample with MS SQL Server, you need to install MS SQL Server. 
-
-In a <em>Commnad Prompt</em> window:
+To run the sample with MS SQL Server, you need to install Microsoft SQL Server.
+After it is installed, you are ready to setup the sample database.
 
-Provided your sql server instance name is SQLEXPRESS, create database using:
+To create a sample database, open a <em>Commnad Prompt</em> window, and Provided your
+SQL Server instance name is SQLEXPRESS, create database using:
 
 ```
 C:\>sqlcmd -S .\SQLEXPRESS -i data\oil_mssql.sql
 ```
 
-Before you run the sample, you need to edit `build.properties` to make `sqlserver.jdbc.connector.path` point
-to your MSSQL server jdbc driver (i.e. mssql-jdbc-7.2.2.jre8.jar)
+Before you run the sample, you need to download the [Microsoft JDBC Driver for SQL Server](https://docs.microsoft.com/fr-fr/sql/connect/jdbc/download-microsoft-jdbc-driver-for-sql-server?view=sql-server-2017).
+
+Once your download finished, decompress the archive. The archive contains jar files that
+look like `mssql-jdbc-7.2.2.jre8.jar`. 
+
+
+Depending on the sample you run, you need to edit `build.properties` to make
+`sqlserver.jdbc.connector.path` point to your MSSQL server jdbc driver (i.e. mssql-jdbc-7.2.2.jre8.jar).
+
+On samples like [advanced_queries](examples/advanced_queries), [embedded_in_dat](examples/embedded_in_dat),
+you will need to edit your `.dat` so that the following line points to where your jdbc driver resides:
 
-Edit `data\db_mssql.xml` for your JDBC connection string and credentials.
+```
+	IloOplImportJava("../../external_libs/mssql-jdbc-7.2.2.jre8.jar")
+```
+
+In sample [studio_integration](examples/studio_integration), you will need to edit `jdbc.js` to point
+to your jdbc driver, *or* add an `OPL_JDBC_DRIVER` environment variable pointing to it:
+
+```
+	var jdbc_driver = IloOplGetEnv("OPL_JDBC_DRIVER");
+	if (! jdbc_driver ) {
+		jdbc_driver = "../../external_libs/mssql-jdbc-7.2.2.jre8.jar";  // default for this project
+	}
+```
+
+For sample [oil](examples/oil), edit `data\db_mssql.xml` for your JDBC connection string and credentials.
 Your connection string looks like `	jdbc:sqlserver://localhost;instanceName=<instance>;databaseName=<database_name>;integratedSecurity=true`
 
 where `instance` is the mssql instance name (default is SQLEXPRESS), `<database_name>` is the name
 of your database (default is `custom_data_source`).
 
-## Run the sample
+## Run the oil sample
+
 Compile and run the sample for MS SQL Server:
 
 ```
@@ -48,4 +75,15 @@ $ ant run_mssql
 
 * Uses data/oil.mod as a model file
 * Uses data/oil.dat as a data file
-* Uses data/db_db2.xml to customize the JDBC custom data source.
+* Uses data/db_mssql.xml to customize the JDBC custom data source.
+
+## Other samples
+
+The other samples do not need to be compiled, and will use `oplrun` executable. Each sample directory
+contains a convenience `run.bat` command line to run the sample. Otherwise you run them using the `run` target:
+
+```
+$ ant run
+```
+
+