Configuring the Adapter for Rdb

In this section:

How to:

Reference:

x

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

To connect to an Rdb database server, the adapter requires connection and authentication information. You supply this information using the SET SERVER command. You can:


Top of page

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 Rdb

The Rdb 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.

Server

Full path to an Rdb data source, or a logical name, such as SQL$DATABASE, which contains the full path. Rdb limits this value to 31 characters. If the full path exceeds this limit, you must specify a logical name to point to the full path.

  • Full Path. Full path specification must be in the following form: device_name:[directory]file.RDB. The RDB extension is required.
  • Logical Name. To use this method, the logical must be set prior to server startup. The trailing blank is optional.
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).

Note: Only one SET SERVER command may be active at any given moment; the last command issued is the active Rdb DBMS file.

Rdb multischema DBMS files are not supported for metadata creation purposes, but are valid for data access purposes provided that the Access File TABLENAME= value points to the table properly. For more information about configuration and metadata creation, see Using Multischema Rdb DBMS Files.


Top of page

x
Syntax: How to Declare Connection Attributes Manually

The adapter connects to Rdb using the credentials of the operating system user impersonated by the data access agent.

ENGINE SQLRDB SET SERVER server

where:

SQLRDB

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

server

Is the full path to an Rdb data source, or a logical name, such as SQL$DATABASE, which contains the full path. Rdb limits this value to 31 characters. If the full path exceeds this limit, you must specify a logical name to point to the full path.

Full Path. Full path specification must be in the following form: device_name:[directory]file.RDB. The RDB extension is required.

Logical Name. To use this method, the logical must be set prior to server startup. The trailing blank is optional.

Note: Once the initial SET SERVER command is saved in a profile, you can manually declare additional connections to more than one Rdb database by including any number of additional Rdb ATTACH ALIAS commands and editing the Access File to properly point to the TABLENAME= value at the alias. For more information about configuration and metadata creation in this context, see Using Multischema Rdb DBMS Files.



Example: Declaring a Connection to ORDERS.RDB

The following example shows how to declare a connection to the ORDERS.RDB data source, located in the OUTBOUND directory on disk.

ENGINE SQLRDB SET SERVER DISK$SHIPPING:[OUTBOUND]ORDERS.RDB

Top of page

x
Overriding the Default Connection

How to:

Once connections have been defined, the connection named in the last SET SERVER command serves as the default connection. You can override this default by reissuing the SET SERVER command.



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

where:

SQLRDB

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 SAMPLE as the default database server:

ENGINE SQLRDB SET DEFAULT_CONNECTION SAMPLE

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 SQLRDB SET AUTODISCONNECT ON {FIN|COMMAND|COMMIT}

where:

SQLRDB

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.


WebFOCUS