Installing MDM modules using the war file

With a WAR file (Talend-MDMServer-YYYYMMDD-<revision number>-VA.B.C.war) and a zipped HOME file (Talend-MDMServer-YYYYMMDD-<revision number>-VA.B.C-HOME.zip) provided by Qlik, you can also install MDM modules by deploying the .war file to Tomcat and then updating some configuration files after unzipping the HOME file.

Here, A.B.C stands for Major, Minor, Patch version respectively. Note that you must use the same versions/revisions of each module.

This installation mode assumes that you are familiar with or have some knowledge of MDM server configuration.

The following lists all the modules involved in this installation mode. To ease their management, you are recommended to centralize all the modules on one single system.

An application server, Apache Tomcat server in this case, which hosts the MDM web application.
A .war file, which contains the MDM server application required to use Talend MDM Web UI.
A zipped HOME file, which contains files and resources for the MDM server.

Procedure

Install the Apache Tomcat application server and stop the Tomcat service if it is already started.
Unzip the HOME file to a local folder. In the following procedure, this local folder will be referred to as MDM_ROOT.
Copy the .war file into the directory <TomcatPath>/webapps/, and then rename it to be talendmdm.war.
Once you have copied this war file, you can either unzip it manually under the same directory, or let Tomcat unzip the web application at startup.
Browse to the directory <TomcatPath>/conf.
If the folder Catalina does not exist, create a new folder Catalina under the directory <TomcatPath>/conf and then create a new folder localhost under <TomcatPath>/conf/Catalina.
Under the directory <TomcatPath>/conf/Catalina/localhost, create a new XML file (for example, talendmdm.xml), and populate it with the following content:
```
<?xml version='1.0' encoding='utf-8'?>
<Context path="talendmdm">
<Parameter name="mdmRootLocation"
value="<MDM_ROOT>"
override="false"/>
</Context>
```
Information noteWarning: The value of the Context path must be identical to the name of your war file which has been placed under <TomcatPath>/webapps, and the value for mdmRootLocation must be the local directory where the HOME file is unzipped.
Under the directory <MDM_ROOT>/conf, edit the datasources.xml file to provide the connection information to the database.
You can use datasources.xml to manage how MDM Server uses SQL databases. For more information, see Managing how MDM Server uses SQL databases.
Edit the mdm.conf file to complete the configuration for the MDM server. For more information, see Configuring MDM Server.

Results

To run the MDM server, execute startup.sh in the <TomcatPath>/bin folder.

Tip: The MDM server cannot start and an exception will be thrown if the product version in MDM system database to which the datasource configuration file datasources.xml points is different from your product version. You need to use the dbmigration tool if you want to do a migration.

To shut down the MDM server, press Ctrl+C in the console window, or run bin/shutdown.sh.

For performance reasons, you can increase the memory of Tomcat. For more information about how to increase the memory size of Tomcat, see Increasing the memory of Apache Tomcat.

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!

Leave your feedback here