Installation | ||
---|---|---|
Previous | Next | |
Tutorial Overview | Introduction to the Semarchy DI Designer |
Before starting this tutorial, make sure that the following requirements are met:
Note: Make sure that you also have the license keys for Semarchy Convergence for MDM and Semarchy Convergence for DI.
Tip: If you have already installed and configured Semarchy Convergence for MDM for the Getting Started with MDM Projects tutorial, the following configuration is not necessary. Simply start the Tomcat server and connect to the Convergence Workbench. In the menu, select Help > Getting Started > Open Demo Application.... In the demo application, use the Reset Sample Data button to restore the sample data to its original state. After performing these steps, you can directly go to the Installing Semarchy Convergence for DI section.
Convergence for MDM uses three schemas for the demonstration environment:
To configure the database schemas:
CREATE USER SEMARCHY_DEMO_REPOSITORY IDENTIFIED BY
SEMARCHY_DEMO_REPOSITORY DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP;
CREATE USER SEMARCHY_DEMO_SOURCE IDENTIFIED BY
SEMARCHY_DEMO_SOURCE DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP;
CREATE USER SEMARCHY_DEMO_MDM IDENTIFIED BY
SEMARCHY_DEMO_MDM DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP;
GRANT CONNECT,RESOURCE TO SEMARCHY_DEMO_REPOSITORY,
SEMARCHY_DEMO_SOURCE, SEMARCHY_DEMO_MDM;
If you have already created these schemas and wish to delete them beforehand, use the following script:
DROP USER SEMARCHY_DEMO_REPOSITORY CASCADE;
DROP USER SEMARCHY_DEMO_SOURCE CASCADE;
DROP USER SEMARCHY_DEMO_MDM CASCADE;
Convergence for MDM runs as a web application in a Java Application Server. A simple Apache Tomcat Server, pre-configured with Convergence for MDM is used for this tutorial.
In the following section, the
semarchy_with_tomcat.zip
file refers to the
Semarchy Convergence for MDM – Full Setup with Apache Tomcat file that you can download to install Semarchy Convergence for MDM. The name of this file varies as it includes the Convergence for MDM version and build number.
Tip: For the tutorial, it is recommended to install Convergence for MDM and Convergence for DI side-by-side in a
/semarchy
folder. For example, install Convergence for MDM in aC:\semarchy\semachy_mdm
folder and Convergence for DI in aC:\semarchy\semachy_di
folder on your disk.
semarchy_with_tomcat.zip
.
semarchy_with_tomcat.zip
file in your machine. This will create a
\semarchy
folder.
\semarchy\bin
.
startup.bat
.
semarchy_with_tomcat.zip
file in your home folder. This will create a
$HOME/semarchy
folder.
$HOME/semarchy/bin/startup.sh
.
Warning: The Apache Tomcat server starts by default on the port 8088. If this port is already used by another application and you wish to start the server on a different port, edit the
/conf/server.xml
file with a text editor, and change the port value in the following line:<Connector port="8088" protocol="HTTP/1.1"
Warning: The Convergence for MDM server is preconfigured with three JDBC datasources pointing to the three schemas you created (called
SEMARCHY_DEMO_REPOSITORY
,SEMARCHY_DEMO_SOURCE
andSEMARCHY_DEMO_MDM
), stored in an Oracle XE instance started on the local machine and listening on port 1521 (that is:localhost:xe:1521
). If the Oracle instance that you are using is configured differently: First, stop the Convergence for MDM server, edit the/conf/catalina/localhost/semarchy.xml
to change the configuration of the datasources and then restart the Convergence for MDM server.
To shutdown the Convergence for MDM server, run the
shutdown.bat
(Windows) or
shutdown.sh
(UNIX/Linux) script in the
/bin
folder.
Convergence for MDM holds all its information in a repository stored in a database schema. The first task when connecting Convergence for MDM is to create this repository structure in the database schema previously created.
http://localhost:8088/semarchy/
(update the port number if you changed it during the installation process)
The repository has been created and Convergence for MDM is now up and running.
The Tutorial Environment contains a Customer and Financial Hub model. This model simulates an MDM project in progress. During this tutorial, you will finish the design of this model, deploy the MDM Hub and load it from sample data sources.
To seed the Customer and Financial Hub model:
The demonstration model is seeded, the MDM Hub is installed, and the Model Edition view is opened.
Note: For this tutorial, we use a demonstration application that accesses sample data stored in the SEMARCHY_DEMO_SOURCE schema.
Note: When you access the Demo Application for the first time, you are prompted to install the sample data for the demo application. Click OK to install the sample data. This step is executed only once.
To load sample data into the MDM Hub:
Warning: Do not use the Publish Data to MDM... button. The purpose of this tutorial is to create the data integration flows to perform all the data publishing operations.
Convergence for DI includes two key components:
In the following section:
semarchy-di-designer.zip
file refers to the
Semarchy Convergence for DI- Full Setup file that you can download to install Semarchy Convergence for Data Integration. The name of this file varies as it includes the platform information, product version and build number.
<semarchy_di>
refers to the installation folder of Semarchy Convergence for DI.
semarchy-di-designer.zip
) corresponding to your platform.
semarchy-di-designer.zip
file in your machine. This will create a
semarchy_di
sub-folder. This sub-folder will be referred to as
<semarchy_di>
(the Semarchy Convergence for DI installation directory).
<semarchy_di>
folder.
semarchy.exe
. The DI Designer starts.
<semarchy_di>
folder.
./semarchy
. The DI Designer starts.
<semarchy_di>/runtime
folder and run
chmod 755 *.sh
to make the runtime scripts executable.
workspace
folder in its installation directory. To install it in a different location:
The
<semarchy_di>
directory contains the following sub-folders:
/samples
contains the files for running this getting started tutorial and other samples.
/workspace
contains the workspace that you have created. Note that you can have several workspaces for a single installation. You can locate these workspaces anywhere in your file system.
/templates
contains the templates provided out of the box with Semarchy Convergence for DI.
/runtime
contains the Semarchy Convergence for DI runtime engine binary and startup scripts.
/plugins
and
configuration
contain the binaries and configuration files for the DI Designer.
The E-LT architecture leverages the capabilities of a database for data integration. For the purpose of data processing, it may create temporary tables in the database it uses.
To host these temporary tables, it is recommended to create a schema called the
Staging Area. We will create a schema called SEMARCHY_STAGING as our staging area.
CREATE USER SEMARCHY_STAGING IDENTIFIED BY
SEMARCHY_STAGING DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP;
GRANT CONNECT,RESOURCE,DBA TO SEMARCHY_STAGING;
Note: In a production environment, if a schema already exists for storing temporary objects in a database, this schema can be specified and used as the staging area. The user attached to this schema should have read access to the tables used as sources of the data integration flows, and write access to the tables used as targets of the integration flows. The user should have full access to the staging area schema.
Note: The
DBA
privilege is required for the user connecting with Semarchy Convergence for DI for working with the SQLExplorer component in the DI Designer to list the objects of the database instance. In production, when only processes need to run, it is recommended to implement a reduced set of privileges for this user.
Previous | Top | Next |
Tutorial Overview | Introduction to the Semarchy DI Designer |