Loading

How to find the AnypointStudio ini file

Publiceringsdatum: Aug 5, 2025
Steg

OBJECTIVE

To get your AnypointStudio.ini file for closer inspection by yourself or Customer Support. This is helpful if you need to make modifications to the default configurations. Note: The AnypointStudio.ini is the Anypoint Studio ini file equivalent of the Eclipse.ini file in generic Eclipse installations. 


STEPS


On Mac:
  1. In your finder, open Anypoint Studio
  2. Right click on the Anypoint Studio folder - click "Show Package Contents"
  3. Open "Contents" - open "Eclipse"
  4. Open the "AnypointStudio.ini" file in a text editor
 
On Windows:
  1. Open your Windows Administrator command prompt
  2. Cd into your Anypoint Studio folder. In this example, Anypoint Studio 7.6.0 is located in the AnypointStudio folder: 
    cd C:\AnypointStudio760\AnypointStudio
  3. Type 
    type AnypointStudio.ini
 

UNDERSTANDING THE RESULTS

In your .ini file, look for the line starting with -vm. It shows the Java version and path Studio is using. In the Mac example below, you can see Studio is using Java 11: 
-vm ../Eclipse/plugins/org.mule.tooling.jdk.macosx.x86_64_1.2.1/Contents/Home/bin/java

Here are examples of what the full .ini file should look like:

Mac:

The output of 'cat AnypointStudio.ini' should look like this in Mac: 
-startup
../Eclipse/plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar
--launcher.library
../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.2.600.v20220720-1916
#To_configure_a_specific_JDK_uncomment_the_following_2_lines_and_point_to_it
#-vm
#/Library/Java/JavaVirtualMachines/jdk1.8.0_191.jdk/Contents/Home/jre
-vm
../Eclipse/plugins/org.mule.tooling.jdk.macosx.x86_64_1.2.1/Contents/Home/bin/java
-vmargs
--add-modules=ALL-SYSTEM
-Xms512m
-Xmx1024m
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.instance.area.default=@user.home/AnypointStudio/studio-workspace
-Dhttps.protocols=TLSv1.2,TLSv1.1,TLSv1
-Dsun.zip.disableMemoryMapping=true
-Dequinox.resolver.revision.batch.size=1
-Dmule.testingMode=true
-Dorg.mule.tooling.runtime.args=-XX:-UseBiasedLocking,-Dfile.encoding=UTF-8,-XX:+UseG1GC,-XX:+UseStringDeduplication
-Djdk.http.auth.tunneling.disabledSchemes=
-XX:ErrorFile=./studio_crash_report.log
-Dorg.mule.tooling.client.usecache=true
-Dtooling.concurrent.local.repository.enabled=false
-Dtooling.client.configuration.filter.parameters.reserved.names=false
-Dfile.encoding=UTF-8
#To_debug_the_mule_instance_uncomment_the_following_line
#-Dmule.tooling.debug=true
#To_specify_the_debug_port_for_the_design_time_mule._E.g._To_debug_connectors_code_at_design_time.
#-Dmule.toolingInstance.debugPort=8000
#To_specify_the_debug_port_for_the_runtime_mule.
#-Dmule.tooling.debugPort=8001
-Djava.awt.headless=true
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts

Windows:

The output of 'type AnypointStudio.ini' should look like this in Windows: 
-startup
plugins/org.eclipse.equinox.launcher_1.5.700.v20200207-2156.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.1100.v20190907-0426
#To_configure_a_specific_JDK_uncomment_the_following_2_lines_and_point_to_it
#-vm
#C:\jdk1.8.0_191\bin\javaw.exe
-vm
plugins/org.mule.tooling.jdk.win32.x86_64_1.0.0.202004281356/bin/javaw.exe
-vmargs
--add-modules=ALL-SYSTEM
-Xms512m
-Xmx1024m
-XX:+UseG1GC
-XX:+UseStringDeduplication
-Dosgi.instance.area.default=@user.home/AnypointStudio/studio-workspace
-Dhttps.protocols=TLSv1.2,TLSv1.1,TLSv1
-Dsun.zip.disableMemoryMapping=true
-Dequinox.resolver.revision.batch.size=1
-Dmule.testingMode=true
-Dorg.mule.tooling.runtime.args=-XX:-UseBiasedLocking,-Dfile.encoding=UTF-8,-XX:+UseG1GC,-XX:+UseStringDeduplication
-Dorg.mule.tooling.runtime.proxyVmArgs=-Dcom.ning.http.client.AsyncHttpClientConfig.useProxyProperties=true
-Djdk.http.auth.tunneling.disabledSchemes=
-XX:ErrorFile=./studio_crash_report.log
-Dorg.mule.tooling.client.usecache=true
-Dtooling.concurrent.local.repository.enabled=false
-Dtooling.client.configuration.filter.parameters.reserved.names=false
-Dfile.encoding=UTF-8
#To_debug_the_mule_instance_uncomment_the_following_line
#-Dmule.tooling.debug=true
#To_specify_the_debug_port_for_the_design_time_mule._E.g._To_debug_connectors_code_at_design_time.
#-Dmule.toolingInstance.debugPort=8000
#To_specify_the_debug_port_for_the_runtime_mule.
#-Dmule.tooling.debugPort=8001

 
Knowledge-artikelnummer

001115951

 
Laddar
Salesforce Help | Article