Configuring the Adapter for ODBC

In this section:

x

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


Top of page

x
Declaring Connection Attributes

How to:

Reference:

In order to connect to the ODBC database server, the adapter requires connection and authentication information. You supply this information using the SET CONNECTION_ATTRIBUTES command. You can:

You can declare connections to more than one ODBC database server by including multiple SET CONNECTION_ATTRIBUTES commands. The actual connection to the ODBC Server takes place when the first query that references the connection is issued. If you issue multiple SET CONNECTION_ATTRIBUTES commands:



x
Procedure: How to Declare Connection Attributes

You can configure the adapter from either the Web Console or the Data Management Console.

  1. From the Web Console menu bar, click Adapters.

    or

    From the Data Management Console, expand the Adapters folder.

    The Adapters folder opens.

  2. Expand the Available folder, if it is not already expanded.
  3. Expand the appropriate group folder and the specific adapter folder. The group folder is described in the connection attributes reference.
  4. Right-click the adapter name and/or version and select Configure.

    The Add Adapter to Configuration pane opens.

  5. Enter values for the parameters required by the adapter, as described in the connection attributes reference.
  6. Click Configure. The configured adapter is added to the Adapters list in the navigation pane.


x
Reference: Connection Attributes for ODBC

The ODBC adapter is under the SQL group folder.

The following list describes the connection attributes for which you can supply values. To complete the attribute declaration, click the Configure button.

Connection name

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

Datasource

The data source name (DSN). There is no default data source name. You must enter a value.

If a File DSN is used this must be the name of the file (for example, samplefdsn.dsn.)

Security

There are two methods by which a use can be authenticated when connecting to an ODBC data source:

  • Explicit. The user ID and password are explicitly specified for each connection pass to the ODBC data source, at connection time, for authentication.
  • Trusted. The adapter connects to the ODBC data source as a Windows login using the credentials of the operating system user impersonated by the server data access agent.
User

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

Password

Password associated with the primary authorization ID.

File DSN parameters (optional)

The path to the ODBC File DSN that is defined on your Windows machine or network.

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).



x
Syntax: How to Declare Connection Attributes Manually

Explicit authentication. The user ID and password are explicitly specified for each connection and passed to ODBC, at connection time, for authentication.

For User/System DSN:

ENGINE SQLODBC SET CONNECTION_ATTRIBUTES connection DSN_name/userid,password

For File DSN:

ENGINE SQLODBC SET CONNECTION_ATTRIBUTES connection
 FileDSN_name/userid,password:'FileDSN_path;' 

Trusted authentication. The adapter connects to ODBC as a Windows login using the credentials of the Windows user impersonated by the server data access agent.

For User/System DSN:

ENGINE SQLODBC SET CONNECTION_ATTRIBUTES connection DSN_name/,

For File DSN:

ENGINE SQLODBC SET CONNECTION_ATTRIBUTES connection 
 FileDSN_name/,:'filedsn=FileDSN_path;',

where:

SQLODBC

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

connection

Is the logical name used to identify this particular set of connection attributes.

Note that one blank space is required between connection and DSN_name.

DSN_name

Is the ODBC Data Source Name (DSN) you wish to access. It must match an entry in the odbc.ini file.

FileDSN_name

Is the name of ODBC File Data Source Name (DSN) you wish to access.

userid

Is the primary authorization ID by which you are known to ODBC.

password

Is the password associated with the primary authorization ID.

FileDSN_path

Is the path to the ODBC File DSN, which may reside on the hard drive or on the network.



Example: Declaring Connection Attributes

For User/System DSN:

The following SET CONNECTION_ATTRIBUTES command declares connection CON1 to the ODBC DSN named SAMPLESERVER with an explicit user ID (MYUSER) and password (PASS). To ensure security, specify connection attributes from the Web Console, which encrypts the password before adding it to the server profile.

ENGINE SQLODBC SET CONNECTION_ATTRIBUTES CON1 SAMPLESERVER/MYUSER,PASS

For File DSN:

The following SET CONNECTION_ATTRIBUTES command declares connection CON1 via the ODBC File DSN named SAMPLESERVER.dsn with an explicit user ID (MYUSER) and password (PASS). To ensure security, specify connection attributes from the Web Console, which encrypts the password before adding it to the server profile.

ENGINE SQLODBC SET CONNECTION_ATTRIBUTES CON2
SAMPLESERVER.dsn /R729999B,1525B6F3331C2FB3:'filedsn=C:\ SAMPLESERVER.dsn;'


x
Reference: Updating the Connection String

The syntax for the CONNECTION_ATTRIBUTES command for this adapter has been enhanced to include a logical connection name that is designed to support the porting of applications from development to production environments. This enhanced syntax may necessitate the migration of existing CONNECTION_ATTRIBUTES commands.

The Web Console Migrate option migrates your server settings to the newer release. To access this option, select Workspace, then Configuration/Monitor from the menu bar. Right-click Migrate from the Server folder in the navigation pane, and select Configure. On the Migrate pane, type the full path of the configuration instance directory (EDACONF) and click the Migrate button. This is the recommended approach.

If you choose not to use the Migrate option, please note the following information:


Top of page

x
Overriding the Default Connection

How to:

Once connections have been defined, the connection named in the first SET CONNECTION_ATTRIBUTES command serves as the default connection. You can override this default using the SET DEFAULT_CONNECTION command.



x
Syntax: How to Change the Default Connection
ENGINE SQLODBC SET DEFAULT_CONNECTION connection

where:

SQLODBC

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

connection

Is the connection defined in a previously issued SET CONNECTION_ATTRIBUTES command. If this name was not previously declared, the following message is issued:

FOC1671, Command out of sequence

Note:



Example: Selecting the Default Connection

The following SET DEFAULT_CONNECTION command selects the database server named SAMPLENAME as the default database server:

ENGINE SQLODBC SET DEFAULT_CONNECTION SAMPLENAME

Top of page

x
Controlling the Connection Scope

How to:

The SET AUTODISCONNECT command controls the persistence of connections when using the adapter for each of the connections you want to establish.



x
Syntax: How to Control the Connection Scope
ENGINE SQLODBC SET AUTODISCONNECT ON {FIN|COMMAND|COMMIT}

where:

SQLODBC

Indicates the adapter. You can omit this value if you previously issued the SET SQLENGINE command.

FIN

Disconnects automatically only after the session has been terminated. FIN is the default value.

COMMAND

Disconnects automatically after each request. Depending on how often the event occurs, the SET AUTODISCONNECT command may result in considerable overhead. Almost all of this overhead is not related to the server. It is related to the operating system and the data source.

COMMIT

Disconnects automatically only after COMMIT or ROLLBACK is issued as a native SQL command.


iWay Software