Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Introduction

This page describes how to deploy projects or selected project components to the Jitterbit Harmony cloud and migrate projects to another environment. Once all components that an operation is dependent on are deployed, those operations can be executed (see Operation Deployment and Execution).

Deploying

There are two options for project deployment: deploying directly and configuring a deploy.

  • Deploy: This option refers to direct deployment of an entire project. Selecting this option immediately deploys the project or reports validation errors preventing deployment.
  • Configurable Deploy: This option refers to deployment of selected project components. Selecting this option opens a deployment configuration screen where you can choose which project components to deploy.

Deploy

The option to deploy an entire project is accessible from the project pane and from the design canvas:

  • Project Pane: At the top of the project pane, click the actions menu icon  to open the actions menu. From the menu, select Deploy:

  • Design Canvas: Along the top of the design canvas, click the orange deploy/migrate icon. From the menu, select Deploy:

Upon selecting this option, a deploy will immediately be attempted for the entire project. In order for the deploy to succeed, all workflows, operations, and components used as part of an operation or in support of an operation in the project must be valid. For example, components used in these ways must be valid:

  • A component used directly as a step in the operation, such as an activity, transformation, or script.
  • A connection that an activity used in the operation is dependent upon.
  • A component called by a script in the operation.

Any component that is not part of an operation will be deployed only if its configuration is complete. If configuration of that component is incomplete, it will be skipped by the deploy.

If any workflows, operations, or components used as part of the operation are invalid, the specific validation error(s) will be provided in a popup message. For documentation on each error and how to resolve it, refer to Workflow ValidityOperation Validity, or Component Validity, respectively.

Configurable Deploy

The option to configure a deploy for all project components is accessible from the project pane and from the design canvas:

  • Project Pane: At the top of the project pane, click the actions menu icon  to open the actions menu. From the menu, select Configurable Deploy:

  • Design Canvas: Along the top of the design canvas, click the orange deploy/migrate icon. From the menu, select Configurable Deploy:

In addition, the configurable deploy option is available on individual project components (see Component Deployment).

Upon selecting this option, a deployment configuration screen opens where you can choose which project components to deploy:

By default, no project components are selected. You must select at least one project component to enable the Deploy button.

When you select a project component, all other project components that it is dependent on will also be selected. Components that are dependencies of other selected components cannot have their selections cleared, as failure to deploy these items would cause the component that has the dependency to become invalid.

To collapse or expand workflows, operations, and operation steps, use the disclosure triangles   displayed to the left of the component name.

The names of invalid components appear in the color red and italics. In addition, the names of components that are not used directly in a workflow are preceded by a tilde ~, as demonstrated with this schedule:

When all the desired project components you want to be deployed are selected, click the Deploy button.

If any selected components are invalid, the specific validation error(s) will be provided in a popup message. For documentation on each error and how to resolve it, refer to Workflow ValidityOperation Validity, or Component Validity, respectively.

Migrating

If you have more than one Harmony environment, you can migrate projects from one environment to another. You can migrate projects regardless of if they have already been deployed.

The option to migrate a project is accessible from the project pane and from the design canvas:

  • Project Pane: At the top of the project pane, click the actions menu icon  to open the actions menu. From the menu, select Migrate:

  • Design Canvas: Along the top of the design canvas, click the orange deploy/migrate icon. From the menu, select Migrate:

Upon selecting this option, a migration configuration screen opens where you can choose the target environment:

  • From: The environment where the project is located will be listed.

  • To: Use the dropdown to select the existing target environment that you want to migrate to.

  • Project: The option to migrate the entire Project is the only available dropdown selection.

    WARNING: If a project with the same name already exists in the target environment, all project components, including values of project variables in that environment, will be overwritten.
  • Migrate: Click the button to migrate the project to the selected environment. If there is already a project with the same name in the target environment, a message will ask you to confirm that you want to migrate, as this will overwrite the existing project with the same name. Upon successful migration, the project in its new environment will open in the project designer.

On This Page

Last updated:  Aug 30, 2019

  • No labels