Deployment and Configuration Overview | ||
---|---|---|
Previous | Next | |
Configuring the Database Schemas | Deploying and Configuring with Apache Tomcat |
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.
In the following chapters, the following variables names are used in the tasks:
semarchy_war_only.zip
file refers to the
Semarchy Convergence for MDM – Standalone Web Application file that you have downloaded to install Semarchy. The name of this file varies as it includes the Convergence for MDM version and build number.
semadmin
user refers to the first user created for connecting to Convergence for MDM. This user is named by default
semadmin. This name can be changed in the installation process.
<semadmin_password>
refers to the password you want to set for the
semadmin
user. This password must comply with the password policy defined for your application server.
temp
folder refers to a temporary folder of your choice.
The application configuration includes the security in the application server.
The goal of this task is to create:
semarchyConnect
role. This built-in role grants the privilege to connect to the application.
semarchyAdmin
role. This built-in role grants full privileges in the application.
semadmin
with
semarchyConnect
and
semarchyAdmin
roles. This user is the administrator for the Semarchy Convergence for MDM application.
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:
semarchyConnectGroup
and
semarchyAdminGroup
groups are created
semarchyConnectGroup
group is mapped to the built-in
semarchyConnect
role.
semarchyAdminGroup
group is mapped to the built-in
semarchyAdmin
role.
semadmin
user is added to both the
semarchyConnectGroup
and
semarchyAdminGroup
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:
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:
<oracle_instance_hostname>
: host name or IP address of the database server
<oracle_listener_port>
: number of the port where the server listens for requests.
<oracle_service_name>
: name of a database on the server. This is the SID or ServiceName in the Oracle terminology.
<repository_user_name>
: name for the user created when configuring the repository schema.
<repository_user_password>
: this user’s password.
Important: The JNDI Name of the repository datasource must always be
jdbc/SEMARCHY_REPOSITORY
. Make sure this name if 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:
<data_location_name>
: name for the data location. You can use this name as the JNDI name for the datasource in which this data location will be hosted.
<oracle_instance_hostname>
: host name or IP address of the database server
<oracle_listener_port>
: number of the port where the server listens for requests.
<oracle_service_name>
: name of a database on the server. This is the SID or ServiceName in the Oracle terminology.
<data_location_user_name>
: name for the user created when configuring the data location schema.
<data_location_user_password>
: this user’s password.
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.
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.
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. |
Previous | Top | Next |
Configuring the Database Schemas | Deploying and Configuring with Apache Tomcat |