---
schema_version: "1"
id: 6e79a6d043c1dc44c48e393d06b0d37f05eb9e140b1526ff59e6aaa4e625ef9f
title: CLI for Hybrid Applications
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-cli/3.x/standalone-apps.md
canonical_url: https://docs.mulesoft.com/anypoint-cli/3.x/standalone-apps
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 3e818d12605e92f0cf154d468e9b3e4ceafe8f56ff0a9328eba525c9794e23a3
description: MuleSoft Documentation Site
release: 3.x
latest: false
---
---
product: Anypoint CLI
version: 3.x
---

# CLI for Hybrid Applications

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Use these commands for apps that are deployed to your local Mule server and managed with Runtime
Manager.

For the Anypoint Platform CLI to recognize your target servers, each server must be manually
registered with the platform.

<table><colgroup><col> <col></colgroup><thead><tr><th>Command</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-artifact">runtime-mgr standalone-application artifact</a></p></div></div></td><td><div><div><p>Downloads a standalone application artifact binary</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-deploy">runtime-mgr standalone-application deploy</a></p></div></div></td><td><div><div><p>Deploys or redeploys an application to an on-premises server, server group, or cluster</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-describe-json">runtime-mgr standalone-application describe-json</a></p></div></div></td><td><div><div><p>Shows a raw standalone application JSON response</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-modify">runtime-mgr standalone-application modify</a></p></div></div></td><td><div><div><p>Changes a standalone application artifact</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-start">runtime-mgr standalone-application start</a></p></div></div></td><td><div><div><p>Starts a standalone application</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-delete">runtime-mgr standalone-application delete</a></p></div></div></td><td><div><div><p>Deletes a standalone application</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-describe">runtime-mgr standalone-application describe</a></p></div></div></td><td><div><div><p>Shows detailed information for a standalone application</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-list">runtime-mgr standalone-application list</a></p></div></div></td><td><div><div><p>Lists all standalone applications in the environment</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-restart">runtime-mgr standalone-application restart</a></p></div></div></td><td><div><div><p>Restarts a standalone application</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-stop">runtime-mgr standalone-application stop</a></p></div></div></td><td><div><div><p>Stops a standalone application</p></div></div></td></tr><tr><td><div><div><p><a href="#runtime-mgr-standalone-application-copy">runtime-mgr standalone-application copy</a></p></div></div></td><td><div><div><p>Copies a standalone application</p></div></div></td></tr></tbody></table>

## runtime-mgr standalone-application artifact

\> runtime-mgr standalone-application artifact \[options\] <identifier> <directory>

This command downloads the application artifact of the `identifier` application, to the directory
passed in `directory`. The `identifier` parameter can be either an application ID or name.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.

## runtime-mgr standalone-application deploy

\> runtime-mgr standalone-application deploy \[options\] <targetIdentifier> <name> <zipfile>

This command deploys or redeploys the application passed as a ZIP file in the path `zipfile` to the
on-premises target passed in `targetIdentifier`.

The `targetIdentifier` parameter can be either a target ID or name.

A target can be either a server, server group, or cluster.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.

To redeploy an app and set a logging level or turn on Insight event tracking, see
[runtime-mgr standalone-application modify](#runtime-mgr-standalone-application-modify).

## runtime-mgr standalone-application describe-json

\> runtime-mgr standalone-application describe-json \[options\] <identifier>

This command describes the standalone (on-premises) application passed in `identifier` as a raw JSON
response.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.

## runtime-mgr standalone-application modify

\> runtime-mgr standalone-application modify \[options\] <identifier> <zipfile>

This command modifies the standalone (on-premises) application passed in `identifier` with the ZIP
file application passed in `zipfile` as a path.

The `identifier` parameter specifies the application identifier. To retrieve the identifier, see
[runtime-mgr standalone-application list](https://docs.mulesoft.com/anypoint-cli/latest/standalone-apps#runtime-mgr-standalone-application-list).

In addition to the default `--help`, `-f`/`--fields` and `-o`/`--output` options, this command also
takes:

<table><colgroup><col> <col></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td><p><code>--insight</code></p></td><td><div><div><p>Stores message metadata of every Mule transaction.</p></div></div></td></tr><tr><td><p><code>--log [level:scope]</code></p></td><td><div><div><p>Sets the logging level and scope pair:</p></div><div><ul><li><p><code>level</code>: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, or OFF</p></li><li><p><code>scope</code>: package name of the class, connector, or module to log, such as <code>org.mule.extension.ftp</code> for Anypoint Connector for FTP</p></li></ul></div><div><p>To set multiple logging levels, provide multiple <code>--log</code> options, for example, <code>--log INFO:org.apache --log WARN:org.mule</code>.</p></div></div></td></tr></tbody></table>

## runtime-mgr standalone-application start

\> runtime-mgr standalone-application start \[options\] <identifier>

This command starts the standalone (on-premises) application passed in `identifier`.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.

## runtime-mgr standalone-application delete

\> runtime-mgr standalone-application delete \[options\] <identifier>

This command deletes the standalone (on-premises) application passed in `identifier`.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.

> [!WARNING] This command does not prompt twice before deleting. If you send a delete instruction,
> it does not ask for confirmation.

## runtime-mgr standalone-application describe

\> runtime-mgr standalone-application describe \[options\] <identifier>

This command shows detailed information, such as status, creation date, and last update, for the
standalone (on-premises) application passed in `identifier`.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.

## runtime-mgr standalone-application list

\> runtime-mgr standalone-application list \[options\]

This command lists all standalone (on-premises) applications.

Besides the default `--help`, `-f`/`--fields` and `-o`/`--output` options, this command also takes:

<table><colgroup><col> <col></colgroup><thead><tr><th>Option</th><th>Description</th></tr></thead><tbody><tr><td><div><div><p><code>--limit &lt;num&gt;</code></p></div></div></td><td><div><div><p>Specifies the number of results to retrieve</p></div></div></td></tr><tr><td><div><div><p><code>--offset &lt;num&gt;</code></p></div></div></td><td><div><div><p>Offsets the number of applications passed</p></div></div></td></tr></tbody></table>

## runtime-mgr standalone-application restart

\> runtime-mgr standalone-application restart \[options\] <identifier>

This command restarts the standalone (on-premises) application passed in `identifier`.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.

## runtime-mgr standalone-application stop

\> runtime-mgr standalone-application stop \[options\] <identifier>

This command stops the standalone (on-premises) application passed in `identifier`.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.

## runtime-mgr standalone-application copy

\> runtime-mgr standalone-application copy \[options\] <source> <target> <targetIdentifier>

This command copies the standalone (on-premises) application passed in `source` to the target passed
in `target` and the server, server group or cluster ID or Name passed in `targetIdentifier`.

Both arguments `source` and `destination` are represented using the format:
`<organizationName>:<environmentName>/<appName>`, for example:

\> runtime-mgr standalone-application copy Services:QA/application-1 Development:QA/application-2
123456

Copies the application named `application-1` from the QA environment of the _Services_ organization
to the QA environment of the `_Development_` organization in the server ID 123456.

If the Anypoint Platform CLI is using the QA environment in the Services organization, the command
can simply take the application name as a `source`:

\> runtime-mgr standalone-application copy application-1 Development/QA/application-2 123456

> [!NOTE] Running this command requires for your user to have read/write access to the `/tmp`
> directory of the OS where the CLI is installed.

This command accepts only the default options: `--help`, `-f`/`--fields` and `-o`/`--output`.