[MUSIC] Hi, welcome to Oracle University's training on Oracle Autonomous Database Connectivity. My name is Angela Wall and I look forward to talking to you about all the various ways that you can connect to the Oracle Autonomous Database As was covered in provisioning and connectivity, here are some of the supported connections to the autonomous data warehouse. You should already know about the credentials wallet file from the section on provisioning and connectivity. As you will be using it in the various types of connections we will cover. Oracle Call Interface or OCI, Open Database Connectivity or ODBC and Java Database Connectivity JDBC all have requirements in order to connect to the autonomous data warehouse. First, you will need the credential wallet file and have it unzipped, as Oracle net services cannot read the zip file. In your sqlnet.ora file, you need to set the wallet location variable to point to the wallet file. When the wallet location is set, then allconnect services allows the application to use the wallet file transparently. Also, the TNS admin environment variables needs to point to the credentials file. Both of these will allow the connections to use the specific configuration files inside of the wallet to connect. Oracle Client 11.2.0.4 or higher is required in order to have the right drivers to connect to the autonomous data warehouse. .NET application requirements vary depending on how the application is deployed. If you're using Visual Studio, you will need to download and install ODT and managed ODP.NET files. If you're using NuGet, then you can use the NuGet package manager to download and install the managed od T and ODP.NET files. If you're using unmanaged ODP.NET or the Oracle Universal Installer version of Oracle data access components, then you will need to download the appropriate ODAC files instead of the ODT files. Once the appropriate files have been installed, then you will need to set the wallet location in the sqlnet.ora file to point to where you actually extracted the wallet file. Depending on your version of Windows, you may need to enable TLS 1.2 Depending on how your JDBC or UCP connections are set up, you will need to do some of the following. You will need JDK8 or higher, specifically JDK8u161 or higher installed. Also, there are specific JAR files needed to be in place. If you're using JDBC Thin Driver 12.2.0.1 OJDBC8.jar, then you will need the 12.2.0.1 UPC.jar file. If you're using the patch JDBC Thin Driver 12.1.0.2 JDBC7.jar, then you will need the 12.1.0.2 UPC.jar file. Once you have the correct drivers installed, then some configuration is needed. If the TNS_ADMIN environment variable is set, copy the ojdbc.properties file from your wallet directed to the TNS_ADMIN directory and set the oracle.net.wallet_location in the ojdbc.properties file. This will allow you to just use the service name in your JDBC URL. If TNS admin is not set, then you would need to specify TNS admin as a part of the URL and point it to your wallet directory. What both these allow is for you to specify a service name that is in your TNS name.ora instead of having to fully spell out all connection information in the JDBC URL. If you need to use an HTTP proxy to get to your autonomous data warehouse, then you will need to edit the tnsnames.ora file. Add the parameters, https_proxy and https_proxy_port. This will also require a JDBC Thin Client 18.1 or higher to use. Applications that use JDBC then driver require the Oracle Database credentials, including the Oracle wallets or Java keystore JKS files. When connecting to the autonomous database, you can include the wallet location in a JDBC URL to make a connection, we will outline that process in this section. If your application uses Oracle JDBC, Thin Driver version 18.1 or higher, the connection can be specified using a JDBC URL. It is recommended that you use version 18.3 or later to make it easier to configure connections with the security credentials wallet. The 18.3 drivers can be downloaded from the Oracle Technology Network. Once you have the necessary drivers, you can set the connection by unzipping the security credentials, wallet zip file, and then specifying the wallet directory in the JDBC URL. You can download the JDBC thin driver, the universal connection pool, their readmes, and companion jar files as a whole or as individual downloads. Once you have the necessary drivers, locate and unzip the autonomous database security credentials files. As a reference, we walked through the credentials download process in a previous section. How the JDBC URL is formed depends on whether the TNS admin environment variable is set on your computer. The TNS admin environment variable points to the directory where Oracle SQL net configuration files are located. If TNS admin is not set in the environment, then you must include the wallet directory in the JDBC thin URL. Here our unzipped directory is / users/ ybaskan/ADW/ wallets. We've got the contents of the file available to us. We simply point to that file location. Here we're using the bin approach without having a TNS admin explained or defined. So we're having a question mark point to it. Same thing on the right. We can see we're using a universal connection pool in the sample. And briefly, this is what it looks like when executing the first sample. And then this is what it looks like when executing the second sample the UCP. Using SQLNet Connections in your sqlnet.ora file. Here's how you would change your wallet location to point to the necessary directory. You'd substitute the question mark with whatever directory you've unzipped your wallet into and you'd set your variable, SSL_SERVER_DN_MATCH=yes. And then you would also set your proxy settings if you're using the proxy. We also support connecting through Python, Node.js, and Other Scripting Languages and we have some samples here on how to do it. These steps include installing the instant client, installing the language driver, unzipping the credentials and lastly, using the TNS names entry file with the various contents While the features used by Enterprise User Security or EUS met the larger set of requirements, a large group of customers just needed authentication and authorization with Active Directory or AD. The complexity with EUS and Oracle Directory Services or ODS was more work and cost the most most customers wanted to offset the little used enterprise domain features. Centrally manage users to be a part of the upcoming Oracle Database release ATNC Enterprise Edition provides a direct connection to AD without using an intermediate directory service and without the EUS enterprise domain features. AD stores authentication and authorization data that is used by the database to authenticate users. Essentially Manage Users supports passwords ,Kerberos and PK II certificates just like EUS does. AD users in groups can map to Oracle schemas as exclusive users or to a shared schema. AD account policies centrally manage their related policies for passwords and lockout. So, to wrap up today, there are numerous ways that applications and tools can choose to connect to a target database. And Oracle is striving to ensure that we can enable a network session from any client application to or any Oracle database, especially the autonomous database. Thank you.
