The instance owner supplies a name to identify the data source, along with the type and version of the data source, the database name for the data source (RDBMS only), and metadata that is specific to the data source. This information is called a server definition. Data sources answer requests for data and are servers in their own right. Servers are supported for DB2 for Common Server v9.7 and higher.
You can manually create a server in any of the following ways:
Select to access the List of Servers, and click the Add a Row tool.
Right-click the model (or a package) in the Browser, and select .
Use the Create tool next to the Server field on the General tab of a nickname or user mapping property sheet (see Servers (DB2)).
You can modify an object's properties from its property sheet. To open a server property sheet, double-click its Browser entry in the Servers folder.
The following extended attributes are available on the General tab:
|
Property |
Description |
|---|---|
|
Authorization / Password |
Required only for DB2 family data sources. Specify the authorization ID and password under which any necessary actions are performed at the data source when the CREATE SERVER statement is processed. This authorization ID is not used when establishing subsequent connections to the server. Scripting name: Authorization, Password |
|
Type / Version |
Specify the type and version of the data source. Scripting name: Type, Version |
|
Wrapper |
Specifies the wrapper (see Wrappers (DB2)) that the DB2 federated server uses to interact with the server object. Use the tools to the right of the list to create, browse for, or view the properties of the currently selected wrapper. Scripting name: Wrapper |
|
Model |
Specifies the PDM containing the structure of the database on the server being referenced. Use the tools to the right of the list to browse for an object or view the properties of the currently selected PDM. Scripting name: Model |
The following extended attributes are available on the Options tab:
|
Property |
Description |
|---|---|
|
Fold login / Fold password |
Specify the case of user IDs and passwords that the DB2 federated server sends to the data source server for authentication, and whether they can be null. Scripting name: FOLD_ID, FOLD_PW |
|
Enable plan hints |
Specifies whether plan hints, which are statement fragments that provide extra information for data source optimizers to help decide whether to use an index, which index to use, or which table join sequence to use. This information can, for certain query types, improve query performance. Scripting name: PLAN_HINTS |
|
Ignore user data types |
Specifies whether the DB2 federated server should determine the built-in type that underlies a UDT without strong typing. Scripting name: IGNORE_UDT |
|
Push down |
Specifies whether the DB2 federated server will consider letting the data source evaluate operations. Scripting name: PUSHDOWN |
|
Collating sequence |
Specifies whether the data source uses the same default collating sequence as the DB2 federated server, based on the NLS code set and the country information. Scripting name: COLLATING_SEQUENCE |
|
Date compatibility |
Specifies whether the DATE compatibility semantics associated with the TIMESTAMP(0) data type are applied to the connected database. Scripting name: DATE_COMPAT |
|
No trailing blanks |
Specifies whether data sources which have variable character data types pad the length with trailing blanks. Scripting name: VARCHAR_NO_TRAILING_BLANKS |
|
Enforce savepoint |
Specifies whether the DB2 federated server should enforce detecting or building of application savepoint statements. Scripting name: IUD_APP_SVPT_ENFORCE |
|
CPU ratio / IO ratio |
Indicate how much faster or slower a data source's CPU and I/O system runs than those of the the DB2 federated server. Scripting name: CPU_RATIO, IO_RATIO |
|
Packet size |
Specifies the packet size of the Sybase interface file in bytes. If the data source does not support the specified packet size, the connection will fail. Increasing the packet size when each record is very large (for example, when inserting rows into large tables) significantly increases performance. Scripting name: PACKET_SIZE |
|
Timeout |
Specifies the number of seconds the DB2 federated server will wait for a response from Sybase Open Client for any SQL statement. The value of seconds is a positive whole number in DB2 Universal Database's integer range.The timeout value that you specify depends on which wrapper you are using. The default behavior of the TIMEOUT option for the Sybase wrappers is 0, which causes DB2 to wait indefinitely for a response. Scripting name: TIMEOUT |
|
Login timeout |
Specifies the number of seconds for the DB2 federated server to wait for a response from Sybase Open Client to the login request. Scripting name: LOGIN_TIMOUT |
|
Communication rate |
Specifies the communication rate between the DB2 federated server and the data source server in megabytes per second. Scripting name: COMM_RATE |
|
Database name |
Specifies the database that you want the the DB2 federated server to access on the data source. For DB2, this value corresponds to a specific database within an instance or, with DB2 for z/OS or OS/390, the database LOCATION value. Not required for Oracle instances, which contain only one database. Scripting name: DBNAME |
|
Sybase OCI path |
Specifies the path and name of the Sybase Open Client interfaces file. On Windows NT servers, the default is %DB2PATH%\interfaces. Scripting name: IFILE |
|
Node |
Specifies the name by which the data source is defined as an instance to its RDBMS. Scripting name: NODE |
|
Additional options |
Can be used to specify any additional options. Scripting name: OtherOptions |