Setting Up Routing Information to Forward Redirected Client Requests
After you configure a server's [Gateway] section to redirect client requests to another server, you must then go to the server now receiving the requests (often the same server, as in many ProjectWise Gateway Service configurations) and configure the [Routing] section in its dmskrnl.cfg file so that that server will know where to forward these requests. Most often you will configure the server now receiving the requests (referred to as the gateway server) to forward requests to the routed server (that is, the final destination of the request). In some cases, however, you may find it necessary to forward requests to another gateway server, which will then forward the request to its destination. This subtle difference affects the way you configure the [Routing] section, as you will see below.
A sample, commented out [Routing] section exists in each dmskrnl.cfg file by default, with general instructions of usage and syntax. It is recommended that you make a copy of the delivered examples so you can use the original as a reference. The following is the entire [Routing] section as delivered in any dmskrnl.cfg file:
;[Routing] ;This section is used by the Gateway server that this config file is installed on ;to determine where to route requests that have been sent to it on behalf of a Routed Server ;If there are multiple hops necessary to get to the Routed server, this will direct this server ;to forward to the next hop on a particular port, otherwise only the information about what ;port number the Routed server is listening on is necessary ;Format ;Routed Server = Port Number,Next Gateway Server ;Examples (shows two different scenarios) ;server1=5800,server3 ;server1=5800