Configuring the Adapter for Snowflake Cloud Data Warehouse (ODBC)

Configuring the adapter consists of specifying connection and authentication information for each of the connections you want to establish.

Configure the Snowflake Cloud Data Warehouse Adapter (ODBC)

You can configure the adapter from either the WebFOCUS Reporting Server browser interface or ibi Data Migrator desktop interface.

    Procedure
  1. From the WebFOCUS Reporting Server browser interface Applications page, click Get Data. The Get Data page opens showing your configured adapters.

    Or

    From the ibi Data Migrator desktop interface, expand the Adapters folder. The Adapters folder opens.

  2. In the WebFOCUS Reporting Server browser interface, click the (+) button, and find the adapter on the page. You can select a category of adapter from the drop-down list or use the search option (magnifying glass) to search for specific characters.

    Or

    In the ibi Data Migrator desktop interface, expand the Available folder if it is not already expanded. Expand the appropriate group folder and the specific adapter folder. The group folder is described in the connection attributes reference.

  3. Right-click the adapter name and/or version and select Configure.

    The Add Adapter to Configuration pane opens.

  4. Enter values for the parameters required by the adapter, as described in the chapter for the specific adapter you want to configure.
  5. Click Configure. The configured adapter is added to the Configured list in the WebFOCUS Reporting Server browser interface or in the Adapters list in the ibi Data Migrator desktop interface resources tree.

    In the WebFOCUS Reporting Server browser interface, the adapter remains on the Available Adapters list with an asterisk to indicate that at least one connection has been configured. You can configure additional connections from either the Configured or Available list by right-clicking the adapter and clicking Add Connection.

Snowflake Cloud Data Warehouse Adapter Configuration Settings (ODBC)

The Adapter for Snowflake Cloud Data Warehouse is under the SQL group folder.

Connection name

Logical name used to identify this particular set of connection attributes. The default is CON01.

DSN-less

A DSN-less connection is an alternative method for connecting to Snowflake Cloud Data Warehouse. When this parameter is selected, the adapter is configured by entering values for the Snowflake server, warehouse, default database, and default schema instead of a Data Source Name (DSN).

Server

Specifies the full domain name for your account provided by Snowflake. For example:

ar59294.us-east-1.snowflakecomputing.com
Warehouse

Specifies the default warehouse to use for a session initiated by the driver. For example:

QAWH
Default Database

Specifies the default database to use for a session initiated by the driver. For example:

QATST
Default Schema

Specifies the default schema to use for a session initiated by the driver. For example:

R729999D
DSN

Is a valid Snowflake Data Source Name (DSN). There is no default DSN, you must enter a value. The DSN name should match the User, System, or File DSN configured in the ODBC Administrator on Windows, or the DSN entry in the $HOME/.odbc.ini file on Linux.

Security

There are three methods by which a user can be authenticated when connecting to a database server:

  • Explicit. The user ID and password are explicitly specified for each connection and passed to the database, at connection time, for authentication.
  • Password Passthru. The user ID and password received from the client application are passed to the database, at connection time, for authentication.
  • Trusted. The adapter connects to the database using the database rules for an impersonated process that are relevant to the current operating system.
User

Primary authorization ID by which you are known to the data source.

Password

Password associated with the primary authorization ID.

Security

There are two methods by which a user can be authenticated when connecting to a database server:

  • Explicit. The user ID and password are explicitly specified for each connection and passed to the database, at connection time, for authentication.
  • Key Pair Authentication. As a minimum, this authentication method requires a 2048-bit RSA key pair. The public key is assigned to the user. For the user authentication, the public key is verified based on the private key submitted with the connection information. For more information, please refer to the Configuring Key Pair Authentication chapter of the Snowflake documentation.

EXPLICIT

The following are the connection attributes for the Explicit security method:

User

Primary authorization ID by which you are known to the data source.

Password

Password associated with the primary authorization ID.

KEY PAIR AUTHENTICATION

The following are the connection attributes for the Key Pair Authentication security method:

User

Primary authorization ID by which you are known to the data source.

Private key file password

Is a password that is used to protect the private key.

Private key file location

Is a secure location of the private key. The private key file location can be on a network, for example:

\\example.cloud.com\sno\keys\rsa_key.p8

Or it can be in a local directory, for example:

/qa/sno/keys/rsa_key.p8
Note: You can use either the slash (/) or backslash (\) character as a delimiter in the pathname for any operating system, UNIX, Linux, or Windows.
Additional connection string keywords (optional)

Is used to add options to the connection string. For example, the tracing=0 parameter is required when no Snowflake ODBC traces are needed.

Advanced Parameters

There are two Advanced Parameters:

  • Allow Data Load. Select Yes to allow Upload, Quick Copy, and Custom Copy for a given connection. The default value is Yes.
  • Connection Description (Optional). User-defined notes used to describe the given connection. This parameter is optional.
Environment

Allows you to define required and informational Environment variables. You must define the required variables before starting the server.

There are three Environment parameters:

  • CLASSPATH. Directory search path for JVM or Java-based applications to find user-defined classes and packages, if not defined in IBI-CLASSPATH.
  • PATH. Directory search path for executable programs that are not in the current directory or called by full path name. To verify if this setting is required, check the vendor documentation.
  • LD_LIBRARY_PATH. Directory search path for DLL files that are used directly or indirectly by a called executable or DLL file. For Unix and Linux operating systems, this parameter is used to specify the path to the UNIX ODBC Driver Manager installation location. To verify if this setting is required, check the vendor documentation.
Select profile

Select a profile from the drop-down menu to indicate the level of profile in which to store the CONNECTION_ATTRIBUTES command. The global profile, edasprof.prf, is the default.

If you wish to create a new profile, either a user profile (user.prf) or a group profile if available on your platform (using the appropriate naming convention), choose New Profile from the drop-down menu and enter a name in the Profile Name field (the extension is added automatically).

Store the connection attributes in the server profile (edasprof).