Integration Lifecycle Management (ILM) overview

Rate this feature
Included in the May 2022 release Integration Lifecycle Management features help you build and manage integrations by supporting snapshots, pulling changes, and reverting changes.

Contents

• Learn about Integration Lifecycle Management
  •  Integration Lifecycle Management overview
    • Benefits
    • Guidelines
    • Examples - Approaches for setup
  • Integration Lifecycle terminology
  • Manage your revisions
• Manage integration lifecycle

Benefits

Integration lifecycle management provides the following benefits:

• It helps you to build and test your integrations in a continuous improvement cycle.
• It helps you adhere to good practices of monitoring and managing changes while building your integrations collaboratively.
• It supports a quick and flexible approach to building integrations. You can clone an integration any number of times in the production or sandbox environment, give any number of individual users access to any of the clones, make and test changes, then pull changes in any of the clones into the production integration.
• It reduces the risks associated with making changes to mission-critical integrations. integrator.io implicitly maintains revisions, and you can always revert to a previous revision at any time.

Guidelines

You can consider these guidelines when planning your integration lifecycle management.

• Build or update an integration, preferably in a sandbox environment.
• Create a clone to build and test changes to an integration. For example, before you build a new feature or enhancement, create a clone in the sandbox environment. If you don’t require or have a sandbox environment in integrator.io, create a clone in the production environment. Note that when developing large features that have different teams using different development/testing clones, it’s good to establish guidelines for merging and pulling changes so that teams work well together.
• Create snapshots as a backup. For example, when you have to fix a critical bug within a short time, you might want to build and test the fix on the integration in the production environment itself. In such a case, snapshots are extremely useful as a backup to quickly revert to a stable state if you run into an issue.
• Create a clear access policy for effective collaboration. To understand access and permissions, see Manage account and integration permissions.

Examples - Approaches for setup

Here are some examples of approaches and workflows to set up and manage your integration lifecycle management.

Note: There are no predefined integration lifecycle workflows, and these examples are merely for guidance. You have to create an integration lifecycle routine based on your company's system development process requirements.