Articles in this section

Set up an ILM lifecycle

Set up an integration lifecycle management (ILM) lifecycle to build and test changes in one copy of an integration and promote them to production. Choose the procedure that matches your account: two environments, three environments, or one environment. To choose a pattern, see Developing with integration lifecycle management.

Prerequisites:

Set up a two-environment lifecycle

In this pattern, you create a Development environment, build an integration there, clone it into Production, and pull changes from Development into Production.

  1. Create a Development environment, and enable it. See Create and manage multiple environments.
  2. Select the Development environment in the list at the top of the page. The list shows your account and environment, for example MyCompany: Production.
  3. Create an integration and create your flows in Development.
  4. Clone the integration into Production, and select or create connections for the new integration. See Clone an integration for Integration Lifecycle Management (ILM).
  5. In Production, open the cloned integration, and pull your changes from Development. See Pull changes from one integration to another.

Two-environment ILM lifecycle.

Set up a three-environment lifecycle

In this pattern, you create Development and QA environments, build an integration in Development, clone it into QA, and clone the QA integration into Production. You then pull changes from Development into QA, and from QA into Production. You can't pull from Development directly into Production.

  1. Create Development and QA environments, and enable them. You now have Production, Development, and QA.
  2. Select the Development environment at the top of the page.
  3. Create an integration and its flows in Development.
  4. Clone the integration into QA. See Clone an integration for Integration Lifecycle Management (ILM).
  5. Clone the QA integration into Production. You now have a daisy-chained lifecycle: Development, then QA, then Production. After each clone, select or create connections for the new integration.
  6. In QA, open the cloned integration, and pull your changes from Development. In Environment, select Development. See Pull changes from one integration to another.
  7. In Production, open the cloned integration, and pull your changes from QA. In Environment, select QA.

Three-environment ILM lifecycle.

Set up a lifecycle in one environment

If your account has only one environment, you can still separate development and testing by daisy-chaining clones inside that environment. The order in which you create the clones sets the order in which changes move, because you can pull only between directly related integrations. See Direct relationships.

In this example, you update your original integration through three daisy-chained clones: a Development (Dev) clone, a Quality Assurance (QA) clone, and a Dev+QA clone. You create the Dev+QA clone from the original integration, the QA clone from the Dev+QA clone, and the Dev clone from the QA clone.

Daisy-chained clones in one environment.

  1. Clone your original integration to create the Dev+QA clone. See Clone an integration for Integration Lifecycle Management (ILM).
  2. Clone the Dev+QA clone to create the QA clone.
  3. Clone the QA clone to create the Dev clone.
  4. Make and test your changes in the Dev clone.
  5. Pull the changes from the Dev clone into the QA clone. See Pull changes from one integration to another.
  6. Pull the changes from the QA clone into the Dev+QA clone.
  7. Pull the changes from the Dev+QA clone into your original integration.

Because the clones start as copies of the same integration, you might see the same conflicts at each pull. See Resolve conflicts.