Running the Publishing Process

Starting the Runtime Engine

Processes are executed by the Runtime Engine component. This component must be started before running the process.

  1. Select the Runtime view.
  2. In the Runtime view, click the Environment button. The Environment dialog opens.
  3. Click the Start Local Runtime button. On Windows, a Runtime Engine is started on your local machine in a command line window. On Linux, it starts as a background process.
  4. Click OK to close the Environment dialog.
  5. Select the Connect option. This option opens a communication channel between the Semarchy DI Designer and the Runtime Engine.
  6. Select the Refresh Diagram option. This option refreshes the process diagram automatically while the process runs in the Runtime Engine and reflects the execution in real time.
    The runtime dialog indicates that the runtime is Connected.

Note: The runtime engine starts on the port 42000. Make sure that no other process uses this same port.

Note: For this tutorial, a local runtime is used and processes are started manually. In production environments, the runtime engine is deployed on a server and is able to serve execution requests remotely or run processes on a schedule.

Testing the Process

Now that the Runtime Engine is running, we can test the process.

  1. Select the background of the PublishDatatoHub process diagram.
  2. Right-click and select Execute.
  3. The process is first built and then starts. You can see the steps running. When a steps runs, it appear in green. A completed step appears in blue.
    When the execution completes, the diagram looks as shown below.

Drilling Down Into the Session

The session was executed successfully. It is possible to drill down into the details of this session.

  1. In the Sessions view, select the latest session.
  2. Select the Session Details view. This view displays the session’s information errors, warnings and the variables used in this session. The External Load ID ( SEM_LOAD_ID variable) is displayed in this view.
  3. In the PublishDatatoHub process diagram, click the Load Data sub-process step.
  4. Select the Statistics view. This view shows the statistics of the selected process step. It shows the number of rows inserted, the number of XML attributes and elements processed.
  5. Double-click the Load Data sub-process, the sub-process opens and shows the executed mappings.
  6. Click the PublishFINCostCentertoHub mapping. The statistics show the number of lines inserted by the mapping: SUM(SQL_STAT_INSERT)=27.
  7. Close the Load Data sub-process editor.

Testing the Error Behavior

To test the error behavior, you can rename one of the source files used in the mappings.

  1. Using the File Explorer, open the <semarchy_di>/samples/files/ folder and rename the cost_centers.txt file to cost_centers.txt.bad file.
  2. Return to the Semarchy DI Designer.
  3. Select the background of the PublishDatatoHub process diagram.
  4. Right-click and select Execute.
  5. The process is first built and then starts. You can see the steps running. As one of the file is missing, the Load Data sub-process fails and the Cancel External Load step is executed.
    When the execution completes, the diagram looks as shown below.
  6. Select the latest session in the Sessions view.
  7. Select the Session Details view, and in this view select the Errors tab. Double-click on the first error in the list. The error opens in a dialog.
  8. In the Windows Explorer, rename the cost_centers.txt.bad file back to cost_centers.txt.

Reviewing the External Load

The publishing process has submitted to the Semarchy Convergence for MDM hub this external load.
It is possible to review this external load in Semarchy Convergence for MDM.

  1. Open your web browser and connect to the following URL: http://localhost:8088/semarchy/ (update the port number if you changed it during the installation process)
  2. In the login prompt, enter the following:
  3. The Convergence for MDM Workbench opens.
  4. In the Overview page, Select the Manage Data Locations link in the Administration section.
  5. In the Data Editions view, expand the CustomerAndFinancialMDM > Data Branches > RootBranch > Latest Loads node. The external loads that you have submitted appear under this node. The first one appears with a Finished status, the second one (the error test) in a Cancelled status.

Note: You can review the golden data consolidated from the data published by your process by Navigating the MDM Hub. See the "Navigating the MDM Hub" section in the "Semarchy Convergence for MDM Getting Started Guide" for more information about navigating the hub.