1.2 Manual installation

1.2.1 Before starting the installation

Prerequisites: see prerequisites.

Download the archive containing the java binaries, SQL scripts and configuration files.

  Snapshots Repository

Warning PostgreSQL configuration: To be able to run the scripts for creating the database, you have to modify the authentication method specified in the pg_hba.conf file. Change: to:

Then restart your database server:

1.2.2 Installation 

Unzip the archive on your computer. It should contain the following directories:

• administration (java binaries of the MDweb administration module and startup scripts)
• apache-tomcat-6.0.18 (binaries of the Java Tomcat application server)
• configuration (MDweb configuration files)
• database (SQL and batch files for creating the MDweb and thesaurus databases)
• doc (user documentation and LGPL 3.0 licence)
• war (MDweb application's web java archive)

1.2.2.1 Step 1: Creating the MDweb 2 database

In this step, we create the local MDweb database which will hold your metadata and the thesaurus database (optional)

In a console, execute the script for creating the MDweb 2 database. It is located in the database directory of the MDweb distribution databases .

Metadata bases

in the version 2.0.4, three metabases are proposed  : 

• mdweb2-ISO : includes ISO 19115/119 profiles. to create this database, download the corresponding shell script and SQL dump : creationDB20-ISO.sh (bat) and mdweb2-ISO.sql mdweb2-ISO.zip
• mdweb2-FRA : includes ISO FRA 19115/119 profiles. to create this database, download the corresponding shell script and SQL dump : creationDB20-FRA.sh (bat) and mdweb2-FRA.sql mdweb2-FRA.zip
• mdweb2-INSPIRE :  includes  ISO INSPIRE 19115/119 profiles. to create this database, download the corresponding shell script and SQL dump : creationDB20-INSPIRE.sh (bat) and mdweb2-INSPIRE.sql mdweb2-INSPIRE.zip

By default, this script creates a database called mdweb2 by using the postgres superuser account. To modify these parameters, edit the files . 

Under Windows, in a DOS box (command.com), go to the database directory and run the command:

to create mdweb2 database with ISO profiles

to create mdweb2 database with FRA ISO profiles

to create mdweb2 database with INSPIRE ISO profiles
Under Linux and MacOS, go to the database directory and run the corresponding shell script (make sure that the user has execution rights on the files):

to create mdweb2 database with ISO profiles

to create mdweb2 database with FRA ISO profiles

to create mdweb2 database with INSPIRE ISO profiles

Thesaurus databases

to associate thesaurus with MDweb2  : 

three SQL dump multi lingual thesaurii are availables in database directory databases :

• thesaurus_gemetML : this database are a SQL version of GEMET v2.1 thesaurus. it includes six schemas and each one corresponds to language : fr, en, it, de, es, pt , download the corresponding shell script and SQL dump : creationDB20-Thesaurus-GEMET.sh (bat) and thesaurus-gemet21.sql  thesaurus_gemetML.zip
• thesaurus-fra: this database are a SQL version of Agrovoc and GEMET thesaurii in french. download the corresponding shell script and SQL dump : creationDB20-Thesaurus-fra.sh (bat) and thesaurus-fra.sql   thesaurus-fra.zip
• thesaurus-eng: this database are a SQL version of Agrovoc and GEMET thesaurii in english. download the corresponding shell script and SQL dump : creationDB20-Thesaurus-eng.sh (bat) and thesaurus-eng.sql thesaurus-eng.zip

To create one of this database :

Under Windows, in a DOS box (command.com), go to the database directory and run the command:

to create thesaurus_gemetML database

to create thesaurus-fra database

to create thesaurus-eng database

Under Linux and MacOS, go to the database directory and run the corresponding shell script (make sure that the user has execution rights on the files):

to create thesaurus_gemetML database

to create thesaurus-fra database

to create thesaurus-eng database

1.2.2.2 Step 2: Copying configuration files

This step consists of copying and updating the configuration files necessary for running the MDweb search client (MDweb DB connection, cartographical context, list of queryable CSWs) and for the functioning of the web catalog service (CSW 2).

To do this, copy the files from the configuration directory to:

• Under Windows: \Documents and Settings[user]\Application Data\Sicade . (The Sicade directory has to be created beforehand.)
• Under Linux:  /home/[user]/.sicade . (The Sicade directory has to be created beforehand.)
• Under MacOS: /Users/[user]/.sicade . (The Sicade directory has to be created beforehand.)

  Be Careful [user] is the user which is owner of tomcat process. It can be tomcat user or root or anything else.

 1.2.2.3 Step 3: Updating the configuration files

The configuration files present in the Sicade or .sicade directory are listed in the following table:

* Necessity of updating this file means that the editing of variables therein is necessary for MDweb to run at all.

Parameters that have to be or can be updated are listed file by file:

 mdweb/search/config.properties

Allows you to specify the parameters for connecting to the MDweb databases.

for each language supported, you must declare the connection parameters the thesaurus database or schema.
following declaration of connection parameters for english thesaurus. the name of the parameter is a concatenation of iso code here en with the generic parameter like this

the connection parameters for the french thesaurus

 mdweb/search/cswdefaultSet.properties

 Allows you to specify which catalog services are included by default in the MDweb search client.

 * The CSW's url should not include parameters such as GetCapabiliites, Version, etc.

To add more than 10 CSWs to the list, increment these two variables thus: csw_url11, csw_name11, etc.

 mdweb/search/map-context.xml

Warning between version 2.0.1 and 2.0.4, the map-context.xml files changes and errors occurs if you don't update it on the newer version.http://mdweb.codehaus.org/1.2+Manual+installation

Contains the parameters of the WMS server which serves as the cartographical background for the MDweb search client.

Edit the map-context.xml file and modify the values of the tags, below. Only version 1.1.1 of WMS is supported.

map-context.xml for current version (2.0.4)

map-context.xml for MDweb 2.0.1

mdweb/admin/AdministrationConfiguration.xml

<metaUserName>mdweb2</metaUserName>
<thesauUserName>mdweb2</thesauUserName>
<metaPassword>mdweb_demo2</metaPassword>
<thesauPassword>mdweb_demo2</thesauPassword>
<userLogin>admin</userLogin>
<userPassword>adminadmin</userPassword>

Holds the default parameters for the MDweb administration module. The value of these parameters are displayed within the administration module when it is run. This file only stores the parameters so that they can be optionally changed for each new use of the administration module. It is therefore not necessary to edit this file.

 csw_configuration/config.xml

Warning between version 2.0.1 and 2.0.4, the csw configuration changes from config.properties file to config.xml including the same informations. If you don't create the config.xml, the changes made on adminstration panel will not take into account.

 Contains the parameters for connecting to the MDweb database which will be connected to the web catalog service and the thesaurus associated. The connexion to the thesaurus allows to add the URI of concept used in the keyword tag of XML 19139

1.2.2.4 Step 4: Deploying the MDweb2 application

The MDweb2 application has been tested under Tomcat 6.x and Glassfish 2.0. We recommend the use of the most recent version of one of these two servers.

1.2.2.4.1  If you do not have an application server installed

Installing a Tomcat 6.x server.  Version 6.0.18 is included in the archive available in our download area or you can download it from the Apache Tomcat site. The installation procedure is available on the Tomcat installation documentation page. When your application server is running, deploy MDweb2 as described in section 1.2.2.4.2, below.

Installing a Glassfish 2.0 server. Version 2.0 is available at the GlassFish community site*.* The installation procedure can be found here: Instructions to unbundle and configure GlassFish. When your application server is running, deploy MDweb2 as described in section 1.2.2.4.2, below.

1.2.2.4.2 If you have an application server running

- Deploying MDweb2 on a Tomcat 6.x server

The mdweb2.war java web archive has to be copied to Tomcat's install-dir/webapps directory. If your server is running, use the management console at http://localhost:8080/manager/ to deploy the mdweb2 war otherwise manually restart the server (see section 1.2.2.5.1). The archive will be deployed during the start up. For additional information on deploying a web application: Tomcat Web application Deployment.

- Deploying MDweb2 on a Glassfish 2.0 server

The mdweb2.war java archive has to be copied to the install-dir/domains/domain1/autodeploy/ directory. When the server has finished deploying the application, it creates a file named mdweb2.war_deployed in the autodeploy directory. Additional information can be found in the Glassfish Quick Start Guide.

1.2.2.5 Starting the application server

You have to start the application server.

1.2.2.5.1  Tomcat start up

- Under Windows :

In $INSTALL_DIR/tomcat/bin/ run the following command:

To shut down Tomcat:

- Under Linux

In $INSTALL_DIR/tomcat/bin/ run the following command: 

To shut down Tomcat:

For additional information, see Apache Tomcat online documentation.

1.2.2.5.2  Glassfish start up

1. Add the install-dir/bin/ directory to the PATH environment variable.
2. Start the server by entering this command: asadmin start-domain domain1.

Additional information at Start the GlassFish server.

Shut down Glassfish by entering this command: asadmin stop-domain domain1.

1.2.3 After installation

You can verify the proper functioning of the application server at the url http://localhost:8080/ and of MDweb2 at http://localhost:8080/mdweb2/.

1.2.3.1 PostgreSQL configuration

Set your initial configuration to ensure access to your databases, change the authentication method to md5 (or other). Restart the database server.

1.2.4 Installation problems

Be Careful If your installation has failed and you want to reattempt installation of MDweb on the same computer, you will need to uninstall it first. Use the uninstaller available in the installation directory. You should then manually delete the configuration files in the .sicade or Sicade directory; they are not deleted automatically during uninstallation.

Consult this site's FAQ for help in resolving problems.