Page History

BellaDati can be customised via set of application properties which can be set in one of the following ways (in order of precedence, some properties support only sub-set of these options):

• Using the administration page in BellaDati, see Managing Configuration (contains also names of the properties to set in application.properties or as an JVM option if any of those is preferred for setting the property). 
• Adding JVM options to the application server which was used for installing BellaDati, see Installing BellaDati manually for available options.
• Changing of application.properties file which 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.

Below is a list of application properties which can be set only via application.properties file and / or JVM options.

General

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.

Limits / Timeouts

JDBC Settings

These settings allow to set JDBC connection to database used internally by BellaDati. It's an alternative to setting up a JDBC resource in the application server which requires manual addition of proper JDBC driver to the server's classpath. 

Cluster Mode

Background Services

ActiveDirectory/LDAP 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.

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:

<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:

application.login.domains=domain1,domain2

4. Update the belladati.war archive.