Skip to main content

Import the DEE library

The DEE dependency must be included in the project’s POM.
<!-- CSV data extraction support -->
<dependency>
    <groupId>com.activeviam.io</groupId>
    <artifactId>data-extraction-engine</artifactId>
    <version>${atoti.server.version}</version>
</dependency>

Set the required properties

The external properties are retrieved using the Spring @Value mechanism. For it to work, the following code must be included in the main Spring Config class.
@Bean
public static PropertySourcesPlaceholderConfigurer propertySourcesPlaceholderConfigurer() {
	final PropertySourcesPlaceholderConfigurer propertySourcesPlaceholderConfigurer = new PropertySourcesPlaceholderConfigurer();
	propertySourcesPlaceholderConfigurer.setIgnoreUnresolvablePlaceholders(true);
	return propertySourcesPlaceholderConfigurer;
}
Here is a list of the required properties.

Importing configurations

The DEE library provides the necessary Spring Config files to enable the DEE, so no additional configuration is required.

All-in-one configuration

All config files can be added by adding the target-specific configuration to the application’s Spring Config. These config files contain all config files needed for DEE.
OutputConfiguration Class
Local CSV FileCsvDataExtractionEngineConfig.class
In MemoryInMemoryDataExtractionEngineConfig.class
Example of what an application config should look like:
@Configuration
@Import({
		// Import the Output-Specific Data Extraction Engine
		CsvDataExtractionEngineConfig.class
})
public class ApplicationConfig {
    //...
}

Individual configuration files

Optionally, users can import specific configs. The following are the configs for the CSV target:
CSV Specific ImplementationDescription
CsvDataExtractionServicesConfigRegisters the services for the Data Extraction Engine (ILocalDataExtractionService) and Enhanced Drillthrough ILocalEnhancedDrillthroughService
CsvDataExtractionRestServicesConfigExposes the services so they can be accessed using REST (work in progress).