Contact Us 1-800-596-4880
  1. Homepage

  2. Anypoint Studio

Anypoint Studio

Anypoint Studio is MuleSoft’s Eclipse-based integration development environment for designing and testing Mule applications.

Anypoint Studio features enhance your productivity when building Mule applications:

  • Instant run of your Mule application inside a local runtime

  • Visual editors to configure API specification files and Mule domains

  • Push changes to a local running app to test changes

  • Integration with Exchange to create projects from templates and examples, and import definitions and other resources from your Anypoint Platform organization

  • Embedded unit testing framework

  • Built-in support to deploy to CloudHub

Watch the Anypoint Studio Product Spotlight video to see a quick overview of Studio.

Anypoint Studio 7.x only supports Mule 4.x projects because the structure of the project, export format, XML and scripting language are different. It isn’t possible to embed Mule 3.x runtimes or older versions into Anypoint Studio 7.x.

Editors

Studio editors help you design and edit the definitions of your applications, APIs, properties, and configuration files:

  • Mule configuration files

  • API specifications

  • Properties files

  • A pom.xml file to handle dependencies

The Mule configuration file editor opens when you double-click on the application XML file in /src/main/mule. The editor contains three tabs which offer different ways to work with your application:

  • The Message Flow tab

    A flowchart showing a listener, payload, and logger

    Contains the canvas in which you can see a visual representation of your flows. You can drag and drop Event Processors from the Mule Palette into the canvas to add them to your flow.

Clicking an Event Processor in the canvas opens up the Mule Properties View with the attributes for the selected processor, allowing you to edit them.

  • The Global Elements tab

    A table that lists global configuration elements, including type, name, and description, with buttons to create, edit, and delete them

    Contains the global Mule configuration elements for your modules. In this tab you can create, edit or delete configuration files.

  • The Configuration XML tab

    XML code for a Mule project

    Contains the XML that defines your Mule Application. All changes applied here are reflected in the canvas and the Properties view of your event processors in the Message Flow tab.

Views

Views in Studio are a graphical representation of project metadata, or properties for the active editor. Move, close, and add views as you develop your Mule project.

Anypoint Studio displays the following default views.

Package Explorer

The Package Explorer view displays the project folders and files that make up a Mule project.

A file tree showing a project’s structure and dependencies

Click the open arrow next to a Mule project folder to expand or contract it. Double-click a folder or file to open it.

Mule Palette

The Mule Palette view helps you manage the modules and connectors in your project. You can also add new elements from Exchange in this view.

A Mule Palette with a search bar, options to add modules, a favorites section, and a core section listing modules and their types

Available event processors, such as scopes, filters, and flow control routers, along with modules and their related operations are displayed.
Drag and drop any event processor to your Favorites or onto the canvas of the Mule Configuration File editor.

Mule Properties

The Mule Properties view allows you to edit the properties of the module that is currently selected in your canvas.

A form with fields to configure a listener

This view includes the DataSense Explorer which supplies real-time information about the data structure of your payload and any available inbound and outbound properties or variables.

Console

The Console view contains the console for the embedded Mule server, which displays a list of events and problems (if any) that Studio reports as you create or run your Mule application.

A console log that displays status information for a Mule application

Problems

The Problems view displays a list of all issues encountered in your project.

A table with two message flow errors

Perspectives

A Perspective in Studio is a collection of views and editors in a specified arrangement. The default perspective is the Mule Design perspective. Studio also supplies a Mule Debug perspective, and an API design perspective.

You can create your own perspectives, and add or remove any of the default views.

To add a new view to your current Perspective in Anypoint Studio navigate to Window > Show view and select the View you want to add.

If your View does not appear on the list, click Other…​ to load an entire list of available Views.

Specific Mule views such as the Mule Palette, or the Mule Debugger View can be found in the MuleSoft folder.

Configure FIPS Compliance in Anypoint Studio

You can configure Anypoint Studio to use FIPS-compliant cryptographic libraries. This configuration is required for GovCloud customers and any environment that must comply with FIPS 140-2 standards.

This page explains how to enable FIPS mode in Studio and how to run Mule applications with FIPS-compliant settings.

Prerequisites

To use FIPS mode in Anypoint Studio, make sure to review these prerequisites:

  • Anypoint Studio 7.23.0

  • Mule runtime 4.9 (LTS) or 4.10 bundled with Studio

  • Java 17 configured when using Runtime 4.9

Enable FIPS Mode in Anypoint Studio

After installing Studio, you can enable FIPS mode to ensure both the Mule runtime and the bundled JVM use FIPS-validated cryptographic providers.

Enable FIPS Support

  1. Navigate to Preferences. Click on Anypoint Studio and then Runtimes.

  2. Select the runtime that you want to configure.

  3. Select the checkbox Enable FIPS support in Mule runtime.

Studio automatically configures all required FIPS components.

When you enable FIPS mode:

  • Studio includes the Bouncy Castle FIPS (BCFIPS) libraries in the Mule runtime boot classpath.
    These libraries provide FIPS-validated cryptographic implementations.

  • Studio generates a custom java.security file that configures the JVM to use BCFIPS providers for all security operations.

  • Studio creates new keystores in BCFKS (Bouncy Castle FIPS KeyStore) format based on your existing (or default) keystores.
    BCFKS is the recommended, FIPS-compliant format for storing keys and certificates.

Run Mule Applications with FIPS Compliance

When FIPS mode is enabled, Studio updates each Mule application’s Run Configuration with the required FIPS parameters.

These parameters instruct the Mule runtime to use the FIPS security providers and the FIPS-compliant keystores generated by Studio.

  • If a Run Configuration was created before FIPS mode was enabled, delete it so Studio can regenerate it using the FIPS parameters.

  • You can edit the generated parameters if you need to use a different keystore or java.security file.

  • All cryptographic operations—including TLS, encryption, and certificate handling—run in FIPS-compliant mode.

See Also