This documentation supports the 22.1 and consecutive patch versions of BMC Helix Multi-Cloud Broker.To view an earlier version, select the version from the Product version menu.

Moving BMC Helix iPaaS, powered by Jitterbit integration projects between environments

As an administrator, you can move an integration project in BMC Helix iPaaS, powered by Jitterbit from one environment to another environment. Regardless of whether or not you have deployed the project, you can move it between environments. When you move an integration project, all the components and metadata of the project are also moved; for example, integration template, project variable, and workflows. Additionally, you can move a project from one organization to another organization in a BMC Helix iPaaS, powered by Jitterbit instance.

BMC Helix iPaaS, powered by Jitterbit environments

You can move an integration project by setting up a migration chain of environments. You move a project between the environments that you have created for an organization while setting up a BMC Helix iPaaS, powered by Jitterbit system.

A project resides in a current environment, and you can choose a target environment from the list of environments you created and move the project.

Example of moving an integration project

Allen, an administrator in Apex Global, wants to integrate BMC Helix ITSM with Jira to synchronize incidents and issues between the two applications. Allen and other users perform the following actions in the development, QA, and production environments:

Development environment

  1. Deploys the integration project and updates relevant project variables with the following details:
    • Host details and user credentials for both the applications
    • Qualification to define which ServiceNow incident should create a corresponding BMC Helix ITSM incident
  2. Moves the project from the development environment to a QA environment

QA environment

  1. Adds the URLs and credentials of the QA environments for BMC Helix iPaaS, powered by Jitterbit in the project variables.
    This action ensures that when the integration is run, the variables use the QA environment to pass the data.
  2. The QA team verifies the project.
    After ensuring there are no issues in the project, the team provides a sign-off to make the project available.

Production environment

  1.  Allen moves the final project to a production environment, and adds the host URL and credentials of the production environment in the integration template variables.
  2. Now, the agents in his organization can leverage the integration functionalities. 

Process of moving an integration project

The following image provides an overview of the process to move a project: 

Process of moving JB project between environments.png

Before you begin

Make sure you have the appropriate role and permission to access BMC Helix iPaaS, powered by Jitterbit and to move a project.

For more details, seeJitterbit Harmony Permissions and Access in the online Jitterbit documentation.

To move an integration project between environments

For steps to move an integration project, see the Project Migration topic in the online Jitterbit documentation.

To verify that the data has moved

After moving the integration project, make sure you verify that all the components of the project have been moved successfully. To do this, review the components across the target environment; for example, verify the variable details in the Project variables section.

Project variables section

Verify JB integration project.png

Troubleshooting

After moving a project, if you are unable to view its components or metadata, perform any of the following actions in BMC Helix iPaaS, powered by Jitterbit:

Action

UI

Check the project history to view a list of migration events for the project.

To learn more, see Project history in the online Jitterbit documentation.

  • The Project History option in the project actions menu:
    Project history option.png

Check the Operation Debug logs to view issues that occurred while moving a project.

To learn more, seeOperation Debug Logging in the online Jitterbit documentation.

  • The View Logs option in the project actions menu:
    Operation Debug Logging.png

To learn about various sections from where you can access the View Logs option, see Operation Logs in the online Jitterbit documentation.

Repeat the process of moving an integration project.

  • The Migrate option in the project actions menu:
    Migrate option from project actions menu.png
  • The Migrate option on the design canvas:
    Migrate option from design canvas.png

Learn more

  • Learn about moving an integration project between organizations in Project Exports and Imports in the online Jitterbit documentation.

  • Learn about Jitterbit Harmony organizations and environments in the following online Jitterbit documentation:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*