Demonstrating Domain Projects in MuleSoft
Demonstrating Domain Projects in MuleSoft
This article will demonstrate how shared connectors work during runtime to help you understand domain projects in Anypoint Studio.
Join the DZone community and get the full member experience.Join For Free
SnapLogic is the leading self-service enterprise-grade integration platform. Download the 2018 GartnerMagic Quadrant for Enterprise iPaaS or play around on the platform, risk free, for 30 days.
Domain projects are for sharing resources; details can be acquired from the Mule documentation. One thing to note is that domain projects only work for on-prem Mule runtimes. It will not work for CloudHub. This article will demonstrate how shared connectors work during runtime.
2.0 Creating the Domain Project
First, we need to create a Domain Project. To do this (in Anypoint Studio), you need to go to File > Mule Domain Project (as per Figure 2.0a).
Then you will see a pop-up dialog; key in the following details to create our first domain project (as per Figure 2.0b), click next and click finish.
Once the domain project is created you will see the following (Figure 2.0c).
Notice that at Figure 2.0c there is a commented area; this is where you put all your global connector settings.
3.0 Creating Mule Apps That Use Domain Projects
Next, create a normal Mule application project by going to File > New > Mule Project (as per Figure 3.0a).
Name it demodomainapp1 as per the following pop-up screen in Figure 3.0b, click next and click finish.
Once demodomainapp1 is created double click on the mule project XML and select the demodomain at the domain list box as per Figure 3.0c.
Once the action on figure 3.0c is done, create the following message processors in demodomainapp1 (Figure 3.0d).
The app in figure 3.0d will have the underlying XML code.
<?xml version="1.0" encoding="UTF-8"?> <mule xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:spring="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd"> <http:listener-config name="HTTP_Listener_Configuration" host="0.0.0.0" port="8081" basePath="/demodomainapp" doc:name="HTTP Listener Configuration"/> <flow name="demodomainapp1Flow"> <http:listener config-ref="HTTP_Listener_Configuration" path="/app1" doc:name="HTTP"/> <logger message="Demo Domain App 1" level="INFO" doc:name="Logger"/> </flow> </mule>
Now we want to share the http:listener connector for both app 1 and app 2; to do this, you need to cut out the listener-config from the app 1 XML and paste it in the domain project. You would also need to replicate the xmlns:http xml namespace import to the domain project.
The Mule domain XML file (mule-domain-config.xml) would now have the following code.
<?xml version="1.0" encoding="UTF-8"?> <domain:mule-domain xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:domain="http://www.mulesoft.org/schema/mule/ee/domain" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:spring="http://www.springframework.org/schema/beans" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:http="http://www.mulesoft.org/schema/mule/http" xsi:schemaLocation=" http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd http://www.mulesoft.org/schema/mule/ee/domain http://www.mulesoft.org/schema/mule/ee/domain/current/mule-domain-ee.xsd http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd"> <http:listener-config name="HTTP_Listener_Configuration" host="0.0.0.0" port="8081" basePath="/demodomainapp" doc:name="HTTP Listener Configuration"/> </domain:mule-domain>
Do the same to create demodomainapp2, except here you need to delete the http:listener connector because it is already declared in the domain project.
Upon finishing creating app 2, you will see the following 3 projects in Anypoint Studio (as per depicted in figure 3.0e).
4.0 Debugging the Apps in Runtime
If you want to run app 1 and app 2 in debug mode at the same time then you will need to run debugging at the domain project, to do this you must go to domain project, right click debug as > mule application with Maven as per Figure 4.0a.
When debug mode is successfully running, you will see the following (Figure 4.0b) in your console logs.
If you use Postman to trigger app 1, you will see that in Anypoint Studio, your debug mode will stop the breakpoint in app 1 (as per figure 4.0c)
Now you do the same for app 2, using Postman browse to app 2 (Figure 4.0e).
You will now see that Anypoint Studio has stopped execution at app 2 breakpoint (as per Figure 4.0f).
Now if you go to the console log in Anypoint Studio, you will see the following log entries from both app 1 and app 2 (Figure 4.0g).
5.0 Deploying Them to On-Prem Runtime
The previous section demonstrated how to run applications via domain project in Anypoint Studio. Here I will go through how to deploy the application into an on-prem Mule runtime (Mule runtime is available from the Mule support site).
Figure 5.0a shows all the folders available in on-prem runtime. Two folders to note are the app and the domains folder.
You need to go to the target directory in the domain project and copy and paste the zip file across to the Mule runtime’s domain folder, as depicted in Figure 5.0b from left to right.
Now do the same for app 1 and app 2, both zip files of app 1 and app 2 are available in their respective target directories (as per Figure 5.0c). After copying it to domain folder rename the domain zip file by deleting the “-1.0.0-SNAPSHOT.”
Now when manual deployment is done, proceed to run the mule runtime. Execute the following command in windows command prompt (figure 5.0d).
Once the on-prem Mule runtime is started successfully, you will see the following in the same command prompt window.
If you test app 1 and app 2 using the same Postman commands, you will see the necessary log entries in their respective log files (figure 5.0f).
I have demonstrated how to share the same HTTP connector using domain projects. This is handy if you only want a single port opened for your on-prem Mule API that is running on the same Mule runtime. You could also share JMS or database connectors using domain projects.
Opinions expressed by DZone contributors are their own.