Micro Focus Enterprise Developer 3.0 for Eclipse > Programming > Mainframe Programming > SQL Option for DB2 > SQL Option Server Administration Guide > Multiserver Security > Outbound Mapping > Setting up Outbound Mapping > Primary Server Configuration

Primary Server Configuration

Restriction: This topic applies to Windows environments only.

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:

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 primary XDB Server, start SQL Wizard (Windows) or Interactive SQL Utility (UNIX).
Log in with an AuthID that has super user privileges, such as the INSTALL AuthID, provided with the XDB Server.
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 outbound mapping.

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.

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

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.

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