Zend Server is comprised of several components that each contributes important functionality to facilitate the development process. The components can be turned on or off, and associated directives can be configured along with the component daemon directives, when available. Additional actions are also available for some of the components.
The table below summarizes the configuration actions that are available for each component.
Note:
These actions can only be performed by an Administrator.
Zend Component |
Status Change |
Restart Daemon |
Clear Cache |
Configure Component Directives |
Configure Daemon Directives |
Comments |
|
|
|
|
|
||||
Activates code tracing for events configured to create a trace file and for manually generating a trace file. |
Code tracing will not be available at all. |
|
|
|
|||
Activates the Data Cache: Scripts that include the Data Cache API can run. |
Disables the Data Cache: Scripts that include the Data Cache API cannot run. |
|
|
This component stores information and therefore has an additional action for clearing information. |
|||
Zend Debugger |
Activates the Debugger for local and remote debugging with Zend Studio. |
Disables the Debugger and does not permit debugging from Zend Studio. |
|
The Debugger requires that you enter a list of IP addresses to allow, deny or permit remote debugging through a firewall. therefore it has an additional option for adding "Allowed Clients" |
|||
Zend Deployment | - |
- |
|
|
|
|
|
Zend Guard Loader |
Scripts encoded with Zend Guard run. |
Scripts encoded with Zend Guard cannot run. |
|
|
|
||
Zend Java Bridge |
The Java Bridge runs: Scripts containing the Java Bridge API can run. |
The Java Bridge stops running: Scripts containing the Java Bridge API cannot run. |
|
|
|
This component can be restarted. |
|
Activates the job queue, only when this component is on will JobsJobs contain information about a specific Job (script to run) that you have set to run in your environment. run. This includes all Jobs either configured from the UI or by using the Job Queue API. |
Jobs will not run. |
|
|
|
If you are using the Job Queue API in your code, always make sure that this option is running otherwise it could cause your code to fail with an "undefined method" fatal error. |
||
Zend Monitor |
Event information, as defined in Applications | Monitoring Rules, is collected and displayed in Monitoring | EventsEvents are a result of the monitoring component checking your system and collecting information about a specific occurrence that indicates that your environment is displaying uncharacteristic behavior.. |
Disables the Monitor component: Event information is not collected. |
|
|
|
|
|
PHP is optimized. |
PHP is not optimized. |
|
|
This component stores information and therefore has an additional action for clearing information. |
|||
Activates the page cache: URLs associated with caching rules are cached. |
Disables the page cache: URLs marked to be cached are not cached. |
|
|
This component stores information and therefore has an additional action for clearing information. |
|||
Zend Session Clustering |
Session information will be centralized for all the servers belonging to the cluster. |
Disables Session Clustering. |
|
If you have Session Clustering running in your environment, do not turn off the component. Only turn the component Off if you do not use Session Clustering. |
|||
Z-Ray | - |
- |
The clean button cleans request information from the database, according to the relevant directive. |
||||
Enables the tracking of various Zend Server features and components. |
Disables tracking. |
|
|
|