Configuring Talend Data Stewardship after installation - Cloud

Talend Cloud Hybrid Installation Guide for Linux

Version
Cloud
Language
English (United States)
EnrichDitaval
linux
Product
Talend Cloud
Module
Talend Data Preparation
Talend Data Stewardship
Talend Management Console
Content
Installation and Upgrade

Procedure

  1. Open the <Tomcat>/conf/data-stewardship.properties file and edit the following Talend Data Stewardship properties for MongoDB:
    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 Stewardship is connected, tds by default
    spring.data.mongodb.username Username used to connect to the database
    spring.data.mongodb.password Password used to connect to the database
    spring.data.mongodb.uri URI of the MongoDB instance to connect to

    If you connect to the MongoDB instance via a URI, the following parameters must be commented out: spring.data.mongodb.host, spring.data.mongodb.port, spring.data.mongodb.database, spring.data.mongodb.username, spring.data.mongodb.password

    Note: This configuration parameter is available only if you have installed the TPS-4354 patch delivered by Talend. For more information, check with your administrator.
  2. Update the following fields with the Gateway configuration parameters:
    Field Description
    tds.front.deploymentMode Set the value of this property to HYBRID.
    frontend.url Replace ${tinstall.tds.tomcat.protocol} with Apache Tomcat protocol and ${tinstall.tds.tomcat.port.http} with Apache Tomcat HTTP port.
    backend.url Replace ${tinstall.tds.tomcat.protocol} with Apache Tomcat protocol and ${tinstall.tds.tomcat.port.http} with Apache Tomcat HTTP port.
    schemaservice.url Replace ${tinstall.tds.tomcat.protocol} with Apache Tomcat protocol and ${tinstall.tds.tomcat.port.http} with Apache Tomcat HTTP port.
    semanticservice.url Enter the URL to Talend Dictionary Service.

    If your license does not include Talend Dictionary Service, delete this line.

    historyservice.url Replace ${tinstall.tds.tomcat.protocol} with Apache Tomcat protocol and ${tinstall.tds.tomcat.port.http} with Apache Tomcat HTTP port.
    monitoringservice.url Replace ${tinstall.tds.tomcat.protocol} with Apache Tomcat protocol and ${tinstall.tds.tomcat.port.http} with Apache Tomcat HTTP port.
  3. Update the following field with the Apache Kafka configuration:
    Field Description
    kafka.broker Enter the host and the port corresponding to your Apache Kafka broker.
  4. Update the following fields with the configuration for Talend Identity and Access Management:
    Field Action
    oidc.url Enter the URL to your Talend Identity and Access Management, https://iam.<region>.cloud.talend.com/oidc. Replace <region> with your account location. You'll find a list of the URLs to use for each data center in Talend Cloud regions and URLs.
    oidc.userauth.url Enter the URL to your Talend Identity and Access ManagementUser Authentication, https://iam.<region>.cloud.talend.com/oidc. Replace <region> with your account location. You'll find a list of the URLs to use for each data center in Talend Cloud regions and URLs.
    scim.url Enter the URL to your Talend Identity and Access Management SCIM, https://api.<region>.cloud.talend.com/v1/scim. Replace <region> with your account location. You'll find a list of the URLs to use for each data center in Talend Cloud regions and URLs.
    oidc.gateway.id Enter the client ID retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.
    oidc.gateway.secret Enter the client secret retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.
    oidc.tds.id Enter the client ID retrieved from . See Configuring hybrid in Talend Cloud Management Console.
    oidc.tds.secret Enter the client secret retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.
    oidc.history.id Enter the client ID retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.
    oidc.history.secret Enter the client secret retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.
    oidc.schema.id Enter the client ID retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.
    oidc.schema.secret Enter the client secret retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.
    oidc.monitoring.id Enter the client ID retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.
    oidc.monitoring.secret Enter the client secret retrieved from Talend Cloud Management Console. See Configuring hybrid in Talend Cloud Management Console.

    All the passwords entered in the properties file are encrypted when you start your Talend Data Stewardship instance.

  5. To configure access to Talend Dictionary Service, edit the following fields:
    Field Description
    tsd.maven.connector.s3Repository.bucket-url Enter the URL of your MinIO or S3 repository bucket.
    tsd.maven.connector.s3Repository.base-path Enter the base path of your MinIO or S3 repository.
    tsd.maven.connector.s3Repository.username Enter the username of your MinIO or S3 repository.
    tsd.maven.connector.s3Repository.password Enter the password of your MinIO or S3 repository.
    tsd.maven.connector.s3Repository.s3.region Enter the region of your MinIO or S3 repository.
    tsd.maven.connector.s3Repository.s3.endpoint Enter the URL of your MinIO or S3 repository server.
    tsd.dictionary-provider-facade.producer-url Enter the URL to your Talend Dictionary Service instance.
  6. Add the following hybrid-specific properties:
    Field Action
    security.oauth2.resource.jwt.key-uri=${security.oidc.client.keyUri} Enables the communication with Talend Cloud.
    spring.profiles.active=hybrid Enables hybrid mode.
    iam.server.url=https://api.<region>.cloud.talend.com/v1/iam Talend Identity and Access Management server URL for Talend Cloud. Replace <region> with your account location. You'll find a list of the URLs to use for each data center in Talend Cloud regions and URLs.
    tds.front.portalUrl=https://portal.<region>.cloud.talend.com/ Talend Cloud portal URL. Replace <region> with your account location. You'll find a list of the URLs to use for each data center in Talend Cloud regions and URLs.
    tds.front.pendoDataCenter=<data_center> Data Center name for your Talend Cloud installation. Replace <data_center> with us-east-1, eu-central-1, ap-south-1 or ap-southeast-2 for AWS, or west-us for Azure.
    tds.front.pendoCloudProvider=<cloud_provider> Cloud provider of your Talend Cloud installation. Replace <cloud_provider> with AWS or Azure.
  7. Disable the log auditing option:
    Field Action
    audit.log.enabled Set this property to false for hybrid configuration. Setting this property to true while using Talend Data Stewardship in hybrid mode can prevent it from starting properly.
  8. To enable the app switcher after installing Talend Data Stewardship and Talend Data Preparation, uncomment the following line and add the URL to your Talend Data Preparation instance:
    tds.front.tdpUrl=<Talend_Data_Preparation_URL>

    You must also add the URL to your Talend Data Stewardship instance to the configuration file for Talend Data Preparation. For more information, see the section about configuring Talend Data Preparation after installation.

  9. Optional: Enable HTTP compression for Talend Data Stewardship in Apache Tomcat:
    1. Open the <Tomcat>\conf\server.xml file.
    2. Add the following attributes to the HTTP Connector configuration used for Talend Data Stewardship:
      compression="on"
      compressionMinSize="2048"
      compressibleMimeType="text/html,text/xml,text/javascript,text/css,application/javascript,application/json"
  10. Start Talend Data Stewardship by launching, in order:
    1. Apache Kafka
    2. MongoDB
    3. Apache Tomcat
    4. MinIO