Glyue User Docs
  • What is Glyue?
  • Tutorials
    • Start Here
    • Building a Single-Step Integration
      • 1. Creating the Integration
      • 2. Calling the External System
      • 3. Running the Integration
      • 4. Crafting the Output
    • Building a Multi-System Integration
      • 1. Connecting to the Core
      • 2. Field Mapping
      • 3. Running the Integration
    • Building an Event-Driven Integration
      • 1. Setting up the Mock CRM
      • 2. Receiving Inbound Requests
      • 3. Triggering the Integration from the CRM
    • Building an Email Integration
      • 1. Create and Configure the Integration
      • 2. Input Validation
      • 3. Get Story IDs from Hacker News
      • 4. Get Story Content
      • 5. Sending the Email
      • 6. Wrapping Up
      • 7. Extra credit
        • extra_credit.json
    • Building a RESTful CRUD Web Service
      • 1. Integration Setup
      • 2. Vault Setup
      • 3. Create Web Service Endpoints
      • 4. Execute Web Service Endpoints with Vault Methods
      • 5. Vault Code Examples and Explanation
    • Building a Retrieval API against FIS CodeConnect
      • 1. Integration Setup
      • 2. Service Request Setup
      • 3. Field Mapping Setup
      • 4. Integration and Service Request Hook Setup
      • 5. Testing the Integration
      • 6. Common Errors
    • What is Pre-Mapping?
      • Before you start
      • Bookmarks
      • Source and Targets
      • Field Mapping Status
      • Field Mapping Comments
      • Summary
  • How-To Guides
    • How to Run an Integration from Glyue
    • How to Invite New Users
    • How to Create a Value Mapping Set
    • How to Build and Deploy a Custom Frontend
    • How to Migrate an Integration
    • How to Set Up Single Sign On (SSO)
      • Glyue Setup
      • JumpCloud Setup
      • Azure Setup
      • Okta Setup
      • Glyue SAML Config Reference
    • How to Install the Glyue App for Zoom Contact Center
    • How to use the Vault
  • Reference
    • Integration Builder Page
    • Integration Anatomy
    • Integration Components
      • Integration
      • Service Request
      • Field Mapping
      • Value Mapping Set
      • Value Mapping
      • Validation Rule
      • Mask
      • Integration Config
      • Integration Engine Versions
    • Integration Lifecycle
    • Special Functions
      • add_run_label
      • callint
      • debug
      • end
      • get_namespace
      • humanize
      • import_helper
      • keep
      • list_files
      • map_value
      • open_glyuefile
      • open_vault
      • Data Manipulation Utilities
      • calladapter
    • Special Variables
      • __adapter_config__
      • input
      • parentint
      • retvalue
      • run_history_id
      • Iterables
        • fitem/fidx
        • sritem/sridx
        • vritem/vridx/vrmsg
    • Adapters
      • Generic HTTP Adapter
      • Email SMTP Adapter
    • Web Service Endpoints
    • Vault Reference
  • Glyue Platform Reference
    • Banking Core Connectivity Guide
    • Authentication
    • Permissions
      • Service Accounts
      • Organizations
    • Frontends
    • Idempotency Layer
    • Integration Scheduler
    • Governance Reports
    • Arbitrary Integration Request Content Support
    • Admin Components
    • Logging
  • ETL
    • Glyue ETL Overview
    • Data Connectors
    • Workflows
    • Run History
    • Scheduler
Powered by GitBook
On this page
  • Migrating a Whole Integration
  • Migrating Part of an Integration

Was this helpful?

  1. How-To Guides

How to Migrate an Integration

PreviousHow to Build and Deploy a Custom FrontendNextHow to Set Up Single Sign On (SSO)

Last updated 7 months ago

Was this helpful?

When developing integrations, Sandbox Banking Solution Engineers utilize separate DEV and PROD environments to write code and test changes before deploying that code to a production environment.

When changes to an integration are ready to be deployed to the PROD environment, Glyue provides two methods for performing a migration:

Migrating a Whole Integration

The Migrate page (pictured below) allows a user to select integrations from a source environment (often, the DEV environment) to be migrated into the destination system (the current logged-in environment, often PROD).

To migrate an integration in its entirety:

  1. Navigate to the Migrate page using the navigation sidebar.

  2. Select the Source environment in the left-hand pane. Often, this is the corresponding DEV environment.

  3. Select the integration(s) to be migrated in the right-hand pane.

  4. Verify that the Standard Migration option is selected, then click Perform Migration.

  5. Verify that the correct integration(s) were migrated by reviewing the migration summary (pictured below).

In the example above, we see that 1 integration, which contained 3 Service Requests, was migrated.

Migrating a whole integration will replace the copy of the integration that's currently in the environment.

Migrating Part of an Integration

Glyue also supports migrating selected portions of an integration, while leaving the rest of the integration as-is. The selected changes are called a changeset, and this type of migration is called a Changeset Migration.

Changeset migrations are useful in situations such as:

  • There is parallel development on different parts of an integration

  • The DEV version of an integration contains development-specific logic that should not be migrated to a production environment

To perform a changeset migration:

  1. Navigate to the Migrate page using the navigation sidebar.

  2. Select the Source environment in the left-hand pane. Often, this is the corresponding DEV environment.

  3. Using the View Changes page, select the changes you wish to include in the migration changeset by setting the Migrate column to true for the selected rows.

  4. When you're finished selecting specific changes, click Save Change Set on the toolbar along the bottom right. This will show a summary of the selected changes, along with a text field to optionally name your change set. Enter a descriptive name for the changes.

  1. Click Migrate Change Set on the toolbar along the bottom right. This will take you back to the Migrate page.

  2. On the Migrate page, reselect the source system and integration. Then select the Change Set Migration mode, select the changeset you created in step 5, then click Migrate Change Set.

  1. Verify that the correct changes were migrated by reviewing the migration summary.

Click View Incoming Changes. This will open the View Changes page, which resembles the Build page, but includes two additional columns. Migrate indicates whether a change should be included in the migration. Change describes the type of change (add / edit / delete).

Migrating a whole integration
Migrating part of an integration
A successful migration summary
The interface reviewing the specific rows selected for a migration.
Selecting a change set to migrate