# Configuring Talend Data Preparation

## Configuring Talend Data Preparation after installation

### Procedure

1. Open the <Data\_Preparation\_Path>/config/application.properties file and edit the following Talend Data Preparation properties:
   | Field | Action |
   | --- | --- |
   | public.ip | Enter the hostname you want to use to access Talend Data Preparation. |
   | server.port | Enter the port you want to use for Talend Data Preparation user interface. |
   | iam.ip | Enter the URL to your Talend Identity and Access Management instance. |
   | spring.security.oauth2.client.registration.oidc.clientId | Enter the Talend Identity and Access Management OIDC client identifier. |
   | spring.security.oauth2.resourceserver.iam.opaque-token.clientId | Enter the Talend Identity and Access Management OIDC client identifier. |
   | spring.security.oauth2.client.registration.oidc.clientSecret | Enter the Talend Identity and Access Management OIDC client password. |
   | spring.security.oauth2.resourceserver.iam.opaque-token.clientSecret | Enter the Talend Identity and Access Management OIDC client password. |
   | iam.uri | Make sure that Talend Identity and Access Management port is correct. |
   | iam.api.uri | Make sure that Talend Identity and Access Management port is correct. |
   | app.products[0].id=TDS<br><br><br>app.products[0].name=Data Stewardship<br><br><br>app.products[0].url=&lt;place\_your\_tds\_url\_here&gt; | Enter the URL to your Talend Data Stewardship instance. |

   All the passwords entered in the properties file are encrypted when you start your Talend Data Preparation instance.
2. Update the following fields with your MongoDB settings:
   | Field | Description |
   | --- | --- |
   | spring.mongodb.host | Host name of your MongoDB instance |
   | spring.mongodb.port | Port number of your MongoDB instance |
   | spring.mongodb.database | Name of the database on which Talend Data Preparation is connected, dataprep by default. The database is<br>created when you first launch Talend Data Preparation. |
   | spring.mongodb.username | Username used to connect to the database |
   | spring.mongodb.password | Password used to connect to the database |
3. To enable the interaction between Talend Data Preparation and the Components Catalog service, edit the following line with your Components Catalog server host and port:

   tcomp.server.url=http://&lt;tcomp\_host&gt;:&lt;tcomp\_port&gt;/tcomp
4. To enable the app switcher after installing Talend Data Preparation and Talend Data Stewardship, uncomment the following lines and add the URL to your Talend Data Stewardship instance:
   ```
   app.products[0].id=TDS
   app.products[0].name=Data Stewardship
   app.products[0].url=<place_your_tds_url_here>
   ```

   You must also add the URL to your Talend Data Preparation instance to the configuration file for Talend Data Stewardship. For more information, see the section about configuring Talend Data Stewardship after installation.
5. By default, audit logs are enabled. You must specify the correct appender.http.url parameter in the audit.properties file, or disable audit logs. For more information, see [Enabling and configuring audit capabilities in Talend Data Preparation](https://help.qlik.com/talend/en-US/data-preparation-user-guide/8.0/enabling-and-configuring-audit-capabilities-in-talend-data-preparation).
6. * Available in:
   * Big Data Platform
   * Data Fabric
   * Data Management Platform
   * Data Services Platform
   * Qlik Cloud Enterprise Edition
   * Qlik Talend Cloud Enterprise Edition
   * Qlik Talend Cloud Premium Edition
   * Real-Time Big Data Platform

   To configure the access to Talend Dictionary Service, edit the following fields:
   | Field | Description |
   | --- | --- |
   | dataquality.semantic.list.enable | Set the value of this parameter to true in order<br>to display the semantic type management interface in Talend Data Preparation. |
   | dataquality.server.url | Enter the URL to your Talend Dictionary Service instance, http://&lt;local machine ip&gt;:8187/ for<br>example. |
   | tsd.enabled | Set the value of this parameter to true in order<br>to enable the interaction between Talend Data Preparation and Talend Dictionary Service |
   | tsd.maven.connector.s3Repository.bucket-url | Enter the URL of your MinIO or S3 repository bucket.<br><br>For example:<br>s3://talend-app-shared. |
   | tsd.maven.connector.s3Repository.base-path | Enter the base path of your MinIO or S3 repository. This property<br>is optional and can be left empty.<br><br>For example:<br>semantic-types-repository. |
   | tsd.maven.connector.s3Repository.username | Enter the username of your MinIO or S3 repository.<br><br>For example:<br>username123. |
   | tsd.maven.connector.s3Repository.password | Enter the password of your MinIO or S3 repository.<br><br>For example:<br>password123. |
   | tsd.maven.connector.s3Repository.s3.region | Enter the region of your MinIO or S3 repository.<br><br>For example:<br>us-east-1. |
   | tsd.maven.connector.s3Repository.s3.endpoint | Enter the URL of your MinIO or S3 repository server.<br><br>For example:<br>https://minio-company.com. |
   | tsd.dictionary-provider-facade.producer-url | Enter the URL to your Talend Dictionary Service instance. |
   | spring.cloud.stream.kafka.binder.brokers | Enter the host corresponding to your Kafka broker. |
7. To enable the semantic types, edit the following lines: dataquality.semantic.list.enable=true and dataquality.server.url=http://&lt;local machine ip&gt;:8187/.
8. Before starting Talend Data Preparation, launch, in this order:
   1. Apache Kafka
   2. MongoDB
   3. MinIO
9. Execute the start.sh file to start your Talend Data Preparation instance.

## Configuring logs for Talend Data Preparation

### About this task

Talend Data Preparation logs allows you to analyze and debug the activity of Talend Data Preparation.

Talend Data Preparation logs are located in &lt;Data\_Preparation\_Path&gt;/data/logs/app.log.

To configure the settings of your log files, edit the &lt;Data\_Preparation\_Path&gt;/config/log4j2.xml file:

### Procedure

* 

  For more information on how to set the Log4j information level, see [the Apache Log4j documentation about information levels](http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html).
* 

  For more information on how to set the log rotation, see [the Apache Log4j documentation about log rotation](https://logging.apache.org/log4j/2.x/manual/configuration.html#AutomaticReconfiguration).