Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration H2L
  • All Products

Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. Migrating a connector from previous versions using the Data Integration REST API

Migrating a connector from previous versions using the Data Integration REST API

Migrating a connector from previous versions using the Data Integration REST API

Back Next

Migration process

Migration process

The migrate API provides a simple way to migrate your connections in the configured assets to the current version.
After you complete the prerequisites, perform the following tasks to migrate the connection:
  1. Using a REST API client tool, log in to your organization that contains the older version of the connector that you want to migrate.
    1. Send a login POST request using the following URL for your login resource: https://dm-<POD region>.informaticacloud.com/ma/api/v2/user/login
    2. Specify the Informatica Intelligent Cloud Services user account and password attributes in the login object.
      The call returns the user object if the request is successful. Returns the error object if errors occur.
      The response includes the following information that you need to include in the header of the migrate REST API call:
      • icSessionId. A REST API session ID that you include in the header for version 2 REST API calls.
      • serverUrl. The base URL that you can use in version 2 resource URIs, for example: <serverUrl>/saas/api/v2/job
      Use the base URL and session ID returned in the response for the subsequent migrate requests during this session. For more information, see login
  2. You can use the objects resource to get a list of asset dependencies of the connection before you start the migration. For more information, see Finding asset dependencies.
  3. Send a migrate POST request to migrate your assets referenced with the old connection to use the new connection.
    1. Use the following URL for your migrate resource: https://<serverURL>/saas/api/v2/connectionMigration/migrate
      For example, the serverUrl is https://na4.dm-us.informaticacloud.com/saas and the URI is /api/v2/connectionMigration/migrate
    2. In the request header, specify the icSessionId.
      1. In the request body, specify following attributes:

          sourceConn. Name of the older version of the connection that you want to migrate.

          targetConn. Name of the current version of the connection to which you want to migrate.

          projectName. Name of the project folder that contains the referenced assets of the source connection. If you do not specify the folder name, the migrate resource considers assets that reference the source connection from all folders.

        The calls returns the migrate job ID, migrate job name, and the source and target folder paths in Cloud Data Integration. The source path contains the old connector version with the referenced assets, while the target path contains the assets updated to use the new current connector version. The target folder path uses the same name as the source and has the migration job ID appended to the name.
        For more information on how to use the migrate API call, see Starting a migrate job.
  4. Under projects in
    Explore
     in Cloud Data Integration, search for the target folder name and verify if the assets are updated to use the current version of the connector.
0 COMMENTS
We’d like to hear from you!