Taking Zend Server for a Spin - (Part 2 Troubleshooting)

In my last article we took Zend Server for a quick spin, getting some Zend Framework demos to work and we started to look at application monitoring. In this article I will be configuring Debugging/Profiling between Zend Server and Zend Studio Eclipse to enable better troubleshooting and quicker resolution. When things go wrong in your app, you want to know about it ASAP and fix the problem quickly before it affects the end-user. Zend Studio Eclipse can be tightly integrated with Zend Server and gives you a powerful way to address application problems. I'll be building upon my last article so if you want to follow along, please install Zend Server and get everything working from my PART 1.

Zend Studio Eclipse (ZSE) by itself supports local debugging out of the box, when you install ZSE, it installs its own PHP environment and allows you to "Debug Scripts". The downside is that the bundled Zend Studio PHP environment may not have all the extensions and capabilities you need to replicate your production/dev environment. This is why Zend Studio also supports "Remote Debugging", and dont be confused by the name, since you can use Remote debugging on the same server. Think of it as Client/Server debugging. The Client is Zend Studio that can debug against any other Server side PHP with the appropriate Zend Debugger installed. In this article I will be using Zend Server with the preinstalled debugger to get all this working.

Steps That I will show in my Video

1) Pre-req to install Zend Server and Zend Studio Eclipse
2) Verify debugger is active on Zend Server
3) Configure debugging permission for the Zend Server
4) Browse website page and Debug from IE or FF toolbar
5) Test Debugging in Zend Eclipse
6) Test Event Debugging and Troubleshooting from Zend Server
7) Test Profiling of an application bottleneck