Working with the Debugger
The that is included in Zend Server for IBM i is a remote debugging tool for developers who work with Zend Studio. If the Debugger Component is not set to "On" in the page, you are not able to run remote debug sessions using Zend Studio. For more information on turning the Debugger Component to "On", see .
From the Zend Server for IBM i perspective, other than defining allowed hosts and denied hosts, no additional interaction is required.
The following procedure describes how to define allowed hosts for debugging. Users define allowed hosts to create a list of IP addresses (of computers that run Zend Studio) that have permission to debug the PHP code that runs on the server.
|
|
|
|
|
To define allowed hosts for debugging:
-
In the Administration Interface go to Server Setup | Debugger.
-
In the "Allowed Zend Studio Clients for Debugging" section, enter a valid IP address or enter a range by entering the beginning of an IP address and adding '0' instead of the rest of the number. To make sure you are using (*) to specify a range of IPs select the pattern you want from the drop-down list.
-
From the drop-down list, select an option according to the type of IP address you entered. Click 'Exact IP address only' for a single IP, or one of the other options to represent a range of hosts.
-
Click  to add the Host.
-
The changes are applied after you restart the Server 
|
|
The IP or range of IPs is allowed to connect to the server to debug PHP code with Zend Studio.
To remove a specific IP from the list, click "Remove".
Important Note:
If your machine has several IP addresses (for example if you are using a wireless network connection on a laptop) verify that you have defined all the possible IP addresses as "Allowed Hosts for Debugging" or that the IP you want to use is first in the list of IPs in Zend Studio for Eclipse. (In Window | Preferences | PHP | Debug | Installed Debuggers, verify that Zend Debugger is selected and click Configure in the Client Host/IP field.)
|
The following procedure describes how to define denied hosts for debugging. Users define denied hosts to create a list of IP addresses (of computers that run Zend Studio) that do not have permission to debug the PHP code that runs on this server.
|
|
|
|
|
To define denied hosts for debugging:
-
In the Administration Interface go to Server Setup | Debugger.
-
In the "Denied Zend Studio Clients for Debugging" section, enter a valid IP address or use (*) to specify a range of IPs.
-
From the drop-down list, select an option according to the type of IP address you entered. Click 'Exact IP address only' for a single IP, or one of the other options to represent a range of hosts.
-
Click to add the host.
-
The changes are applied after you restart the Server .
|
|
The IP or range of IPs is denied permission to connect to the server to debug PHP code with Zend Studio.
To remove a specific IP from the list, click "Remove".
|
Note:
Do not add the same IP address to both the Allowed and Denied host lists. Pay attention when you specify a range of IP addresses: If you deny a range of addresses that includes an IP that was specified in the Allowed hosts, the host is not allowed to create a debug session.
Wildcards (Net Mask)
Wildcards use the asterisk (*) to define a string of IP addresses and to specify a range of IPs that are either allowed or denied hosts. This option makes it possible to specify a range of IPs from 0-255, according to the selected number of wildcards. For example, if you use the Net Mask option to deny the IPs 10.1.3. *, all the IP addresses beginning with 10.1.3. are denied access to the Studio Server (i.e., integration with Studio is not permitted for these IP addresses).
Remote Debugging Through a Firewall?
Remote debugging is the process of creating a connection between two machines: For example, the machine on which the Debugger (Zend Studio) resides and the machine on which the Zend Server for IBM i resides. When these machines are on the same local network or there are no security devices that limit remote connections, no additional action is required. However, if one or both of the machines are behind a firewall, the communication required to run the debug process is not allowed. To allow debugging and still maintain a secure environment, you need to use firewall tunneling. For more information on how to setup firewall tunneling, see .
