Contact Us 1-800-596-4880
  1. Homepage
  2. Archived Release Notes

  3. Anypoint Studio 7.1 with Mule Runtime Engine 4.1.1 Release Notes

Anypoint Studio 7.1 with Mule Runtime Engine 4.1.1 Release Notes

March 16, 2018
Build ID: 201803182216

Skip to Migration Guide

Compatibility

Product

Version

Mule Runtime

Version: 4.1.1

Anypoint Studio

Version: 7.1.1
Build Id: 201803182216

Maven

Version: 3.3.9

DataWeave

Version: 2.0.0

MUnit

Version: 2.1.1 (munit-studio-plugin)

Eclipse

Version: 4.7.2

Modules bundled with Studio:

Module

Version

APIkit
Scripting
VM
WSC

Version: 1.1.1

SFTP
APIKit for SOAP

Version: 1.1.2

Email
Java

Version: 1.0.0

Sockets
Validation
File
Spring
XML
Objectstore

Version: 1.1.0

HTTP
JMS

Version: 1.2.0

Database

Version: 1.3.1

OAuth

Version: 1.1.1

MUnit Runner
MUnit Tools

Version: 2.1.0

Salesforce Connector

Version: 9.1.0

Workday Connector

Version: 9.2.0

NetSuite Connector

Version: 8.1.0

ServiceNow Connector

Version: 6.2.0

What’s New

This version of Anypoint Studio introduces Mule domain projects support from Anypoint Studio.
It also introduces Proxy configuration options, and support for Mule Runtime 4.1.1.

Hardware Requirements

  • For most use cases, Anypoint Studio with the 4.1.0 Runtime does not change hardware or software requirements from the previous Studio 7 versions.

  • MuleSoft recommends a minimum of 4GB of free RAM available on a developer workstation. As applications become complex, consider adding more RAM.

  • 4GB of free memory available.

  • 2GHz CPU.

  • 10GB free hard drive space.

Software Requirements

Software

Version

Java Environments

  • Oracle JDK 1.8.0

Operating Systems

  • MacOS 10.12.0

  • Windows (32- and 64-bit) Windows 7, Windows 8, Windows 10

  • RHEL 7.0

  • Ubuntu 15.04 or later

Maven

Studio comes with Maven 3.3.9 bundled, but you can externally use the versions: 3.3.3 or your own 3.3.9

Running real-time antivirus protection software on your operating system might have a negative impact on Anypoint Studio performance. Although this issue is prominent on Windows, it also occurs on Linux and macOS.

Although the steps to solve these performance issues vary depending on your antivirus software, a typical solution is to either allow or exclude the Anypoint Studio and java executables, the Studio install and workspace filesystem locations, or some combination of both. See examples of solutions for McAfee Viruscan, Windows Defender, and Symantec Endpoint Protection.

Migration Guide

Studio 7.1 only supports Mule 4.x projects. The structure of the project, export format, XML and scripting language are different.
Users must migrate Mule 3 projects to Mule 4 manually, before they can be used in Studio 7. See the Mule migration guide for more information.

Workspaces created using Anypoint Studio 6.x or below are not compatible with Anypoint Studio 7 workspaces.

JIRA Ticket List for Anypoint Studio

Known Issues

  • Some existing features in Studio 6.x are not yet supported in Studio 7.1: Custom Policies, API Sync, Anypoint Private Cloud.

  • Because the metadata propagation works differently in Studio 7, Datasense might display errors if your DataWeave code has references to unknown metadata either because you didn’t define the metadata before writing your code, or because your flow is still incomplete.
    See Understanding How DataSense Uses Mule Event Metadata and Transform Message Component for more information.

  • Anypoint Studio uses your configured default browser to display web content such as Exchange and the Runtime Manager UI when deploying an application to Anypoint Platform. If your default internet browser does not display this content correctly, you can configure Anypoint Studio to use a Mozilla/XULRunner runtime environment as the underlying renderer for the Web UI.
    Follow the FAQ: Troubleshooting Issues with Your Default OS Browser for more details.

  • When referencing a RAML spec using Json Schema draft 3, DataSense fails. STUDIO-10033

  • Copybook import fails with no message. STUDIO-10206

  • Copybook import file not copied to project. STUDIO-10207

  • Menu items get grayed out after opening Exchange using XulRunner. STUDIO-9684

  • Mule modules needs to provide icons, today many of the modules have the generic icon. STUDIO-9628

  • Running application "Pom.xml" is not updated when changing dependencies. STUDIO-9148

  • Debugger: payload shown while debugging is partial but there is no way to view the rest of the payload STUDIO-9704

  • When referencing a RAML spec using Json Schema draft 3, DataSense fails STUDIO-10033

  • When setting WSC, it does not trigger datasense and not update metadata tree automatically. STUDIO-10242

  • Mule plugins with snapshot versions should always be regenerated.STUDIO-8716

  • Studio hangs when trying to open a big sample data file in DataWeave STUDIO-10523

  • When setting WSC, it does not trigger datasense and not update metadata tree automatically STUDIO-10523

  • Datasense/Runtime not working correctly through proxy on connectors using TCP/IP or connectors which don’t yet support it STUDIO-10377

  • Using the "Validate" option in your Mule configuration files is not supported.
    In your Package Explorer view, when right-clicking your Mule configuration file and selecting Validate, Studio runs a non-supported validation inherited from Eclipse. It is not recommended to use this feature.
    You can choose to disable these validators:

    • At Workspace level: By clicking Preferences, Validation, and disabling "Manual" and "Build" checkbox for XML Schema Validator and XML Validator.

    • At Project level: By right-clicking on your project in your Package Explorer View, select Properties, Validation, and disabling "Manual" and "Build" checkbox for XML Schema Validator and XML Validator.

Enhancement Requests

  • STUDIO-9638 - Copybook import should warn when tabs are present.

  • STUDIO-10312 - Studio 7 import should change the project from Template to regular Mule app.

  • STUDIO-10366 - Support evaluation of dynamic DW scripts.

  • STUDIO-10587 - Allow the user to install local jars to local maven repository to be used as a dependency.

Epics

  • STUDIO-8435 - Domains in Studio 7.x.

  • STUDIO-10094 - Add Gateway support in Studio 7.x.

  • STUDIO-10385 - Proxy support for Studio 7.x.

Tasks

  • STUDIO-10585 - Reduce base memory usage for service mule and runtime mule in Studio.

  • STUDIO-10586 - Migrate Studio Eclipse version to 4.7.2.

  • STUDIO-10595 - Validate Deploy to Cloudhub when using proxies.

  • STUDIO-10597 - Validate importing APIs from VCS when using proxies.

  • STUDIO-10610 - Make Mule Server 4.1.1 feature update the Mule 4.1.0 runtime for 7.1.1 (GA) release.

  • STUDIO-10622 - Update Mule dependencies to 4.1.1.

  • STUDIO-10625 - Add support for global property element.

  • STUDIO-10626 - Update Import labels to improve the UX between Flow Designer and Studio.

Support