> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/applications/mule-applications.md).

# Mule Applications

{% hint style="warning" %}

* To start scanning the applications, a schedule has to be created to scan the applications deployed in Anypoint **`Runtime Manager`**
* To create a schedule follow the steps mentioned at [Configure Schedule](/product-guides/integral-zone/iz-suite/iz-eye/azure-ais/schedule-configuration.md)
* All applications deployed in **`CLOUD HUB`** and **`CLOUD HUB 2.0`** targets will be scanned.
  {% endhint %}

### Configuring Schedule

1. While configuring the schedule select `Anypoint Mule Runtime Analysis` job type
2. In the next step, select the required `Organizations` and `Environments`
3. Choose the appropriate schedule

### To view all the applications

1. Navigate to **`IZ Eye`** -> **`Anypoint Platform`**-> **`Mule Projects`** <br>

   <figure><img src="broken://files/XrzV4tF26mXErT30BSFo" alt=""><figcaption></figcaption></figure>
2. The **`Status`** column indicates whether the application is running in Anypoint Platform **`Runtime Manager`**
3. Summary details include -
   1. **`Target`** - Indicates the deployment target, e.g. CloudHub or CloudHub 2.0
   2. **`Total Issues`** - Indicates total number of issues once the application is scanned
   3. **`App Size`** - Total size of the deployed artifact
   4. **`Last Scan`** - Time since the last scan was performed
4. Actions include -
   1. **`View Dashboard`** - Summary report of all the issues. [View Dashboard](/product-guides/integral-zone/iz-suite/iz-eye/dashboard.md)
   2. **`View Issues`** - Detailed report of the issues with file names and line numbers. [View Issues](/product-guides/integral-zone/iz-suite/iz-eye/application-issues.md)
5. Click on the settings icon to view additional columns like total worker, worker size, domain, etc. <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FafL67dBymQy7A7kzb3s2%2Fmule-app-col-settings.png?alt=media&amp;token=15997b43-8de2-44bb-88b1-301906d6581e" alt=""><figcaption></figcaption></figure>

### See Also

* [API Applications](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/applications/exchange-apis.md)
* [Application Issues](/product-guides/integral-zone/iz-suite/iz-eye/application-issues.md)
* [Application Dashboard](/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/application-dashboard.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/anypoint-platform/applications/mule-applications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.