The Web Client Server role is used to configure Security Center Web Client, a web application that gives users remote access to Security Center. Each role created defines a unique web address (URL) that users enter in their web browser to log on to the Security Center Web Client and access information from Security Center.
Multiple instances of the Web Client Server role are permitted. You might create one role for local users and a different role for remote users, who access the Security Center network over the Internet.
Configuration requirements
- It is recommended to deploy Web Client Server roles on separate expansion servers.
- Each Web Client Server role must have a unique URL. The URL format is https://<host>:<port>/<webAddress>.
- If multiple roles are created on the same server, they must each use a different HTTPS port or web address. Otherwise, the role entity turns yellow and an Entity warning event is generated.
- To view video in the Security Center Web Client, Media Gateway must be running on the server that hosts the Web Client Server role.
- If end-users will monitor video in the Security Center Web Client using Mozilla
Firefox or Microsoft Edge browsers, make sure that one of the following
conditions is met:
- A valid SSL certificate is installed on the server hosting the Web
Client Server role.NOTE: If a third-party certificate was already installed on the server through Windows, you can apply the certificate to Security Center from Server Admin:
- In the Secure communication section, select your server from the list.
- Click Select certificate.
- Select the certificate you want, and then click .
- If using the default self-signed SSL certificate, make sure that the web ports on the
Media Gateway role and the Web Client Server port settings match.
The defaults are port 80 for HTTP and port 443 for HTTPS.
- A valid SSL certificate is installed on the server hosting the Web
Client Server role.