Anypoint Studio 7.1 with Mule Runtime Engine 4.1.1 Update Site 2 Release Notes
March 18, 2018
Build ID: 201803281412
Compatibility
Product |
Version |
Mule Runtime |
Version: 4.1.1 |
Anypoint Studio |
Version: 7.1.2 |
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 |
Version: 1.1.1 |
SFTP |
Version: 1.1.2 |
Email |
Version: 1.0.0 |
Sockets |
Version: 1.1.0 |
HTTP |
Version: 1.2.0 |
Database |
Version: 1.3.1 |
OAuth |
Version: 1.1.1 |
MUnit Runner |
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 |
Hardware Requirements
-
For most use cases, Anypoint Studio with the 4.1.1 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 |
|
Operating Systems |
|
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
For first time installment, refer to Studio 7.1 release notes for instructions and known issues.
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.
From version 7.1.1 there is no special migration needed. When opening a previous Workspace which has projects that were created with Studio 7.1.0, and metadata stored in disk, Studio asks you to perform an update to all the projects so that the Metadata Manager can handle the types and to show the types in your project.
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.
-