Creating a port public endpoint

Use this procedure to create a new port public endpoint. Port public endpoints can communicate with or without SSL/TLS.
  1. Log in to the Control Center browser interface.
  2. In the Application column of the Applications table, click the application name (Zenoss.resmgr).
  3. On the right, above the Public Endpoints table, click Add Public Endpoints.
    The default view of the Add Public Endpoint dialog box displays the fields for creating a port public endpoint.
  4. Define a new port public endpoint.
    1. In the Type area, click Port.
    2. From the Service - Endpoint list, select Zenoss.resmgr - zproxy.
      The selection is the last entry in the list.
    3. In the Host field, enter a hostname or IP address that is assigned to a network interface on the Control Center master host.
      The default value is the hostname that was added with the Deployment Wizard when Resource Manager was initially deployed. If the Control Center master host has more than one network interface, you can add the hostname or IP address that is assigned to another interface.
    4. In the Port field, enter a safe, unused port number that is greater than or equal to 1024 and less than or equal to 65535.
      For a list of ports that are considered unsafe, see Unsafe ports on Chrome. For the list of ports that the Control Center master host uses, refer to the Zenoss Resource Manager Planning Guide.
    5. In the Protocol field, select HTTPS or HTTP.
      Optionally, you can set up a secure proxy server to handle HTTP requests that are sent to a port public endpoint.
    6. Click Add.
Next step: Configure the Zope service to use the new port public endpoint. Choose one of the configuration options in the following table.
Zope configuration Procedure
HTTPS and the default secure proxy server Configuring Zope for HTTPS and the default secure proxy server
HTTP and no proxy server

Note that when you configure Zope for HTTP protocol and no proxy server, you can only gain access to the Resource Manager browser interface through port public endpoints that are configured for HTTP. Because virtual host public endpoints must use HTTPS protocol, any existing virtual host public endpoints stop working.

Configuring Zope for HTTP and no proxy server
HTTP and a secure proxy server other than the default Configuring Zope for HTTP and a secure proxy server