Domain projects in Mule ESB allow resources like connectors to be shared across multiple applications. A domain project defines common configurations that can then be used by Mule projects associated with that domain. When deploying domains, the domain file must be copied to the mule/domains folder rather than mule/apps, and domain projects do not support minor version changes in their names.

1. MULE ESB – Domain Concept
1

2. Objectives
 Learn about Domain concept in MULE ESB
2

3. MULE ESB - Domain and deployment
3
• Topics :
1. How to create domain project
2. Define Common/ Global configuration under domain project
3. How to create Mule project
4. Use Common/Global configuration into Mule project
• Pre-requisites :
1. Basic under standing of Mule ESB
2. JDK 1.8 or above
3. Anypoint Studio v 6.0.3 or above
4. Mule Server v 3.8.0 EE or above

4. MULE ESB - Domain and deployment
4
Domains projects in mule are a way to share resources among multiple mule
applications. Think of it just like declaring global connector configurations but
instead of sharing the configurations within multiple flows in a single application, it
is now shared across multiple flows and multiple applications. Every mule project
is associated to a domain.
Observe the mule-deploy.properties, by default the domain value is set
as “default”. This means every project has its own independent domain and no
application is sharing any resources outside its boundary.

5. MULE ESB - Domain and deployment
5
While deploying domains/projects using domains, be aware that you need to
copy the domain inside mule/domains folder instead of mule/apps folder.
Domain projects don’t support minor versions which means, if your domain
project name is httpdomain, you can deploy the domain project as
httpconnector.1.0 but you can not deploy the same as httpconnect.1.2. This is a
strange behavior which was observed.