zoomdata.properties Properties

access.control.allow.origin=<user-defined>

For more information, see Enable Visual Data Discovery Component Access From Other Sites Using Cross-Origin Resource Sharing (CORS).

Path to Symphony logs. The placeholder <ZD_install_directory> is replaced with the actual location where Symphony is installed.

Verify that this log directory has all the necessary permissions and that the owner of the directory is set to zoomdata.

The /home directory cannot be used for logging.

Example: logs.dir=/opt/<composer>/logs)

Example: saml.maxAuthAge=86400

Enables gzip compression for http requests.

Example: server.compression.enabled=true

Example: server.servlet.context-path=/composer

Example: server.session-timeout=1800

If you alter this value, also alter the value of the zoomdata.server.ws.idle.timeout property to match it.

Example: source.attribute.values.limit=1000

Example: spring.servlet.multipart.max-file-size=500Mb

Example: spring.servlet.multipart.max-request-size=500Mb

Example: keystore.location=classpath:security/zoomkeystore.jks

See Create a Symmetric Key to Encrypt Data Source Passwords for further guidance.

Example: keystore.password=zoomkey

Example: keystore.key.alias=zoomkey

Example:keystore.key.password=zoomkey

Example: server.ssl.key-store=HOME/conf/keystore

Example: server.ssl.key-store-password=<YourPassword>

Example: saml.artifactBindingDefault=true

Example: saml.useMultiValueList=true

Example: saml.stringDelimiter=;

Example: spring.datasource.url=jdbc:postgresql://localhost:5432/zoomdata

Example: spring.datasource.username=zoomdata

Example: keyset.destination.params.jdbc_url=jdbc:postgresql://10.2.1.4:5432/zoomdata-keyset

Example: keyset.destination.params.user_name=zoomdata

Example: upload.destination.params.jdbc_url=jdbc:postgresql://10.2.1.4:5432/zoomdata-upload

Example: upload.destination.params.user_name=zoomdata

Example: source.sampling.rows=1000

Example: source.attribute.values.limit=1000

Sets the host IP address for Fluentd server message logging. For more information, see Set Up Unified Logging Using Fluentd.

Example: logging.unified.host=123.4.5.6

Sets the log level for messages logged to the Fluentd server. The following options are available for this property: TRACE, DEBUG, INFO, WARN, ERROR, and OFF. If set to OFF, Fluentd unified logging is disabled. For more information, see Set Up Unified Logging Using Fluentd.

Example: logging.unified.level=INFO

Sets the port for Fluentd server message logging. For more information, see Set Up Unified Logging Using Fluentd.

Example: logging.unified.port=1234

Sets the microservice tag name for messages logged to the Fluentd server. This is important because the tag identifies the microservice to which the log messages apply. Valid values are query-engine, zoomdata-server, stream-writer, upload-service, and edc-<connector-name> (where <connector-name> is one of the names listed in Connector Properties and Property Files). For more information, see Set Up Unified Logging Using Fluentd.

Example: logging.unified.tag = zoomdata-server

Example: syslog.host=127.0.0.1

Example: syslog.log.level=DEBUG

Example: syslog.port=1514

Example: syslog.suffix=local

Use this property to define the maximum number of columns that can be exported for two-dimensional visuals (such as a pivot table). Symphony enforces this limit for visual data, but does not enforce it for raw data.

The distributed default for this setting is 1000 columns. Valid values can range from 0 through 2147483647 columns.

Use this property to define the maximum number of rows that can be exported for visuals. Symphony enforces this limit for visual data. However, for raw data, Symphony produces an error if the number of rows requested for export exceeds this setting.

The distributed default for this setting is 100000 rows. Valid values can range from 0 through 2147483647 rows.

Specifies the number of milliseconds that can elapse before Symphony stops trying to read from the screenshot microservice client.

Note: If you increase the time set by the dashboard.scheduling.screenshot.timeout property, make sure that you increase the value of this property as well. The total time set by screenshot.service.http.client.read.timeout.milliseconds should always be greater than or equal to the time set by the dashboard.scheduling.screenshot.timeout property. Bear in mind that this property is specified in milliseconds, but the dashboard.scheduling.screenshot.timeout property is specified in seconds.

Specifies the timeout (in seconds) to take a screenshot for a dashboard email report.

Note: The time specified by this property must be less than or equal to the time set by the screenshot.service.http.client.read.timeout.milliseconds property. If you increase the value of this property, make sure that you increase the value of the screenshot.service.http.client.read.timeout.milliseconds property accordingly. Bear in mind that this property is specified in seconds, but the screenshot.service.http.client.read.timeout.milliseconds property is specified in milliseconds.

In addition, JavaMail API properties (Symphony supports both IMAP and SMTP protocols) should be added to the zoomdata.properties file to identify the mail server and other mail properties required to use that server to send the scheduled dashboard (for example, mail.smtp.auth, mail.smtp.host, mail.smtp.port, mail.imap.host, and mail.imap.port). Complete descriptions of IMAP and SMTP protocol JavaMail properties can be found at these links:

• IMAP: https://javaee.github.io/javamail/docs/api/com/sun/mail/imap/package-summary.html
• SMTP: https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html