Automating Anypoint with CLI, APIs and connected apps
Automate Anypoint Platform with Anypoint CLI 4.x and the platform APIs: how the CLI is installed, reaches the platform through proxies and other control planes, resolves credentials and defaults, deploys and promotes per deployment option, and how connected apps and their grant types authorize unattended automation.
Identify the features and characteristics for automating interactions with Anypoint Platform.
~7 min read · 11 practice questions
What the exam expects
- Recognize Anypoint CLI 4.x prerequisites, run modes and defaults, including which host, organization and environment a command acts on.
- Configure the CLI for proxies, other control planes and credentials, and predict which credential source wins.
- Choose the CLI command family that matches the deployment option (CloudHub 1.0, CloudHub 2.0, customer-hosted servers) and the flags that carry configuration during copy and promotion.
- Choose between the CLI and direct Anypoint Platform API calls, and pick a connected app grant for unattended automation.
Anypoint CLI 4.x: the anypoint-cli-v4 command-line tool that scripts a subset of platform actions. Connected app: an OAuth 2.0 and OpenID Connect client that lets an application call Anypoint Platform APIs. Grant type: the OAuth flow a connected app uses to get an access token. Application allowlist: an organization setting that controls which apps can access the organization's user data (CLI 4.x Overview, Connected Apps for Developers, Creating Connected Apps).
Key facts
- Detail
- Built with Node.js; install npm, then the CLI with npm.
- Detail
- 4.0 and later run in batch mode only.
- Detail
- Production, when none is specified.
- Detail
anypoint.mulesoft.com; override with--hostorANYPOINT_HOST.
- Detail
- Flags, then environment variables, then the config file.
- Detail
ANYPOINT_CERTIFICATEsets certificates the proxy requires.
- Detail
runtime-mgr:application:deployuses an Exchange application.
- Detail
- Pass them with
--propertyin the copy command.
- Detail
- Alerts, policies, tiers copied only with their
--copy*flags.
- Detail
- Servers must be manually registered first.
- Detail
- Gets tokens without transmitting the client secret.
Sources for this section (8)
- CLI 4.x Overviewdocs.mulesoft.com (opens in a new tab)
- CLI Authenticationdocs.mulesoft.com (opens in a new tab)
- CLI with a Network Proxydocs.mulesoft.com (opens in a new tab)
- Deploying Apps with Anypoint CLIdocs.mulesoft.com (opens in a new tab)
- CLI for CloudHub Applicationsdocs.mulesoft.com (opens in a new tab)
- CLI for API Managerdocs.mulesoft.com (opens in a new tab)
- CLI 4.x Commandsdocs.mulesoft.com (opens in a new tab)
- Creating Connected Appsdocs.mulesoft.com (opens in a new tab)
- When a CloudHub 1.0 CLI deploy prints the status
UNDEPLOYED, what does that mean? - What range of values does the CloudHub 1.0 deploy
--timeoutflag accept? - Why can a CloudHub 2.0 CLI deploy fail even though the Mule version exists?
- When
--replicaSizeis omitted from a CloudHub 2.0 CLI deploy, what size is used?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both