These steps must be performed on the XDB Server that will be performing outbound mapping. In the examples, the XDB Server develop is performing outbound mapping.
To update the system tables:
SET LOCATION TO system;
UPDATE sysibm.syslunames SET username = "O" WHERE luname = "remote-server";
where:
O | indicates that requests going to the remote XDB Server will be subject to outbound mapping. |
remote-server | is the name of a remote XDB Server for which AuthIDs will be mapped. |
Other columns in the SYSIBM.SYSLUNAMES table are used for trusting servers. See the section Trusting for more information on using these values.
In the examples on outbound mapping used in this topic, the SQL command:
UPDATE sysibm.syslunames SET username = "O" WHERE luname = "sales";
would have been issued on the XDB Server develop.
INSERT INTO SYSIBM.SYSUSERNAMES VALUES("O","authid","servername", "newauthid","password");
where:
O | indicates outbound mapping will be performed. |
authid | is the name of the AuthID to be translated from. |
servername | is the name of the server for which this AuthID will be translated. |
newauthid | is the new AuthID that will be given. |
password | is the password to be used with the new AuthID. Enter the password as regular ASCII text. It will be encrypted by the engine before being stored. Subsequent displays of PASSWORD column data show the encrypted password. |
In the examples on outbound mapping used in this topic, the SQL command:
INSERT INTO SYSIBM.SYSUSERNAMES VALUES("O","bob","sales", "devbob","devbpass");
would have been issued on the XDB Server develop.
REFRESH LOCATIONS;