Managing Repositories | ||
---|---|---|
Previous | ||
Managing Runtime Engines |
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.).
Repositories are listed in the
Navigator View
under the
Repositories node
.
To create a new repository:
The repository is created and the repository editor opens.
In a repository, you can:
To import a package:
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.
Configurations
store the configuration and the deliverables' metadata.
To define a new configuration:
It is possible to create deliverables
from packages using configurations.
To create a deliverable:
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.
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:
You can build a deliverable version when all the metadata properties for this deliverable are configured
To build a deliverable version:
A deliverable version appears under the deliverable node.
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.
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.
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.
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:
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.
Previous | Top | |
Managing Runtime Engines |