Deployment and Configuration Overview

The Semarchy Convergence for MDM Application is a Java EE application that can be deployed to a number of environments. It requires a Java EE applications server (for example: Tomcat, Glassfish, JBoss, etc). This section details the steps required to configure the application server and deploy the application in the application server.

Tip: The instructions provided in the following chapters detail one method and approach to configure the application server. Note that the method may vary depending on the application server version. Please refer to the application server documentation for the up-to-date instructions and instruction details. Approaches also differ depending on the best practices used in your information system. Please contact the application server administrator and review these instructions to adapt them to your practices.

Conventions

In the following chapters, the following variables names are used in the tasks:

Security

The application configuration includes the security in the application server.
The goal of this task is to create:

Depending on the application server, users are directly mapped to roles, or are mapped to roles via a Group concept. When an application server uses groups:

This basic configuration allows you to connect with the semadmin user and have full privileges for the application.

It is recommended to tune and enhance the security by:

Datasources

The configuration of the application includes creating datasources to connect to the repository and the various data locations that will be used by your MDM projects.

To configure the repository datasource, make sure that you have the following information:

Important: The JNDI Name of the repository datasource must always be jdbc/SEMARCHY_REPOSITORY. Make sure this name is used for the repository datasource as it is referred to with that name by the application.

To configure the data location datasources, make sure that you have the following information for each data location schema:

If you are planning to use Convergence for MDM dashboards powered by Convergence Pulse Metrics, make sure to have the same connection information for your Pulse Metrics Warehouse schema.

JavaMail Session

Semarchy Convergence for MDM uses email servers for example to send email notifications.
For the email features to work, you must configure an email notification server.

A notification server can be configured either:

This latter option is described in the next chapters for each application server.

Note: If a JavaMail Session resource is already configured in the application server, you can skip these steps. You will reuse the existing JavaMail Session resource when configuring the notification server.

Note: The resource name used for the JavaMail session resource is set to mail/Session. This value can be changed when running the installation process, and the changed value must be used when configuring the notification server.

Application Deployment

The application is deployed by default with the semarchy context. Therefore it is accessible on the application server on the following URL: http://<application_server_host>:<application_server_port>/semarchy/.

During the application deployment, it is possible to use a different context than semarchy. If you use a different context, make sure to take it into account in the URL to test and connect to the application.

Package Content

The semarchy_war_only.zip file contains the files described in the following table:

File Description
README.txt File describing the package
geronimo-javamail_1.4_mail-1.8.3.jar Library to install to enable JavaMail for Apache Tomcat Servers. Ignore this file if you are using a different application server.
semarchy.war The Semarchy Application web application archive file.