![Example
• <sfdc:config name="Salesforce1" username="username"
password="password" doc:name="Salesforce"
securityToken="IQZjCdweSF45JD90Me2BWLLVDo">
• <sfdc:connection-pooling-profile initialisationPolicy="INITIALISE_ONE"
exhaustedAction="WHEN_EXHAUSTED_GROW"/>
• </sfdc:config>
•
• <flow name="Contacts_to_SFDC" doc:name="Contacts_to_SFDC">
• ...
• <sfdc:create config-ref="Salesforce1" type="" doc:name="Salesforce
Connector">
• <sfdc:objects ref="#[payload]"/>
• </sfdc:create>
• </flow>](https://image.slidesharecdn.com/globalelements-150709120402-lva1-app6891/85/Global-elements-7-320.jpg)
Global elements
- 2. • 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.
- 3. 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.
- 4. 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.
- 5. • Creating a Global Element • HTTP Connector • JDBC Connector • JMS Connector
- 6. 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.
- 7. Example • <sfdc:config name="Salesforce1" username="username" password="password" doc:name="Salesforce" securityToken="IQZjCdweSF45JD90Me2BWLLVDo"> • <sfdc:connection-pooling-profile initialisationPolicy="INITIALISE_ONE" exhaustedAction="WHEN_EXHAUSTED_GROW"/> • </sfdc:config> • • <flow name="Contacts_to_SFDC" doc:name="Contacts_to_SFDC"> • ... • <sfdc:create config-ref="Salesforce1" type="" doc:name="Salesforce Connector"> • <sfdc:objects ref="#[payload]"/> • </sfdc:create> • </flow>