- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with Pentaho
- 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
A puppet module that allows one to install the Pentaho BA server component on a system. This module aims to configure only Pentaho component and is not responsible to configure the database or the application server.
As stated above this module allow one to automate the installation and configuration of the Pentaho BA serrver. It handles the configuration of either MySQL or PostgreSQL as a database backend. It has been tested with the Tomcat application server but should work with any other application server.
- Pentaho's pentaho-solution folder
- Pentaho's tomcat configuration
- Database backend data
As stated above, this module only handle the Pentaho installation and configuration. One needs to properly configure the other pieces needed to have a working environment, database, application server, etc..
In a properly configured environment, to get started simply run :
include ::pentaho
All the interaction with the Pentaho BA server is done via pentaho
.
Interactions with the actual tables to load in database is done via pentaho::database
.
pentaho
: Installs and configures Pentahopentaho::database
: Installs and configures required databases
pentaho::config
: Configures the file in the pentaho-solutions directorypentaho::setup
: Installs the required drivers and file to proceed with installationpentaho::webapp
: Configures the web application withing the servlet container
####pentaho
#####version
The Pentaho BA server version that will be installed.
#####applicationserver_base
The application server directory.
#####applicationserver_user
The application server user name.
#####applicationserver_group
The application server group name.
#####listen_ip
The IP address Pentaho shoud listen on. Note: It is unrelated to the application server configuration, it relates strictly to the parameter that will be present in web.xml.
#####manage_jdbc_drivers
A list of jdbc drivers the installation should manage.
#####db_type
The type of the database backend.
#####db_host
The host of the database backend.
#####db_port
The port of the database backend.
#####quartz_db_user
The quartz database user name.
#####quartz_db_password
The quartz database user password.
#####hibernate_db_user
The hibernate database user name.
#####hibernate_db_password
The hibernate database user password.
#####jackrabbit_db_user
The jackrabbit database user name.
#####jackrabbit_db_password
The jackrabbit database user password.
#####pentaho_solutions_path
The pentaho-solutions directory path
#####pentaho_source_url
The pentaho source url to retrieve from.
#####h2driver_source_url
Since the h2 jdbc driver is not packaged, the url where to retrieve the driver from.
#####temp_folder
A temporary folder that will server as cache and drop temporary file into.
#####log_directory
The log directory.
####pentaho::database
#####db_type
The type of the database backend.
#####db_host
The host of the database backend.
#####db_port
The port of the database backend.
#####quartz_db_user
The quartz database user name.
#####quartz_db_password
The quartz database user password.
#####hibernate_db_user
The hibernate database user name.
#####hibernate_db_password
The hibernate database user password.
#####jackrabbit_db_user
The jackrabbit database user name.
#####jackrabbit_db_password
The jackrabbit database user password.
#####db_charset
The database charset
#####db_collate
The database collate
This is modules has been tested on :
- RedHat Enterprise 6
- CentOS 6
- MySQL (MariaDB)
- Tomcat
The list of contributors can be found at Contributors