This article covers how to install the Oracle client and connect to an Oracle data source.
What you need to establish a connection:
All versions of Oracle are supported. If you do not have an Oracle connector or drivers already installed, the following are instructions on how to install a lean connector that will enable you to connect to your Oracle database using AutoTag:
To install the ODAC (ODP.NET) Oracle connector, and only the drivers needed, do the following:
- Go to the ‘Oracle Data Access Components’ page: http://www.oracle.com/technetwork/database/windows/downloads/utilsoft-087491.html
- Click the ‘Accept License Agreement’ radio button.
- Find the ‘ODP.NET, Managed Driver Xcopy version only’ section (the latest version will change from sample shown below).
- Click the ‘ODP.NET_Managed_ODAC…zip’ link (see sample screenshot below).
- Oracle will request you sign in before download (if you don’t have an account, you must create one).
- After signing in, the necessary .zip file will be downloaded.
- Close all Office files.
- Once you have downloaded the .zip file, extract all the files to your Downloads folder.
- Open a command prompt as the Administrator and navigate (cd) to the extracted Downloads folder (i.e. ODP.NET_Managed_ODAC12cR4).
- Run, as administrator, the command: install_odpm.bat c:\oracle both true
- You should see several “The operation completed successfully” prompts.
- You have installed the necessary drivers to connect to your Oracle database.
Connecting your Template to an Oracle data source:
From MS Word, Excel or PowerPoint, navigate to the AutoTag Manager tab.
Once on the AutoTag Manager tab, click on the Data Source button.
This will open the DataSources list dialog box. Click the Add button.
Select the ‘Oracle Managed Driver’ connector from the ‘Vendor:’ drop down list.
Do not use the ‘OracleClient Database (deprecated)’ option, if you see one. This is a connector that installs with the .NET framework, however, even Microsoft says it is horrible.
Fill in the details for your Oracle connection in the Datasource Connector window. You can also test your connection by using Windward’s sample Oracle database (details below).
Datasource Connector Fields:
|Select the Oracle Managed Driver option from the drop down list.|
Type a name for your datasource connection.
Enter the server name here.
The Windward Sample Oracle credentials are:
‘User’ is selected by default. Select ‘User & System’ to grab the metadata of the tables created for a database and the system tables used to administer and configure each database.
Read in metadata:
|Check this to read in additional information from the database, primarily the descriptions of tables, views, & columns and the primary key - foreign key relationships. It is a good idea to have this selected.|
Use Connection String:
|This is optional. You can enter the connection string directly instead of entering the Server, Database, & credentials in the previous fields. When unchecked, it will allow you to type the connection string that AutoTag will use to connect to your data source.|
|Root directory:||Optional. This is the "default directory" for any import tag requests where the requested file does not have an absolute path. If left blank, AutoTag will use the directory where the data source file is located. If the data source is not a file it will use the directory where the template is located.|
|You can test your Oracle connection by clicking this button. If all parameters and credentials are correct and a connection is made, you will receive a successful notification.|
If you have difficulty connecting to your Oracle data source, you can use the optional Debug SQL Connection tool to narrow down your issue. You can find this by clicking on the AutoTag Manager tab, then click on the Debug Conn drop down button. Next, click the Debug SQL Connection option. You will be prompted to enter your credentials to your Oracle database. You will want to use the ODP.NET, Managed Driver for the Connector field (see sample screen shot below).
Any exception you find will be displayed in the Exceptions section of the Debugger.