Managing Repositories

Introduction

Semarchy Convergence for DI Analytics uses Repositories to manage the deployment of integration processes. A repository contains packages, versions of deliverables as well as topology and configuration information (connection data, metadata configuration, etc.).

Creating a repository

Repositories are listed in the Navigator View under the Repositories node .

To create a new repository:

  1. Right-click the Repositories node in the Navigator View
  2. Select New > Repository
  3. Enter a name for this repository and then click Finish.

The repository is created and the repository editor opens.

The Deployment process

In a repository, you can:

Importing a Package

To import a package:

  1. In the repository editor, select the Build tab.
  2. Click the Import button.
  3. Browse and select Package file (with the extension .pck).
  4. Click OK when the import is complete.

The package is imported and appears in the repository, attached to a process node. Different packages files generated from the same process are attached to a same process node named after this process.

Packages generated from the Designer UI are stored in the runtime/build/packages/ sub-directory of the Designer installation directory.

Defining Configurations

Configurations store the configuration and the deliverables' metadata.

To define a new configuration:

  1. Select the Configuration tab in the repository editor.
  2. Click the Add button.
  3. Select the new configuration that appears in the list.
  4. Fill the Code field. The code is the unique identifier for the configuration. For example: PRODUCTION, UAT and TEST.
  5. Optionally fill in the Author and Description fields.
  6. Press CTRL+S to save this new configuration.

Creating a Deliverable

It is possible to create deliverables from packages using configurations.

To create a deliverable:

  1. Select the Build tab in the repository editor.
  2. Right-click a Process node and then select Add Deliverable. The new deliverable appears under the process node.
  3. Select the new deliverable. In the Properties section, select a configuration to associate to your deliverable by clicking the button next to the Conf field.
  4. Optionally associate existing runtimes to this deliverable by clicking the button next to the Runtime field.

Tip: You associate several configurations to a deliverable. In this case, the order of the configurations is important, as the last configuration in the list will have the priority. This is useful to handle configuration exceptions for certain processes, and have a generic configuration for most cases.

Configuring the Metadata Properties

Once the deliverable/configuration is created, you can configure the metadata properties for these configurations on the left hand-side of the editor.

An icon indicates whether a metadata property is correctly configured:

Note: Several packages may share the same metadata. In this case, some metadata would appear as already configured thanks to a previous deployment operation.

To configure the metadata properties:

  1. Select in the list the property that you want to configure.
  2. In the lower part of the editor, the property appears with a default value exported from design-time with the package:
    1. Preserve the same value by clicking on the configuration link.
    2. Define your own value by filling the text field.
  3. Repeat the previous steps for each property flagged with the Error icon
  4. Press CTRL+S to save the repository editor.

Building a Deliverable Version

You can build a deliverable version when all the metadata properties for this deliverable are configured

To build a deliverable version:

  1. Select the Build tab in the repository editor.
  2. Select the deliverable node .
  3. Right-click and select Build.

A deliverable version appears under the deliverable node.

Deploying a Deliverable Version

You can deploy a deliverable version using one of the following methods:

Note: You can deploy a deliverable on a runtime remotely only if the runtime is started and accessible.

Note: It is also possible to download the deliverable file by clicking the Download link, and deploy the deliverable manually on the runtime.

Managing Versions

Current Version

If you import new versions of an existing package, the latest package becomes the Current Version of the package , which is the package used to generate the deliverables.

Similarly, if you create a new version of a deliverable, the latest deliverable version becomes the Current Version of the deliverable , which is the deliverable version used for deployments.

Checking for Differences

Changes since the Latest Build

If differences exist between an imported package and the current (latest built) deliverable version, a warning icon appears on the objects (tree nodes and metadata properties). Such a warning indicates that metadata has been changed.

Changes since Latest Deployment

It is also possible to check differences exist between the current (latest built) version and the deployed on runtimes.

Under the current version node the runtimes are listed with a status icon:

Reverting to a Previous Version

It is possible to revert to a previous version of a package or a deliverable.

The Selected option on a package or deliverable allows you do force the current package/deliverable to a previous version. The default green icon appears on the selected element.