Manage config files for the Scheduler plugin

The following configuration files for using the Scheduler plugin with LDBC and LDAP should only be customized by someone with the necessary qualifications and experience.

settings.xml

This file is located in the pentaho-server/pentaho-solutions/system/scheduler-plugin directory and contains properties that you can use to control the plugin cache for development purposes. In most cases, it is best not to modify any of the properties for cache-messages, max-age, or cache elements.

It also contains a section for defining the data source to be used for email group administration purposes in order to import existing emails and groups under the email-source element.

Example:

<email-source>pentaho</email-source>

Valid value for the email-source element:

Valid values	Description
jdbc	Uses a JDBC data source to import emails and groups.
ldap	Uses an LDAP data source to import emails and groups.
pentaho	Does not import emails and groups. Instead, you can create emails and groups using the email group administration module in PUC.

The configuration properties for the JDBC and LDAP data sources are located in the applicationContext-email-import.properties file.

applicationContext-email-import.properties

This file is located in the pentaho-server/pentaho-solutions/system/scheduler-plugin directory and contains the configuration properties for the JDBC and LDAP data sources. These data sources can be changed in the settings.xml file under the email-source element.

Note: Only someone with sufficient understanding of JDBC and LDAP should make changes to this file.

File location: pentaho-server/pentaho-solutions/system/scheduler-plugin

The password is encrypted using the Encr utility. The Encr.bat and Encr.sh files are located in the same directory as the startup script for Pentaho Server.

The emails-imported property defines whether emails have already been imported. If true, then no more emails are imported. After initial import, this property is automatically set to true. If more imports are done from a different data source, then this property needs to be set back to false.

Example based on a JDBC data source. The actual query depends on the source RDBMS. Prerequisites: The correct JDBC driver must be in the classpath for the JDBC configuration to work. In the example, the <datasource>.emails-query must return first name, last name, and email in that order. Field names in the output are dependent on the table columns that are imported. JDBC example: jdbc.emails-query=SELECT firstName, lastName, email FROM public.emails ORDER BY email ASC

Example based on a LDAP data source. Prerequisites: Attributes required for LDAP must be in the following order: <firstName>,<lastName>,<email>. LDAP example: ldap.required-attributes=<firstName>,<lastName>,<email>

For more information about JDBC, see [https://www.oracle.com/java/technologies/javase/javase-tech-database.html](https://www.oracle.com/java/technologies/javase/javase-tech-database.html)

For more information about LDAP, see https://ldap.com/

quartz.properties

This file is located in the pentaho-server/pentaho-solutions/system/scheduler-plugin/quartz directory and is the properties file for the open source job scheduling framework, Quartz. Refer to the official Quartz documentation at http://www.quartz-scheduler.org/documentation/.