A [Routing] section must be configured in the dmskrnl.cfg file on the ProjectWise server (Integration Server, Caching Server, or Gateway Service running in Caching Server mode) on which files are to be cached. Routing information tells the server where (which server) to forward requests received from clients. For file caching, this section tells the server that if a remote file is requested but is not in its local cache, or if a remote file is requested but the copy in cache is not up to date, to go get the file from the specified server, through the specified port.
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 section so you can use the original as a reference.
Below is an example [Routing] section for use in a caching configuration. This example states that if the server receives a request for a file that is on the Caching Server named PCS, to then get the file from PCS, through port 5800.
However, you may have a situation in which to retrieve a remote file, the local server must forward client requests through a chain of servers. In this case, rather than forwarding the request directly to the server containing the file, you only configure the server to forward the request to the next server in the chain. This next example states that if the local server receives a request for a file that is on the Caching Server named PCS, to forward the request to the server named INTSERVER, through port 5800.
Note: For this second example to work, you will also need a line in the [Routing] section on the server named INTSERVER, which will forward the request to the next server in the chain. When the next server in the chain happens to be the last server in the chain, your Routing line only needs server=portnumber (for example PCS=5800), as shown in the first example above.