Editing the servertemplate file
- Big Data Platform
- Data Fabric
- Data Management Platform
- Data Services Platform
- MDM Platform
- Real-Time Big Data Platform
Procedure
- Open the dqportal/resources/hsql/servertemplate file to edit it.
- Replace [%TOMCAT_IP%] and [%TOMCAT_PORT%] with the IP address of the Apache Tomcat server and the appropriate SApache Tomcat server port (as set by the user) respectively.
-
Replace [%TDQ_DB_DRIVER_CLASS_NAME%] with
-
com.mysql.jdbc.Driver if you use MySQL,
-
oracle.jdbc.OracleDriver if you use Oracle,
-
net.sourceforge.jtds.jdbc.Driver if you use MS SQL Server,
-
org.postgresql.Driver if you use PostgreSQL.
-
-
Replace [%TDQ_DB_URL%] with the
connection URL to the data mart database.
Database Type
Connection URL
MySQL
jdbc:mysql://$ip:$dmport/$datamart?characterEncoding=UTF8&useOldAliasMetadataBehavior=true
Oracle
jdbc:oracle:thin:@$ip:$dmport:$datamart
MS SQL Server
url="jdbc:jtds:sqlserver://$ip:$dmport/$datamart" validationQuery="select 1"
PostgreSQL
jdbc:postgresql://$ip:$dmport/$datamart
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. - Replace [%TDQ_DB_USERNAME%] and [%TDQ_DB_PASSWORD%] with the username and password of the data mart database respectively.
- Delete [%VALIDATION_QUERY%].
-
In <Environment name="spagobi_resource_path" type="java.lang.String"
value="../resources"/>, replace ../resources by
the absolute file path.
For example: value="C:/Program Files/Tomcat 9.0/resources"
- 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.
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!