30.07.2012 Views

Reference Guide

Reference Guide

Reference Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Zend Server <strong>Reference</strong> Manual<br />

Understanding the Package Structure<br />

Your .zpk package contains the data, scripts, and an XML descriptor file for your application.<br />

74<br />

Data - Your application (all the source code files of your application).<br />

Descriptor File - This XML file, which is defined by an XSD file, describes all necessary<br />

information in order to deploy your application using Zend Server’s deployment feature. For an<br />

example of the descriptor template see The XML Descriptor File.<br />

It contains three parts:<br />

1. General information about the package:<br />

name - (Required) The application's name.<br />

summary - The application's short description.<br />

description - The application's long description.<br />

version - (Required) The application's version number.<br />

eula - The EULA file.<br />

appdir - (Required) The applications directory. By default, this is the data folder of<br />

your package.<br />

docroot - The alias will point to the directory you specify.<br />

scriptsdir - The directory in which your scripts are located. By default, this is the<br />

scripts folder of your package.<br />

variables - Define environment variables for the deployment scripts.<br />

2. Dependencies which need to be satisfied in order for the application to function correctly.<br />

For example, PHP version and PHP directive values.<br />

3. User parameters that are required for the application’s deployment. For example,<br />

database name. These, along with the values you define, will appear in the User<br />

Parameters dialog during deployment. For more information see Deploying an<br />

Application.<br />

• Scripts (PHP hook scripts) - Zend Serverdeployment consists of four actions: two for deployment,<br />

and two for removal. Two hook scripts are provided for each action (pre and post), allowing you to<br />

customize the actions according to your needs.<br />

2. Deploy:<br />

Stage - Place the contents of the .zpk application package on the server or on<br />

the cluster nodes.<br />

• Pre-stage - All customized actions that must be executed before the<br />

staging process begins.<br />

• Post-stage - All customized actions that must be executed after the<br />

staging process ends.<br />

Activate - Perform the final steps necessary to make a staged application public.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!