In this Topic Hide
Zend Server is a tool that requires a minimal amount of actual interaction with the Administration Interface. Once your environment is setup, apart from occasionally logging in to view your system settings or your php.ini, there are not many day-to-day activities that require the Administration Interface.
The first point of reference for working with Zend Server is what to do after installation.
The following section describes the tasks that should be performed after
installing Zend Server
for the first time.
These tasks cover all the different
installation types (DEB, RPM,
Tarball and Windows).
Each task is accompanied by a description of its purpose and the expected
results.
Purpose: To verify the installation and that the Administration Interface is accessible.
Result: the Administration Interface opens in a browser.
The Administration Interface is a Web interface
that runs through a browser.
This procedure describes how to view the Administration Interface.
|
|
To view the Administration Interface:
|
|
The next time you log in to Zend Server, you are prompted for the password you set the first time you opened Zend Server. |
Purpose: To ensure that you can access the Administration Interface.
Result: Your password is created.
When you first run Zend Server, the registration screen is displayed. Define your Zend Server login password in this screen.
To view the different password management options, click Password Management.
Purpose: To verify that Apache is running.
Result: System confirmation.
This procedure describes how to check if the Apache Web server is running.
|
|
To check if the Apache server is running: DEB, RPM, Tarball: from the command line, run ps -ef | grep -E 'apache2|httpd'. Windows: In the system tray, hover over the Apache Monitor icon to view the Apache status. If necessary, click to open a dialog with the Stop, Start and Restart options. |
|
A notification with the Apache server status is displayed. |
Note:
Every time the
Apache is restarted, the following message is displayed: "httpd:
Could not reliably determine the server's fully qualified domain name,
using 127.0.0.1 for ServerName".
To resolve this situation, add a line to the Apache configuration file,
as follows:
Open the file <install_path>/apache2/conf/httpd.conf and add the
following line, placing your server's Host name in the brackets: ServerName
[server name]
Purpose: To verify that the bundled webserver is installed and running.
Result: System confirmation.
This procedure describes how to check if the IIS server is running.
|
|
To check if the IIS server is running: Use Microsoft: http://support.microsoft.com/kb/314771 [^] HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp Iisreset /status |
|
If
the following message is received, then IIS is not
running: If the following messages are received, then IIS is running: “Status for Windows Process Activation Service ( WAS ) : Running" "Status for World Wide Web Publishing Service ( W3SVC ) : Running” ---&61664; installed |
Purpose: To verify that the installed Web server is running properly.
Result: The "Hello World" message is displayed in your browser.
This procedure describes how to run a test PHP script.
|
|
To run a simple test script:
<?php The "Hello World" message is displayed when the code runs in a browser.
|
|
Your browser displays the "Hello World" message. |
Purpose: To enable PHP debugging using Zend Studio and Zend Server.
Result: You are able to debug your PHP code and view the results in Zend Studio.
Before working with the Debugger, configure the allowed hosts in Server Setup | Debugger.
Note:
By default, Zend Server comes with a permissive setting that allows all standard private IP addresses (for example 10.*.*.*) to access the Debugger. For security reasons, if you do not have an immediate need for permissive access, remove these ranges from the Allowed Hosts: 10.*.*.* / 192.168.*.* / 172.16.*.*.
Additional setup information can be found in the Installation Guide, in Package Setup and Control Scripts.
|
|
|
Related Links: |
|
|