IBM Bluemix Integration

Zend Server's integration with IBM Bluemix allows you to quickly get your PHP applications up and running on a highly available PHP production environment which includes, amongst other features, a highly reliable PHP stack, application monitoring, troubleshooting, and more.

IBM Bluemix is based on Cloud Foundry technology. Therefore, the Zend Server buildpack can be used on any Cloud Foundry-based cloud.

Tell me more about Zend Server

How do I deploy my application?


Get acquainted with basic Cloud Foundry concepts:

Term Description


A buildpack is a set of scripts and data files that Cloud Foundry runs on an application package to create a droplet that contains everything the application needs to run. A buildpack is specific to a particular framework or runtime environment.


A droplet is the result of the application staging process, it is an uploaded application to which a buildpack has been applied. It is the original application, with a wrapper around it that accepts one input – the port where it should listen for HTTP requests, and has two methods, a start and a stop.

Application Manifest

An application manifest defines application deployment settings, such as the name of an application, the number of instances to deploy, the maximum memory available to an instance, the services it uses, and so on. The default name for a manifest is manifest.yml. Use of a manifest automates application deployment, allowing a user to provide deployment settings in a file rather than at the command line.


Cloud Foundry Services are any type of add-on that can be provisioned alongside your application; for example, a database or an account on a third-party SaaS provider.

For information on additional Cloud Foundry terms, check out the Cloud Foundry glossary at

Known Issues

  • Zend Server Code Tracing may not work properly in this version.

  • Zend Server Session Clustering may not work properly.
  • In the Zend Server UI, the Logs page does not work correctly when Zend Server is running in cluster mode.

  • Several issues might be encountered if you do not bind MySQL providing service to the app (SQL/MaraiaDB):

    • You can change settings using the Zend Server UI and apply them - but they will not survive application pushes and restarts, nor will they be propagated to new application instances.

    • Application packages deployed using Zend Server's deployment mechanism (.zpk packages) will not be propagated to new app instances.

    • Zend Server will not operate in cluster mode.

  • Application generated data is not persistent (this is a limitation of Cloud Foundry) unless saved to a third party storage provider (like S3).

  • MySQL is not included in the buildpack. If you require MySQL then you will have to setup your own server and configure your app to use it, or use a MySQL service.

  • If the application does not contain an 'index.php' file you will most likely encounter a "403 permission denied error".