Using Non-DataDirect Drivers

In This Section:

Creating Configuration Files for Non-DataDirect Drivers

About Non-DataDirect Drivers

You must configure all non-DataDirect drivers (drivers other than the DataDirect drivers distributed with Essbase) for all data sources.

Some, but not all, non-DataDirect drivers are tested and supported for Essbase. For detailed information about qualified drivers and data sources, see the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.

The information in the section also applies if you want to change the default settings for DataDirect ODBC drivers that are distributed with Essbase.

Creating Configuration Files for Non-DataDirect Drivers

You create a configuration file (ESSBASEPATH/bin/esssql.cfg) when you want to connect to a database using non-DataDirect drivers, or when you want to change the default settings for the DataDirect ODBC drivers that are distributed with Essbase.

Keywords and Values Used Within Configuration Files

The configuration file must contain the driver file names (DriverName), and an optional description (Description), the value for which must be enclosed in double quotation marks (the default value for Description is " "); it may contain additional keywords, the values for which are 0 or 1, as shown in Table 1.

Keywords and values must be separated by at least one space, and the set of keywords and values for each driver must be enclosed within brackets ( [ ] ).

Different drivers may require additional values. See the driver documentation for specific information.

In the following example, the first entry for Oracle changes the default settings for the DataDirect drivers distributed with Essbase. The second entry is for Microsoft SQL Server, a non-DataDirect driver.

Sample esssql.cfg

[
Description "Oracle Wire Protocol"
DriverName ARORA
UpperCaseConnection 0
UserId 1
Password 1
Database 1
SingleConnection 0
IsQEDriver 1
]

[
Description "Microsoft SQL Server 32-bit"
DriverName SQLSRV32
UpperCaseConnection 0
UserId 1
Password 1
Database 1
SingleConnection 0
IsQEDriver 0
]

Defaults apply to values that are not specified. The defaults applied within configuration files differ from the Essbase default values that apply if no esssql.cfg file exists.

Table 1. Configuration File Keywords and Values for Non-DataDirect Drivers

Keyword	Value = 0	Value = 1
UserId	User ID not required (default)	User ID required
Password	Password not required (default)	Password required
Database	Database name not required (default)	Database name required
Server	Server name not required (default)	Server name required
Application	Application name not required (default)	Application name required
Dictionary	Dictionary name not required (default)	Dictionary name required
Files	File name not required (default)	File name required
SingleConnection	Driver thread-safe—Multiple active connections permitted Note: Not recommended for non-Data Direct drivers, or for DataDirect drivers except for those used to connect to Oracle 11g databases, for which it is the default; may cause instability.	Driver not thread-safe—One active connection permitted The default and the recommendation for all DataDirect drivers except for those used to connect to Oracle 11g databases.
UpperCaseConnection	Driver case-sensitive—Connection information not converted (default) Tip: If the connection to the database server fails and the Application log shows an “invalid username/password; logon denied” message, check the case of the username and password in your database and compare it to what you are entering in Administration Services Console. To switch off case-sensitivity, change this value from 0 to 1.	Driver not case-sensitive—Connection information converted to uppercase
IsQEDriver	Driver a non-DataDirect driver (default)	Driver a DataDirect driver Note: You can specify configuration information for DataDirect drivers. For example, you can specify information for a version of a DataDirect driver that Essbase does not support.

Note:

The DataDirect ODBC drivers that connect to Oracle 11g databases are configured to enable multi-threaded connections and to disable uppercase conversion. To enable multi-threaded connections for the SQL Server Wire Protocol driver, see Performing Multiple SQL Data Loads in Parallel to Aggregate Storage Databases.

Finding Driver Names on Windows

To find driver names on Windows:

Using a method from step 1 in Configuring Data Sources on Windows, start ODBC Administrator:
The ODBC Data Source Administrator dialog box opens.
Configured data sources are listed in the User Data Sources box. Drivers that are not properly configured but are listed in the User Data Sources box can be ignored.
Select the Drivers tab.
Obtain the file name of the preferred driver by scrolling to the right.
For example, the file name for the Microsoft Access Driver is ODBCJT32.DLL.

Finding Driver Names on UNIX

To find driver names on UNIX, view the .odbc.ini file.

See Configuring Data Sources on UNIX.

Configuring Non-DataDirect Drivers

Essbase recognizes the basic configuration information for DataDirect drivers, such as the name of the driver and whether the name and password are case-sensitive. You must provide configuration information for non-DataDirect drivers, or if you want to change the default settings for the DataDirect drivers that are distributed with Essbase.

To provide configuration information:

Create a configuration file (a text file) named esssql.cfg.
Place the file in the $ESSBASEPATH/bin directory on Essbase Server.
If Essbase is installed in the default directory, use c:/Hyperion/products/Essbase/EssbaseServer/bin for Windows and/home/hyperion/products/essbase/essbaseserver/bin for UNIX.

Note:

If you do not create a configuration file, Essbase uses default values that may prevent you from connecting to SQL databases.