> 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-scan/anypoint-studio/source-code-analysis/anypoint-studio-analysis.md).

# Anypoint Studio Analysis

## Code Analysis in Studio

{% hint style="warning" %}
Before analyzing the source code in Studio, make sure you have either:

* Installed [IZ Scan - Anypoint Studio Plugin](/product-guides/integral-zone/iz-suite/iz-scan/anypoint-studio/installation/install-iz-analyzer-studio.md)
* Configured the plugin either for:
  * [IZ Analyzer](/product-guides/integral-zone/iz-suite/iz-scan/anypoint-studio/configuration/iz-analyzer-configuration.md)
  * [IZ Scan](/product-guides/integral-zone/iz-suite/iz-scan/anypoint-studio/configuration/iz-suite-configuration.md)
    {% endhint %}

### On The Fly Results

**`On The Fly Results`** table/view will display the issues related to the project that the user is working on. Project is determined based on the current active file (i.e., the file that the user is working on) in Anypoint Studio.\
Issues will be detected and reported as and when the connectors are configured in the editor. With this, the issues can be fixed even before they exist.\
Follow the steps below to explore **`On The Fly Results`** view.

1. Go to **`Window`** -> **`Show View`** -> **`other`** -> **`IZ Scan`** -> select **`On the Fly Results`** <br>

   <figure><img src="/files/5vM6h2CMHV3O6Kqki0Zy" alt=""><figcaption></figcaption></figure>
2. Open any mule project xml, the issues will be automatically detected and the results can be seen in **`On the Fly Results`** panel. <br>

   * NOTE: **`On The Fly Results`** scans the whole project corresponding to current mule project xml and displays the results

   <figure><img src="/files/rXG1fFYKb2Hj6vt9T4iI" alt=""><figcaption></figcaption></figure>

### On The Fly Results Tab Features

The Results tab provides options such as start or stop analysis, sync rules from the server, reload on the fly results, and helps us to quickly sort through the results based on file type, component type, and severity.

1. Navigate to **`Window`** -> **`Show View`** -> **`other`** -> **`IZ Scan`** -> select **`On the Fly Results`**. The options are displayed at the top right corner. <br>

   <figure><img src="/files/SwhEBd4H5t88A8ZQ8zyo" alt=""><figcaption></figcaption></figure>
2. By default, the analysis is active and will immediately report any issues it sees fit. Clicking on the **`Stop Button`** will stop the analysis. You can start it at a later time once a part of your development is completed.\
   &#x20;

   <figure><img src="/files/klPA7afLaTgA8oz2ZpUw" alt=""><figcaption></figcaption></figure>
3. Your organization might have added new rules or updated the rules in server. By clicking on the **`Sync Rules`** option, you will be importing these updated rules onto Anypoint studio.\
   &#x20;

   <figure><img src="/files/Gz9tNhVdU2B5T17qd5Oq" alt=""><figcaption></figcaption></figure>
4. By Clicking on **`Reload on the fly results`** option, your project will be validated against the rules to refresh the tab so as to display any new issues along with the previously displayed issues. <br>

   <figure><img src="/files/CIInzSlFeqV3UpOS2b7I" alt=""><figcaption></figcaption></figure>
5. The Issues seen in the On The Fly Results tab can be grouped based on file type, component type and severity.

   1. Grouping based on **`File Type`**. <br>

      <figure><img src="/files/wrXtUY8jIWgCfZwMLFEz" alt=""><figcaption></figcaption></figure>
   2. Grouping based on **`Component Type`**. <br>

      <figure><img src="/files/wNooBilxaLW4ouMLDhXd" alt=""><figcaption></figcaption></figure>
   3. Grouping based on **`Severity`**. <br>

      <figure><img src="/files/ekBBuWzlLdBspqve8t3p" alt=""><figcaption></figcaption></figure>

   \== Issue Fix Recommendation

**`On The Fly Results`** precisely point out the problem in each file with line number, but many users might not be aware of the issue fix.\
Issue fix recommendation helps to deal with this scenario with a detailed description and examples on how to fix the issue.

1. Double-click on any issue that needs a fix to open up the **`Rule Description`** view.\
   &#x20;

   <figure><img src="/files/8ZVdpnQIe1zZuxqLwY7h" alt=""><figcaption></figcaption></figure>
2. **`Rule Description`** view provides information about:
   1. Type of Issue. E.g.: **`Code Smell`**, **`Bug`**
   2. Detailed description of the violated rule/issue
   3. Noncompliant Code Example
   4. Compliant Code Example, which guides developers on how to fix the issue
   5. Optionally, an external link to any official documentation for further information about the fix

### Upload to Server

After development is complete, users might want to upload the project to the server and save the analysis results or for any other purposes.

IZ Analyzer provides an easy option to upload a project to the server from Anypoint Studio.

{% hint style="info" %}
This step assumes that the server details are configured well in advance as mentioned in Installing Studio Plugin SonarQube version 9.x and above requires Java version 11 to scan the projects. It is recommended to use Anypoint Studio version greater than 7.9.0 to use this feature with the latest versions of SonarQube.
{% endhint %}

1. Right-click on the project that needs to be uploaded to the server, then click on **`IZ Scan - Server Upload`** <br>

   <figure><img src="/files/zDV3GeaUXHUAUsq2Bto7" alt=""><figcaption></figcaption></figure>
2. Fill in the values required for server upload and click on **`Finish`**:
   1. Project Key - Unique key of the project
   2. Project Name - Display name of the project
   3. Project version - Version of the project
3. Detailed logs of upload/scanner process will be displayed in **`console`** view <br>

   <figure><img src="/files/oZ7XjkPMbI51YauRfs7e" alt=""><figcaption></figcaption></figure>
4. Results of analysis can be further explored in web application dashboard<br>

   <figure><img src="/files/CRuqn3Uy4tXRpDSntz6J" alt=""><figcaption></figcaption></figure>

### See Also

* [Source Code Analysis - Auto Fix Issues](/product-guides/integral-zone/iz-suite/iz-scan/anypoint-studio/source-code-analysis/anypoint-studio-autofix.md)
* [Rules Playground - Custom Rules Editor](/product-guides/integral-zone/iz-suite/iz-scan/anypoint-studio/source-code-analysis/anypoint-studio-rules-playground.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-scan/anypoint-studio/source-code-analysis/anypoint-studio-analysis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.