Configuring the stewardship console database - 6.2

Talend Big Data Platform Installation Guide for Linux

EnrichVersion
6.2
EnrichProdName
Talend Big Data Platform
task
Installation and Upgrade
EnrichPlatform
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend DQ Portal
Talend Installer
Talend JobServer
Talend Log Server
Talend Project Audit
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio

Replacing the default database when you installed the stewardship console using a .jar file

When you install Talend Data Stewardship Console as a standalone application using the .jar file provided by Talend, H2 is the default embedded database. However, you have the possibility to make the console work with other databases (MySQL, Oracle, SQL Server, MSSQL, PostgreSQL, DB2, HSQL).

  1. Open the context.xml file which can be found in the <TomcatPath>\webapps\org.talend.datastewardship\META-INF folder, where <TomcatPath> is the Tomcat installation directory.

  2. Open the context-template.xml file in parallel to find examples of some edits to make to adapt the stewardship console to other databases, and copy the template corresponding to your database.

  3. Paste this template into context.xml and change the properties (database URL, username and password) to suit your database.

Configuring the database if you installed the stewardship console manually using a .war file

If you installed Talend Data Stewardship Console as a standalone application using the .war file provided by Talend, it may not be adapted to your environment.

To configure the stewardship console database, do the following.

  1. Browse to the directory <DSC_WAR_FOLDER>\META-INF, and then create a new file context.xml under the directory.

  2. Open the file context-template.xml in parallel to find and copy the template corresponding to the database you are using for Talend Data Stewardship Console.

  3. Paste the template into context.xml and change the properties (database URL, username and password) to suit your database.

    The specified password in the file will be encrypted upon the application server startup. For more information, see Managing the password in the context.xml file.