Introduction to the Semarchy DI Designer

Opening the Semarchy DI Designer

To open the Semarchy DI Designer:

  1. In the Semarchy Convergence for DI installation folder, double-click the SemarchyDI.exe file.
  2. The Semarchy DI Designer opens.

Semarchy DI Designer Overview

The Semarchy Convergence for DI Designer appears as follows.

In the DI Designer, the following sections are available:

Design-Time Views

The following section describes the main views used at design-time.

The Project Explorer

The Project Explorer contains a hierarchical view of the resources in the workspace.
These resources are organized into projects and folders.

The following types of resources appear in the projects:

Resource Type File Extension Description
Metadata .md A metadata resource describes source or target systems and datastores or variables that participate in a mapping or a process.
Mapping .map A mapping is used to load data between source and target datastores.
Process .proc A process is a sequence of tasks and sub-tasks that will be executed during run-time. Certain processes are Template Processes, which are used to generate a process from a mapping.
Templates Rules .tpc Templates Rules file describe the conditions upon which template processes can be used. For example, an Oracle integration template can be used when integrating data to a target datastore in an Oracle database, but is not suitable when targeting XML files.
Configuration Definition .cfc A configuration makes the metadata variable. For example, configurations can contain the connection information to the data servers and you can use configurations to switch between production and development environments.
Runtime Definition .egc Definition of a runtime engine. A runtime engine executes the integration processes created with the Semarchy Convergence for DI Designer.

From the project explorer toolbar (highlighted in the previous screenshot) you can create the three main types of design-time resources: Metadata, Mappings and Processes.

The Properties View

The Properties view displays the list of properties of the object currently selected.

The Expression Editor

The Expression Editor displays code related to the object being edited. For example, the mapping expressions, the code of the actions, etc.

This editor provides two options:

The Outline View

The Outline view provides a high-level hierarchical or graphical view of the object currently edited.

The Impact View

The Impact view allows you to analyze the usage of an object in the project and perform impact analysis and cross-referencing.

To use the Impact Monitor:

  1. Check the Active Monitoring option in the Impact editor.
  2. Select the object that you want to analyze. The Impact view displays the list of usages for this object.
  3. Double-click on one of the objects in the list to open it for edition.

Note: Impact Monitoring may be a resource consuming operation on your system. It is recommended to switch it off when you do not use it by un-selecting the Active Monitoring option in the Impact editor.

The Cache Manager tab of the Impact view allows you to explicitly refresh the cross-references cache for your workspace. In the normal course of operations, the cache is automatically refreshed.

The Run-Time Views

Three views are used to monitor the run-time components and executions of the sessions.

The Runtime View

The Runtime view allows monitoring of a Runtime Engine.

From this view, you can perform the following operations:

To create a new runtime definition:

  1. In the Runtime view, click the Runtime Editor button. The runtime definition (conf.egc) opens.
  2. Select the root node, right-click and select New > Engine.
  3. In the Properties view, enter the following information:

The Sessions View

The Sessions view displays the list of sessions of the connected runtime engine.

This list includes the following session properties:

In this view, you can filter the sessions using parameters such as the session Name or Status, filter a number of sessions, or only the session started by the current user. If the log is shared by several runtime engines, it is also possible to filter only sessions of the current runtime engine.

From this view, you can also purge the log by clicking the Delete All and Delete Until buttons.

The Session Detail View

This view displays the details of the session selected in the Sessions view. The Errors and Warning tabs display the list of issues, and the Variables tab displays the list of session and metadata variables.

Standard session variables include:

The Statistics View

The Statistics displays the list of statistics aggregated for the sessions.

The following default statistics are available:

This view can be parameterized via the preferences ( Window > Preferences), in the Semarchy Convergence for DI > Monitor section.
You can select which of the variables need to be aggregated using which aggregate function.

The Step Detail View

This view displays the details of the steps executed in a session.
It displays the code at various stages in three tabs:

The Detail Of selection box allows you to select one of the iterations of a step that was executed several times.

The Variable View

The Variable view displays the variables for the selected step. The list of variables depends on the steps. The following standard variables appear for all steps: