When an application is deployed, the content is not found in a subdirectory of /www/zendsvr6/htdocs. Instead, an Alias directive is used to define the content directory. This article tells how to find that content.
Zend Server 6 or 7 for IBM i, running on any supported version of IBM i.
This example uses the IBM i Samples application that is installed using these instructions:
When the application is deployed the content goes to a directory based on the Virtual Host configuration. The Samples application was installed to the default virtual host. To find it, we can start by looking at the Apache configuration file for Zend Server:
These lines define the default virtual host:
Notice that most of the definition is found in this include file:
The contents of the include file look like this:
Note: for applications deployed to other virtual hosts rather than the default, see the note at the end of the article.
Each application deployed to this virtual host will have a configuration file in this directory:
The configuration files will all have the '.conf' prefix, and will be picked up by the include of '*.conf'.
For the Samples application, the configuration file is named something like this:
Here are the contents of that file:
The Alias and Directory directives tell us the directory where content for the Samples application can be found:
It is useful to know where the application content is deployed, and in the case of an example application like the Samples application it can be useful to examine the code. However, it is not recommended to make changes to a deployed application by making code changes to the content in this location. Such changes would be lost if an update to the application is deployed. Instead, the changes are made in the source on the machine where the application is developed and tested, and then packaged and deployed as an update.