Versions Compared

Old Version 36

changes.mady.by.user Unknown User (huyennth@fpt.com.vn)

Saved on

compared with

New Version 37

changes.mady.by.user Ondrej Špalek

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Sv translation
languageen

 

Parameters in application.properties

The file application.properties is located in the BellaDati WAR archive or in the installation directory of BellaDati standalone. To extract the file from the BellaDati WAR, you can use tools such as 7-Zip for Windows or Linux's/GNU unzip tools.

 

 

Parameter name

Description

application.url

Specifies the URL on which is BellaDati running. The default value is http://localhost.

application.production-mode

Determines whether BellaDati is running in production mode. The default value is true.

application.secure-mode

Determines whether BellaDati is running in SSL/TLS mode. If set to true, the application enforces all pages to be opened using SSL. Please note that you must configure your container use SSL/TLS in order to use this parameter.

jdbc.driverClassName

JDBC driver used by BellaDati for database connections. Currently, only org.postgresql.Driver is supported.

jdbc.url

If you don't have a JNDI data source configured, you can use the jdbc.url, jdbc.username and jdbc.password parameters. BellaDati automatically creates a JNDI data source with these parameters.
The URL should look like: jdbc:postgresql://db_host:5432/belladati_db where db_host is the host name of your database server.
Visit Setting up the PostgreSQL Database for more information.

jdbc.username

Username used by BellaDati to access the database. This parameter is used only when jdbc.url is set.

jdbc.password

Password used by BellaDati to access the database. This parameter is used only when jdbc.url is set.

jdbc.pool.maxActive

Maximum number of active database connections.

jdbc.pool.minIdle

Minimum number of database connections in idle state.

jdbc.pool.maxIdle

Maximum number of database connections in idle state.

jdbc.resource

Name of the JNDI resource to access the database, e.g. jdbc/belladati_db. Specify only if you are using a JNDI data source.

smtp.server.address

URL of the SMTP server used for sending email. Default value is localhost.

smtp.server.port

SMTP server port. Default value is 25.

smtp.server.ssl

Determines whether SSL is used for SMTP. Default value is false.

smtp.server.username

Username for accessing the SMTP server.

smtp.server.password

Password for accessing the SMTP server.

email.sender

This parameter allows you to change the email sender address. support@belladati.com is used by default.

email.footer

The value of this parameter is automatically appended to all outgoing emails. The default value is BellaDati Inc..

lucene.indexes

Specifies the directory for report and data set indexes. Default value is indexes.

facebook.applicationId

Consumer application ID for the Facebook connector.

facebook.applicationSecret

Consumer application secret for the Facebook connector.

twitter.consumerKey

Consumer key for the Twitter connector.

twitter.consumerSecret

Consumer secret for the Twitter connector.

salesForce.consumerKey

Consumer key for the SalesForce connector.

salesForce.consumerSecret

Consumer secret for the SalesForce connector.

core.membersLimit

(warning) Note that by increasing default value from 1000 to larger values. Users can use Attribute Looping Functions exp. eachMember() on larger datasets. Important: read best practices. You may need higher hardware configuration especially for multi-tenant BellaDati environment.

core.joins.limitRows limit of the maximum join size 
core.joins.previewLimitJoins preview limit - sometimes it is reasonable to use just the preview instead of materializing the join

If you change the lucene.indexes parameter on a system that's already in use, you will need to reindex your reports and data sets. After restarting the server and logging in, move the mouse over your username and click the link to your domain. On the left side, reindex your reports and data sets.

ActiveDirectory/LDAP Authentication

Tip

Since version 2.7.9.1 you can configure the ActiveDirectory authentication directly from the user interface. See Setup Active Directory Authentication.

 

BellaDati supports customizable authentication providers. Among the basic providers is the Active Directory and LDAP authentication provider. To enable this authentication provider, follow the instructions below:

BellaDati v2.7.4.1 and higher

1. Unzip the WEB-INF/classes/conf/application.properties configuration file from the BellaDati WAR file or edit the WEB-INF/classes/conf/application.properties in your BellaDati installation directory.

application.login.domains

List of authentication domains - names are displayed on the login page. E.g. application.login.domains=domain1,domain2.

adauth.createNotExistingAccounts

Determines whether accounts that don't exist are automatically created.

adauth.domainId

Specifies the id of the destination domain if adauth.createNotExistingAccounts=true.

adauth.domain1.spec.url

Specifies the search URL, e.g. LDAP://adhost:389/OU=Unit,OU=test,DC=company,DC=com

adauth.domain1.spec.bindDN

The DN of the user with search permission.

adauth.domain1.spec.bindPassword

The password of the user with search permission.

adauth.domain1.spec.loginAttribute

The login attribute, e.g. sAMAccountName.

2. If you have extracted the application.properties file from belladati.war archive, update this archive.

BellaDati v2.7.4 and below

 

1. Unzip the WEB-INF/classes/conf/beans-common.xml configuration file from the BellaDati WAR file.
2. Replace the bean element with id="userAuthenticityProvider" with this content:

Code Block
xml
xml
<bean id="userAuthenticityVerifier" class="cz.trgiman.belladati.auth.ADUserAuthenticityVerifier" autowire="byType">
	<property name="createNotExistingAccounts" value="true"/>
	<property name="workspaceId" value="1"/>
	<property name="domains">
		<map>
			<entry>
				<key><value>domain1</value></key>
				<bean class="cz.trgiman.belladati.auth.DomainSpecification">
					<property name="url" value="LDAP://host1:389/dc=xyz"/>
					<property name="bindDN" value="bindUser"/>
					<property name="bindPassword" value="bindUserPassword"/>
					<property name="loginAttribute" value="sAMAccountName"/>
					<property name="workspaceId" value="1"/>
				</bean>
			</entry>
			<entry>
				<key><value>domain2</value></key>
				<bean class="cz.trgiman.belladati.auth.DomainSpecification">
					<property name="url" value="LDAP://host2:389/dc=xyz"/>
					<property name="bindDN" value="bindUser2"/>
					<property name="bindPassword" value="bindUserPassword2"/>
					<property name="loginAttribute" value="cn"/>
					<property name="workspaceId" value="1"/>
				</bean>
			</entry>
		</map>
	</property>
</bean>

3. Add the following parameter to the WEB-INF/classes/conf/application.properties file:

Code Block
application.login.domains=domain1,domain2

4. Update the belladati.war archive.

...