Configuring Talend Data Preparation after installation
Procedure
-
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 Comment out this property for hybrid configuration. security.oauth2.client.clientId Enter the client ID retrieved from Talend Management Console. See Configuring hybrid in Talend Management Console. security.oauth2.client.clientSecret Enter the client secret retrieved from Talend Management Console. See Configuring hybrid in Talend Management Console. iam.scim.url Make sure that Talend Identity and Access Management port is correct. iam.uri Comment out this property for hybrid configuration. iam.api.uri Comment out this property for hybrid configuration. iam.license.url Comment out this property for hybrid configuration. security.oidc.client.keyUri Comment out this property for hybrid configuration. app.products[0].id=TDS app.products[0].name=Data Stewardship
app.products[0].url=<place_your_tds_url_here>
Enter the URL to your Talend Data Stewardship instance. audit.log.enabled Set this property to false for hybrid configuration. Setting this property to true while using Talend Data Preparation in hybrid mode can prevent it from starting properly. security.oauth2.client.scope Set the value for this property to openid refreshToken entitlements. All the passwords entered in the properties file are encrypted when you start your Talend Data Preparation instance.
-
If you connect Talend Data Preparation
hybrid to your AWS account through a Route 53, add the following property to the
application.properties file:
security.xframe.options=DENY
-
Uncomment the following hybrid-specific properties located at
the end of the properties file by removing the # character at the beginning of
the corresponding lines. If needed, update the default URLs according to your
Talend Cloud account region.
You'll find a list of the URLs to use for each data center in Accessing Talend Cloud applications.
Field Description dataprep.hybrid.enabled When set to true, activates the hybrid mode. client.session-management.enabled Activates the hybrid mode. iam.uri Updates the Talend Identity and Access Management URLs for Talend Cloud. iam.api.uri Updates the Talend Identity and Access Management URLs for Talend Cloud. iamproxy.service.url Allows to switch seamlessly between Talend Cloud and the hybrid application. server.portal.url Sets the URL for the Talend icon in the application header to the Talend Cloud portal. external.user.preferences.url Updates the user preferences link to Talend Cloud. security.oauth2.resource.jwt.key-uri Enables JWT usage for hybrid. security.oidc.client.sessionManagementUri Sets the session check endpoint. -
Update the following fields with your MongoDB settings:
Field Description spring.data.mongodb.host Host name of your MongoDB instance spring.data.mongodb.port Port number of your MongoDB instance spring.data.mongodb.database Name of the database on which Talend Data Preparation is connected, dataprep by default. The database is created when you first launch Talend Data Preparation. spring.data.mongodb.username Username used to connect to the database spring.data.mongodb.password Password used to connect to the database -
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://<tcomp_host>:<tcomp_port>/tcomp
-
To enable the application 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.
- 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.
-
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 to display the semantic type management interface in Talend Data Preparation. dataquality.server.url Enter the URL to your Talend Cloud Data Preparation instance, for example: https://tdp.<region>.cloud.talend.com/dq/semanticservice. Replace <region> with your account location. You'll find a list of the URLs to use for each data center in Accessing Talend Cloud applications. If your license does not include Talend Dictionary Service, delete this line.
tsd.maven.connector.s3Repository.bucket-url Enter the URL of your MinIO or S3 repository bucket. For example: s3://talend-app-shared.
tsd.maven.connector.s3Repository.base-path Enter the base path of your MinIO or S3 repository. For example: semantic-types-repository.
tsd.maven.connector.s3Repository.username Enter the username of your MinIO or S3 repository. For example: username123.
tsd.maven.connector.s3Repository.password Enter the password of your MinIO or S3 repository. For example: password123.
tsd.maven.connector.s3Repository.s3.region Enter the region of your MinIO or S3 repository. For example: us-east-1.
tsd.maven.connector.s3Repository.s3.endpoint Enter the URL of your MinIO or S3 repository server. For example: 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. - Execute the start.bat file to start your Talend Data Preparation instance.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!