Reports Scheduler - Property File - KB 300 - OpenLM Software License Management
Israel +972 4 6308447         USA +1 619 831 0029              JAPAN +81 505 893 6263 担当:萩原

Reports Scheduler – Property File – KB 300

You are here:
< All Topics

 

This document provides the Report Scheduler – Properties File information.

 

Table of Contents:

Report Scheduler – Properties

 

Report Scheduler – Properties

The section provides the information about the Report Scheduler – Properties File Settings:

 

report_scheduler.properties File Settings

Database – DB URL points to a ‘report_scheduler’ database in ‘db’ relative folder:

For memory DB you can use jdbc:hsqldb:mem:testdb

db.url=jdbc:hsqldb:file:data/report_scheduler
db.schema=REPORT_SCHEDULER
db.username=SA
db.password=2
db.pool.size=2

Note: In case, you would like to use your preferred DB, for e.g. MySQL or SQL Server, the JDBC driver and the classpath configuration to use the JDBC driver is required.

 

The Report Scheduler will read the SMTP settings from the OpenLM Server. In case, the Report Scheduler is unable to access the OpenLM Server, then the below-mentioned SMTP settings can be used:

Mail – Useful for detailed error messages from mail server:

mail.debug=false
mail.smtp.host=localhost
mail.smtp.port=25
mail.smtp.auth=false
mail.smtp.ssl=false
mail.smtp.username=
mail.smtp.password=
mail.smtp.sender=openlm@openlm.com
mail.sending.tries=5
mail.sending.try.timeout=3000

 

Semicolon separated list of emails to send error notifications: ex: recipient1@openlm.com;recipient2@openlm.com

mail.recipients=

 

OpenLM:

openlm.connect.retries=5
openlm.protocol=http
openlm.host=localhost
openlm.soap.port=5015
openlm.ea.port=5015
openlm.ea.protocol=http
openlm.client.id=openlm.reportscheduler.client
openlm.client.secret=reportscheduler_secret
openlm.client.scope=openlm.server.scope

 

Scheduler – Start delay for a job that fires once – in seconds:

scheduler.default.delay=30

 

Directory to copy generated files to:

Windows backslash paths have to be escaped or converted to slash.

e.g. C:\\OpenLM\\Scheduler Or C:/OpenLM/Scheduler

You can use the path relative to the current drive root.

e.g. /OpenLM/Scheduler

scheduler.report.files.directory=

 

HTTP Server:

server.address=0.0.0.0
server.port=8888
server.context.path=report_scheduler
browser.path=chromium/chrome.exe

 

Webdriver:

webdriver.debug.mode=false

 

Path to Chrome webdriver executable (system-dependent so it is usually given as CMD param):

webdriver.impl.path=chromedriver.exe

Note: Report Scheduler is not supported for the Linux operating system.

 

Port on which webdriver should start:

webdriver.port=3400
webdriver.free.port.tries=2
webdriver.log.level=INFO

 

Seconds – how long webdriver stands by to wait while async sources load:

webdriver.page.default.timeout=120
webdriver.page.switch.timeout=5

 

Pixels:

webdriver.page.size.width=1366
webdriver.page.size.height=768

 

Note: Please know .Jar file holds the original Property (internal) file that holds all default configuration values for all parameters. This file gets updated with the Report Scheduler new version upgrade.

You can edit the external Property file (report_scheduler.properties). This file will not be updated with the Report Scheduler new version upgrade. If report_scheduler.properties is missing any configuration value, then the missing value is taken from default configuration values set in the Property (internal) file.

 

Previous Install and Configure – Reports Scheduler – HT828
Next Updating ChromeDriver for Reports Scheduler – HT908
Table of Contents