GitHub - ndelic0/puppetlabs-tomcat: PuppetLabs Tomcat module

#tomcat

####Table of Contents

Overview
Module Description - What the module does and why it is useful
Setup - The basics of getting started with tomcat
- Setup requirements
- Beginning with tomcat
Usage - Configuration options and additional functionality
Reference - An under-the-hood peek at what the module is doing and how
Limitations - OS compatibility, etc.
Development - Guide for contributing to the module

##Overview

The tomcat module lets you use Puppet to install, deploy, and configure Tomcat web services.

##Module Description

Tomcat is a Java web service provider. The tomcat module lets you use Puppet to install Tomcat, manage its configuration file, and deploy web apps to it. It supports multiple instances of Tomcat spanning multiple versions.

##Setup

###Setup requirements

The tomcat module requires puppetlabs-stdlib version 4.0 or newer. On Puppet Enterprise you must meet this requirement before installing the module. To update stdlib, run:

puppet module upgrade puppetlabs-stdlib

Beginning with tomcat

The simplest way to get Tomcat up and running with the tomcat module is to install the Tomcat source and start the service:

tomcat::install { '/opt/tomcat':
  source_url => 'http://www-us.apache.org/dist/tomcat/tomcat-7/v7.0.68/bin/apache-tomcat-7.0.68.tar.gz',
}
tomcat::instance { 'default':
  catalina_home => '/opt/tomcat',
}

Usage

I want to run multiple instances of multiple versions tomcat

class { 'java': }

tomcat::install { '/opt/tomcat8':
  source_url => 'http://www-eu.apache.org/dist/tomcat/tomcat-8/v8.0.32/bin/apache-tomcat-8.0.32.tar.gz'
}
tomcat::instance { 'tomcat8-first':
  catalina_home => '/opt/tomcat8',
  catalina_base => '/opt/tomcat8/first',
}
tomcat::instance { 'tomcat8-second':
  catalina_home => '/opt/tomcat8',
  catalina_base => '/opt/tomcat8/second',
}
# Change the default port of the second instance server and HTTP connector
tomcat::config::server { 'tomcat8-second':
  catalina_base => '/opt/tomcat8/second',
  port          => '8006',
}
tomcat::config::server::connector { 'tomcat8-second-http':
  catalina_base         => '/opt/tomcat8/second',
  port                  => '8081',
  protocol              => 'HTTP/1.1',
  additional_attributes => {
    'redirectPort' => '8443'
  },
}

tomcat::install { '/opt/tomcat6':
  source_url => 'http://www-eu.apache.org/dist/tomcat/tomcat-6/v6.0.45/bin/apache-tomcat-6.0.45.tar.gz',
}
tomcat::instance { 'tomcat6':
  catalina_home => '/opt/tomcat6',
}
# Change tomcat 6's server and HTTP/AJP connectors
tomcat::config::server { 'tomcat6':
  catalina_base => '/opt/tomcat6',
  port          => '8105',
}
tomcat::config::server::connector { 'tomcat6-http':
  catalina_base         => '/opt/tomcat6',
  port                  => '8180',
  protocol              => 'HTTP/1.1',
  additional_attributes => {
    'redirectPort' => '8543'
  },
}
tomcat::config::server::connector { 'tomcat6-ajp':
  catalina_base         => '/opt/tomcat6',
  port                  => '8109',
  protocol              => 'AJP/1.3',
  additional_attributes => {
    'redirectPort' => '8543'
  },
}

I want to deploy WAR files

Add the following to any existing installation with your own war source:

tomcat::war { 'sample.war':
  catalina_base => '/opt/tomcat8/first',
  war_source    => '/opt/tomcat8/webapps/docs/appdev/sample/sample.war',
}

The name of the WAR file must end with '.war'.

The war_source can be a local path or a puppet:///, http://, or ftp:// URL.

I want to remove some configuration

Different configuration defines will allow an ensure parameter to be passed, though the name may vary based on the define.

To remove a connector, for instance, the following configuration ensure that it is absent:

tomcat::config::server::connector { 'tomcat8-jsvc':
  connector_ensure => 'absent',
  catalina_base    => '/opt/tomcat8/first',
  port             => '8080',
  protocol         => 'HTTP/1.1',
}

I want to manage a Connector or Realm that already exists

Describe the Realm or HTTP Connector element using tomcat::config::server::realm or tomcat::config::server::connector, and set purge_realms or purge_connectors to 'true'.

tomcat::config::server::realm { 'org.apache.catalina.realm.LockOutRealm':
  realm_ensure => 'present',
  purge_realms => true,
}

Puppet removes any existing Connectors or Realms and leaves only the ones you've specified.

##Reference

###Classes

####Public Classes

tomcat: Main class. Manages some of the defaults for installing and configuring Tomcat.

####Private Classes

tomcat::params: Manages Tomcat parameters.

###Defines

####Public Defines

tomcat::config::properties::property: Adds a property to catalina.properties file
tomcat::config::server: Configures attributes for the Server element in $CATALINA_BASE/conf/server.xml.
tomcat::config::server::connector: Configures Connector elements in $CATALINA_BASE/conf/server.xml.
tomcat::config::server::context: Configures Context elements in $CATALINA_BASE/conf/server.xml.
tomcat::config::server::engine: Configures Engine elements in $CATALINA_BASE/conf/server.xml.
tomcat::config::server::globalnamingresource: Configures Global Resource elements
tomcat::config::server::host: Configures Host elements in $CATALINA_BASE/conf/server.xml.
tomcat::config::server::listener: Configures Listener elements in $CATALINA_BASE/conf/server.xml.
tomcat::config::server::realm: Configures Realm elements in $CATALINA_BASE/conf/server.xml.
tomcat::config::server::service: Configures a Service element element nested in the Server element in $CATALINA_BASE/conf/server.xml.
tomcat::config::server::tomcat_users: Configures user and role elements for [UserDatabaseRealm] (http://tomcat.apache.org/tomcat-8.0-doc/realm-howto.html#UserDatabaseRealm) or [MemoryRealm] (http://tomcat.apache.org/tomcat-8.0-doc/realm-howto.html#MemoryRealm) in $CATALINA_BASE/conf/tomcat-users.xml or any other specified file.
tomcat::config::server::valve: Configures a Valve element in $CATALINA_BASE/conf/server.xml.
tomcat::config::context: Configures a Context element in $CATALINA_BASE/conf/context.xml.
tomcat::config::context::resource: Configures a Resource element in $CATALINA_BASE/conf/context.xml.
tomcat::config::context::resourcelink: Configures a ResourceLink element in $CATALINA_BASE/conf/context.xml.
tomcat::install: Installs a Tomcat instance.
tomcat::instance: Configures a Tomcat instance.
tomcat::service: Provides Tomcat service management.
tomcat::setenv::entry: Adds an entry to a Tomcat configuration file (e.g., setenv.sh or /etc/sysconfig/tomcat).
tomcat::war: Manages the deployment of WAR files.

####Private Defines

tomcat::install::package: Installs Tomcat from a package.
tomcat::install::source: Installs Tomcat from source.
tomcat::instance::copy_from_home: Copies required files from installation to instance
tomcat::instance::dependencies: Declares puppet dependency chain for an instance.
tomcat::config::properties: Creates instance catalina.properties

###Parameters

All parameters are optional except where otherwise noted.

####tomcat The base class sets defaults used by other defined types, such as tomcat::install and tomcat::instance, such as a default catalina_home.

#####catalina_home

Specifies the default root directory of the Tomcat installation. Valid options: a string containing an absolute path. Default: '/opt/apache-tomcat'.

#####group

Specifies a default group to run Tomcat as. Valid options: a string containing a valid group name. Default: 'tomcat'.

#####install_from_source

Specifies whether to default to installing Tomcat from source. Valid options: 'true' and 'false'. Default: 'true'.

#####manage_group

Determines whether defines should default to creating the specified group, if it doesn't exist. Uses Puppet's native group resource type with default parameters. Valid options: 'true' and 'false'. Default: 'true'.

#####manage_user

Determines whether defines should default to creating the specified user, if it doesn't exist. Uses Puppet's native user resource type with default parameters. Valid options: 'true' and 'false'. Default: 'true'.

#####purge_connectors

Specifies whether to purge any unmanaged Connector elements that match defined protocol but have a different port from the configuration file by default. Valid options: 'true' and 'false'. Default: 'false'.

#####purge_realms

Specifies whether to purge any unmanaged realm elements from the configuration file by default. Valid options: 'true' and 'false'. Default: 'false'. If two realms are defined for a specific server config only use purge_realms for the first realm and ensure the realms enforce a strict order between each other.

#####user

Specifies a default user to run Tomcat as. Valid options: a string containing a valid username. Default: 'tomcat'.

tomcat::config::properties::property

Specifies an additional entry for the catalina.properties file a given catalina base.

`property`

The name of the property. Default: $name

`catalina_base`

The catalina base of the catalina.properties file. The resource will manage the values in ${catalina_base}/conf/catalina.properties . Required.

`value`

The value of the property. Required.

####tomcat::config::server

#####address

Specifies a TCP/IP address on which to listen for the shutdown command. Maps to the address XML attribute. Valid options: a string. Default: undef.

#####address_ensure

Specifies whether the address XML attribute should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####catalina_base

Specifies the base directory of the Tomcat installation to manage. Valid options: a string containing an absolute path. Default: $tomcat::catalina_home.

#####class_name

Specifies the Java class name of a server implementation to use. Maps to the className XML attribute in the configuration file. Valid options: a string containing a Java class name. Default: undef.

#####class_name_ensure

Specifies whether the className XML attribute should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####port

Specifies a port on which to listen for the designated shutdown command. Maps to the port XML attribute. Valid options: a string containing a port number. Default: undef.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

#####shutdown

Designates a command that shuts down Tomcat when the command is received through the specified address and port. Maps to the shutdown XML attribute Valid options: a string. Default: undef.

####tomcat::config::server::connector

#####additional_attributes

Specifies any further attributes to add to the Connector. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: {}.

#####attributes_to_remove

Specifies any attributes to remove from the Connector. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: [].

#####catalina_base

Specifies the base directory of the Tomcat installation to manage. Valid options: a string containing an absolute path. Default: $::tomcat/catalina_home.

#####connector_ensure

Specifies whether the Connector XML element should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####parent_service

Specifies which Service element the Connector should nest under. Valid options: a string containing the name attribute of the Service. Default: 'Catalina'.

#####port

Required if connector_ensure is set to 'true' or 'present'. Sets a TCP port on which to create a server socket. Maps to the port XML attribute. Valid options: a string.

#####protocol

Specifies a protocol to use for handling incoming traffic. Maps to the protocol XML attribute. Valid options: a string. Default: $name.

#####purge_connectors

Specifies whether to purge any unmanaged Connector elements that match defined protocol but have a different port from the configuration file. Valid options: 'true' and 'false'. Default: 'false'.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

####tomcat::config::server::context

#####additional_attributes

Specifies any further attributes to add to the Context. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: {}.

#####attributes_to_remove

Specifies any attributes to remove from the Context. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: [].

#####catalina_base

Specifies the base directory of the Tomcat installation to manage. Valid options: a string containing an absolute path. Default: $::tomcat/catalina_home.

#####context_ensure

Specifies whether the Context XML element should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####doc_base

Specifies a Document Base (or Context Root) directory or archive file. Maps to the docBase XML attribute. Valid options: a string containing a path (either an absolute path or a path relative to the appBase directory of the owning Host). Default: $name.

#####parent_engine

Specifies which Engine element the Context should nest under. Only valid if parent_host is specified. Valid options: a string containing the name attribute of the Engine. Default: undef.

#####parent_host

Specifies which Host element the Context should nest under. Valid options: a string containing the name attribute of the Host. Default: undef.

#####parent_service

Specifies which Service XML element the Context should nest under. Valid options: a string containing the name attribute of the Service. Default: 'Catalina'.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

####tomcat::config::server::engine

#####background_processor_delay

Determines the delay between invoking the backgroundProcess method on this engine and its child containers. Maps to the backgroundProcessorDelay XML attribute. Valid options: an integer, in seconds. Default: undef.

#####background_processor_delay_ensure

Specifies whether the backgroundProcessorDelay XML attribute should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####catalina_base

Specifies the base directory of the Tomcat installation to manage. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####class_name

Specifies the Java class name of a server implementation to use. Maps to the className XML attribute. Valid options: a string containing a Java class name. Default: undef.

#####class_name_ensure

Specifies whether the className XML attribute should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####default_host

Required. Specifies a host to handle any requests directed to hostnames that exist on the server but are not defined in this configuration file. Maps to the defaultHost XML attribute of the Engine. Valid options: a string containing a hostname.

#####engine_name

Specifies the logical name of the Engine, used in log and error messages. Maps to the name XML attribute. Valid options: a string. Default: the '[name]' passed in your define.

#####jvm_route

Specifies an identifier to enable session affinity in load balancing. Maps to the jvmRoute XML attribute. Valid options: string. Default: undef.

#####jvm_route_ensure

Specifies whether the jvmRoute XML attribute should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####parent_service

Specifies which Service element the Engine should nest under. Valid options: a string containing the name attribute of the Service. Default: 'Catalina'.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

#####start_stop_threads

Sets how many threads the Engine should use to start child Host elements in parallel. Maps to the startStopThreads XML attribute. Valid options: a string. Default: undef.

#####start_stop_threads_ensure

Specifies whether the startStopThreads XML attribute should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

tomcat::config::server::globalnamingresource

Configure GlobalNamingResources Resource elements in $CATALINA_BASE/conf/server.xml

`ensure`

Determines whether the specified XML element should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

`catalina_base`

Specifies the base directory of the Tomcat instance. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home

`additional_attributes`

Specifies any further attributes to add to the Host. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: {}.

`attributes_to_remove`

Specifies any attributes to remove from the Host. Valid options: an array of '< attribute >' => '< value >' pairs. Default: [].

`server_config`

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: ${catalina_base}/config/server.xml

####tomcat::config::server::host

#####additional_attributes

Specifies any further attributes to add to the Host. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: {}.

#####aliases

Optional array that specifies the list of Host Name Aliases for this particular Host. If omitted, any currently-defined Aliases will not be altered. If present, the list Aliases will be set to exactly match the contents of this array. Thus, for example, an empty array can be used to explicitly force there to be no Aliases for the Host.

#####app_base

Required unless host_ensure is set to 'false' or 'absent'. Specifies the Application Base directory for the virtual host. Maps to the appBase XML attribute. Valid options: a string.

#####attributes_to_remove

Specifies any attributes to remove from the Host. Valid options: an array of '< attribute >' => '< value >' pairs. Default: [].

#####catalina_base

Specifies the base directory of the Tomcat installation to manage. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####host_ensure

Specifies whether the virtual host (the Host XML element) should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####host_name

Specifies the network name of the virtual host, as registered on your DNS server. Maps to the name XML attribute. Valid options: a string. Default: the '[name]' passed in your define.

#####parent_service

Specifies which Service element the Host should nest under. Valid options: a string containing the name attribute of the Service. Default: 'Catalina'.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

####tomcat::config::server::listener

#####additional_attributes

Specifies any further attributes to add to the Listener. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: {}.

#####attributes_to_remove

Specifies any attributes to remove from the Listener. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: [].

#####catalina_base

Specifies the base directory of the Tomcat installation. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####class_name

Specifies the Java class name of a server implementation to use. Maps to the className XML attribute of a Listener Element. Valid options: a string containing a Java class name. Default: $name.

#####listener_ensure

Specifies whether the Listener XML element should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####parent_engine

Specifies which Engine element this Listener should nest under. Valid options: a string containing the name attribute of the Engine. Default: undef.

#####parent_host

Specifies which Host element this Listener should nest under. Valid options: a string containing the name attribute of the Host. Default: undef.

#####parent_service

Specifies which Service element the Listener should nest under. Only valid if parent_engine or parent_host is specified. Valid options: a string containing the name attribute of the Service. Default: 'Catalina'.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

####tomcat::config::server::realm

#####additional_attributes

Specifies any further attributes to add to the Realm element. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: {}.

#####attributes_to_remove

Specifies any attributes to remove from the Realm element. Valid options: an array of '< attribute >' => '< value >' pairs. Default: [].

#####catalina_base

Specifies the base directory of the Tomcat installation. Default: $::tomcat::catalina_home.

#####class_name

Specifies the Java class name of a Realm implementation to use. Maps to the className XML attribute. Valid options: a string containing a Java class name. Default: the '[name]' passed in your define.

#####parent_engine

Specifies which Engine element this Realm should nest under. Valid options: a string containing the name attribute of the Engine. Default: 'Catalina'.

#####parent_host

Specifies which Host element this Realm should nest under. Valid options: a string containing the name attribute of the Host. Default: undef.

#####parent_realm

Specifies which Realm element this Realm should nest under. Valid options: a string containing the className attribute of the Realm element. Default: undef.

#####parent_service

Specifies which Service element this Realm element should nest under. Valid options: a string containing the name attribute of the Service. Default: 'Catalina'.

#####purge_realms

Specifies whether to purge any unmanaged Realm elements from the configuration file. Valid options: 'true' and 'false'. Default: 'false'.

#####realm_ensure

Specifies whether the Realm element should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

####tomcat::config::server::service

#####catalina_base

Specifies the base directory of the Tomcat installation. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####class_name

Specifies the Java class name of a server implementation to use. Maps to the className XML attribute. Valid options: a string containing a Java class name. Default: undef.

#####class_name_ensure

Specifies whether the className XML attribute should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

#####service_ensure

Specifies whether the Service element should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

####tomcat::config::server::tomcat_users

#####catalina_base

Specifies the base directory of the Tomcat installation. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####element

Specifies the type of element to manage. Valid options: 'user' or 'role'. Default: 'user'.

#####element_name

Sets the element's username (or rolename, if element is set to 'role'). Valid options: a string. Default: $name.

#####ensure

Determines whether the specified XML element should exist in the configuration file. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####file

Specifies the configuration file to manage. Valid options: a string containing a fully-qualified path. Default: '$CATALINA_BASE/conf/tomcat-users.xml'.

#####manage_file

Specifies whether to create the specified configuration file if it doesn't exist. Uses Puppet's native file resource type with default parameters. Valid options: 'true' and 'false'. Default: 'true'.

#####password

Specifies a password for user elements. Valid options: a string. Default: undef.

#####roles

Specifies one or more roles. Only valid if element is set to 'role'. Valid options: an array of strings. Default: [].

####tomcat::config::server::valve

#####additional_attributes

Specifies any further attributes to add to the Valve. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: {}.

#####attributes_to_remove

Specifies any attributes to remove from the Valve. Valid options: a hash of '< attribute >' => '< value >' pairs. Default: [].

#####catalina_base

Specifies the base directory of the Tomcat installation. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####class_name

Specifies the Java class name of a server implementation to use. Maps to the className XML attribute. Valid options: a string containing a Java class name. Default: the '[name]' passed in your define.

#####parent_host

Specifies which virtual host the Valve should nest under. Valid options: a string containing the name of a Host element. Default: If you don't specify a host, the Valve element nests under the Engine of your specified parent Service.

#####parent_service

Specifies which Service element the Valve should nest under. Valid options: a string containing the name of a Service element. Default: 'Catalina'.

#####server_config

Specifies a server.xml file to manage. Valid options: a string containing an absolute path. Default: '${catalina_base}/config/server.xml'.

#####valve_ensure

Specifies whether the Valve should exist in the configuration file. Maps to the Valve XML element. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

tomcat::config::context

Specifies a configuration Context element in ${catalina_base}/conf/context.xml for other tomcat::config::context::* defines.

`catalina_base`

Specifies the root of the Tomcat installation.

tomcat::config::context::resource

Specifies Resource elements in ${catalina_base}/conf/context.xml

`ensure`

specifies whether you are trying to add or remove the Resource element. Valid values are 'true', 'false', 'present', and 'absent'. Defaults to 'present'

`resource_name`

The name of the Resource to be created, relative to the java:comp/env context. Default: $name

`resource_type`

The fully qualified Java class name expected by the web application when it performs a lookup for this resource. Required to create the resource.

`catalina_base`

Specifies the root of the Tomcat installation. Default: $tomcat::catalina_home

`additional_attributes`

Specifies any additional attributes to add to the Valve. Should be a hash of the format 'attribute' => 'value'. This parameter is optional.

`attributes_to_remove`

Specifies any attributes to remove from the Valve. Should be a hash of the format 'attribute' => 'value'. This parameter is optional.

tomcat::config::context::resourcelink

Specifies a ResourceLink element in the designated xml configuration.

`ensure`

specifies whether you are trying to add or remove the ResourceLink element. Valid values are 'true', 'false', 'present', and 'absent'. Defaults to 'present'

`catalina_base`

Specifies the root of the Tomcat installation. Default: $tomcat::catalina_home

`resourcelink_name`

The name of the ResourceLink to be created, relative to the java:comp/env context. Default: $name

`resourcelink_type`

The fully qualified Java class name expected by the web application when it performs a lookup for this resource link.

`additional_attributes`

Specifies any additional attributes to add to the Valve. Should be a hash of the format 'attribute' => 'value'. This parameter is optional.

`attributes_to_remove`

Specifies any attributes to remove from the Valve. Should be a hash of the format 'attribute' => 'value'. This parameter is optional.

tomcat::install

Installs the software into the given directory from a source Apache Tomcat tarball. Alternatively, it may be used to install a tomcat package.

Tomcat instances may then be created from the install using tomcat::instance and pointing tomcat::instance::catalina_home to the directory managed by tomcat::install.

`catalina_home`

specifies the directory of the Tomcat installation from which the instance should be created. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

`install_from_source`

Specifies whether to install from source or from a package. If set to true installation uses the source_url, source_strip_first_dir, user, group, manage_user, and manage_group parameters. If set to false installation uses the package_ensure, package_name, and package_options parameters.

Valid options: true and false. Default: true.

`source_url`

In single-instance mode: Required if install_from_source is set to true. Specifies the source URL to install from.

Valid options: a string containing a puppet://, http(s)://, or ftp:// URL.

`source_strip_first_dir`

Specifies whether to strip the topmost directory of the tarball when unpacking it. Only valid if install_from_source is set to true. Valid options: true and false. Default: true.

`user`

Specifies the owner of the source installation directory. Default: $::tomcat::user

`group`

Specifies the group of the source installation directory. Default: $::tomcat::group

`manage_user`

Specifies whether the user should be managed by this module or not. Default: $::tomcat::manage_user

`manage_group`

Specifies whether the group should be managed by this module or not. Default: $::tomcat::manage_group

`package_ensure`

Determines whether the specified package should be installed. Only valid if install_from_source is set to false. Maps to the ensure parameter of Puppet's native package resource type. Default: 'present'.

`package_name`

Required if install_from_source is set to false. Specifies the package to install. Valid options: a string containing a valid package name.

`package_options`

Unused if install_from_source is set to true. Specify additional options to use on the generated package resource. See the documentation of the package resource type for possible values.

tomcat::instance

Declares a tomcat instance.

There are two different modes of use: a single tomcat installation and instance (called "single-instance" by this readme), or a single tomcat installation with multiple instances, each with its own directory structure (called "multi-instance" by this readme).

single-instance: If a tomcat::instance is declared with catalina_home and catalina_base both pointing to the directory of a tomcat::install then it only configures a single instance.
multi-instance: If a tomcat::instance is declared with catalina_home pointing to the same directory as a tomcat::install and catalina_base pointing at a different directory then it is configured as an instance of the Apache Tomcat software. Multiple instances of a single install may be created using this method.

`catalina_base`

Specifies the $CATALINA_BASE of the Tomcat instance where logs, configuration files, and the 'webapps' directory are managed. For single-instance installs, this is the same as the catalina_home parameter

Valid options: a string containing an absolute path. Default: $catalina_home

`catalina_home`

Specifies the directory where the Apache Tomcat software is installed by a tomcat::install resource.

Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home

`user`

Specifies the owner of the instance directories and files. Default: $::tomcat::user

`group`

Specifies the group of the instance directories and files. Default: $::tomcat::group

`manage_user`

Specifies whether the user should be managed by this module or not. Default: $::tomcat::manage_user

`manage_group`

Specifies whether the group should be managed by this module or not. Default: $::tomcat::manage_group

`manage_service`

Specifies whether a tomcat::service corresponding to this instance should be declared. Defaults to true for multi-instance installs and false for single-instance installs.

`java_home`

Specifies the java home to be used when declaring a tomcat::service instance. See tomcat::service

`use_jsvc`

Specifies whether jsvc should be used when declaring a tomcat::service instance. Note that this module will not compile and install jsvc for you. See tomcat::service

`use_init`

Specifies whether an init script should be managed when declaring a tomcat::service instance. See tomcat::service

tomcat::service

#####catalina_base

Specifies the base directory of the Tomcat installation. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####catalina_home

Specifies the root directory of the Tomcat installation. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####java_home

Specifies where Java is installed. Only applies if use_jsvc is set to 'true'. Valid options: a string containing an absolute path. Default: undef. Note: if you don't specify a home path in this parameter, Puppet does not pass the -home switch to Tomcat. That can cause problems on some systems, so we recommend including this parameter.

#####service_enable

Specifies whether to enable the Tomcat service at boot. Only valid if use_init is set to 'true'. Valid options: 'true' and 'false'. Default: 'true', if use_init is set to 'true' and service_ensure is set to 'running' or 'true'.

#####service_ensure

Specifies whether the Tomcat service should be running. Maps to the ensure parameter of Puppet's native service resource type. Valid options: 'running', 'stopped', 'true', and 'false'. Default: 'present'.

#####service_name

Required if use_init is set to 'true'. Specifies the name of the Tomcat service. Valid options: a string.

#####start_command

Designates a command to start the service. Valid options: a string. Default: determined by the values of use_init and use_jsvc.

#####stop_command

Designates a command to stop the service. Valid options: a string. Default: determined by the values of use_init and use_jsvc.

`use_init`

Specifies whether to use a package-provided init script for service management. Note that the tomcat module does not supply an init script. If both use_jsvc and use_init are set to 'false', tomcat uses the following commands for service management:

$CATALINA_HOME/bin/catalina.sh start
$CATALINA_HOME/bin/catalina.sh stop

Valid options: 'true' and 'false'. Default: 'false'.

`use_jsvc`

Specifies whether to use Jsvc for service management. If both use_jsvc and use_init are set to 'false', tomcat uses the following commands for service management:

$CATALINA_HOME/bin/catalina.sh start
$CATALINA_HOME/bin/catalina.sh stop

Valid options: 'true' and 'false'. Default: 'false'.

`user`

The user of the jsvc process when use_init => true

####tomcat::setenv::entry

#####base_path

Deprecated. Please use config_file instead.

#####config_file

Specifies the configuration file to edit. Valid options: a string containing an absolute path. Default: $'::tomcat::catalina_home/bin/setenv.sh'.

#####ensure

Determines whether the fragment should exist in the configuration file. Valid options: 'present', 'absent'. Default: 'present'.

#####order

Determines the ordering of your parameters in the configuration file (parameters with lower order values appear first.) Valid options: an integer or a string containing an integer. Default: '10'.

`addto`

Defines an additional environment variable that will be added to the beginning of the param

#####param

Specifies a parameter to manage. Valid options: a string. Default: the '[name]' passed in your define.

#####quote_char

Specifies a character to include before and after the specified value. Valid options: a string (usually a single or double quote). Default: (blank).

#####value

Required. Provides the value(s) of the managed parameter. Valid options: a string or an array. If passing an array, separate values with a single space.

####tomcat::war

#####app_base

Specifies where to deploy the WAR. Cannot be used in combination with deployment_path. Valid options: a string containing a path relative to $CATALINA_BASE. Default: If you don't specify an app_base, Puppet deploys the WAR to your specified deployment_path. If you don't specify that either, the WAR deploys to '${catalina_base}/webapps'.

#####catalina_base

Specifies the base directory of the Tomcat installation. Valid options: a string containing an absolute path. Default: $::tomcat::catalina_home.

#####deployment_path

Specifies where to deploy the WAR. Cannot be used in combination with app_base. Valid options: a string containing an absolute path. Default: If you don't specify a deployment_path, Puppet deploys the WAR to your specified app_base. If you don't specify that either, the WAR deploys to '${catalina_base}/webapps'.

#####war_ensure

Specifies whether the WAR should exist. Valid options: 'true', 'false', 'present', and 'absent'. Default: 'present'.

#####war_name

Specifies the name of the WAR. Valid options: a string containing a filename that ends in '.war'. Default: the '[name]' passed in your define.

#####war_purge

Specifies whether to purge the exploded WAR directory. Only applicable when war_ensure is set to 'absent' or 'false'.

Note: Setting this parameter to 'false' does not prevent Tomcat from removing the exploded WAR directory if Tomcat is running and autoDeploy is set to 'true'. Valid options: 'true' and 'false'. Default: 'true'.

#####war_source

Required unless war_ensure is set to 'false' or 'absent'. Specifies the source to deploy the WAR from. Valid options: a string containing a puppet://, http(s)://, or ftp:// URL.

##Limitations

This module only supports Tomcat installations on *nix systems. The tomcat::config::server* defines require Augeas version 1.0.0 or newer.

###Multiple Instances

Some Tomcat packages do not let you install more than one instance. You can avoid this limitation by installing Tomcat from source.

##Development

Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can't access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.

We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

For more information, see our module contribution guide.

###Contributors

To see who's already involved, see the list of contributors.

###Running tests

This project contains tests for both rspec-puppet and beaker-rspec to verify functionality. For in-depth information, please see their respective documentation.

Quickstart:

gem install bundler
bundle install
bundle exec rake spec
bundle exec rspec spec/acceptance
RS_DEBUG=yes bundle exec rspec spec/acceptance

Name		Name	Last commit message	Last commit date
Latest commit History 280 Commits
examples		examples
manifests		manifests
spec		spec
templates		templates
.fixtures.yml		.fixtures.yml
.geppetto-rc.json		.geppetto-rc.json
.gitattributes		.gitattributes
.gitignore		.gitignore
.rspec		.rspec
.travis.yml		.travis.yml
CHANGELOG.md		CHANGELOG.md
CONTRIBUTING.md		CONTRIBUTING.md
Gemfile		Gemfile
LICENSE		LICENSE
NOTICE		NOTICE
README.md		README.md
Rakefile		Rakefile
metadata.json		metadata.json

License

ndelic0/puppetlabs-tomcat

Folders and files

Latest commit

History

Repository files navigation

Beginning with tomcat

Usage

I want to run multiple instances of multiple versions tomcat

I want to deploy WAR files

I want to remove some configuration

I want to manage a Connector or Realm that already exists

tomcat::config::properties::property

property

catalina_base

value

tomcat::config::server::globalnamingresource

ensure

catalina_base

additional_attributes

attributes_to_remove

server_config

tomcat::config::context

catalina_base

tomcat::config::context::resource

ensure

resource_name

resource_type

catalina_base

additional_attributes

attributes_to_remove

tomcat::config::context::resourcelink

ensure

catalina_base

resourcelink_name

resourcelink_type

additional_attributes

attributes_to_remove

tomcat::install

catalina_home

install_from_source

source_url

source_strip_first_dir

user

group

manage_user

manage_group

package_ensure

package_name

package_options

tomcat::instance

catalina_base

catalina_home

user

group

manage_user

manage_group

manage_service

java_home

use_jsvc

use_init

tomcat::service

use_init

use_jsvc

user

addto

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

`property`

`catalina_base`

`value`

`ensure`

`catalina_base`

`additional_attributes`

`attributes_to_remove`

`server_config`

`catalina_base`

`ensure`

`resource_name`

`resource_type`

`catalina_base`

`additional_attributes`

`attributes_to_remove`

`ensure`

`catalina_base`

`resourcelink_name`

`resourcelink_type`

`additional_attributes`

`attributes_to_remove`

`catalina_home`

`install_from_source`

`source_url`

`source_strip_first_dir`

`user`

`group`

`manage_user`

`manage_group`

`package_ensure`

`package_name`

`package_options`

`catalina_base`

`catalina_home`

`user`

`group`

`manage_user`

`manage_group`

`manage_service`

`java_home`

`use_jsvc`

`use_init`

`use_init`

`use_jsvc`

`user`

`addto`

Packages