1. Run the following curl command to put the JAR file into your Exchange:
a) Organization ID (<YOUR_ORG_ID>): How to know my Organization ID (Org ID) on the Anypoint Platform
b) Bearer token (<YOUR_ACCESS_TOKEN>): How to generate your Authorization Bearer token for Anypoint Platform
c) Environment ID (<YOUR_ENVIRONMENT_ID>) can be retrieved with this API call.
Example:
$ curl -H "Authorization: Bearer <YOUR_ACCESS_TOKEN>" https://anypoint.mulesoft.com/accounts/api/organizations/<YOUR_ORG_ID>/environments
d) Please refer to the API documentation - https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/exchange-experience-api/minor/2.3/pages/Asset%20Creation/
$ curl -v \
-H 'Authorization: Bearer <YOUR_ACCESS_TOKEN>' \
-H 'x-sync-publication: true' \
-F 'files.pom=@/<file-path>/pom.xml' \
-F 'files.mule-application.jar=@/<file-path>/<application-jar>' \
https://anypoint.mulesoft.com/exchange/api/v2/organizations/:organizationId/assets/:groupId/:assetId/:version
3. Final step is to deploy into RTF. Most of the options to fill in are the same repeats as of the previous 2 steps. There are two values to be aware of (targetID and publicUrl):
a) targetID (<TARGET_ID>): The following is the example curl to get targetID of the Runtime Fabric to be deployed in. The value is in the result key "uid".
Example:
$ curl -L -X GET 'https://anypoint.mulesoft.com/runtimefabric/api/organizations/<YOUR_ORG_ID>/fabrics/' \ -H 'Accept: application/json, text/plain, */*' \ -H 'Authorization: Bearer <YOUR_ACCESS_TOKEN>' \ -H 'X-ANYPNT-ORG-ID: <YOUR_ORG_ID>' \ -H 'Connection: keep-alive'
$ curl -L -X POST 'https://anypoint.mulesoft.com/amc/application-manager/api/v2/organizations/<YOUR_ORG_ID>/environments/<YOUR_ENVIRONMENT_ID>/deployments' \
-H 'Accept: application/json, text/plain, */*' \
-H 'Content-Type: application/json;charset=utf-8' \
-H 'Authorization: bearer <YOUR_ACCESS_TOKEN>' \
-H 'X-ANYPNT-ENV-ID: <YOUR_ENVIRONMENT_ID>' \
-H 'X-ANYPNT-ORG-ID: <YOUR_ORG_ID>' \
-H 'Connection: keep-alive' \
--data-raw '{
"name": "<APP-NAME>",
"labels": [
"beta"
],
"target": {
"provider": "MC",
"targetId": "<TARGET_ID>",
"deploymentSettings": {
"resources": {
"cpu": {
"reserved": "300m",
"limit": "1700m"
},
"memory": {
"reserved": "3400Mi",
"limit": "3400Mi"
}
},
"clustered": false,
"enforceDeployingReplicasAcrossNodes": false,
"http": {
"inbound": {
"publicUrl": "<YOUR_DOMAIN_URL>"
}
},
"jvm": {},
"runtimeVersion": "<RUNTIME_VERSION>",
"lastMileSecurity": false,
"updateStrategy": "rolling",
"disableAmLogForwarding": false
},
"replicas": 1
},
"application": {
"ref": {
"groupId": "<YOUR_ORG_ID>",
"artifactId": "<APP-NAME>",
"version": "1.0.0",
"packaging": "jar"
},
"assets": [],
"desiredState": "STARTED",
"configuration": {
"mule.agent.application.properties.service": {
"applicationName": "<APP-NAME>",
"properties": {},
"secureproperties": {}
}
}
}
}'
Note, the AMC Application Manager API
For more information about the payload properties, please check: Detailed Payload Description and Example for RTF AMC Deployment API
001115979

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.