Using the deployment manager command line, transfer
the targetTree.xml file from the deployment manager
to the profile_root/staticRoutes directory
for the proxy server. The file is transferred from the
deployment manager to the proxy server by FTP or some other protocol.
If
your secure proxy server is interfacing with multiple cells, you can
add the static routing file for each cell to the profile_root/staticRoutes directory.
The secure proxy server considers any xxx.xml file
that is included in the in the profile_root/staticRoutes directory
a static routing file. The file does not have to be named targetTree.xml.
When
you add multiple xxx.xml files
to the profile_root/staticRoutes directory
for a secure proxy server, the secure proxy server merges the content
of all of these files. The result of this merge is a single static
routing file that the secure proxy server can use to route requests
to servers in any of the cells.
Avoid trouble: The
merger process does not include any files in subdirectories of the
profile_root/staticRoutes directory.
Therefore the secure proxy server does not use any content that is
contained in files located in any subdirectory when it routes requests
to a servers.
gotcha
Any attribute change that affects the content
of the static routing file, such as a virtual host change, addition
or deletion of a proxy server cluster member, a change in weight of
a proxy server cluster member, or the installation or uninstallation
of an application, automatically regenerates the static routing file.