Installing your Talend Data Quality Portal - 6.4

Talend MDM Platform Installation Guide for Windows

Talend MDM Platform
Installation and Upgrade
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend Data Preparation
Talend Data Stewardship
Talend DQ Portal
Talend ESB
Talend Identity Management
Talend Installer
Talend JobServer
Talend Log Server
Talend MDM Server
Talend MDM Web UI
Talend Project Audit
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio


  • If you use MySQL, the my.ini file of your MySQL server installation directory must be edited in order to increase the size of query packets processed by the server. For more details, please see Table 26, "Talend Data Quality Portal".

  • The talend_dq database exists and is correctly initialized: it contains tables such as the TDQ_PRODUCT table. The database can have another name set by the user in the Studio. Use the same name in the Portal configuration (in the server.xml file). See Editing the servertemplate file for more information.

  • The file has been downloaded and unzipped.

  • The drivers (.jar files) corresponding to your Talend Data Quality Portal configuration database are downloaded.

Customizing and restoring the Talend Data Quality Portal configuration database

  1. Open the file dqportal/script/hsql/database/tdqportal.script to edit it.

  2. Find all http://localhost:8080 and replace localhost and 8080 with the server IP address and port number if needed.


    If you don't replace localhost with the server IP address, the Talend Data Quality Portal will not be accessible from another site.

  3. Replace tdq_utf8','','','','',60 with

    • tdq_utf8','','','','',65 if the database type is MySQL, or

    • tdq_utf8','','','','',61 if the database type is Oracle, or

    • tdq_utf8','','','','',63 if the database type is MS SQL Server, or

    • tdq_utf8','','','','',66 if the database type is PostgreSQL.

  4. Copy the dqportal/script/hsql/database folder at the root of the Tomcat installation directory.

Copying the libraries, the resources and the .war file

  1. Copy the content of dqportal/resources/common/lib into <TomcatPath>/lib.

  2. Copy the dqportal/resources/common/resources folder at the root of the Tomcat installation directory.

    Edit the host and port information (localhost:8080 by default) in the following files according to your installation:




  3. Copy the dqportal/resources/hsql/webapps/tdqportal.war file into <TomcatPath>/webapps.

  4. Copy all files from resources/common/webapps to <TomcatPath>/webapps.

  5. Start the Tomcat server to enable the deployment of tdqportal.war, SpagoBIQbeEngine.war and some other war files copied to <TomcatPath>/webapps. This will create the <TomcatPath>/webapps/tdqportal/WEB-INF/lib folder, the <TomcatPath>/webapps/SpagoBIQbeEngine/WEB-INF/lib folder, and many other folders.

  6. Copy the jdbc .jar file for the data mart database into <TomcatPath>/lib or into <TomcatPath>/webapps/tdqportal/WEB-INF/lib and webapps/SpagoBIQbeEngine/WEB-INF/lib (recommended).

    Note that the jar version must match the data mart database version.

  7. Restart Tomcat to have changes in the .lib file take effect.

Editing the servertemplate file

  1. Open the file dqportal/resources/hsql/servertemplate to edit it.

  2. Replace [%TOMCAT_IP%] and [%TOMCAT_PORT%] with the IP address of the Tomcat server and the appropriate Tomcat server port (as set by the user) respectively.

  3. Replace [%TDQ_DB_DRIVER_CLASS_NAME%] with

    • com.mysql.jdbc.Driver if you use MySQL, or

    • oracle.jdbc.OracleDriver if you use Oracle, or

    • net.sourceforge.jtds.jdbc.Driver if you use MS SQL Server, or

    • org.postgresql.Driver if you use PostgreSQL.

  4. Replace [%TDQ_DB_URL%] with the connection URL to the data mart database.

    Database Type

    Connection URL





    MS SQL Server

    url="jdbc:jtds:sqlserver://$ip:$dmport/$datamart" validationQuery="select 1"



    Note that $ip, $dmport and $datamart in the connection URL need to be replaced with the IP address, port number, and name of the data mart database respectively. By default, the database created by the Studio is named talend_dq. Make sure you use the same database name in the connection URL and in the Studio. For further information about setting up a distant database from the studio, see Talend Studio User Guide.

  5. Replace [%TDQ_DB_USERNAME%] and [%TDQ_DB_PASSWORD%] with the username and password of the data mart database respectively.

  6. Delete [%VALIDATION_QUERY%].

  7. Copy the content of the servertemplate file inside the <GlobalNamingResources> part of the <TomcatPath>/conf/server.xml file, then save your edits before closing the file.

Changing the default port used by the embedded HSQL database (optional)

  1. Open the <TomcatPath>/database/startup.bat file to edit it.

  2. Add the following at the end of the line:

    -port <portNumber>

    where <portNumber> is to be replaced with the port number that will be actually used by the database.

  3. Open the <TomcatPath>/conf/server.xml file and update the port number accordingly.

Starting Tomcat

  1. Before starting Tomcat, start the HSQL database:

    Go to the <TomcatPath>/database directory and execute the startup script (startup.bat).

  2. Go to the <TomcatPath>/bin directory and launch the startup.bat, then log in to the Talend Data Quality Portal.

    For more information about how to log into the portal, please see the Talend Data Quality Portal User and Administrator Guide.