The following procedures describe how to configure Zend Server to allow local and remote PHP debugging and profiling of web applications using an IDE (e.g., Zend Studio) and Zend Server's Debugger component.
This procedure describes how to define the IDE client used to debug, profile and view, event source code.
|
|
|
To configure IDE client settings:
|
Zend Studio Note: Manual configuration settings should be based on the IP and port configured in Zend Studio's Installed Debuggers preferences page. The preferences page is accessed in Zend Studio from Window | Preferences | PHP | Debug | Installed Debuggers. The default port number is 20080. |
This procedure describes how to enable or block specific IP addresses from initiating remote PHP debugging and profiling using the Zend Debugger component.
|
|
|
To configure IDE client settings:
|
To remove an IP from the lists, just click the X to the right of the IP address you wish to remove. |
This procedure explains how to integrate with your IDE to quickly identify event root cause analysis. These actions can be applied to each event group to investigate what caused the event. By default, the settings are set to run diagnostic actions on the originating server (the server on which the event was created). You can change the settings to run on a different server.
Important:
These action items are only available if the IDE is installed on your machine, and Zend Server is configured to communicate with it.
PhpStorm:
Before initiating a debugging/profiling session from Z-Ray, make sure PhpStorm is listening to debug connections. For more information, see PhpStorm documentation.
|
|
|
To diagnose with your IDE:
-OR-
|
These actions can also be performed from the Event Details page. For more information, see Events. |
This procedure explains how to diagnose events with your IDE using a different server than the one upon which the event originated on.
Important:
These action items are only available if your IDE is installed on your machine, and Zend Server is configured to communicate with it.
|
|
|
To diagnose with your IDE using an alternative server:
|
Tip: If you are using the UI of a different server than the one upon which the event originated on, and would like to perform your IDE diagnostic actions on the originating server, follow the same steps and select Originating server in the IDE Diagnostics Settings dialog. |