Nav

To Migrate Assets from Exchange 1 to Exchange 2

Anypoint Exchange 2 introduces a new way of working with your assets. Where Exchange 1 is a listing service that only provides links to where assets are stored, Exchange 2 is a package management system that stores assets.

Migration to Exchange 2 differs by asset type:

Asset Type Migration Approach

Example, Template

Anypoint Studio > Publish to Exchange
Document: To Migrate an Example or Template to Exchange

OAS REST API

Publish using Exchange
Document: Add an Asset to Exchange

RAML REST API

Publish using Design Center - Note: The API Designer in Design Center is only available to new customers. Existing customers must continue to use the API Designer in API Manager and must wait for Crowd Phase 2 release to migrate APIs.
Document: To Upload an Existing RAML File to Exchange and To Migrate a RAML.
Video: REST Assets

WSDL SOAP API

Manual publish in Exchange
Document: To Add an Asset to Exchange and To Migrate a WSDL.
Video: SOAP Assets

To Migrate an Example or Template to Exchange

Note: This procedure requires Maven and that you have an Organization Administrators role.

  1. In Anypoint Exchange 1, locate an example or template from your private Exchange and click Download. This puts the example or template on your computer.

  2. If you are using Anypoint Studio 6.3.0, create the .m2/setting.xml file. In a Mac or Linux, create the ~/.m2/settings.xml file. In Windows create the \Users\LOGIN_NAME\.m2\settings.xml file.

    Use this content in the settings.xml file:

    
                
             
    1
    2
    3
    4
    5
    
    <?xml version="1.0" encoding="UTF-8"?>
    <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
    </settings>
  3. Open Anypoint Studio 6.3.0 and later, and click File > Import.

  4. In the Import menu, click Anypoint Studio > Anypoint Studio Generated Deployable Archive (.zip). Click Next. For the zip file name, click the …​ browse button, click the name of the zip file you downloaded, and click Open.

  5. Click Finish. Click OK for the Runtime version.

  6. If you have not used Maven before, right-click the project name in the Package Explorer and click Mule > Configure Maven to locate the folder where you downloaded Maven. In Studio, click Test Maven Configuration to ensure Maven is ready to use and click OK.

    When Maven is ready, right-click the project name in the Package Explorer and click Mule > Mavenize. At the Maven Support prompt, click Yes.

  7. In the Action to Perform menu, click OK.

  8. Right-click the project name and click Anypoint Platform > Publish to Exchange.

  9. Studio prompts you for your Anypoint Platform username and password. Click Signin. Or click Configure to specify an external identity provider such as OAuth and the organization’s domain.

  10. In the Publish to Exchange menu:

    1. If present in the Name field, remove special characters such as an underscore and parentheses. Only letters, numbers, spaces, dots, and dashes are permitted.

    2. If present in the Version field, remove the -SNAPSHOT value.

    3. Set the Project Type to either Example or Template as needed.

  11. After setting all fields as required, click Finish. Click Yes for the Proceed Anyway prompt.

  12. Upon successful deployment, a link appears to let you view the asset in Exchange 2. Click the link.

  13. Click the asset in Exchange 2 and click Edit. In the Exchange editor, click Visual. Copy the description text from Exchange 1 to the Exchange 2 editor and paste the description into the editor. Format as needed. Click Save As Draft to save your edits. Click Publish.

  14. In Studio, click OK to dismiss the publish to Exchange menu.

To Migrate a SOAP API WSDL

  1. Go to Exchange 1 and download your WSDL file.

  2. Go to Exchange 2 and click New.

  3. Select API Spec - WSDL in the types drop-down.

  4. In the File field, select your WSDL file.

  5. Fill in the remaining fields.

  6. Click Create.

To Migrate a REST API RAML

  1. Go to the API Manager Portal for the API and export the API Specification as a zip file.

  2. Go to Design Center API Designer and create a project of type API Specification.

  3. Import the zip.

  4. Publish to Exchange 2.