Deploy a Model Edition

After the initial model edition is deployed, it is possible to deploy other model editions. This single mechanism is used for example to:

  • Update the deployed model edition with the latest changes performed in an open model edition.

  • Deploy a new closed model version to a production or test environment.

  • Revert a deployed model edition to a previous edition.

Deploying open model editions is only possible in a Development Data Location.

Deploy a Model Edition

To deploy a model edition:

  1. In the Management view, expand the Data Locations node, right-click the data location node and select Deploy Model Edition….

  2. If you have unsaved editors, select those to save when prompted.

  3. In the The Deploy Model Edition wizard, select in the Deployed Model Edition the model edition you want to deploy.

  4. Leave the Generate Jobs Definition option checked to generate new integration jobs.

  5. Select the Clear API Enricher Caches option to force the deletion of the Enricher Caches.

  6. Click Next. The changes to perform on the data location, to support this new model edition, are computed. A second page shows the SQL script to run on the schema to deploy this model edition.

  7. Click Finish to run the script and close the wizard.
    The model edition deploys the jobs first and then runs the SQL code to create or modify the database objects. You can follow this second operation in the Console view at the bottom of the Application Builder.

The new model edition is deployed and the previous model deployment appears under the Deployment History node in the data location.

Deploying a model edition does not modify data already in place in the data location.
Although it is recommended to update both the jobs and schemas at the same time, you may want to update the data structure first then the jobs later. For example, if the data you have in the data editions using this model edition is not fit for the new version of the jobs. In that case, you may want to run some transformation on the data with the updated data structures before updating the jobs.
Another use case for not deploying the job definition is when you know that the new and old job definitions are similar and you want to preserve the existing job logs.
It is not possible to deploy a model edition in a data location that requires an upgrade.
When deploying a model edition, Semarchy lists the database objects in the data location schema and detects those it needs to create or modify. If you need to create database objects (such as indexes) in the data location schema, make sure to prefix their name with USR_. Semarchy always ignores objects named with this prefix.

Deployment History

After multiple deployments, you may decide to remove old elements in the Deployment History.

To remove historized deployments:

  1. In the Management view, expand the Deployment History node under the data location.

  2. Select one or many historized deployments (hold Shift for multiple selection).

  3. Right-click and select Delete.

The selected historized deployments are deleted.