This procedure describes how Platform users can configure the Studio side to connect with Platform using a Communication Tunnel. Communication tunnels are used to circumvent Firewalls and other security devices to enable the use of Platform's advanced diagnostics options. These options include editing, debugging and profiling Event source code using Studio.
Tunneling is used for editing PHP code with Studio in instances when the code and the IDE are located on different machines separated by a Firewall.
The following instructions pertain to the following IDEs:
Note:
The Debug port for Studio 5.5 is 10000 and in Studio for Eclipse 10137.
There are several steps to defining Tunneling in Studio for Eclipse as follows:
Define a server
Configure Server Preferences
Configure Platform Integration
Set Tunneling Settings
|
|
|
|
|
To configure Tunneling Settings for Studio for Eclipse:
Now when clicking the Event Details options: Reproduce in Debugger and Reproduce in Profiler, a Studio Session will be initiated. When debugging and profiling make sure you are in the correct perspective or that you confirm the perspective switch in Studio Eclipse otherwise the session will not start. Note: To start a Debug Session click the Resume button in Studio Eclipse's Debug perspective. |
|
Useful Information:
|
|
To view debug preferences to ensure that the information is suits the Tunneling Preferences go in Studio for Eclipse to: Window | Preferences | PHP | Debug:

Studio for Eclipse Debug Preferences
In the section called "Connection to debug server", make sure the following settings are configured:
Debug Options:
PHP Debugger - Defines the component for running the debug session. The integration with Platform works with the Zend Debugger only.
Default Server - Defines which server the debugger will use by default. Click the "PHP Servers" category to be taken to the PHP Servers management page.
Set this to Zend Platform
Default PHP Executable - the required PHP version. Select the version which Platform is using.
Debug Transfer Encoding - Click the arrow to select the required transfer encoding from the drop-down list.
Debug Output Encoding - Click the arrow to select the required output encoding from the drop-down list.
Break at First Line - Mark this checkbox to force the debugging process to stop at the first line of code.
Client Host/IP - Enter the Client's Host/IP.
|
|
|
|
|
To configure Tunneling Settings for Studio:
|
|
Note: Information in Studio's Debug Preferences, must match the information in Studio’s Tunneling Settings for tunneling to work. |
|
To view debug preferences to ensure that the information is suits the Tunneling Preferences go in Studio to: Tools | Preferences | Debug:

Studio Debug Preferences
In the section called "Connection to debug server", make sure the following settings are configured:
Debug Mode - Sets the Debugger to Internal or Remote.
Select remote for integrating with Platform
Debugger Server URL - The IP or URL of the host that runs the Debug Server. To check the connection to the debug server, select the Check Debug Server Connection, from the Debug menu.
If the test fails, check the list of common problems in Appendix A – Troubleshooting Zend Platform
Client IP - Set the IP address of Studio’s host machine.
Client Debug Port - Set the port number for communication with the Debug Server.
Broadcasting Port - Studio’s communication tunnel is implemented via a persistent broadcasting port that broadcasts information about tunneling to Platform. Specify the port number in this field.
Dummy File - This file used during the debug process for storing interim information.
Server Response Timeout - The amount of time allowed for a server response. If no response is received within this time, a notification will be generated to inform you that the Server is not responding.
Encrypt Communications using SSL - To enable SSL encryption make sure this option is selected here and in Platform’s Dashboard | Preferences.
|
|
|
|
|
Related Links: |
|
|
|