Introduction

This document describes the functionality provided by the Webserver plugin.

See the Deployit Reference Manual for background information on Deployit and deployment concepts.

Overview

The webserver-plugin is a Deployit plugin that supports deployment of web content and webserver configuration to a webserver.

Features

• Runs on Deployit 3.6 and up.
• Supports deployment to Apache and IHS webservers.
• Deploys and undeploys webserver artifacts:
  • Web content (HTML pages, images, etc.)
  • Virtual host configuration
  • Any configuration fragment
• Supports starting, stopping and restarting of webservers as control tasks.

Requirements

• Deployit requirements

  • Deployit: version 3.6+
  • Other Deployit Plugins: None

• Infrastructural requirements

  • User credentials for accessing the webserver executables on the host running the webserver.

Usage

The following table describes which deployable/container combinations are possible.

Deployable vs. Container table

The following table describes the effect a deployed has on it's container.

Deployed Actions Table

Using www.ApacheVirtualHost

The following is a manifest snippet that shows how web content and a virtual host can be included in a deployment package. The web content CI refers to a folder, html, included in the deployment package.

<udm.DeploymentPackage version="2.0" application="PetClinic-ear" >
    <jee.Ear name="PetClinic" file="PetClinic-2.0.ear" />
    <www.WebContent name="PetClnic-html" file="html" />
    <www.ApacheVirtualHostSpec name="PetClinic-vh">
        <host>*</host>
        <port>8080</port>
    </www.ApacheVirtualHostSpec>
</udm.DeploymentPackage>

Using www.ApacheConfFragment

Defining a new fragment to deploy to the Apache configuration takes two steps:

1. Defining the type of configuration fragment and its properties
2. Supplying a template for the configuration fragment implementation, per default the script searches for DEPLOYIT_HOME/ext/www/apache/${deployed.type}.conf.ftl.

Example:

1. Define an ApacheProxyPassSetting type in DEPLOYIT_HOME/ext/synthetic.xml :

    <type type="www.ApacheProxyPassSetting" extends="www.ApacheConfFragment" deployable-type="www.ApacheProxyPassSpec">
     <generate-deployable type="www.ApacheProxyPassSpec" extends="generic.Resource" />
     <property name="from" />
     <property name="to" />
     <property name="options" required="false" default="" />
     <property name="reverse" kind="boolean" required="false" default="false" />
    </type>  

2. Create a www.ApacheProxyPassSetting.conf.ftl in DEPLOYIT_HOME/ext/www/apache:

     --- start www.ApacheProxyPassSetting.conf.ftl ---
     ProxyPass ${deployed.from} ${deployed.to} <#if (deployed.options?has_content)>${deployed.options}</#if>
     <#if (deployed.reverse)>
     ProxyPassReverse ${deployed.from} ${deployed.to}
     </#if>
     --- end www.ApacheProxyPassSetting.conf.ftl ---