Micro Focus Enterprise Developer 3.0 for Eclipse > Programming > Mainframe Programming > SQL Option for DB2 > SQL Option Server Administration Guide > Multiserver Security > Trusting > Setting Up Trusting > Remote Server Configuration

Remote Server Configuration

Restriction: This topic applies to Windows environments only.

You must perform these steps on the XDB Server that will trust requests and perform inbound mapping. In the examples, the XDB Server sales is trusting and performing inbound mapping.

To update the system tables:

Note: When updating system tables, do not delete any seemingly empty records; these contain space characters in some columns and refer to locations controlled by your local XDB Server.

On any client logged in to the remote XDB Server, start the SQL Wizard (Windows) or Interactive SQL Utility (UNIX).
Once inside the XDB Server Configuration Utility, press F5 to access the Multiuser Configuration screen.
From an SQL Window, set the current location to the SYSTEM location:
```
SET LOCATION TO system;
```

Issue the following SQL command to update information in the SYSIBM.SYSLUNAMES table about server-to-server connectivity and inbound mapping and trusting.

UPDATE sysibm.syslunames SET usersecurity = "A" 
    WHERE luname = "servername" AND usernames = "I";

where:

A	indicates that requests from the XDB Server should be trusted.
`servername`	is the name of another XDB Server from which AuthIDs will be mapped.
I	indicates inbound mapping will be performed.

In the examples on inbound mapping used in this topic, the SQL command:

UPDATE sysibm.syslunames SET usersecurity = "A" 
    WHERE luname = "develop" AND usernames = "I";

would have been issued on the XDB Server sales.

Issue the following SQL command to insert information into the SYSIBM.SYSUSERNAMES table about AuthIDs that will be subject to inbound mapping.

INSERT INTO sysibm.sysusernames 
    VALUES("I","authid","servername", 
           "newauthid","");

where:

I	indicates inbound mapping will be performed.
`authid`	is the name of the AuthID to be translated from.
`servername`	is the name of the server from which the AuthID to be translated will originate.
`newauthid`	is the new AuthID that will be given.

In the examples on inbound mapping used in this topic, the SQL command:

INSERT INTO sysibm.sysusernames 
    VALUES("I","bruce","develop","developr","");

would have been issued on the XDB Server sales.

Repeat Step 4 for each server that will be subject to inbound mapping. Repeat Step 5 for each AuthID that will be subject to inbound mapping.
Issue the following SQL command to refresh the system:
```
REFRESH LOCATIONS;
```
Exit the SQL Wizard (Windows) or Interactive SQL Utility (UNIX).

Use the SQL GRANT command to grant the appropriate privileges to the new AuthIDs. In the examples on inbound mapping and trusting used in this topic, the AuthID developr would have to be granted SELECT privileges on the table may in the location orders.