Contact Free trial Login

Global Elements


In Mule, a Global Element is one that you configure once, then reference many times from elements within multiple flows. Rather than repeatedly writing the same code to apply the same configuration to multiple elements in flows, you can create one global element that details your configurations or transport details. Then, you can instruct any number of elements across flows in your Mule application to reference the global element for specifics on how to behave.

  • Global elements provide flexibility. An element can apply a global element’s configuration exactly as defined, or can enhance the global configuration with modifications.

  • Global elements are reusable. You can configure a global element just once, then share that configuration among building blocks of the same type. This is particularly useful when you have to define the connection details and login credentials for an external source, such as a SaaS application or database.

  • Global elements offer efficiency. Rather than changing the same configuration multiple times within many building blocks, you can change a configuration once, in the “master”, and Studio applies the changes to all that reference it.


This document assumes that you are familiar with the Visual Editor in Anypoint Studio. Review the Anypoint Studio Essentials document to learn more about developing with Mule’s graphical user interface.

Creating a Global Element

The configuration of some elements requires a reference to a global element. For example, some message sources must reference a global connector configuration in order to function. The majority of elements, however, use global elements merely as a matter of convenience and efficiency.

Studio Visual Editor

  1. In the visual editor, click the Global Elements tab at the base of the canvas to access a list of all global elements in an application.

  2. Click Create to add a new global element.

  3. In the Choose Global Type wizard, navigate the directories or use the filter to select the type of global element you wish to create, then click OK.

  4. Define the configurable parameters of your global element, then click OK to save.

  5. To configure a local element in flow to reference a global element, use the drop-down menu next to the Connector Configuration, Connector Endpoint, or other reference field to select a global element from a list of those you have created.


    You can create a new global element from within a local element in your flow.

    Click the plus icon next to the Connector Configuration, Connector Endpoint, or other reference field, then follow the steps above to configure a global element. Click the edit icon to edit an existing global element.


XML Editor or Standalone

  1. In the XML Editor in Studio, or in your XML config file, create a global element above and outside any flows within your application.

  2. Define the values of attributes associated with the type of global element you added (see Examples below).

  3. To configure an element in flow to reference a global element, add a config-ref or connector-ref attribute to the element. The example below includes a global Salesforce element (sfdc:config), and a flow which includes a Salesforce connector (sfdc:create) that references the global Salesforce element.

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:data-mapper="" xmlns:sfdc="" xmlns:file="" xmlns:tracking="" xmlns="" xmlns:doc="" xmlns:spring="" xmlns:xsi="" xsi:schemaLocation="">

    <sfdc:config name="Salesforce1" username="username" password="password"  doc:name="Salesforce" securityToken="IQZjCdweSF45JD90Me2BWLLVDo">
        <sfdc:connection-pooling-profile initialisationPolicy="INITIALISE_ONE" exhaustedAction="WHEN_EXHAUSTED_GROW"/>

    <flow name="Contacts_to_SFDC" doc:name="Contacts_to_SFDC">
        <sfdc:create config-ref="Salesforce1" type="" doc:name="Salesforce Connector">
            <sfdc:objects ref="#[payload]"/>


Name Attribute for Security Manager Global Element

Although not required by the Mule runtime, the name attribute for the security manager global element is now required in Anypoint Studio as of version 6.0.0. If you are coding by hand in Anypoint Studio, be sure to define the name attribute on the security-manager element to suppress errors that may be reported by Studio.


HTTP Connector

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:http="" xmlns="" xmlns:doc="" xmlns:spring="" xmlns:xsi="" xsi:schemaLocation="">

    <http:listener-config name="HTTP_Listener_Configuration" host="localhost" port="8081" doc:name="HTTP Listener Configuration">
        <http:worker-threading-profile threadWaitTimeout="1500" maxBufferSize="10"/>

    <flow name="myNewProjectFlow1" doc:name="myNewProjectFlow1">
        <http:listener config-ref="HTTP_Listener_Configuration" path="/" doc:name="HTTP Connector"/>

JDBC Connector

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:jdbc-ee="" xmlns="" xmlns:doc="" xmlns:spring="" xmlns:xsi="" xsi:schemaLocation="">

    <jdbc-ee:mysql-data-source name="MySQL_Data_Source" user="test" password="test" url="jdbc:mysql://localhost:3306/[dbName]" transactionIsolation="UNSPECIFIED" doc:name="MySQL Data Source"/>

    <jdbc-ee:connector name="Database_Connector" dataSource-ref="MySQL_Data_Source" validateConnections="true" queryTimeout="-1" pollingFrequency="0" doc:name="Database"/>

    <flow name="myNewProjectFlow1" doc:name="myNewProjectFlow1">
        <jdbc-ee:inbound-endpoint queryKey="test" queryTimeout="-1" pollingFrequency="1000" connector-ref="Database_Connector" doc:name="Database">
            <jdbc-ee:query key="test" value="test"/>


JMS Connector

<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:jms="" xmlns="" xmlns:doc="" xmlns:spring="" xmlns:xsi="" xsi:schemaLocation="">

    <jms:activemq-connector name="Active_MQ" username="test" password="test" brokerURL="tcp://localhost:61616" validateConnections="true" doc:name="Active MQ"/>

    <flow name="myNewProjectFlow1" doc:name="myNewProjectFlow1">
        <jms:inbound-endpoint queue="test" connector-ref="Active_MQ" doc:name="JMS Endpoint"/>


See Also

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.