Content Gateway processes
Content Gateway has 4 primary processes:
| Process name | Description |
|---|---|
| content_gateway | Accepts connections, processes protocol requests, and serves documents from the origin server. |
| content_manager |
Launches, monitors, and reconfigures the content_gateway process. The content_manager process is also responsible for the Content Gateway manager user interface, the proxy auto- configuration port, the statistics interface, cluster administration, and virtual IP failover. If the content_manager process detects a content_gateway process failure, it restarts the process and also maintains a connection queue of all incoming requests. Incoming connections that arrive in the several seconds before server restart are saved in the connection queue and processed in sequence. This connection queuing shields users from server restart downtime. |
| content_cop |
Monitors the health of content_gateway and content_manager. The content_cop process periodically (several times each minute) queries content_gateway and content_manager by issuing heartbeat requests to fetch synthetic Web pages. If no response is received within the timeout interval or if an incorrect response is received, content_cop restarts content_manager and content_gateway. The content_cop process uses the port defined by proxy.config.admin.heartbeat_port. |
| analytics_server | Manages the requests made and processes spawned for analytics. |