Nodes are the Web servers that run PHP. Nodes are individual servers that service a Web application. A collection of nodes are referred to as a cluster.
The central server governs clusters.
The following components need to be on each Node:
A supported operating system (Linux, Unix, Mac, i5/OS and Windows)
A supported Web Server (Apache, IIS)
PHP version 4 or 5
Nodes have to be registered with the Central Server by a user with administrator rights in order to enable communication between the Node and the Central Server. There are two ways to register a Node to the Central Server: through the installation process or by manually registering the Node.
Platform Nodes consist of several components that report information to the Central Server and provide debug capabilities for PHP scripts residing on a node.
A Collector Component for transferring event information to the Central Server
Debug Infrastructure for debugging live pages directly from a node (This option is supported by Studio)
The following illustration is a representation of Platform Node components:
Platform Node Components
The Collector component listens to the running processes and collects event information (for more on Events go to ”Configuring Events”), to be reported to the Central Server over a regular TCP/IP connection. However, only if the node and the central have the same key will the Central Server agree to receive event information from a node’s collector (the key is generated when Nodes are registered in the installation process or in the "Setup Tool").
The type of information the Collector listens to and collects is event information determined by Event Rules that are configured on the Central Server. Event information is sent to the Central Server where it is aggregated according to event type (more about event aggregation can be found in "Appendix B - Event Aggregation Mechanism"). Different Rules can be applied to different nodes in a cluster environment or specific settings can be applied to more than one node in a cluster (by using the Clone Server feature).
The Debugger Infrastructure is enabled via the Studio/Platform Communication Tunnel that is geared to work in development and production environments. With the appropriate configuration, the Debugger Infrastructure can work through Firewalls or NAT devices that may be positioned between the Node and Studio (more about Firewall traversal can be found in ”Configuring Communication with Studio"). The Debugger Infrastructure provides full lifecycle support for editing, debugging, profiling and deploying code by enabling to view and edit Event source code in the Studio development environment. This provides Zend Studio users with access to the remote debugger via the same communication tunnel that routes full-duplex traffic over HTTP. The Debugger Infrastructure utilizes the Communication Tunnel, ensuring that multiple servers can be debugged through the same Communication Tunnel at once.
Communication with Studio