Integration with Exchange 2.0
Anypoint Studio 6.4 allows you to connect to Exchange 2.0 to publish your project as a new asset.
| The integration with Exchange 2.0 only works for Mavenized projects. |
By default, Studio 6.4 points to the Exchange 2.0 URL https://anypoint.mulesoft.com/exchange2/.
Before You Begin
Because Exchange 2.0 provides its own repository and versioning implementation, every new asset that you publish to Exchange 2.0 gets a new Group ID, Asset ID, and Version (GAV) combination.
If you are publishing an asset that already has a GAV combination configured, those Maven coordinates will be overwritten by the new GAV combination when publishing. To avoid messing up your dependencies, you have two options:
-
You can choose to move all your Mule assets to Exchange. Consider that this option requires you to update all your dependencies to reference your new Group ID.
-
If you prefer to preserve the GAV combination as it was originally assigned to your dependent assets, you can move your Mule applications with all their dependencies included in the project to Exchange.
See this related Help Center Article for more information.
To Publish to Exchange 2.0
-
In a Mavenized project, right click the project folder on your Package Explorer View.
-
Select Anypoint Platform and then Publish to Exchange.
-
Select your Anypoint Platform user and business group.
-
Additionally you can click the "Add Account" button to use a new Anypoint Platform account.
-
-
Review the information about your project:
-
Group Id: This field is required. The group Id for your project is the Organization Id of your Anypoint Platform Organization.
-
Artifact Id: This field is required. The artifact Id is the name of your project without a version. By default, Studio uses the artifact Id configured in your pom.xml file.
-
Version: This field is required. The version of the asset you are publishing.
-
-
Select a project type.
-
Select the "Save updated project information to the pom.xml" if you want to update your pom.xml file with the data you just provided.
If selected, the "Save updated project information to the pom.xml" option updates your local project’s information with the data configured in the Publish to Exchange window.
If not, the project is deployed with the configured data, but your local project information is not updated. -
Click Finish.
You can follow the deployment progress in the Console View.
After confirmed, the deployment to Exchange 2.0 cannot be stopped.