F-SECURE POLICY MANAGER 7.0 -, Руководство администратора

Страница: 52 / 241

CHAPTER 3 52
Installing F-Secure Policy Manager Server
5. Start the F-Secure Policy Manager Server service.
6. Check that everything still works.
7. Delete the old commdir files.
3.4.2 Changing the Ports Where the Server Listens for
Requests
There are two directives that define the ports for both of the WebServer
Modules that constitute F-Secure Policy Manager Server:
Listen
and
<VirtualHost>
. By default, F-Secure Policy Manager Server Admin
Module (the component that handles requests coming from Policy
Manager Console) listens in port 8080, and F-Secure Policy Manager
Server Host Module (the component that handles requests from
workstations) listens in port 80. You can, however, define what ports they
should listen in, if the defaults are not suitable.
If you want to change the port in which F-Secure Policy Manager Server
Admin Module listens, add a
Listen
entry in the configuration file with the
new port (e.g.
Listen 8888
), and remove the
Listen
directive that
defines the default port in which F-Secure Policy Manager Server Admin
Module listens:
Listen 8080
.
After adding the
Listen
directive, F-Secure Policy Manager Server
knows that it should listen in the new port (8888 in our example).
However, you must still configure it to associate the F-Secure Policy
Manager Server Admin Module to that new port. This is done by changing
When a new Listen entry is added, be sure to remove the obsolete
entry. Otherwise, the server will unnecessarily consume system
resources, such as a network port.