A user mapping is an association between an authorization ID on the federated server and the information that is required to connect to the remote data source. User mappings are supported for DB2 for Common Server v9.7 and higher.
You can create a user mapping in any of the following ways:
Select to access the List of User Mappings, and click the Add a Row tool.
You can modify an object's properties from its property sheet. To open a user mapping property sheet, double-click its Browser entry in the User Mappings folder.
The following extended attribute is available on the General tab:
| Property | Description |
|---|---|
|
Server |
Specifies the name of the server object (see Servers (DB2)) for the data source that the authorization-name can access. The server name is the local name for the remote server that is registered with the federated database. Scripting name: Server |
The following extended attributes are available on the Options tab:
| Property | Description |
|---|---|
|
Accounting string |
Specifies a DRDA accounting string. Valid values include any string that has 255 characters or fewer. Scripting name: ACCOUNTING_STRING |
|
Remote user ID / password |
Specify the remote user ID to which the local user ID is mapped, and its password in the remote system. If you do not specify a password, the password used to connect to the federated database is used. Scripting name: REMOTE_AUTHID, REMOTE_PASSWORD |
|
Use trusted context |
Specifies whether the user mapping is trusted. Scripting name: USE_TRUSTED_CONTEXT |
|
Additional options |
Can be used to specify any additional options. Scripting name: OtherOptions |