Going to Production

Running Processes

Running a process allows you to review its behavior at design-time or execute it for run-time.

Tip: Before running a process, make sure that the runtime engine is currently running. Connect to it and activate the Refresh Diagram option to see the execution progress in the process diagram.

To run a process:

  1. Open the process editor.
  2. Right-click the process editor background and then select Execute.
  3. The process starts to execute.

You can monitor the process execution:

Working with Deliveries

A delivery is a standalone compiled element that can be executed from a runtime engine. It is generated from a process.

Generating Deliveries

To generate a delivery:

  1. Open the process editor.
  2. Right-click the process editor background and then select Build > Delivery.
  3. The delivery file (with a .deliv extension) is generated in the /runtime/build/deliveries/ sub-directory of the Semarchy DI installation folder.

Note: It is possible to generate from a mapping a delivery by selecting the Generate Delivery option from the context menu of the mapping background.

Deploying Deliveries

By default, the deliveries are generated in the deliveries folder of the runtime engine embedded into the Semarchy DI Designer.
To deploy a delivery to another runtime engine, copy the delivery file ( .deliv extension) in the /build/deliveries/ sub-directory of the remote runtime engine.

Working with Packages

A package is a pre-compiled element that can be used to generate deliveries. Unlike a delivery, a package supports re-configuration for run-time.

When a separate production team owns the production environment, the development team ships to this team packages.

The production team is able to:

  1. Extract the development configuration from the package.
  2. Create from this configuration a new configuration for the production environment
  3. Build from the package and the configuration a delivery that will be executed in the production environment.

Generating a Package

To generate a package:

  1. Open the process editor.
  2. Right-click the process editor background and then select Build > Package.
  3. The package file (with a .pck extension) is generated in the /runtime/build/packages/ sub-directory of the Semarchy DI Designer installation folder.

Generating a Delivery From a Package

From a package, it is possible to generate a delivery using an existing configuration or a configuration file.

Creating and modifying a configuration can be done from the DI Designer. For more information, see Working with Configurations.
Alternately, you can extract a configuration file template from the delivery and modify it to create your own configuration file. See Extracting a Configuration File for more information.

To generate a delivery from a package:

  1. Open an operating system command line.
  2. Go to the /runtime/ directory of the runtime engine into which the package is deployed (in the /runtime/build/packages/ sub-directory).
  3. Use the following command to extract the configuration:
buildDelivery.bat <package_name> [-conf <configuration_name>] [-confFile <configuration_file>]

where:

Note: A configuration file or a configuration name must be specified. If both are specified, the content of the configuration file overrides the configuration when it exists.

Extracting a Configuration File

This operation extracts a configuration from a package in the form of a file. This configuration file can be modified and used to generate a delivery from the package.

To extract a configuration file:

  1. Open an operating system command line.
  2. Go to the /runtime/ directory of the runtime engine into which the package is deployed (in the /runtime/build/packages/ sub-directory).
  3. Use the following command to extract the configuration:
buildDelivery.bat <package_name> [-conf <configuration_name>] [-confFile <configuration_file>] -extract

where:

The configuration file ( .properties extension) is created in the /build/packages/ sub-directory of the runtime installation directory.

The configuration file appears as in the example below:

#################################################################
### Name: Local XE/Semarchy MDM Hub (Dev)
### Type: com.stambia.rdbms.schema
#_QRNAcD34EeGJfa9nNKKg6w/TABLE_SCHEM=SEMARCHY_DEV_MDM
#_QRNAcD34EeGJfa9nNKKg6w/TABLE_CAT=
#################################################################
### Name: Local XE
### Type: com.stambia.rdbms.server
#_ldsxMD3pEeGJfa9nNKKg6w/physicalName=
#_ldsxMD3pEeGJfa9nNKKg6w/driver=oracle.jdbc.driver.OracleDriver
#_ldsxMD3pEeGJfa9nNKKg6w/url=jdbc:oracle:thin:@localhost:1521:XE
#_ldsxMD3pEeGJfa9nNKKg6w/user=SEMARCHY_DEV_MDM
#_ldsxMD3pEeGJfa9nNKKg6w/password=1355279685E38F0C392FEC2B8550200B3951C0D79B227B95C1DC348DD0BCE8F1

Uncomment the elements in this file that you want to modify.

It is possible to override the value for any metadata object property (even those not listed in the configuration template) in the configuration by specifying in the property file the value in the following way:

<object_id>/<property>=<value>

where:

After editing the configuration file, you can use it to generate a delivery.