Changing Talend Identity and Access Management database - 8.0

Talend Installation Guide

Version
8.0
Language
English
Operating system
Windows
Subscription type
Subscription
Product
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend Data Preparation
Talend Data Stewardship
Talend ESB
Talend Identity and Access Management
Talend Installer
Talend JobServer
Talend LogServer
Talend MDM Server
Talend MDM Web UI
Talend Runtime
Talend SAP RFC Server
Talend Studio
Content
Installation and Upgrade
Last publication date
2022-10-30

As the embedded H2 database is not recommended for production environments, it is advised to change the Talend Identity and Access Management database.

Talend Identity and Access Management uses two different databases:
  • One for the OpenId Connect service: oidc
  • One for the Fediz Identity Provider: idp

Procedure

  1. Stop Talend Identity and Access Management if it has been already started.
  2. Place the JDBC driver jar file corresponding to the database you want to use in the iam-A.B.C\apache-tomcat-x.x.xx\lib folder and make sure that it has the same permissions as the other jar files.
    For more information on the supported databases, see Compatible databases.
  3. Update the provisioning.properties and domains\Master.properties files as described in Apache Syncope documentation.
  4. Edit the iam-A.B.C\apache-tomcat-x.x.xx\conf\iam.properties file and update the following parameters:
    Parameter Description
    idp.db.url IDP database JDBC URL.
    idp.db.driverClassName Fully qualified driver class name, com.mysql.jdbc.Driver for example.
    idp.db.username User name used to connect to the IDP database.
    idp.db.password Password used to connect to the IDP database.

    The password is encrypted at first launch.

    idp.db.platform OpenJPA 2.4.2 platform name without the package name.
    Example:
    idp.db.platform=MySQLDictionary

    For more information, see https://openjpa.apache.org/builds/3.0.0/apache-openjpa/docs/ref_guide_dbsetup_dbsupport.html.

    oidc.db.url OIDC database JDBC URL.
    oidc.db.driverClassName Fully qualified driver class name, com.mysql.jdbc.Driver for example.
    oidc.db.username User name used to connect to the OIDC database.
    oidc.db.password Password used to connect to the OIDC database.

    The password is encrypted at first launch.

    oidc.db.databasePlatform Hibernate 5 platform name.
    Example:
    oidc.db.databasePlatform=org.apache.openjpa.jdbc.sql.MySQLDictionary

    For more information, see https://openjpa.apache.org/builds/3.0.0/apache-openjpa/docs/ref_guide_dbsetup_dbsupport.html.

    oidc.db.dialect Hibernate 5 dialect for the database.
    Example:
    oidc.db.dialect=org.hibernate.dialect.MySQL57Dialect

    For more information, see https://docs.jboss.org/hibernate/orm/6.0/javadocs/org/hibernate/dialect/package-summary.html.

  5. Delete the iam\apache-tomcat\webapps\oidc and iam\apache-tomcat\webapps\idp folders.
  6. Start Talend Identity and Access Management by executing the startup.bat file.