Tomcat7 App Server (v13 Infinity)

Software Application Versions

• Apache 2.2
• Tomcat 7.0
• mod_jk 1.2
• Java 1.6
• MySQL Client (5.1 or 5.5)

The PHP App Server ServerTemplate install Apache with PHP on a single instance. The application code is downloaded from a git repository and placed into the webserver directory to be hosted. There are recipes to set up tags so the PHP App Server can be found by a Load Balancer and to request that a Load Balancer find it. The PHP App Server can be used in a RightScale autoscaling application server array. Below are descriptions of the various scripts avaiable in the PHP App Server ServerTemplate.

Boot Sequence:

• ephemeral_lvm::default - This recipe sets up available ephemeral devices to be an LVM device, formats it, and mounts it.
• rightscale_tag::default - Sets the standard machine tags for a RightScale server which are server:uuid, server:public_ip_X, server:private_ip_X (where X is 0, 1, etc.)
• rs-application_php::default - Installs PHP and required dependencies and deploys the application code.

Operational Scripts:

• rs-application_php::default - Installs PHP and required dependencies and deploys the application code.
• rs-application_php::tags - Adds machine tags to the application server with application server tags used in setting up a 3-tier architecture in a RightScale environment.
• rs-application_php::collectd - This recipe sets up collectd monitoring for the application server by installing the collectd package for Apache.
• rs-application_php::application_backend - This recipe attaches the application server to the load balancer servers serving the same application name as that of the application server and existing in the same deployment. This recipe schedules the execution of the recipe specified in node['rs-application_php']['remote_attach_recipe'] attribute on the load balancer servers matching the machine tag ‘load_balancers:active_<application_name>=true’. This remote recipe execution is achieved by the rs_run_recipe utility.
• rs-application_php::application_backend_detached - This recipe detaches the application server from the load balancer servers serving the same application name as that of the application server and existing in the same deployment. This recipe schedules the execution of the recipe specified in node['rs-application_php']['remote_detach_recipe'] attribute on the load balancer servers matching the machine tag ‘load_balancers:active_<application_name>=true’. This remote recipe execution is achieved by the rs_run_recipe utility.

Retrieval of Application Code

The ServerTemplate contains scripts that support the retrieval of application code from the following locations:

• ROS Container (*.zip, *.tgz)
• SVN Repository
• Git Repository
• FTP Server
• Specified URL (http://www.example.com/myapp.zip)
• rsync

The application code will be placed on the local instance in a location that is based upon the values specified for the following inputs. 

• Project App root - text: /home/webapps   (default)
• Application Name - text: myapp

In the example above, the root directory for the application code will be stored in: /home/webapps/myapp

Location of WAR file

By default, the retrieved WAR file is retrieved from the specified ROS container or software repository, renamed ROOT.war and saved to the same directory as the application's root directory, which is specified by the 'Project App root' input (default: /home/webapps). However, you can use the 'War file for ROOT' input to store the WAR file in a different location relative to the application's root directory.