<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sinjon Nath on Medium]]></title>
        <description><![CDATA[Stories by Sinjon Nath on Medium]]></description>
        <link>https://medium.com/@sinjonnath25?source=rss-02b6bb85ec06------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5Kw4RtmlViSdqdcANlPOrQ.jpeg</url>
            <title>Stories by Sinjon Nath on Medium</title>
            <link>https://medium.com/@sinjonnath25?source=rss-02b6bb85ec06------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 12:04:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sinjonnath25/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[HL7 Integration with MuleSoft]]></title>
            <link>https://medium.com/@sinjonnath25/hl7-integration-with-mulesoft-82c20b063bbc?source=rss-02b6bb85ec06------2</link>
            <guid isPermaLink="false">https://medium.com/p/82c20b063bbc</guid>
            <dc:creator><![CDATA[Sinjon Nath]]></dc:creator>
            <pubDate>Sat, 28 Jun 2025 15:01:50 GMT</pubDate>
            <atom:updated>2025-06-28T15:01:50.639Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*EZBKt10lNK-bJ9sJdzZzyw.png" /><figcaption>HL7 With MuleSoft</figcaption></figure><p>Healthcare is increasingly digital, yet fragmented. A patient’s data may sit across electronic medical records (EMRs), labs, pharmacies, and insurance platforms — all speaking different “languages.” That’s where <strong>HL7</strong> comes in — the backbone of healthcare data exchange — and with <strong>MuleSoft</strong>, integrating HL7 can become both scalable and manageable.</p><p>In this blog, I’ll break down HL7’s core concepts, message types, challenges, and how MuleSoft can help you efficiently integrate HL7 messages into modern healthcare ecosystems.</p><h3>📘 What is HL7?</h3><p><strong>HL7 (Health Level Seven)</strong> is a set of international standards used to facilitate the exchange of clinical and administrative data between software systems in healthcare. It defines:</p><ul><li>Message structure</li><li>Encoding rules</li><li>Field definitions</li><li>Interoperability standards</li></ul><p>The most widely used versions include:</p><ul><li><strong>HL7 v2.x</strong> — Pipe-delimited, widely adopted, real-time messaging</li><li><strong>HL7 v3</strong> — XML-based, more standardized but less adopted</li><li><strong>FHIR (Fast Healthcare Interoperability Resources)</strong> — Modern, REST-based, JSON/XML formats</li></ul><h3>🏥 HL7 in Action — Real-world Use Cases</h3><ul><li><strong>Patient admissions &amp; discharges (ADT)</strong></li><li><strong>Lab test orders &amp; results (ORM/ORU)</strong></li><li><strong>Immunization updates (VXU)</strong></li><li><strong>Pharmacy orders (RDE/RDS)</strong></li><li><strong>Appointment scheduling (SIU)</strong></li><li><strong>Billing and claims processing (DFT)</strong></li></ul><h3>🧩 HL7 Message Structure</h3><p>HL7 v2.x messages are structured as lines (segments), with each segment starting with a <strong>3-letter identifier</strong> (e.g., MSH, PID, OBX). Fields in each segment are separated by the pipe | symbol, and sub-fields by ^.</p><h3>🔹 Example: ADT^A01 (Patient Admit)</h3><pre>MSH|^~\&amp;|HospApp|Hosp|EHR|Main|202506261230||ADT^A01|123456|P|2.3<br>PID|1||P12345^^^HOSP^MR||Doe^John||19800101|M|||123 Main St^^New York^NY^10001||(555)555-1234<br>PV1|1|I|Ward^305^1^HOSP|||12345^Smith^Robert</pre><h4>Breakdown:</h4><ul><li><strong>MSH</strong> — Message header: who sent it, when, what kind.</li><li><strong>PID</strong> — Patient identification: name, ID, DOB, gender.</li><li><strong>PV1</strong> — Patient visit: ward, attending doctor.</li></ul><h3>🧰 HL7 Integration Challenges</h3><ol><li><strong>Non-Readable Format</strong> — HL7 v2 messages are not easily human-readable.</li><li><strong>Variability</strong> — Even within HL7 v2, different vendors implement the standard differently.</li><li><strong>Legacy Protocols</strong> — Messages are often transmitted over <strong>MLLP (Minimal Lower Layer Protocol)</strong>, not HTTP.</li><li><strong>Security Concerns</strong> — Sensitive patient data must be encrypted and compliant (e.g., HIPAA).</li><li><strong>Scalability</strong> — High-volume environments (labs, hospitals) require performance optimization.</li></ol><h3>🔗 Why MuleSoft for HL7?</h3><p>MuleSoft’s <strong>Anypoint Platform</strong> simplifies integration across legacy healthcare systems and modern cloud APIs. Benefits include:</p><p>MuleSoft’s Anypoint Platform simplifies HL7 processing with:</p><ul><li>✅ Native HL7 EDI Connector</li><li>✅ Schema-based validation using .esl files</li><li>✅ Parsing &amp; transformation with DataWeave</li><li>✅ MLLP, TCP, HTTP support</li><li>✅ Secure, scalable API-based flows</li><li>✅ Audit, monitoring, alerts (HIPAA-friendly)</li></ul><h3>🔧 Let’s create a MuleSoft application with HL7</h3><p>STEP 1: Create sample Mule project in Anypoint Studio.</p><p>STEP 2: Add following dependency in pom.xml.</p><p><a href="https://www.anypoint.mulesoft.com/exchange/com.mulesoft.connectors/mule-hl7-extension/">https://www.anypoint.mulesoft.com/exchange/com.mulesoft.connectors/mule-hl7-extension/</a></p><pre>&lt;dependency&gt;<br>   &lt;groupId&gt;com.mulesoft.connectors&lt;/groupId&gt;<br>   &lt;artifactId&gt;mule-hl7-extension&lt;/artifactId&gt;<br>   &lt;version&gt;4.2.12&lt;/version&gt;<br>   &lt;classifier&gt;mule-plugin&lt;/classifier&gt;<br>  &lt;/dependency&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/1*Ts1xcpe3BC8joxXN4b-LLA.png" /></figure><p>STEP 3: Create a mule flow where a http Listener takes HL7 data and reads the HL7 data, validates it with schema and finally transforms it to json .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*nomYOELfYTkRghB75KBf9A.png" /></figure><p>STEP 4: Do the below steps to configure the HL7 EDI Connector</p><ul><li>Set <strong>Name</strong>: HL7_EDI_Config</li><li>For <strong>Schema Definition</strong>, select: Edit Inline and give hl7/v2_4/ORU_R01.esl in the value as we are here working with a patient Observation Result data.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8jZE3Vx9a68TEei5WAWayA.png" /></figure><p>💡 <strong>Note:</strong> Make sure to select the correct .esl schema based on the structure and type of HL7 messages you&#39;re receiving. Mismatched schemas can cause validation errors. you can check those from the connector schemas section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TG3RyFz7VgR3OIcCY9Jm4A.png" /><figcaption>ORU_R01 schema</figcaption></figure><p>Please find the sample code for the flow<strong> </strong>below</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br><br>&lt;mule xmlns:hl7=&quot;http://www.mulesoft.org/schema/mule/hl7&quot; xmlns:ee=&quot;http://www.mulesoft.org/schema/mule/ee/core&quot;<br> xmlns:http=&quot;http://www.mulesoft.org/schema/mule/http&quot;<br> xmlns=&quot;http://www.mulesoft.org/schema/mule/core&quot; xmlns:doc=&quot;http://www.mulesoft.org/schema/mule/documentation&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation=&quot;http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd<br>http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd<br>http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd<br>http://www.mulesoft.org/schema/mule/hl7 http://www.mulesoft.org/schema/mule/hl7/current/mule-hl7.xsd&quot;&gt;<br> &lt;http:listener-config name=&quot;HTTP_Listener_config&quot; doc:name=&quot;HTTP Listener config&quot; doc:id=&quot;f207383c-230e-4cbb-b2a6-c405c9d97ece&quot; &gt;<br>  &lt;http:listener-connection host=&quot;0.0.0.0&quot; port=&quot;8081&quot; /&gt;<br> &lt;/http:listener-config&gt;<br> &lt;hl7:config name=&quot;HL7_EDI_Config&quot; doc:name=&quot;HL7 EDI Config&quot; doc:id=&quot;b7c8c8da-d31f-4aeb-a2a5-fff75152d5c6&quot; &gt;<br>  &lt;hl7:schemas &gt;<br>   &lt;hl7:schema value=&quot;/hl7/v2_4/ORU_R01.esl&quot; /&gt;<br>  &lt;/hl7:schemas&gt;<br> &lt;/hl7:config&gt;<br> &lt;flow name=&quot;hl7-apiFlow&quot; doc:id=&quot;cdab3939-145e-4b46-a3f3-ffcc9ce330a3&quot; &gt;<br>  &lt;http:listener doc:name=&quot;Listener&quot; doc:id=&quot;54607bfb-ecbf-4170-a63d-dae34f3a6273&quot; config-ref=&quot;HTTP_Listener_config&quot; path=&quot;/hl7&quot;/&gt;<br>  &lt;hl7:read doc:name=&quot;Read&quot; doc:id=&quot;aa703ab9-d942-44a2-b231-ee36f4af4a33&quot; config-ref=&quot;HL7_EDI_Config&quot;/&gt;<br>  &lt;ee:transform doc:name=&quot;Transform Message&quot; doc:id=&quot;dcb3c312-8c7c-4d2a-b611-fa21afc3d362&quot; &gt;<br>   &lt;ee:message &gt;<br>    &lt;ee:set-payload &gt;&lt;![CDATA[%dw 2.0<br>output application/json<br>var patient = payload.Data.ORU_R01.PATIENT_RESULT[0].PATIENT.PID<br>var observations = payload.Data.ORU_R01.PATIENT_RESULT[0].ORDER_OBSERVATION[0].OBSERVATION<br>---<br>{<br>  patient: {<br>    id: patient.&quot;PID-03&quot;[0].&quot;CX-01&quot;,<br>    hospital: patient.&quot;PID-03&quot;[0].&quot;CX-04&quot;.&quot;HD-01&quot;,<br>    idType: patient.&quot;PID-03&quot;[0].&quot;CX-05&quot;,<br>    firstName: patient.&quot;PID-05&quot;[0].&quot;XPN-02&quot;,<br>    lastName: patient.&quot;PID-05&quot;[0].&quot;XPN-01&quot;.&quot;FN-01&quot;,<br>    middleName: patient.&quot;PID-05&quot;[0].&quot;XPN-03&quot;,<br>    dob: patient.&quot;PID-07&quot;.&quot;TS-01&quot;,<br>    gender: patient.&quot;PID-08&quot;,<br>    phone: patient.&quot;PID-13&quot;[0].&quot;XTN-01&quot;,<br>    address: {<br>      street: patient.&quot;PID-11&quot;[0].&quot;XAD-01&quot;.&quot;SAD-01&quot;,<br>      city: patient.&quot;PID-11&quot;[0].&quot;XAD-03&quot;,<br>      state: patient.&quot;PID-11&quot;[0].&quot;XAD-04&quot;,<br>      zip: patient.&quot;PID-11&quot;[0].&quot;XAD-05&quot;<br>    }<br>  },<br>  observations: observations map (obs) -&gt; {<br>    testCode: obs.OBX.&quot;OBX-03&quot;.&quot;CE-01&quot;,<br>    testName: obs.OBX.&quot;OBX-03&quot;.&quot;CE-02&quot;,<br>    value: obs.OBX.&quot;OBX-05&quot;[0].&quot;OBX-05&quot; as Number,<br>    units: if (obs.OBX.&quot;OBX-06&quot;.&quot;CE-02&quot; != null) obs.OBX.&quot;OBX-06&quot;.&quot;CE-02&quot; else obs.OBX.&quot;OBX-06&quot;.&quot;CE-01&quot;,<br>    referenceRange: obs.OBX.&quot;OBX-07&quot;,<br>    abnormalFlag: obs.OBX.&quot;OBX-08&quot;<br>  }<br>}<br>]]&gt;&lt;/ee:set-payload&gt;<br>   &lt;/ee:message&gt;<br>  &lt;/ee:transform&gt;<br>  &lt;logger level=&quot;INFO&quot; doc:name=&quot;Logger&quot; doc:id=&quot;17f83b4d-ff1e-414c-80cf-fd6acaa6543a&quot; message=&quot;HL7 Data Transformation Completed&quot;/&gt;<br> &lt;/flow&gt;<br>&lt;/mule&gt; </pre><p>Now you can transform and map this data as per your business logic and do necessary actions.</p><p>Now test the flow with the below sample <strong>HL7 ORU^R01 Message</strong> (Raw)</p><p><strong>INPUT</strong></p><pre>MSH|^~\&amp;|LABSYS|LAB|EHR|HOSPITAL|202506280915||ORU^R01|123456|P|2.4<br>PID|1||P123456^^^HOSPITAL^MR||Smith^John^A||19820315|M|||456 Wellness Dr^^Cityville^CA^90210||(555)123-4567|||M<br>OBR|1||ORD1234^LABSYS|88304^BIOPSY^CPT||202506280900|||||||||123456^Doe^Jane^L|||202506280915||LAB123|||<br>OBX|1|NM|GLU^Glucose||98|mg/dL|70-110|N|||F<br>OBX|2|NM|WBC^White Blood Cell Count||5.5|10^3/uL|4.0-11.0|N|||F<br>OBX|3|NM|HGB^Hemoglobin||13.7|g/dL|13.0-17.0|N|||F</pre><p><strong>OUTPUT</strong></p><pre>{<br> &quot;patient&quot;: {<br>  &quot;id&quot;: &quot;P123456&quot;,<br>  &quot;hospital&quot;: &quot;HOSPITAL&quot;,<br>  &quot;idType&quot;: &quot;MR&quot;,<br>  &quot;firstName&quot;: &quot;John&quot;,<br>  &quot;lastName&quot;: &quot;Smith&quot;,<br>  &quot;middleName&quot;: &quot;A&quot;,<br>  &quot;dob&quot;: &quot;19820315&quot;,<br>  &quot;gender&quot;: &quot;M&quot;,<br>  &quot;phone&quot;: &quot;(555)123-4567&quot;,<br>  &quot;address&quot;: {<br>   &quot;street&quot;: &quot;456 Wellness Dr&quot;,<br>   &quot;city&quot;: &quot;Cityville&quot;,<br>   &quot;state&quot;: &quot;CA&quot;,<br>   &quot;zip&quot;: &quot;90210&quot;<br>  }<br> },<br> &quot;observations&quot;: [<br>  {<br>   &quot;testCode&quot;: &quot;GLU&quot;,<br>   &quot;testName&quot;: &quot;Glucose&quot;,<br>   &quot;value&quot;: 98,<br>   &quot;units&quot;: &quot;mg/dL&quot;,<br>   &quot;referenceRange&quot;: &quot;70-110&quot;,<br>   &quot;abnormalFlag&quot;: &quot;N&quot;<br>  },<br>  {<br>   &quot;testCode&quot;: &quot;WBC&quot;,<br>   &quot;testName&quot;: &quot;White Blood Cell Count&quot;,<br>   &quot;value&quot;: 5.5,<br>   &quot;units&quot;: &quot;3/uL&quot;,<br>   &quot;referenceRange&quot;: &quot;4.0-11.0&quot;,<br>   &quot;abnormalFlag&quot;: &quot;N&quot;<br>  },<br>  {<br>   &quot;testCode&quot;: &quot;HGB&quot;,<br>   &quot;testName&quot;: &quot;Hemoglobin&quot;,<br>   &quot;value&quot;: 13.7,<br>   &quot;units&quot;: &quot;g/dL&quot;,<br>   &quot;referenceRange&quot;: &quot;13.0-17.0&quot;,<br>   &quot;abnormalFlag&quot;: &quot;N&quot;<br>  }<br> ]<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3LCnnEsu30ZLgrCYfkCWNQ.png" /><figcaption>Output of Hl7 Message — transformed into Json</figcaption></figure><h3>✅ Conclusion</h3><p>HL7 is foundational to healthcare interoperability. With <strong>MuleSoft</strong>, you gain the ability to parse, validate, transform, and securely route HL7 messages across systems. Whether you’re working with ADT, ORU, or migrating to <strong>FHIR</strong>, MuleSoft&#39;s tools enable scalable, API-led transformation pipelines.</p><p>By combining HL7 standards with MuleSoft’s modern iPaaS capabilities, healthcare providers and payers can build <strong>truly interoperable</strong>, patient-centered digital ecosystems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82c20b063bbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MuleSoft with OpenAPI Specification (OAS 3.0): Enhancing API Development]]></title>
            <link>https://medium.com/@sinjonnath25/mulesoft-with-openapi-specification-oas-3-0-enhancing-api-development-d64bdac33201?source=rss-02b6bb85ec06------2</link>
            <guid isPermaLink="false">https://medium.com/p/d64bdac33201</guid>
            <dc:creator><![CDATA[Sinjon Nath]]></dc:creator>
            <pubDate>Fri, 21 Mar 2025 16:00:41 GMT</pubDate>
            <atom:updated>2025-03-21T16:00:41.363Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>API development is a critical aspect of modern software architecture, enabling seamless integration between applications and services. <strong>MuleSoft</strong>, a leading integration platform, provides robust support for API design and implementation. One of the most powerful tools for standardizing API documentation and design is the <strong>OpenAPI Specification (OAS 3.0)</strong>.</p><p>OAS 3.0 is widely used across industries such as <strong>finance, healthcare, e-commerce, telecommunications, and cloud services</strong> due to its ability to standardize API definitions, enhance interoperability, and provide automated documentation. Organizations leverage OAS 3.0 to <strong>define, document, and govern APIs efficiently</strong>, ensuring smooth communication between microservices, third-party integrations, and cloud-based platforms.</p><p>This blog explores how <strong>MuleSoft integrates with OAS 3.0</strong>, which is similar to <strong>RAML</strong> in many aspects, to streamline API development, improve interoperability, and enhance security. Additionally, we compare OAS 3.0 with <strong>RAML</strong> to help you choose the right specification for your projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*uiednzqXAOvHHCT4mtBG-Q.png" /></figure><h3>What is OpenAPI Specification (OAS 3.0)?</h3><p>The <strong>OpenAPI Specification (OAS 3.0)</strong> is a widely adopted standard for defining RESTful APIs. Formerly known as <strong>Swagger</strong>, OAS 3.0 allows developers to define API endpoints, request-response structures, authentication mechanisms, and more in a <strong>machine-readable format</strong> (YAML or JSON).</p><h3>Integrating OAS 3.0 with MuleSoft</h3><p>MuleSoft’s <strong>Anypoint Platform</strong> supports <strong>OAS 3.0</strong>, just like it supports <strong>RAML</strong>, enabling seamless API lifecycle management.</p><h3><strong>1. Designing APIs with OAS 3.0 in Anypoint Design Center</strong></h3><ul><li>Developers can <strong>import OAS 3.0 definitions</strong> into <strong>API Designer</strong>.</li><li>Provides a visual representation of API endpoints, request parameters, and responses.</li><li>Supports conversion between OAS and <strong>RAML</strong> if needed.</li></ul><p>Please find the below snaps where I have created a OAS 3.0 (YAML) Specification in Design Center and published it in Exchange</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VVhRjfibF-Yu1A0ZcuXNTw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xiJLAJi0bA0opKALP07ISA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e3bNf0Gah3E0mAJwcWWcaQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TxrpXSFQ8QIV1lJUdu8Vkg.png" /></figure><h3>2. Generating MuleSoft Flows from OAS 3.0</h3><ul><li>MuleSoft offers <strong>automatic flow generation</strong> based on OAS 3.0 definitions.</li><li>The <strong>APIkit module</strong> generates scaffolding for API implementation.</li><li>Simplifies development by auto-generating Mule flows for API endpoints.</li></ul><p>Check the below spans where I have created a mule application by importing the previously published OAS 3.0 API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4vPPRyL-hjXyAq33UOJ4Mw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NWGO4tOfJ8yua5wwX8yWnw.png" /></figure><h3>3. Validating API Requests and Responses</h3><ul><li>MuleSoft’s <strong>API Gateway</strong> enforces contract validation using OAS 3.0 schemas.</li><li>Requests that don’t conform to the OAS 3.0 schema are automatically rejected.</li></ul><h3>4. Security Implementation with OAS 3.0 in MuleSoft</h3><ul><li>OAS 3.0 supports authentication schemes like <strong>OAuth 2.0, JWT, and Mutual TLS</strong>.</li><li>MuleSoft enforces these security policies at the API gateway level.</li></ul><h3>5. Testing and Mocking APIs</h3><ul><li><strong>MuleSoft’s mocking service</strong> allows testing API endpoints before full implementation.</li><li>OAS 3.0 definitions generate mock responses for front-end development.</li></ul><h3>6. Deploying OAS 3.0-Based APIs in CloudHub</h3><ul><li>MuleSoft allows seamless deployment of APIs to <strong>CloudHub</strong> while ensuring compliance with OpenAPI contracts.</li><li>Supports API versioning, monitoring, and analytics.</li></ul><h3>Comparing OAS 3.0 and RAML in MuleSoft</h3><p>MuleSoft supports both <strong>OpenAPI Specification (OAS 3.0)</strong> and <strong>RESTful API Modeling Language (RAML)</strong>. Here’s a comparison:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uW-0cuBQttORt89jGKhGNg.png" /></figure><h3>Benefits of OAS 3.0 Over RAML</h3><ol><li><strong>Better Security Mechanisms</strong> — Enhanced authentication options such as mutual TLS and OAuth 2.0.</li><li><strong>Stronger Industry Adoption</strong> — OAS 3.0 is widely used across multiple industries, ensuring better interoperability.</li><li><strong>Advanced API Documentation</strong> — Interactive documentation improves developer experience and onboarding.</li><li><strong>Native Support for Multiple Servers</strong> — OAS 3.0 allows defining multiple server URLs within the same API definition.</li></ol><h3>Which One to Choose?</h3><ul><li>If working <strong>exclusively with MuleSoft</strong>, <strong>RAML</strong> provides a more <strong>native experience</strong> with better support for APIkit.</li><li>If <strong>broader industry adoption</strong> and <strong>interoperability with external tools</strong> (Swagger UI, Postman) are required, <strong>OpenAPI 3.0 is the better choice</strong>.</li><li>MuleSoft allows <strong>conversion between RAML and OAS 3.0</strong>, so you can leverage the strengths of both.</li></ul><p>Here’s a sample <strong>OpenAPI Specification (OAS) 3.0 YAML file</strong> with four endpoints</p><pre>openapi: 3.0.0<br>info:<br>  title: User Management API<br>  description: API for managing users in the system<br>  version: 1.0.0<br><br>paths:<br>  /users:<br>    get:<br>      summary: Get all users<br>      operationId: getUsers<br>      tags:<br>        - Users<br>      responses:<br>        &#39;200&#39;:<br>          description: A list of users<br>          content:<br>            application/json:<br>              schema:<br>                type: array<br>                items:<br>                  $ref: &#39;#/components/schemas/User&#39;<br>    post:<br>      summary: Create a new user<br>      operationId: createUser<br>      tags:<br>        - Users<br>      requestBody:<br>        required: true<br>        content:<br>          application/json:<br>            schema:<br>              $ref: &#39;#/components/schemas/User&#39;<br>      responses:<br>        &#39;201&#39;:<br>          description: User created successfully<br>          content:<br>            application/json:<br>              schema:<br>                $ref: &#39;#/components/schemas/User&#39;<br>  /users/{id}:<br>    get:<br>      summary: Get a user by ID<br>      operationId: getUserById<br>      tags:<br>        - Users<br>      parameters:<br>        - name: id<br>          in: path<br>          required: true<br>          description: ID of the user to retrieve<br>          schema:<br>            type: string<br>      responses:<br>        &#39;200&#39;:<br>          description: User details<br>          content:<br>            application/json:<br>              schema:<br>                $ref: &#39;#/components/schemas/User&#39;<br>        &#39;404&#39;:<br>          description: User not found<br>    put:<br>      summary: Update a user by ID<br>      operationId: updateUser<br>      tags:<br>        - Users<br>      parameters:<br>        - name: id<br>          in: path<br>          required: true<br>          description: ID of the user to update<br>          schema:<br>            type: string<br>      requestBody:<br>        required: true<br>        content:<br>          application/json:<br>            schema:<br>              $ref: &#39;#/components/schemas/User&#39;<br>      responses:<br>        &#39;200&#39;:<br>          description: User updated successfully<br>          content:<br>            application/json:<br>              schema:<br>                $ref: &#39;#/components/schemas/User&#39;<br>        &#39;404&#39;:<br>          description: User not found<br>components:<br>  schemas:<br>    User:<br>      type: object<br>      properties:<br>        id:<br>          type: string<br>          example: &quot;12345&quot;<br>        name:<br>          type: string<br>          example: &quot;John Doe&quot;<br>        email:<br>          type: string<br>          format: email<br>          example: &quot;john.doe@example.com&quot;<br>        age:<br>          type: integer<br>          example: 30</pre><p>Integrating <strong>MuleSoft with OpenAPI Specification (OAS 3.0)</strong> transforms the API development process by enforcing best practices, reducing errors, and improving security. Since <strong>OAS 3.0 and RAML share many similarities</strong>, teams already familiar with MuleSoft’s API development workflow can easily adapt to OAS 3.0.</p><p>By leveraging <strong>APIkit, Anypoint Platform, and API Gateway</strong>, developers can efficiently build, test, and deploy APIs that adhere to industry standards.</p><p>Whether you are designing new APIs or modernizing existing ones, adopting <strong>OAS 3.0 with MuleSoft</strong> is a strategic move towards a <strong>scalable and robust API ecosystem</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d64bdac33201" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outlook 365 Connector vs. Email Connector: The Best Choice for MuleSoft Integrations]]></title>
            <link>https://medium.com/@sinjonnath25/outlook-365-connector-vs-email-connector-the-best-choice-for-mulesoft-integrations-0897405a6c2a?source=rss-02b6bb85ec06------2</link>
            <guid isPermaLink="false">https://medium.com/p/0897405a6c2a</guid>
            <dc:creator><![CDATA[Sinjon Nath]]></dc:creator>
            <pubDate>Tue, 25 Feb 2025 17:11:34 GMT</pubDate>
            <atom:updated>2025-02-25T17:50:42.319Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s digital world, secure and efficient email communication is critical for businesses. While MuleSoft provides both the <strong>Traditional Email Connector</strong> (SMTP, IMAP, POP3) and the <strong>Outlook 365 Connector</strong>, many organizations are shifting towards Outlook 365 due to its enhanced security and seamless Microsoft integration. In this blog, we will explore why the <strong>Outlook 365 Connector</strong> is a superior choice and how it improves security and operational efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*HaZ5jpBU1Fr_kqQ7YO3dFQ.png" /></figure><h3>1. Enhanced Security</h3><h4>OAuth 2.0 Authentication</h4><p>The Outlook 365 Connector uses <strong>OAuth 2.0</strong> for authentication, which is far more secure than the basic authentication (username/password) used by the traditional Email Connector. Many providers, including Microsoft, are deprecating basic authentication due to security risks like credential theft.</p><h4>Multi-Factor Authentication (MFA) &amp; Conditional Access</h4><p>With Outlook 365, organizations can enforce <strong>Multi-Factor Authentication (MFA)</strong> and <strong>conditional access policies</strong>, significantly improving security. The traditional Email Connector does not support these features, making it vulnerable to unauthorized access.</p><h3>2. Simplified Configuration &amp; Maintenance</h3><h4>No SMTP/IMAP/POP3 Setup</h4><p>The Email Connector requires manually configuring SMTP, IMAP, or POP3 servers, which can be complex and error-prone. In contrast, the Outlook 365 Connector eliminates this hassle by directly integrating with <strong>Microsoft Graph API</strong>, allowing for easier setup and maintenance.</p><h4>Built-in API Support</h4><p>Since the Outlook 365 Connector uses the <strong>Microsoft Graph API</strong>, developers can leverage existing Microsoft 365 functionalities without dealing with the complexity of email protocols.</p><h3>3. Better Integration with the Microsoft Ecosystem</h3><h4>Seamless Integration with Microsoft 365 Services</h4><p>Beyond just email, the Outlook 365 Connector can interact with <strong>calendar events, contacts, OneDrive, and Teams</strong>, making it a more versatile option for enterprises deeply embedded in the Microsoft ecosystem.</p><h4>Cloud Compatibility</h4><p>As Outlook 365 is a cloud-based service, it ensures smoother integration with <strong>Azure and other Microsoft cloud solutions</strong>, making it an ideal choice for cloud-native applications.</p><h3>4. Improved Reliability &amp; Performance</h3><h4>Event-Driven Processing (Push Model)</h4><p>The traditional Email Connector relies on <strong>polling</strong>, where MuleSoft repeatedly checks the mail server for new messages. This approach can be inefficient and lead to performance bottlenecks. The Outlook 365 Connector supports <strong>event-driven processing</strong>, meaning emails can trigger MuleSoft flows in real-time, reducing resource consumption.</p><h4>Scalability &amp; Uptime</h4><p>Microsoft 365 is designed for high availability and scalability, ensuring that email processing remains <strong>fast, reliable, and resilient</strong> to failures.</p><h3>5. Compliance &amp; Governance</h3><h4>Adherence to Enterprise Security Standards</h4><p>The Outlook 365 Connector helps businesses stay compliant with industry regulations like <strong>GDPR, HIPAA, and SOC 2</strong>. Microsoft 365 includes built-in compliance tools that help organizations enforce <strong>data retention, encryption, and auditing policies.</strong></p><h4>Advanced Logging &amp; Monitoring</h4><p>With Microsoft 365, businesses get <strong>better logging, auditing, and monitoring capabilities</strong> compared to traditional email servers, making it easier to track and troubleshoot email-related workflows.</p><p>Now Let’s start creating a Mule application with Outlook365</p><h4>Create an Azure Active Directory Application &amp; Set up Permissions</h4><p>Go to Azure portal and search for app registration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pRIumd0ZTrknwNDwmfndtA.png" /></figure><p>Register an application with proper account types</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uSsaMPRXLCdWAU4wiFDEHQ.png" /></figure><p>After registering the new app registration take note of the ClientId and the TenantId.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MbHvHCct1jr5EB-CWxK4tA.png" /></figure><p>Next we need a secret as our “password”. Click on “Certificates &amp; secrets” and create a new client secret. Also take note of the secret right away as it will only show once:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wEV_CgTxFVSohwnjkyTr_g.png" /></figure><p>Finally this app registration needs to have the right API permission. Under “API permissions” select “Add permission” and then select “Microsoft Graph”. Since we’re building a background service with no user present, choose “Application permissions”, search for “Mail.Send” and select it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xwitv42f4RqrU0LaBPnjFg.png" /></figure><p>Important: After adding a permission a admin needs to grant this permission for the entire organization:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SfBDIrSlyn9Brge2uaR00w.png" /></figure><p>Now we are done with every step. Last step is to get the user id, go to <a href="https://developer.microsoft.com/en-us/graph/graph-explorer">https://developer.microsoft.com/en-us/graph/graph-explorer</a> and sign in with the microsoft account. Hit the GET my profile query and fetch the id</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tOqMnmTWSqQL05458ZWinA.png" /></figure><h4>Sample Mule Application to Send Mail with Outlook365 Connector</h4><ol><li>Create a mule project and add outlook365 connector dependency in pom.xml.</li></ol><pre>&lt;dependency&gt;<br>  &lt;groupId&gt;com.mulesoft.connectors&lt;/groupId&gt;<br>  &lt;artifactId&gt;mule4-outlook365-connector&lt;/artifactId&gt;<br>  &lt;version&gt;1.2.4&lt;/version&gt;<br>  &lt;classifier&gt;mule-plugin&lt;/classifier&gt;<br>&lt;/dependency&gt;</pre><p>2. Add an <strong>HTTP Listener</strong> as the trigger.</p><p>3. Drag and drop the <strong>Outlook 365 Connector</strong> and configure the connector with <strong>Client ID, Client Secret, tokenUrl and scope.</strong></p><p>4. Configure the Sed mail with proper values such as Recipient email address, Subject, Body content, Attachments (if needed).</p><p>5. Deploy the application and test the flow by sending a request to the HTTP endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TTOJ1pz7Qdf0rixiT7Rc-A.png" /></figure><p>Please find the sample code below</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br><br>&lt;mule xmlns:outlook365=&quot;http://www.mulesoft.org/schema/mule/outlook365&quot; xmlns:ee=&quot;http://www.mulesoft.org/schema/mule/ee/core&quot;<br> xmlns:http=&quot;http://www.mulesoft.org/schema/mule/http&quot;<br> xmlns=&quot;http://www.mulesoft.org/schema/mule/core&quot; xmlns:doc=&quot;http://www.mulesoft.org/schema/mule/documentation&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation=&quot;http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd<br>http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd<br>http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd<br>http://www.mulesoft.org/schema/mule/outlook365 http://www.mulesoft.org/schema/mule/outlook365/current/mule-outlook365.xsd&quot;&gt;<br> &lt;http:listener-config name=&quot;HTTP_Listener_config&quot; doc:name=&quot;HTTP Listener config&quot; doc:id=&quot;afcf18fc-9244-49f0-98bc-692f0bbe59bd&quot; &gt;<br>  &lt;http:listener-connection host=&quot;0.0.0.0&quot; port=&quot;8081&quot; /&gt;<br> &lt;/http:listener-config&gt;<br> &lt;outlook365:outlook365-config name=&quot;Outlook365_Outlook365_Config&quot; doc:name=&quot;Outlook365 Outlook365 Config&quot; doc:id=&quot;5d8da69a-692e-4679-93bd-0137418396c8&quot; &gt;<br>  &lt;outlook365:oauth-client-credentials-connection &gt;<br>   &lt;outlook365:oauth-client-credentials clientId=&quot;{clientID}&quot; clientSecret=&quot;{clientSecret}&quot; tokenUrl=&quot;{tokenURL}&quot; scopes=&quot;${scope}&quot; /&gt;<br>  &lt;/outlook365:oauth-client-credentials-connection&gt;<br> &lt;/outlook365:outlook365-config&gt;<br> &lt;flow name=&quot;outlook-pocFlow&quot; doc:id=&quot;c0dea72b-777a-4b33-a689-d2edba1c07b2&quot; &gt;<br>  &lt;http:listener doc:name=&quot;Listener&quot; doc:id=&quot;1db23ea7-689f-4243-97d0-06dde8761cf4&quot; config-ref=&quot;HTTP_Listener_config&quot; path=&quot;/sendMail&quot;/&gt;<br>  &lt;ee:transform doc:name=&quot;Transform Message&quot; doc:id=&quot;732ab547-da50-4a08-bf20-426839fc34c4&quot; &gt;<br>   &lt;ee:message &gt;<br>    &lt;ee:set-payload &gt;&lt;![CDATA[%dw 2.0<br>output application/java<br>---<br>&quot;&lt;html&gt;<br>&lt;head&gt;<br>&lt;style&gt;<br>h3 {<br>font-family: Arial, Helvetica, sans-serif;<br>color: #073761;<br>&lt;/style&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>&lt;h3&gt;Hello Muleys!&lt;/h3&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;&quot;]]&gt;&lt;/ee:set-payload&gt;<br>   &lt;/ee:message&gt;<br>  &lt;/ee:transform&gt;<br>  &lt;outlook365:send-mail doc:name=&quot;Send mail&quot; doc:id=&quot;28cd4c04-55d4-4846-9156-4bcbbf01f66b&quot; config-ref=&quot;Outlook365_Outlook365_Config&quot; userId=&quot;#[p(&#39;email.fromAddress&#39;)]&quot;&gt;<br>   &lt;outlook365:message &gt;&lt;![CDATA[#[%dw 2.0<br><br>output application/json<br>---<br>{<br>&quot;message&quot;: {<br><br>&quot;subject&quot;: &quot;Mail From Outlook Connector&quot;,<br>&quot;body&quot;:<br>{<br>&quot;contentType&quot;: &quot;HTML&quot;,<br><br>&quot;content&quot;: payload<br>},<br>&quot;toRecipients&quot;: p(&#39;email.toAddress&#39;) splitBy &quot;;&quot; map {<br><br>&quot;emailAddress&quot;:{<br><br>&quot;address&quot;: $<br>}}<br><br>},<br><br>&quot;saveToSentItems&quot;: &quot;false&quot;<br><br>}]]]&gt;&lt;/outlook365:message&gt;<br>  &lt;/outlook365:send-mail&gt;<br>  &lt;ee:transform doc:name=&quot;Transform Message&quot; doc:id=&quot;5ae1d702-042a-4005-b783-940dc562819d&quot; &gt;<br>   &lt;ee:message &gt;<br>    &lt;ee:set-payload &gt;&lt;![CDATA[%dw 2.0<br>output application/java<br>---<br>{<br> &quot;Status&quot;:&quot;OK&quot;<br>}]]&gt;&lt;/ee:set-payload&gt;<br>   &lt;/ee:message&gt;<br>  &lt;/ee:transform&gt;<br> &lt;/flow&gt;<br>&lt;/mule&gt;</pre><p>After running the flow we received a mail successfully</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uyGuogdGqtfcECKOnhT6Pw.png" /></figure><h4>Note :</h4><p>If you want to send mail with attachments modify the message and add your attachment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T1oHoSGr1nsgyRyPZHGd8g.png" /></figure><p>Please find the code below</p><pre>%dw 2.0<br>import * from dw::core::Binaries<br>output application/json<br>---<br>{<br>&quot;message&quot;: {<br> &quot;subject&quot;: &quot;Mail From Outlook Connector&quot;,<br> &quot;body&quot;:<br>  {<br>  &quot;contentType&quot;: &quot;HTML&quot;,<br>  &quot;content&quot;: payload<br>},<br>&quot;toRecipients&quot;: p(&#39;email.toAddress&#39;) splitBy &quot;;&quot; map {<br> &quot;emailAddress&quot;:{<br>  &quot;address&quot;: $<br> }<br>},<br>&quot;ccRecipients&quot;: p(&#39;email.ccAddress&#39;) splitBy &quot;;&quot; map {<br> &quot;emailAddress&quot;:{<br>  &quot;address&quot;: $<br> }<br>},<br>&quot;attachments&quot;: [<br>        {<br>            &quot;@odata.type&quot;: &quot;#microsoft.graph.fileAttachment&quot;,<br>            &quot;name&quot;: &quot;test.txt&quot;,<br>            &quot;contentType&quot;: &quot;text/plain&quot;,<br>            &quot;contentBytes&quot;: &quot;VGhpcyBpcyBhIHRlc3Qh&quot;<br>        },<br>        {<br>            &quot;@odata.type&quot;: &quot;#microsoft.graph.fileAttachment&quot;,<br>            &quot;name&quot;: &quot;sampleXML.xml&quot;,<br>            &quot;contentType&quot;: &quot;application/xml&quot;,<br>            &quot;contentBytes&quot;: toBase64(write(vars.xmlAttachment,&quot;application/xml&quot;))<br>        }<br>    ]<br>},<br>&quot;saveToSentItems&quot;: &quot;false&quot;<br>}</pre><h3>Conclusion</h3><p>The <strong>Outlook 365 Connector</strong> in MuleSoft provides enhanced security, better email deliverability, and seamless Microsoft integration compared to the <strong>Traditional Email Connector</strong>. If your organization relies on Microsoft services and prioritizes security, adopting the Outlook 365 Connector is a smart move.</p><p>🚀 Ready to improve your email automation in MuleSoft? Start using the <strong>Outlook 365 Connector</strong> today!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0897405a6c2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrating MuleSoft with Azure Storage: Compatibility with Java 17 and CloudHub 2.0]]></title>
            <link>https://medium.com/@sinjonnath25/integrating-mulesoft-with-azure-storage-compatibility-with-java-17-and-cloudhub-2-0-b9c97566d7df?source=rss-02b6bb85ec06------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9c97566d7df</guid>
            <dc:creator><![CDATA[Sinjon Nath]]></dc:creator>
            <pubDate>Sun, 09 Feb 2025 14:24:40 GMT</pubDate>
            <atom:updated>2025-02-09T14:36:08.611Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Cloud storage is an essential component of modern applications, ensuring scalable, secure, and reliable data management. <strong>Microsoft Azure Storage</strong> is widely used for storing <strong>Blob, Queue, Table, and File</strong> data. Integrating <strong>MuleSoft</strong> with <strong>Azure Storage</strong> enables seamless data movement, processing, and retrieval across cloud and on-premise environments.</p><p>The <strong>Anypoint Azure Storage Connector</strong> enables businesses to accelerate cloud storage integrations for modern data storage scenarios across <strong>Azure Cloud</strong>.</p><p>This article explores how to integrate <strong>MuleSoft with Azure Storage</strong>, focusing on the latest updates to the <strong>Azure Storage Connector</strong>, its <strong>compatibility with Java 17 and CloudHub 2.0</strong>, and its full range of supported operations.</p><h3>Overview of Azure Blob Storage</h3><p>Azure Blob Storage is a highly scalable <strong>object storage solution</strong> designed for handling large amounts of unstructured data, such as <strong>images, videos, backups, and logs</strong>. It provides:</p><ul><li><strong>Scalability</strong>: Supports large-scale data storage for enterprise applications.</li><li><strong>Durability</strong>: Ensures high availability by replicating data across different Azure regions.</li><li><strong>Security</strong>: Supports encryption, <strong>role-based access control (RBAC)</strong>, and <strong>private endpoint configurations</strong>.</li><li><strong>Access Tiers</strong>: Offers <strong>Hot, Cool, and Archive tiers</strong> to optimize cost and performance.</li></ul><h3>Common Use Cases for Blob Storage</h3><p>Automate business operations by integrating Azure Storage with other business applications for cloud storage:</p><ul><li>Uploading and retrieving images or documents in the cloud.</li><li>Storing files for distributed access.</li><li>Managing cloud-based data backups, disaster recovery, and archiving.</li><li>Creating a queue-based backlog for asynchronous processing.</li><li>Enabling message passing between cloud services and applications.</li><li>Storing large structured datasets without the need for complex relational database features.</li><li>Enhancing data retrieval speed with optimized indexing and querying techniques.</li></ul><h3>Integrating MuleSoft with Azure Storage</h3><p>MuleSoft provides an <strong>Anypoint Azure Storage Connector</strong>, simplifying the interaction between <strong>Mule applications</strong> and <strong>Azure Storage</strong>. The connector supports operations for <strong>Blob, Queue, Table, and File storage</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*hi6sPi-DzELeAFcIBCwQWA.png" /></figure><h3>Prerequisites</h3><p>Before integrating MuleSoft with Azure Storage, ensure that:</p><ol><li>You have an active <strong>Azure subscription</strong>.</li><li>You have an <strong>Azure Storage account</strong> with <strong>Blob Storage enabled</strong>.</li><li>You are using <strong>Mule 4 runtime</strong> (preferably <strong>4.1.5 or later</strong> for <strong>Java 17 compatibility</strong>).</li><li>You have imported the <strong>Azure Storage Connector</strong> into <strong>Anypoint Studio</strong>.</li></ol><h3>Supported Operations in Mule Azure Storage Connector</h3><h4>Blob Storage Operations</h4><ul><li><strong>Download Blob</strong> — Retrieve a blob from a specified container.</li><li><strong>List All Containers</strong> — Retrieve a list of all blob containers in the storage account.</li><li><strong>Create Container</strong> — Create a new blob container.</li><li><strong>List Blobs In Container</strong> — Retrieve a list of blobs within a specified container.</li><li><strong>Upload Blob</strong> — Upload a blob to a specified container.</li><li><strong>Upload Blob From Path</strong> — Upload a blob from a local file path to a specified container.</li><li><strong>Delete Blob</strong> — Remove a blob from a specified container.</li><li><strong>Delete Container</strong> — Remove a container from the storage account.</li></ul><h4>Queue Storage Operations</h4><ul><li><strong>Create Queue</strong> — Create a new queue in the storage account.</li><li><strong>Add Message To Queue</strong> — Add a message to a specified queue.</li><li><strong>Peek Message From Queue</strong> — Peek at the message at the front of a queue without removing it.</li><li><strong>Update Message In Queue</strong> — Update an existing message in a queue.</li><li><strong>Delete Message From Queue</strong> — Remove a message from a queue.</li><li><strong>Delete Queue</strong> — Remove a queue from the storage account.</li></ul><h4>Table Storage Operations</h4><ul><li><strong>Create Table</strong> — Create a new table in the storage account.</li><li><strong>Insert Entity</strong> — Add a new entity to a specified table.</li><li><strong>Update Entity</strong> — Update an existing entity in a table.</li><li><strong>Delete Entity</strong> — Remove an entity from a table.</li><li><strong>Query Entities</strong> — Retrieve entities from a table based on a query.</li><li><strong>Delete Table</strong> — Remove a table from the storage account.</li></ul><h4>File Storage Operations</h4><ul><li><strong>Create File Share</strong> — Create a new file share in the storage account.</li><li><strong>Upload File</strong> — Upload a file to a specified file share.</li><li><strong>Download File</strong> — Download a file from a specified file share.</li><li><strong>Delete File</strong> — Remove a file from a file share.</li><li><strong>Delete File Share</strong> — Remove a file share from the storage account.</li></ul><h3>What’s New in the Azure Storage Connector?</h3><p>The latest version of the <strong>Azure Storage Connector (v3.0.0, released in September 2024)</strong> introduces several enhancements:</p><ul><li><strong>Java 17 Compatibility</strong>: Now supports the latest Java version for improved performance and security.</li><li><strong>CloudHub 2.0 Compatibility</strong>: Fully compatible with CloudHub 2.0 for seamless deployment.</li><li><strong>Enhanced Blob Search</strong>: Provides detailed error handling if a blob is not found.</li><li><strong>Nested Operations</strong>: Allows searching within specific blob paths.</li><li><strong>Improved Date Handling</strong>: Moves from java.util.Date to java.time.LocalDate for better compatibility.</li><li><strong>Better Error Handling</strong>: Introduces PatternSyntaxException for incorrect regex patterns in search queries.</li><li><strong>Content type parameter:</strong> Added new input parameter to specify the content type of the file to be uploaded in blob storage</li></ul><p>For a complete list of changes, refer to the <a href="https://whishworks.github.io/mule-azure-storage-connector/release-notes.html">Azure Storage Connector Release Notes</a>.</p><h3>Let’s make a sample Mule application to Upload files to Azure blob</h3><h4><strong>Step 1 : Setup Azure Storage Account</strong></h4><p>Login to Azure portal &amp; create a storage account</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1GezMyFJpDS0N2N-k6qC2g.png" /></figure><p>Fill all the details and create the storage account, once the creation success you’ll see the below message</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sCUmTBo7MHZf32KuRRqMdA.png" /></figure><p>Next steps is to create a container in the storage account</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O-GBvXeLxLVOe7srg9zF4A.png" /></figure><p>&amp; finally we need to get access key to access the account. Now we are ready to configure it on our MuleSoft application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*imV09h0yLDifInuIslVKsg.png" /></figure><h4>Step 2: Start creating MuleSoft Application to upload a video file in Azure Blob Storage</h4><ul><li>Create a sample mule 4 application in studio and add the Azure Storage connector( Search no exchange if it’s not available in studio)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3sS1MoZ-N9Gg_uLtS0yK0A.png" /></figure><pre>&lt;dependency&gt;<br>  &lt;groupId&gt;org.mule.modules&lt;/groupId&gt;<br>  &lt;artifactId&gt;azure-storage-connector&lt;/artifactId&gt;<br>  &lt;version&gt;3.0.0&lt;/version&gt;<br>  &lt;classifier&gt;mule-plugin&lt;/classifier&gt;<br>&lt;/dependency&gt;</pre><ul><li>Configure the Azure storage connector config with the credentials we have noted previously</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ik2YUrIF-7pcQszmDWvog.png" /></figure><ul><li>Create the flow to upload a file in Azure storage, here I have create a flow to upload a video file.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DBO8cT8U-FmBCWd38oiQVQ.png" /></figure><ul><li>Now Let’s the application, I sending a video file from postman to test the application.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*awvAAoV3AYAviH78_cXKgg.png" /></figure><ul><li>We got success response &amp; file got uploaded successfully in Azure.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*52TP-zakrlzuQu4Rb11LOQ.png" /></figure><ul><li>Find the sample code below</li></ul><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br><br>&lt;mule xmlns:ee=&quot;http://www.mulesoft.org/schema/mule/ee/core&quot; xmlns:azure-storage=&quot;http://www.mulesoft.org/schema/mule/azure-storage&quot;<br> xmlns:http=&quot;http://www.mulesoft.org/schema/mule/http&quot;<br> xmlns=&quot;http://www.mulesoft.org/schema/mule/core&quot; xmlns:doc=&quot;http://www.mulesoft.org/schema/mule/documentation&quot; xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xsi:schemaLocation=&quot;http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd<br>http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd<br>http://www.mulesoft.org/schema/mule/azure-storage http://www.mulesoft.org/schema/mule/azure-storage/current/mule-azure-storage.xsd<br>http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd&quot;&gt;<br> &lt;http:listener-config name=&quot;HTTP_Listener_config&quot; doc:name=&quot;HTTP Listener config&quot; doc:id=&quot;8773fb47-302d-42aa-a1de-4c3ac0d54c4d&quot; &gt;<br>  &lt;http:listener-connection host=&quot;0.0.0.0&quot; port=&quot;8085&quot; /&gt;<br> &lt;/http:listener-config&gt;<br> &lt;azure-storage:config name=&quot;Azure_Storage_Config&quot; doc:name=&quot;Azure Storage Config&quot; doc:id=&quot;2216390b-ea38-4e54-ac22-e04c877ec16e&quot; &gt;<br>  &lt;azure-storage:access-key-azure-connection accountName=&quot;{azure.accountName}&quot; accountKey=&quot;{azure.accountKey}&quot; /&gt;<br> &lt;/azure-storage:config&gt;<br> &lt;configuration-properties doc:name=&quot;Configuration properties&quot; doc:id=&quot;beaf1de5-e483-4e7a-8fa8-fe92ee5c96fd&quot; file=&quot;app.properties&quot; /&gt;<br> &lt;flow name=&quot;uploadBlobFlow&quot; doc:id=&quot;b78b365f-aa2a-4711-8c25-3e9b92bd94c3&quot; &gt;<br>  &lt;http:listener doc:name=&quot;Listener&quot; doc:id=&quot;84337cdd-b9a2-4e8c-ba6b-59e0f08bdeb3&quot; config-ref=&quot;HTTP_Listener_config&quot; path=&quot;/demo&quot;/&gt;<br>  &lt;ee:transform doc:name=&quot;Transform Payload&quot; doc:id=&quot;b42b9484-e7e3-465c-bd0c-694e88f198c5&quot; &gt;<br>   &lt;ee:message &gt;<br>    &lt;ee:set-payload &gt;&lt;![CDATA[%dw 2.0<br>output application/dw<br>---<br>payload]]&gt;&lt;/ee:set-payload&gt;<br>   &lt;/ee:message&gt;<br>  &lt;/ee:transform&gt;<br>  &lt;ee:transform doc:name=&quot;Extract Video Content&quot; doc:id=&quot;716604a8-ca6b-4f75-ae5a-91fa9e4dad62&quot; &gt;<br>   &lt;ee:message &gt;<br>    &lt;ee:set-payload &gt;&lt;![CDATA[%dw 2.0<br>output application/java<br>---<br>payload.parts.video.content]]&gt;&lt;/ee:set-payload&gt;<br>   &lt;/ee:message&gt;<br>  &lt;/ee:transform&gt;<br>  &lt;logger level=&quot;INFO&quot; doc:name=&quot;Uploading to Azure&quot; doc:id=&quot;d20ebad6-b428-4028-ac22-624336b91c01&quot; message=&quot;Uploading to Azure&quot; /&gt;<br>  &lt;azure-storage:upload-blob doc:name=&quot;Upload blob&quot; doc:id=&quot;6f1114c0-dc26-4852-8897-ef182b6a751e&quot; config-ref=&quot;Azure_Storage_Config&quot; contentType=&quot;video/mp4&quot;&gt;<br>   &lt;azure-storage:storblob container=&quot;mymulecontainer&quot; fileName=&quot;firstvideo.mp4&quot; fileStream=&quot;#[payload]&quot; /&gt;<br>  &lt;/azure-storage:upload-blob&gt;<br>  &lt;logger level=&quot;INFO&quot; doc:name=&quot;Uploaded to Azure&quot; doc:id=&quot;84433a28-2e8a-49dc-9c42-5d9fd06dbb0d&quot; message=&quot;Uploaded to Azure&quot; /&gt;<br>  &lt;ee:transform doc:name=&quot;Transform Message&quot; doc:id=&quot;f1cad9a6-9d56-4233-9316-d859c4f0d9d2&quot; &gt;<br>   &lt;ee:message &gt;<br>    &lt;ee:set-payload &gt;&lt;![CDATA[%dw 2.0<br>output application/json<br>---<br>{<br> &quot;Status&quot;: &quot;OK&quot;,<br> &quot;Message&quot;: &quot;File Uploaded to Azure Storage&quot;<br>}]]&gt;&lt;/ee:set-payload&gt;<br>   &lt;/ee:message&gt;<br>  &lt;/ee:transform&gt;<br> &lt;/flow&gt;<br>&lt;/mule&gt;</pre><ul><li>Similar to this you can upload other files such as txt, json, xml, pdf, images etc. in Azure Storage.</li></ul><h3>Best Practices for Using Azure Storage with MuleSoft</h3><ul><li><strong>Use Azure AD Authentication</strong> instead of access keys for improved security.</li><li><strong>Optimize Cost</strong> by leveraging the appropriate <strong>storage tier</strong> (Hot, Cool, or Archive) for your data.</li><li><strong>Implement Retry Logic</strong> in <strong>MuleSoft flows</strong> to handle transient failures.</li><li><strong>Monitor and Log Storage Operations</strong> to ensure visibility and quick debugging.</li></ul><h3>Conclusion</h3><p>Integrating <strong>MuleSoft with Azure Storage</strong> enables efficient <strong>data storage and management</strong> in cloud-native applications. With the latest enhancements in the <strong>Azure Storage Connector</strong>, developers can take advantage of <strong>Java 17 and CloudHub 2.0 compatibility</strong> and improved <strong>blob operations</strong> for better performance and reliability.</p><p>By following <strong>best practices</strong> and leveraging the full capabilities of <strong>Azure Blob Storage</strong>, organizations can enhance their <strong>cloud data workflows</strong> and achieve <strong>scalable solutions</strong>.</p><p>For more details, check out the <a href="https://www.mulesoft.com/exchange/org.mule.modules/azure-storage-connector/">official Azure Storage Connector documentation</a>.</p><p>Let me know if you need modifications or additional sections!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9c97566d7df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>