<?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 Vinay Rana on Medium]]></title>
        <description><![CDATA[Stories by Vinay Rana on Medium]]></description>
        <link>https://medium.com/@maharanavinay?source=rss-c6071c10f18e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*m9_AOgBsg10s528_q5poSQ.jpeg</url>
            <title>Stories by Vinay Rana on Medium</title>
            <link>https://medium.com/@maharanavinay?source=rss-c6071c10f18e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:59:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@maharanavinay/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[From APIs to AI Agents: Building a Secure MCP Platform with MuleSoft and Omni Gateway]]></title>
            <link>https://medium.com/another-integration-blog/from-apis-to-ai-agents-building-a-secure-mcp-platform-with-mulesoft-and-omni-gateway-66e38e74cda3?source=rss-c6071c10f18e------2</link>
            <guid isPermaLink="false">https://medium.com/p/66e38e74cda3</guid>
            <dc:creator><![CDATA[Vinay Rana]]></dc:creator>
            <pubDate>Sat, 22 Aug 2026 15:15:20 GMT</pubDate>
            <atom:updated>2026-08-22T15:15:20.253Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This article discusses how we built a secure MCP platform using MuleSoft, Omni Gateway, and MCP Bridge to expose existing APIs as AI-accessible tools while maintaining enterprise-grade security and governance.</em></p><h3>Introduction</h3><p>The rise of Agentic AI platforms such as ChatGPT, Claude, Microsoft Copilot, and Gemini is fundamentally changing how users interact with enterprise systems.</p><p>Traditionally, consuming enterprise services required custom integrations, SDKs, REST clients, and application-specific logic. With the introduction of the Model Context Protocol (MCP), AI agents can now discover and invoke business capabilities through a standardized interface.</p><p>However, enterprises face a challenge:</p><ul><li>Existing APIs were built for applications, not AI agents.</li><li>Security, governance, and observability become more critical when LLMs start invoking enterprise services.</li><li>Organizations need a way to expose APIs as MCP tools without modifying production APIs.</li></ul><h3>What is MCP?</h3><p>Model Context Protocol (MCP) is becoming a standard way for AI agents to interact with tools, APIs, databases, and enterprise services. It acts as a universal connector between AI systems and external capabilities.</p><p>Instead of building one-off integrations:</p><blockquote>ChatGPT -&gt; API A</blockquote><blockquote>ChatGPT -&gt; API B</blockquote><blockquote>Claude -&gt; API C</blockquote><p>MCP standardizes the communication layer.</p><blockquote>AI Agent</blockquote><blockquote>↓</blockquote><blockquote>MCP</blockquote><blockquote>↓</blockquote><blockquote>Enterprise Services</blockquote><h3>The Business Challenge</h3><p>In our environment, we already had multiple MuleSoft APIs serving business capabilities.</p><p>The challenge was:</p><ul><li>Enable AI agents to access these capabilities.</li><li>Avoid changing existing production APIs.</li><li>Maintain governance, security, and monitoring.</li><li>Provide a reusable architecture for future APIs.</li></ul><p>The goal was to create a foundation that would allow future APIs to become AI-ready with minimal effort.</p><h3>High-Level Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/817/1*QHoUYutttRmSs-mkxceXTw.png" /></figure><p>This architecture aligns with how MCP Bridge exposes existing APIs as MCP tools without modifying the API implementation.</p><h3>Why MCP Bridge?</h3><p>Traditionally, implementing an MCP server required:</p><ul><li>MCP connector development</li><li>Tool definitions</li><li>Custom schemas</li><li>New applications</li><li>Redeployments</li></ul><p>MCP Bridge changes this by transforming existing APIs into MCP tools at the gateway layer.</p><p>Benefits:</p><p>✅ No code changes</p><p>✅ No application redeployment</p><p>✅ Uses existing API contracts</p><p>✅ Faster AI adoption</p><p>✅ Centralized governance</p><h3>Security Architecture</h3><p>One of the key design goals was ensuring AI access does not bypass enterprise security controls.</p><h4>Security Controls Implemented</h4><h4>Omni Gateway</h4><p>Provides centralized policy enforcement, governance, visibility, and monitoring for MCP and API traffic.</p><h4>Client ID Enforcement</h4><p>Ensures only authorized consumers can access the MCP endpoint.</p><h4>JWT Validation</h4><p>Validates identity and authorization claims using enterprise identity providers.</p><h4>Rate Limiting</h4><p>Protects backend systems from excessive AI-generated traffic.</p><h4>IP Allowlisting</h4><p>Restricts MCP access to approved consumer networks.</p><h4>MCP PII Detector</h4><p>Prevents accidental exposure of sensitive data such as:</p><ul><li>Customer details</li><li>Email addresses</li><li>Personal identifiers</li></ul><h3>MCP Tool Design</h3><p>We exposed business functionality as meaningful AI tools.</p><p>This significantly improves tool discoverability and LLM comprehension.</p><h3>Lessons Learned</h3><h4>1. Not Every API Should Become an MCP Tool</h4><p>Expose only business capabilities that are meaningful to AI agents.</p><p>Avoid exposing:</p><blockquote>Utility APIs</blockquote><blockquote>Low-level technical APIs</blockquote><blockquote>Internal maintenance endpoints</blockquote><h4>2. Security Must Come First</h4><p>AI agents interact differently than traditional applications.</p><p>Authentication, authorization, and PII protection should be part of the initial design rather than added later.</p><h4>3. Tool Naming Matters</h4><p>LLMs perform better with business-oriented names.</p><h4>4. Governance is Critical</h4><p>Enterprise adoption requires:</p><ul><li>Auditability</li><li>Monitoring</li><li>Access controls</li><li>Centralized policy management</li></ul><h3>Future Roadmap</h3><p>Potential future enhancements:</p><ul><li>Dynamic tool onboarding</li><li>Multi-domain MCP Servers</li><li>AI governance dashboards</li><li>MCP access analytics</li><li>Tool-level authorization</li><li>Agent-specific tool catalogs</li></ul><h3>Conclusion</h3><p><em>MCP is rapidly becoming the standard mechanism for connecting AI agents to enterprise capabilities. By leveraging MuleSoft MCP Bridge and Omni Gateway, organizations can transform existing APIs into AI-ready tools without changing application implementations.</em></p><p><em>This approach accelerates Agentic AI adoption while maintaining security, governance, observability, and reuse across the enterprise.</em></p><p><em>The result is a scalable foundation that allows OpenAI, Claude, Copilot, and future AI platforms to interact with enterprise services through a single governed MCP layer.</em></p><h3>Enjoyed the read? Let’s stay connected!</h3><p>👏 Clap (up to 50 times!) to show support and help others find this article.<br>💬 Comment with your thoughts or questions — I’d love to hear from you.<br>📤 Share this with someone who might find it helpful.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66e38e74cda3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/another-integration-blog/from-apis-to-ai-agents-building-a-secure-mcp-platform-with-mulesoft-and-omni-gateway-66e38e74cda3">From APIs to AI Agents: Building a Secure MCP Platform with MuleSoft and Omni Gateway</a> was originally published in <a href="https://medium.com/another-integration-blog">Another Integration Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS PrivateLink with CloudHub 2.0 Building Secure and Isolated Connectivity for Modern Integrations]]></title>
            <link>https://medium.com/another-integration-blog/aws-privatelink-with-cloudhub-2-0-building-secure-and-isolated-connectivity-for-modern-integrations-4f305efcd001?source=rss-c6071c10f18e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f305efcd001</guid>
            <dc:creator><![CDATA[Vinay Rana]]></dc:creator>
            <pubDate>Sat, 22 Aug 2026 15:15:10 GMT</pubDate>
            <atom:updated>2026-08-22T15:15:10.201Z</atom:updated>
            <content:encoded><![CDATA[<p><em>As enterprises continue to modernize their integration landscapes, security and network isolation have become critical architecture considerations. Organizations running APIs and integrations on MuleSoft CloudHub 2.0 frequently need secure access to applications, databases, and services hosted within AWS without exposing traffic to the public internet.</em></p><p><em>AWS PrivateLink addresses this challenge by providing a secure, service-level connectivity model between CloudHub 2.0 Private Spaces and AWS-hosted resources. This approach offers greater isolation, tighter security controls, and reduced operational risk compared to traditional network connectivity options.</em></p><p><em>In this article, we’ll explore how AWS PrivateLink works with CloudHub 2.0, its benefits, common use cases, implementation steps, and key considerations for enterprise deployments.</em></p><h3>Understanding Connectivity Options in CloudHub 2.0</h3><p>CloudHub 2.0 supports multiple private connectivity mechanisms:</p><h4>Virtual Private Network (VPN)</h4><p>VPN establishes network-level connectivity between CloudHub and external networks, operating at the OSI Layer 3 (Network Layer).</p><h4>AWS Transit Gateway (TGW)</h4><p>Transit Gateway provides scalable routing between multiple networks and AWS environments. Like VPN, it operates at OSI Layer 3.</p><h4>AWS PrivateLink</h4><p>PrivateLink operates at OSI Layer 4 (Transport Layer) and takes a fundamentally different approach. Instead of connecting entire networks, it enables access to specific services through private endpoints.</p><p>This service-oriented model significantly improves security because networks remain isolated while only explicitly approved services become accessible.</p><h4>Why Choose AWS PrivateLink?</h4><p>Unlike VPNs or Transit Gateways, PrivateLink does not create network-to-network connectivity.</p><p>The service remains accessible privately, but the CloudHub 2.0 Private Space and the AWS VPC remain logically isolated from each other.</p><p>This design delivers several enterprise-grade advantages.</p><h4>1. Enhanced Security</h4><p>Traffic never traverses the public internet. Communication occurs entirely through AWS private networking infrastructure, reducing exposure to external threats.</p><h4>2. Better Network Isolation</h4><p>PrivateLink follows the principle of least privilege. Applications can only access services explicitly published through endpoint services.</p><h4>3. Reduced Blast Radius</h4><p>Since connectivity is limited to individual services rather than entire networks, security incidents or misconfigurations have a much smaller impact.</p><h4>4. Granular Service Control</h4><p>Organizations maintain precise control over which services are exposed to CloudHub Private Spaces, minimizing accidental exposure of sensitive resources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y_2AuIqENCLxyXP5lQb6iw.png" /></figure><h3>Common Use Cases</h3><p>AWS PrivateLink is particularly valuable for enterprises operating in highly regulated environments or implementing zero-trust networking principles.</p><p>Typical scenarios include:</p><h4>Accessing Internal AWS Services</h4><p>Organizations can securely connect CloudHub applications to services hosted in their own AWS environments, such as:</p><ul><li>Internal APIs</li><li>Databases</li><li>Microservices</li><li>Backend applications</li></ul><h4>Accessing AWS Managed Services</h4><p>CloudHub applications can privately connect to AWS services such as:</p><ul><li>Amazon S3</li><li>Amazon Kinesis</li><li>Amazon OpenSearch</li><li>Amazon Secrets Manager</li></ul><h4>Connecting to Third-Party Services</h4><p>Many SaaS providers host PrivateLink-enabled services within AWS. These services can be consumed securely without exposing traffic over public endpoints.</p><h3>Reference Architecture</h3><p>A typical PrivateLink architecture consists of the following components:</p><ol><li>CloudHub 2.0 Private Space</li><li>AWS VPC hosting the target service</li><li>Network Load Balancer (NLB) or Application Load Balancer (ALB)</li><li>AWS VPC Endpoint Service</li><li>CloudHub-created VPC Endpoint (VPCE)</li></ol><p>The workflow is straightforward:</p><ul><li>The service is deployed behind an AWS load balancer.</li><li>AWS exposes the service through a VPC Endpoint Service.</li><li>CloudHub creates a VPC Endpoint targeting that service.</li><li>AWS approves the endpoint connection.</li><li>Mule applications access the service using private DNS endpoints.</li></ul><p>The result is secure, private communication without network peering or internet exposure.</p><h3>Prerequisites</h3><p>Before configuring AWS PrivateLink, ensure the following requirements are met:</p><ul><li>A CloudHub 2.0 Private Space is provisioned.</li><li>API access credentials (Bearer Token) are available.</li><li>The user creating the configuration has Private Space administrative permissions.</li><li>The target service is deployed within AWS.</li><li>Appropriate availability zones are identified.</li></ul><h3>Implementation Overview</h3><h4>Step 1: Retrieve Private Space Availability Zones</h4><p>Before creating a PrivateLink endpoint, identify the AWS Availability Zones associated with the CloudHub Private Space.</p><h4>cURL</h4><blockquote>curl — location — request GET \</blockquote><blockquote>‘https://anypoint.mulesoft.com/runtimefabric/api/organizations/{{orgId}}/privatespaces/{{spaceId}}/azs&#39; \</blockquote><blockquote>— header ‘Authorization: Bearer {{access_token}}’</blockquote><h4>Postman</h4><p><strong>Method:</strong> GET</p><blockquote><a href="https://anypoint.mulesoft.com/runtimefabric/api/organizations/%7B%7BorgId%7D%7D/privatespaces/%7B%7BspaceId%7D%7D/azs">https://anypoint.mulesoft.com/runtimefabric/api/organizations/{{orgId}}/privatespaces/{{spaceId}}/azs</a></blockquote><p><strong>Headers</strong></p><blockquote>Authorization: Bearer {{access_token}}</blockquote><h3>Sample Response</h3><p>JSON</p><blockquote>[</blockquote><blockquote>“use1-az1”,</blockquote><blockquote>“use1-az2”,</blockquote><blockquote>“use1-az5”</blockquote><blockquote>]</blockquote><p>These Availability Zones must align with the endpoint service deployed within AWS.</p><h3>Step 2: Retrieve CloudHub AWS Account ID</h3><p>CloudHub Private Spaces operate within MuleSoft-managed AWS accounts. This account ID must be added as an allowed principal in AWS.</p><h4>cURL</h4><blockquote>curl — location — request GET \</blockquote><blockquote>‘https://anypoint.mulesoft.com/runtimefabric/api/organizations/{{orgId}}/privatespaces/{{spaceId}}/accounts&#39; \</blockquote><blockquote>— header ‘Authorization: Bearer {{access_token}}’</blockquote><h4>Sample Response</h4><p>JSON</p><blockquote>“328752079326”</blockquote><h3>Step 3: Configure AWS Endpoint Service</h3><p>Within AWS:</p><ol><li>Deploy application behind a Network Load Balancer.</li><li>Create a VPC Endpoint Service.</li><li>Enable:</li></ol><blockquote>Acceptance Required = Yes</blockquote><ol><li>Add the CloudHub AWS Account as an allowed principal:</li></ol><blockquote>arn:aws:iam::&lt;account-id&gt;:root</blockquote><h3>Step 4: Create the PrivateLink Endpoint</h3><p>Once the AWS endpoint service is available, create a VPC endpoint within CloudHub 2.0.</p><h4>cURL</h4><blockquote>curl — location — request POST \</blockquote><blockquote>‘https://anypoint.mulesoft.com/runtimefabric/api/organizations/{{orgId}}/privatespaces/{{spaceId}}/vpces&#39; \</blockquote><blockquote>— header ‘Authorization: Bearer {{access_token}}’ \</blockquote><blockquote>— header ‘Content-Type: application/json’ \</blockquote><blockquote>— data ‘{</blockquote><blockquote>“name”: “Customer API Service”,</blockquote><blockquote>“serviceName”: “com.amazonaws.vpce.us-east-1.vpce-svc-0abc123456789”,</blockquote><blockquote>“serviceRegion”: “us-east-1”,</blockquote><blockquote>“serviceOwner”: “123456789012”,</blockquote><blockquote>“azIds”: [</blockquote><blockquote>“use1-az1”,</blockquote><blockquote>“use1-az2”</blockquote><blockquote>]</blockquote><blockquote>}’</blockquote><h4>Postman Request Body</h4><p>JSON</p><blockquote>{</blockquote><blockquote>“name”: “Customer API Service”,</blockquote><blockquote>“serviceName”: “com.amazonaws.vpce.us-east-1.vpce-svc-0abc123456789”,</blockquote><blockquote>“serviceRegion”: “us-east-1”,</blockquote><blockquote>“serviceOwner”: “123456789012”,</blockquote><blockquote>“azIds”: [</blockquote><blockquote>“use1-az1”,</blockquote><blockquote>“use1-az2”</blockquote><blockquote>]</blockquote><blockquote>}</blockquote><h4>Successful Response</h4><p>JSON</p><blockquote>{</blockquote><blockquote>“vpceId”: “fc5c9c55-d943–4383–88ac-cc2b51446d54”</blockquote><blockquote>}</blockquote><p>Save the returned vpceId for subsequent operations.</p><h3>Step 5: Monitor Endpoint Provisioning</h3><p>After creating the endpoint, monitor its lifecycle status.</p><h4>cURL</h4><blockquote>curl — location — request GET \</blockquote><blockquote>‘https://anypoint.mulesoft.com/runtimefabric/api/organizations/{{orgId}}/privatespaces/{{spaceId}}/vpces/{{vpceId}}&#39; \</blockquote><blockquote>— header ‘Authorization: Bearer {{access_token}}’</blockquote><h4>Example Response:</h4><p>JSON</p><blockquote>{</blockquote><blockquote>“status”: “pendingAcceptance”,</blockquote><blockquote>“awsId”: “vpce-0d971d98cb910b3b1”</blockquote><blockquote>}</blockquote><h4>Status Definitions</h4><p>StatusMeaningPendingAcceptanceWaiting for AWS approvalValidProvisioning in progressAvailableReady for trafficInvalidCreation failed</p><h3>Step 6: Accept Endpoint Connection in AWS</h3><p>The service owner must approve the connection request.</p><p>Navigate to:</p><blockquote>AWS Console</blockquote><blockquote>→ VPC</blockquote><blockquote>→ Endpoint Services</blockquote><blockquote>→ Endpoint Connections</blockquote><p>Verify:</p><ul><li>Endpoint ID</li><li>AWS Account Owner</li><li>Service Name</li></ul><p>Approve the request.</p><p>Once approved, the endpoint status changes to:</p><blockquote>Available</blockquote><h3>Step 7: Retrieve DNS Entries</h3><p>Applications running in CloudHub 2.0 access the target service using endpoint DNS records.</p><h4>cURL</h4><blockquote>curl — location — request GET \</blockquote><blockquote>‘https://anypoint.mulesoft.com/runtimefabric/api/organizations/{{orgId}}/privatespaces/{{spaceId}}/vpces/{{vpceId}}&#39; \</blockquote><blockquote>— header ‘Authorization: Bearer {{access_token}}’</blockquote><h4>Example Response</h4><p>JSON</p><blockquote>{</blockquote><blockquote>“dnsEntries”: [</blockquote><blockquote>“vpce-0d971d98cb910b3b1.amazonaws.com”,</blockquote><blockquote>“vpce-0d971d98cb910b3b1-us-east-1d.amazonaws.com”</blockquote><blockquote>]</blockquote><blockquote>}</blockquote><p>These DNS names can be directly referenced within Mule applications, eliminating the need for public endpoints.</p><h3>Step 8: Update Existing Endpoint</h3><p>When migrating services or changing availability zones, endpoint details can be updated.</p><h4>cURL</h4><blockquote>curl — location — request PATCH \</blockquote><blockquote>‘https://anypoint.mulesoft.com/runtimefabric/api/organizations/{{orgId}}/privatespaces/{{spaceId}}/vpces/{{vpceId}}&#39; \</blockquote><blockquote>— header ‘Authorization: Bearer {{access_token}}’ \</blockquote><blockquote>— header ‘Content-Type: application/json’ \</blockquote><blockquote>— data ‘{</blockquote><blockquote>“name”: “Customer API Service Updated”,</blockquote><blockquote>“serviceName”: “com.amazonaws.vpce.us-east-1.vpce-svc-0abc123456789”,</blockquote><blockquote>“serviceRegion”: “us-east-1”,</blockquote><blockquote>“serviceOwner”: “123456789012”,</blockquote><blockquote>“azIds”: [</blockquote><blockquote>“use1-az1”,</blockquote><blockquote>“use1-az2”</blockquote><blockquote>]</blockquote><blockquote>}’</blockquote><h3>Step 9: Delete Endpoint</h3><p>When the connection is no longer required, remove the VPC endpoint.</p><h4>cURL</h4><blockquote>curl — location — request DELETE \</blockquote><blockquote>‘https://anypoint.mulesoft.com/runtimefabric/api/organizations/{{orgId}}/privatespaces/{{spaceId}}/vpces/{{vpceId}}&#39; \</blockquote><blockquote>— header ‘Authorization: Bearer {{access_token}}’</blockquote><h3>Important Limitations</h3><p>While AWS PrivateLink is an excellent connectivity option, several limitations should be considered.</p><h3>Amazon MSK Considerations</h3><p>Amazon Managed Streaming for Apache Kafka (MSK) introduces additional complexity because each cluster contains multiple brokers.</p><p>Since PrivateLink endpoint services are typically fronted by load balancers that expose a single service endpoint, additional AWS networking design may be necessary.</p><p>Organizations planning Kafka integrations should carefully evaluate architecture options, including:</p><ul><li>Transit Gateway</li><li>Anypoint VPN</li><li>Specialized MSK networking patterns</li></ul><h3>Platform Restrictions</h3><p>PrivateLink currently does not support:</p><ul><li>CloudHub VPC environments</li><li>CloudHub VPC upgraded Private Spaces</li><li>Resource VPC Endpoints</li></ul><p>Only Interface VPC Endpoints are supported.</p><h3>Service Limits</h3><p>Current connectivity limits per Private Space include:</p><p>ResourceLimitVPN Connections10Transit Gateways5VPC Endpoints20</p><p>Additionally, outbound traffic is limited to approximately <strong>56.48 GB per hour per root organization</strong>.</p><h3>Best Practices for Enterprise Deployments</h3><p>Based on real-world integration platforms, the following recommendations help ensure a robust deployment:</p><ul><li>Deploy services across at least two Availability Zones.</li><li>Always enable endpoint connection approval.</li><li>Use Network Load Balancers whenever possible.</li><li>Enable private DNS for simplified service discovery.</li><li>Restrict security groups to CloudHub Private Space CIDR ranges.</li><li>Maintain a centralized inventory of VPC endpoints for governance and audit purposes.</li><li>Regularly review endpoint utilization and connectivity limits.</li></ul><h3>Final Thoughts</h3><p>AWS PrivateLink provides one of the most secure and controlled connectivity models available for CloudHub 2.0 integrations. By focusing on service-level access instead of network-level connectivity, organizations gain stronger isolation, reduced attack surfaces, and greater governance control.</p><p>For enterprises adopting API-led connectivity and zero-trust networking principles, PrivateLink is often the preferred option when full network connectivity is unnecessary. It delivers the balance of security, simplicity, and operational control required for modern cloud-native integration architectures.</p><p>As organizations continue to migrate sensitive workloads into AWS and CloudHub 2.0, PrivateLink remains a powerful tool for building secure, resilient, and compliant integration platforms.</p><h3>Enjoyed the read? Let’s stay connected!</h3><p>👏 Clap (up to 50 times!) to show support and help others find this article.<br>💬 Comment with your thoughts or questions — I’d love to hear from you.<br>📤 Share this with someone who might find it helpful.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f305efcd001" width="1" height="1" alt=""><hr><p><a href="https://medium.com/another-integration-blog/aws-privatelink-with-cloudhub-2-0-building-secure-and-isolated-connectivity-for-modern-integrations-4f305efcd001">AWS PrivateLink with CloudHub 2.0 Building Secure and Isolated Connectivity for Modern Integrations</a> was originally published in <a href="https://medium.com/another-integration-blog">Another Integration Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitLab to GitHub Migration: A Practical Guide to Code and Governance]]></title>
            <link>https://medium.com/@maharanavinay/gitlab-to-github-migration-a-practical-guide-to-code-and-governance-4298f4f2715a?source=rss-c6071c10f18e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4298f4f2715a</guid>
            <dc:creator><![CDATA[Vinay Rana]]></dc:creator>
            <pubDate>Fri, 17 Apr 2026 04:32:33 GMT</pubDate>
            <atom:updated>2026-04-17T04:32:33.782Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Migrating source code repositories from </em><strong><em>GitLab to GitHub</em></strong><em> is not just a tooling change — it’s an opportunity to standardize repository structure, enforce governance. This blog walks through the </em><strong><em>key migration approaches</em></strong><em>, </em><strong><em>repository organization strategies and governance best practices</em></strong><em> that worked well during a real-world enterprise migration.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v7dFy2h6SoM5bwCL1wizsw.png" /></figure><h3>1. Methods of Code Migration</h3><p>There are multiple ways to migrate repositories from GitLab to GitHub. The right choice depends on scale, automation needs, and level of control required.</p><h4>1.1 Third‑Party Migration Tools</h4><p>Several third‑party tools support GitLab‑to‑GitHub migration and can transfer:</p><ul><li>Repositories</li><li>Issues</li><li>Pull / Merge Requests</li><li>Labels and metadata</li></ul><p>These tools are useful for <strong>large-scale migrations</strong>, but they often require licenses and may need additional validation post‑migration.</p><h4>1.2 Scripts and Command‑Line Migration</h4><p>For teams that prefer full control and transparency, script‑based migration is ideal.</p><p>Typical steps include:</p><ul><li>Cloning the GitLab repository</li><li>Adding GitHub as a remote</li><li>Pushing all branches and tags</li></ul><p>This approach works best when:</p><ul><li>Only source code and history are required</li><li>Issue tracking is handled separately</li><li>Automation is needed at scale</li></ul><h4>1.3 GitHub Importer</h4><p>GitHub provides a <strong>built‑in importer</strong> that supports GitLab repositories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M4b8_hHnj09HqpK0AGnZWQ.png" /></figure><p><strong>Pros</strong></p><ul><li>Simple UI‑based migration</li><li>Good for small migrations</li></ul><p><strong>Cons</strong></p><ul><li>Limited customization</li></ul><h3>2. Repository Organization in GitHub</h3><p>Unlike GitLab, <strong>GitHub does not support organizing repositories into folders</strong>. All repositories live in a <strong>flat namespace</strong> within an organization.</p><p>While this may initially feel restrictive, GitHub provides several effective workarounds.</p><h3>3. Workarounds for Organizing Repositories Without Folders</h3><h4>3.1 Naming Conventions: “Virtual Folders”</h4><p>A strong naming convention is the simplest and most powerful way to organize repositories.</p><p><strong>Example</strong></p><pre>apac-customer-profile-api<br>apac-order-management-api</pre><p>By prefixing all APAC‑related APIs with apac-, we can easily:</p><ul><li>Identify related repositories</li><li>Filter and search consistently</li><li>Maintain visual grouping without folders</li></ul><h4>3.2 Organizations and Teams</h4><p>GitHub <strong>Organizations</strong> and <strong>Teams</strong> help group repositories by:</p><ul><li>Functional domains</li><li>Business groups</li><li>Ownership</li></ul><p>Benefits:</p><ul><li>Access control via teams</li><li>Clear ownership model</li><li>Better collaboration and security boundaries</li></ul><h4>3.3 Topics (Tags): Fine‑Grained Classification</h4><p>GitHub supports <strong>multiple topics per repository</strong>, which enables flexible classification beyond naming conventions.</p><p><strong>Example topics</strong></p><ul><li>apac</li><li>agentic</li><li>anthropic</li></ul><p>Topics help with:</p><ul><li>Filtering repositories</li><li>Reporting</li><li>Project‑level grouping</li></ul><h4>3.4 Combining Naming Conventions and Topics (Best Practice)</h4><p>The most effective approach is combining <strong>both</strong> naming conventions and topics.</p><p><strong>Example</strong></p><ul><li><strong>Repository name</strong>: apac-customer-profile-api</li><li><strong>Topics</strong>: apac, agentic</li></ul><p>This allows us to:</p><ul><li>Quickly identify all APAC APIs by name</li><li>Use topics for project‑ or program‑level filtering</li><li>Support accurate reporting and governance</li></ul><h3>4. Standardizing Default Branch Strategy</h3><h4>4.1 Default Branch for New Repositories</h4><p>At the organization level:</p><pre>Org Settings → Repositories → Default branch name</pre><p><strong>Recommended setup</strong></p><ul><li>Default branch: main</li><li>Optional long‑living branch: develop</li></ul><h4>4.2 Protecting Critical Branches (Org‑wide)</h4><p>Typical rules for main and develop:</p><ul><li>Require pull requests</li><li>Require <strong>1–2 approvals</strong></li><li>Require status checks to pass</li><li>Require conversation resolution</li><li>Block force pushes</li><li>Block branch deletion</li></ul><p>This ensures:</p><ul><li>Code quality</li><li>Audit compliance</li><li>Controlled deployments</li></ul><h3>5. Enforcing Branch Naming Conventions</h3><p>To maintain consistency and automation readiness, enforce branch naming rules.</p><h4>5.1 Allowed Branch Patterns</h4><pre>feature/*<br>bugfix/*<br>hotfix/*<br>release/*<br>support/*<br>develop<br>main</pre><p><strong>Ruleset example</strong></p><pre>&quot;feature/**/*&quot;,<br>&quot;bugfix/**/*&quot;,<br>&quot;hotfix/**/*&quot;,<br>&quot;release/**/*&quot;,<br>&quot;support/**/*&quot;</pre><p>This prevents:</p><ul><li>Ad‑hoc branches</li><li>CI/CD misfires</li><li>Governance violations</li></ul><h3>6. Repository Templates: Enforcing Standards from Day One</h3><p>A <strong>repository template</strong> ensures every new repo starts compliant.</p><h4>Template Includes</h4><ul><li>main branch</li><li>Optional develop branch</li><li>.github/workflows/ (starter CI pipeline)</li><li>CODEOWNERS</li><li>README.md</li><li>.gitignore</li></ul><p><strong>Benefits</strong></p><ul><li>Zero manual setup</li><li>Consistent structure</li><li>Faster onboarding</li></ul><h3>7. GitHub Rulesets: Practical Examples</h3><h4>Example Ruleset 1 — Protected Branches</h4><p><strong>Target</strong>: main, develop</p><ul><li>Pull request required</li><li>Minimum 1 approval</li><li>Status checks required</li><li>No force push</li><li>No delete</li></ul><h4>Example Ruleset 2 — Branch Naming Enforcement</h4><p><strong>Target</strong>: All branches<br> <strong>Pattern</strong></p><pre>^(feature|bugfix|hotfix|release)/.+$</pre><h3>Conclusion</h3><p>A successful GitLab‑to‑GitHub migration is not just about moving repositories — it’s about <strong>establishing strong foundations</strong>:</p><ul><li>Clear repository organization</li><li>Enforced governance</li><li>Scalable CI/CD workflows</li><li>Environment‑aware deployments</li></ul><p>By combining <strong>naming conventions, topics, rulesets, templates, and well‑defined pipelines</strong>, teams can achieve a clean, compliant, and future‑ready GitHub ecosystem.</p><h3>Enjoyed the read? Let’s stay connected!</h3><p>👏 Clap (up to 50 times!) to show support and help others find this article.<br>💬 Comment with your thoughts or questions — I’d love to hear from you.<br>📤 Share this with someone who might find it helpful.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4298f4f2715a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Complete Guide to Implementing Microsoft Entra ID (Azure AD) SSO in MuleSoft Anypoint Platform]]></title>
            <link>https://medium.com/another-integration-blog/complete-guide-to-implementing-microsoft-entra-id-azure-ad-sso-in-mulesoft-anypoint-platform-27238cb722d2?source=rss-c6071c10f18e------2</link>
            <guid isPermaLink="false">https://medium.com/p/27238cb722d2</guid>
            <dc:creator><![CDATA[Vinay Rana]]></dc:creator>
            <pubDate>Fri, 23 Jan 2026 08:34:05 GMT</pubDate>
            <atom:updated>2026-01-26T23:53:22.251Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Single Sign-On (SSO) simplifies authentication, enhances security, and improves user experience across enterprise platforms. MuleSoft Anypoint Platform supports OpenID Connect (OIDC), making Microsoft Entra ID (formerly Azure AD) an ideal identity provider (IdP) for enterprise-grade authentication.</blockquote><blockquote>This guide walks you end‑to‑end through configuring <strong>Microsoft Entra ID → MuleSoft Anypoint Platform</strong> SSO using OIDC — including app registration, redirect URIs, certificate setup, role mapping, testing, troubleshooting, and best practices.</blockquote><h3>🧩 1. Understanding the Architecture</h3><p>Anypoint Platform relies on OIDC standards to federate identity with external IdPs.</p><p><strong>Authentication Flow:</strong></p><ol><li>User accesses the Anypoint login page.</li><li>User selects <strong>Continue with Entra ID</strong>.</li><li>User is redirected to the Microsoft Entra authentication page.</li><li>User logs in → Microsoft issues tokens.</li><li>Tokens are validated by Anypoint → user gets access.</li></ol><h3>🛠️ 2. Prerequisites</h3><p>Before starting, ensure:</p><ul><li>You have <strong>Admin access</strong> to Microsoft Entra ID.</li><li>You have <strong>Organization Owner or Admin</strong> access in MuleSoft Anypoint.</li><li>Your organization’s domain is defined (e.g., poweredbytest).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hZ2FuxWcdS7yaQhML0r-Aw.png" /></figure><h3>🏗️ 3. Step-by-Step Setup in Microsoft Entra ID</h3><h4>3.1 Register an Application in Entra ID</h4><ol><li>Go to <strong>Microsoft Entra admin center</strong> → <em>App Registrations</em> → <em>New Registration</em>.</li><li>Enter Application Name — e.g., Anypoint SSO.</li><li>Supported account types:<br> <strong>Accounts in this organizational directory only</strong>.</li><li>Redirect URI (leave empty for now — we will add it later).</li><li>Click <strong>Register</strong>.</li></ol><h4>3.2 Capture Required IDs</h4><p>From the app overview page, capture:</p><ul><li><strong>Application (client) ID</strong></li><li><strong>Directory (tenant) ID</strong></li></ul><p>These values are used later in Anypoint.</p><h4>3.3 Add Redirect URI</h4><p>Go to: <strong>Authentication → Add a platform → Web</strong></p><p>Add your exact Anypoint redirect URI:</p><pre>https://anypoint.mulesoft.com/accounts/login/&lt;yourDomain&gt;/providers/&lt;providerId&gt;/redirect</pre><p>Example:</p><pre>https://anypoint.mulesoft.com/accounts/login/poweredbytest/providers/12345abc-1ab7-4aed-8b36-a63add7c7c70/redirect</pre><p>✔ Must match <em>exactly</em> — no trailing slashes, no case differences.</p><h4>3.4 Enable ID Tokens</h4><p>Under Authentication:</p><ul><li>Check <strong>ID tokens</strong> (required for OIDC).</li></ul><h4>3.5 Create a Client Secret</h4><ol><li>Navigate to <strong>Certificates &amp; Secrets</strong> → <em>New Client Secret</em>.</li><li>Add a description (e.g., “MuleSoft OIDC Secret”).</li><li>Set an expiration (recommended: 6–12 months).</li><li>Copy the generated <strong>Secret Value</strong>.</li></ol><h4>3.6 Configure API Permissions</h4><p>No special API permissions are required beyond the OIDC scopes:</p><ul><li>openid</li><li>profile</li><li>email</li></ul><p>Anypoint will consume theseduring authentication.</p><h3>🌐 4. Configure OIDC in MuleSoft Anypoint Platform</h3><h4>4.1 Navigate to Identity Providersthese during</h4><p>Go to: <strong>Access Management → Identity Providers → OpenID Connect</strong></p><p>Click <strong>Add Identity Provider</strong>.</p><h4>4.2 Fill OIDC Fields</h4><p>Use the following configuration:</p><blockquote>Issuer URL</blockquote><pre>https://login.microsoftonline.com/&lt;tenant_id&gt;/v2.0</pre><blockquote>Authorize URL</blockquote><pre>https://login.microsoftonline.com/&lt;tenant_id&gt;/oauth2/v2.0/authorize</pre><blockquote>Token URL</blockquote><pre>https://login.microsoftonline.com/&lt;tenant_id&gt;/oauth2/v2.0/token</pre><blockquote>User Info URL</blockquote><pre>https://graph.microsoft.com/oidc/userinfo</pre><blockquote>Client ID / Secret</blockquote><p>Paste the values obtained from Entra ID.</p><h4>4.4 Save and Activate</h4><p>Click <strong>Save Changes</strong>.</p><p>Anypoint will generate a <strong>Redirect URI</strong> — this must already match the value you added earlier in Entra ID.</p><h3>🧪 5. Test the SSO Integration (Step-by-Step)</h3><h4>Step 1: Log out of Anypoint Platform</h4><p>Ensure you start from a clean session.</p><h4>Step 2: Open Custom Domain Login</h4><p>Example:</p><pre>https://anypoint.mulesoft.com/accounts/login/poweredbytest</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*ZmVn9_uAxnYvI239k1vK7A.png" /></figure><h4>Step 3: Click “Continue with OpenID Identity Management EntraID”</h4><p>(This page shows your configured custom domain login screen.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*n29B7SwiZo68LXDdaWgqug.png" /></figure><h4>Step 4: Authenticate via Microsoft Entra ID</h4><p>Enter your credentials → complete MFA.</p><h4>Step 5: Verify Successful Login</h4><p>You should land on the Anypoint Home dashboard.</p><h3>🔐 6. Optional: Configure Role Mapping</h3><p>You can map Microsoft Entra ID application roles to Anypoint roles.</p><p>Example scenarios:</p><ul><li>Entra role “API Admin” → Anypoint API Manager Admin.</li><li>Entra role “Developer” → Anypoint Read-only.</li></ul><p>Go to: <strong>Access Management → Identity Providers → Mappings</strong></p><h3>🩺 7. Troubleshooting Guide</h3><h4>Error: “The request could not be processed at this time.”</h4><p>Usually caused by:</p><ul><li>Redirect URI mismatch</li><li>Invalid Client Secret</li><li>Tenant mismatch (v1 vs v2 mismatch)</li></ul><h4>Error: User redirected back without login</h4><p>Check:</p><ul><li>ID Tokens ✓</li><li>Scopes ✓</li><li>No Conditional Access policy blocking</li></ul><h4>Token invalid or expired</h4><p>Ensure system clocks aren’t skewed, and secrets haven’t expired.</p><h3>🧭 8. Best Practices</h3><h4>Rotate Client Secret regularly</h4><p>Set reminders before expiry.</p><h4>Use a dedicated Enterprise Application.</h4><p>Prevent accidental changes across environments.</p><p>Use conditional access wisely.</p><p>e.g., Enforce MFA, trusted device login, location restrictions.</p><h4>Enable audit logs in Entra ID.</h4><p>Monitor sign-ins and anomalies.</p><h3>9. Limitations</h3><h4><strong>Not supported in:</strong></h4><ul><li>Azure Government</li><li>Azure China 21Vianet</li><li>Azure Germany</li><li>No custom scopes</li><li>Old client secrets must be <strong>manually deleted in the Azure Portal</strong></li></ul><h3>🎉 10. Conclusion</h3><p>Implementing Microsoft Entra ID SSO with Anypoint Platform provides a secure, seamless login experience for your users while centralizing identity and enforcing enterprise-grade security policies.</p><p>With OIDC fully supported on both sides, this integration is straightforward, scalable, and aligns with modern IAM standards.</p><h3>Enjoyed the read? Let’s stay connected!</h3><p>👏 Clap (up to 50 times!) to show support and help others find this article.<br>💬 Comment with your thoughts or questions — I’d love to hear from you.<br>📤 Share this with someone who might find it helpful.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27238cb722d2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/another-integration-blog/complete-guide-to-implementing-microsoft-entra-id-azure-ad-sso-in-mulesoft-anypoint-platform-27238cb722d2">Complete Guide to Implementing Microsoft Entra ID (Azure AD) SSO in MuleSoft Anypoint Platform</a> was originally published in <a href="https://medium.com/another-integration-blog">Another Integration Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enhancing API Observability: Integrating MuleSoft CloudHub with New Relic Using Log4j2]]></title>
            <link>https://medium.com/another-integration-blog/enhancing-api-observability-integrating-mulesoft-cloudhub-with-new-relic-using-log4j2-91a27502902e?source=rss-c6071c10f18e------2</link>
            <guid isPermaLink="false">https://medium.com/p/91a27502902e</guid>
            <category><![CDATA[cloudhub]]></category>
            <category><![CDATA[mulesoft]]></category>
            <category><![CDATA[new-relic]]></category>
            <category><![CDATA[logging-and-monitoring]]></category>
            <category><![CDATA[log4j2]]></category>
            <dc:creator><![CDATA[Vinay Rana]]></dc:creator>
            <pubDate>Mon, 16 Jun 2025 05:11:06 GMT</pubDate>
            <atom:updated>2025-07-18T03:34:45.430Z</atom:updated>
            <content:encoded><![CDATA[<h3>Enhancing API Observability: Integrating MuleSoft CloudHub logs with New Relic</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/616/1*Esh-NKN7rulErCtpHYRFMg.png" /></figure><p><em>In this article, we explore the process of integrating MuleSoft CloudHub with New Relic enables powerful observability across APIs and integrations. While CloudHub restricts direct agent installation, developers can still achieve robust logging and monitoring using Log4j2, Telemetry Exporter, and OpenTelemetry-based custom instrumentation.</em></p><p><em>This article provides a technically detailed guide for integrating MuleSoft logs with New Relic, including configuration examples, runtime properties, and architectural considerations.</em></p><h3>Integration Methods</h3><ol><li><strong>Log4j2 with New Relic Insights API</strong></li></ol><ul><li>Uses Log4j2 appenders (HTTP or New Relic-specific) to send logs directly to New Relic.</li><li>Requires configuration in log4j2.xml, runtime properties, and secure deployment settings.</li><li>Ideal for structured logging and real-time log streaming.</li></ul><p>2. <strong>Telemetry Exporter</strong></p><ul><li>Built-in MuleSoft feature that exports logs and metrics to third-party platforms like New Relic.</li><li>Uses OTLP protocol and supports custom filtering via NRQL.</li><li>Best suited for centralized, rule-based log and metric export.</li></ul><p>3. <strong>Custom Instrumentation with OpenTelemetry</strong></p><ul><li>Enables distributed tracing and deep observability.</li><li>Involves configuring Mule Runtime for OpenTelemetry and developing custom policies.</li><li>Recommended for advanced use cases requiring trace-level insights and custom monitoring logic.</li></ul><h4>1. New Relic Insights API via Log4j2</h4><p>This method uses Log4j2 to send logs directly to New Relic’s <strong>Insights API</strong>.</p><p><strong>Configuration Steps:</strong><br>a. Log4j2 HTTP Appender<br>Update your log4j2.xml file:</p><pre>&lt;Appenders&gt;<br>  &lt;Http name=&quot;NewRelicAppender&quot; url=&quot;${sys:newrelic.url}&quot;&gt;<br>    &lt;Property name=&quot;Api-Key&quot; value=&quot;${sys:newrelic.apiKey}&quot;/&gt;<br>    &lt;Property name=&quot;Content-Type&quot; value=&quot;application/json&quot;/&gt;<br>    &lt;JSONLayout compact=&quot;true&quot; eventEol=&quot;true&quot; properties=&quot;true&quot;<br>                stacktraceAsString=&quot;true&quot; includeTimeMillis=&quot;true&quot;/&gt;<br>  &lt;/Http&gt;<br>&lt;/Appenders&gt;</pre><pre>&lt;AsyncRoot level=&quot;info&quot;&gt;<br>  &lt;AppenderRef ref=&quot;NewRelicAppender&quot;/&gt;<br>&lt;/AsyncRoot&gt;</pre><p>b. <strong>Runtime Properties</strong><br>Set these during deployment:</p><pre>-Dnewrelic.url=https://insights-collector.newrelic.com/v1/log<br>-Dnewrelic.apiKey=YOUR_INSERT_KEY</pre><p><strong>c. Secure Properties in </strong><strong>artifact.json</strong></p><pre>&quot;secureProperties&quot;: [&quot;newrelic.apiKey&quot;]</pre><p><strong>d. Disable CloudHub Logs</strong></p><p>Disable default CloudHub logging in the deployment settings. If this option is not available in your environment raise a ticket with MuleSoft.</p><h4><strong>Alternative: New Relic Log4j2 Appender</strong></h4><p>Use the official New Relic Log4j2 appender for advanced features like batching, retries, and structured logging.</p><p><strong>Maven Dependency:</strong></p><pre>&lt;dependency&gt;<br>  &lt;groupId&gt;com.newrelic.logging&lt;/groupId&gt;<br>  &lt;artifactId&gt;log4j2-newrelic&lt;/artifactId&gt;<br>  &lt;version&gt;1.0.0&lt;/version&gt;<br>&lt;/dependency&gt;</pre><p><strong>Appender Configuration Example:</strong></p><pre>&lt;NewRelic name=&quot;NewRelicAppender&quot; apiKey=&quot;YOUR_API_KEY&quot;<br>          apiUrl=&quot;https://log-api.newrelic.com/log/v1&quot;<br>          applicationName=&quot;MyMuleApp&quot;<br>          batchSize=&quot;2000&quot;<br>          flushInterval=&quot;120000&quot;<br>          logType=&quot;muleLog&quot;<br>          customFields=&quot;env=prod,team=integration&quot;/&gt;</pre><h4>2. Telemetry Exporter</h4><p>MuleSoft’s <strong>Telemetry Exporter</strong> allows exporting metrics and logs to New Relic via OTLP.</p><h4>Steps to Configure</h4><ol><li><strong>Access Telemetry Exporter</strong> in Anypoint Monitoring.</li><li><strong>Create a Connection:</strong><br>Endpoint: <a href="https://otlp.nr-data.net:4318/">https://otlp.nr-data.net:4318</a><br>Protocol: OTLP over HTTP</li><li><strong>Define Export Rules:</strong> <br>Use NRQL to filter and route logs.<br>Example: SELECT * FROM Log WHERE applicationName = ‘MyMuleApp’</li><li><strong>Apply Configuration:</strong><br>Save and activate the exporter to begin streaming data.</li></ol><h4>3. Custom Instrumentation with OpenTelemetry</h4><p>For distributed tracing and deep observability, use <strong>OpenTelemetry</strong> and <strong>custom policies</strong>.</p><h4>Steps to Implement</h4><p><strong>a. Enable OpenTelemetry in Mule Runtime</strong></p><p>Add the following to your mule-artifact.json:</p><pre>&quot;exporters&quot;: {<br>  &quot;otel&quot;: {<br>    &quot;enabled&quot;: true,<br>    &quot;endpoint&quot;: &quot;https://otlp.nr-data.net:4318&quot;<br>  }<br>}</pre><p><strong>b. Configure HTTP Connector for Tracing</strong></p><p>Ensure connectors are instrumented to emit trace data. Use headers like traceparent and tracestate.</p><p><strong>c. Develop Custom Policies</strong></p><p>Use Maven to scaffold a policy project:</p><pre>mvn archetype:generate -DarchetypeArtifactId=mule-policy-archetype</pre><p>Define logic in XML/YAML:</p><pre>id: custom-logging-policy<br>name: Custom Logging Policy<br>configuration:<br>  - logLevel: INFO<br>  - logMessage: &quot;Request received at ${request.path}&quot;</pre><p><strong>d. Deploy and Apply via API Manager</strong></p><p>Upload the JAR to Anypoint Exchange and apply it to your APIs.</p><h3>Architecture Diagram</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*QTH5V46XWeaaIzET3mUpwA.png" /></figure><h3>Conclusion</h3><p><em>By leveraging Log4j2, Telemetry Exporter, and OpenTelemetry, MuleSoft developers can achieve comprehensive observability in New Relic — even without agent installation. Each method offers flexibility depending on your use case, infrastructure, and monitoring goals.</em></p><h3>💬 Enjoyed the read? Let’s stay connected!</h3><p>👏 Clap (up to 50 times!) to show support and help others find this article.<br>💬 Comment with your thoughts or questions — I’d love to hear from you.<br>📤 Share this with someone who might find it useful.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91a27502902e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/another-integration-blog/enhancing-api-observability-integrating-mulesoft-cloudhub-with-new-relic-using-log4j2-91a27502902e">Enhancing API Observability: Integrating MuleSoft CloudHub with New Relic Using Log4j2</a> was originally published in <a href="https://medium.com/another-integration-blog">Another Integration Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrading Mule Applications to Java 17 and latest mule runtime]]></title>
            <link>https://medium.com/another-integration-blog/migrating-mule-applications-to-java-17-and-latest-mule-runtime-16094319d555?source=rss-c6071c10f18e------2</link>
            <guid isPermaLink="false">https://medium.com/p/16094319d555</guid>
            <dc:creator><![CDATA[Vinay Rana]]></dc:creator>
            <pubDate>Thu, 14 Nov 2024 06:29:16 GMT</pubDate>
            <atom:updated>2025-06-25T12:44:26.417Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>In this article, we explore the process of upgrading Mule applications to leverage the powerful features of Java 17 and the latest Mule runtime. We’ll guide you through the key steps, best practices, and potential challenges you might encounter during the migration. Whether you’re looking to enhance performance, improve security, or take advantage of new language features, this comprehensive guide will help you seamlessly transition your Mule applications to the cutting-edge Java 17 environment.</blockquote><h3><strong>Step by Step Guide:</strong></h3><ol><li><strong>Download Anypoint Studio</strong>: Get the latest version (7.17.0) with runtime 4.6.0 or later.</li><li>In the studio run configuration select the JRE as JDK 17.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5gVsRv2Lw3yl6xpy0hgx0g.png" /></figure><p><strong>3.</strong> In mule code, if you are using any parent bom file to manage dependencies for testing purpose temporarily remove parent BOM dependencies. After development, add common dependencies to bom.xml instead of the local pom.xml.</p><p><strong>4. Manage Dependencies in Anypoint Studio</strong>: Right-click on the project, select “Manage Dependencies,” then “Manage Modules.” Add and upgrade project dependencies as needed.</p><p><strong>5. Update Mule Runtime Version</strong>: Change the Mule runtime version to 4.7.0 in the pom.xml file.</p><p><strong>6. Clean the Project</strong>: Clean the project before running it.</p><p><strong>7. Run the Code</strong>: Execute the project.</p><p>These are the generic steps which we need to perform to upgrade the code.</p><p>Sometimes when we run the code we got some issues specific to the connectors. Listing some of them here:</p><ol><li><strong>Anypoint MQ Configuration</strong></li></ol><p>For connectors version 3.x and below, the URL format was:</p><pre>https://mq-us-east-1.anypoint.mulesoft.com/api/v1 (JDK 8)</pre><p>For connectors version 4.x and above, the URL format has changed to:</p><pre>https://mq-us-east-1.anypoint.mulesoft.com/api/v1/organizations/{org}/environments/{env} (JDK 17)</pre><p>When deploying, make sure to update this runtime property to the new URL format.</p><p><strong>2. Upload Part S3 connector</strong></p><p>In the updated Upload Part S3 connector, certain attributes such as Is Last Part and Part Size have been removed. If your code currently uses these attributes, you’ll need to remove them to ensure compatibility with the new version.</p><p><strong>3.</strong> Amazon S3 Connector create object operation not available in new mule-amazon-s3-connector 6.x versions</p><ul><li><strong>Create Object</strong> is now <strong>Put Object</strong>.</li></ul><p><strong>4. Custom Connectors</strong></p><p>Custom connectors (including custom configuration properties providers) are any connectors that are not developed and maintained by MuleSoft, including connectors that are built by MuleSoft partners or customers. If you are using a custom connector in your app, you must update your connector to run on Java 17 and Mule runtime 4.6 and later.</p><p><strong>5. Error Structure Differences</strong></p><p>When upgrading from Java 8 to Java 17, note the following changes in error structures:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e2N2acikC_qUx0ww9SUHJg.png" /></figure><p>In Java 17 Error structure (from MuleSoft documentation) :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a_tCD-YHZbnmsB9B4_Pe9g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1006/1*7Y2dhKcnRRkhp3ea_jx-PQ.png" /></figure><h3><strong>Post-Upgrade:</strong></h3><ol><li>Monitor your apps for any unexpected behavior.</li><li>Update any relevant documentation to reflect changes made during the upgrade.</li></ol><p>More detailed information available:</p><p><a href="https://docs.mulesoft.com/general/java-support">Java Support</a></p><h3>💬 Enjoyed the read? Let’s stay connected!</h3><p>👏 Clap (up to 50 times!) to show support and help others find this article.<br>💬 Comment with your thoughts or questions — I’d love to hear from you.<br>📤 Share this with someone who might find it useful.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16094319d555" width="1" height="1" alt=""><hr><p><a href="https://medium.com/another-integration-blog/migrating-mule-applications-to-java-17-and-latest-mule-runtime-16094319d555">Upgrading Mule Applications to Java 17 and latest mule runtime</a> was originally published in <a href="https://medium.com/another-integration-blog">Another Integration Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>