<?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 Ram Changalva on Medium]]></title>
        <description><![CDATA[Stories by Ram Changalva on Medium]]></description>
        <link>https://medium.com/@ram.changalva?source=rss-7352be1e457d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Ram Changalva on Medium</title>
            <link>https://medium.com/@ram.changalva?source=rss-7352be1e457d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:39:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ram.changalva/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[CloudHub 2.0]]></title>
            <link>https://medium.com/@ram.changalva/cloudhub-2-0-339719896840?source=rss-7352be1e457d------2</link>
            <guid isPermaLink="false">https://medium.com/p/339719896840</guid>
            <dc:creator><![CDATA[Ram Changalva]]></dc:creator>
            <pubDate>Mon, 27 Jul 2026 01:13:15 GMT</pubDate>
            <atom:updated>2026-07-27T01:16:51.096Z</atom:updated>
            <content:encoded><![CDATA[<h2>CloudHub 2.0 Explained: How MuleSoft Delivers Enterprise-Grade APIs Without Infrastructure Management</h2><p>Modern cloud-native integration isn’t just about deploying APIs — it’s about building resilient, scalable services while letting the platform handle the operational complexity. CloudHub 2.0 was designed with exactly that goal in mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*XGs3c3J5gE2izPmfTNZ3-Q@2x.jpeg" /></figure><p>Why CloudHub 2.0 Matters</p><p>Building an API is only one part of delivering a successful integration solution.</p><p>The larger challenge begins after deployment:</p><ul><li>How do you handle sudden traffic spikes?</li><li>What happens if a runtime instance fails?</li><li>How do you securely manage certificates and secrets?</li><li>How do you deploy globally while maintaining high availability?</li></ul><p>These are the types of operational problems that traditionally required dedicated infrastructure teams. CloudHub 2.0 abstracts those responsibilities, allowing integration developers to concentrate on business logic instead of platform management.</p><p>Built on Kubernetes, CloudHub 2.0 provides a fully managed runtime that automates deployment, scaling, monitoring, and security for Mule applications.</p><p>From Infrastructure Management to API Innovation</p><p>Traditional deployments often require teams to provision servers, configure networking, monitor resource utilization, patch operating systems, and manage runtime availability.</p><p>With CloudHub 2.0, developers package their Mule application and deploy it through Anypoint Platform. The platform automatically provisions the required infrastructure, deploys containers, monitors runtime health, and adjusts capacity as application demand changes.</p><p>The operational burden shifts from developers to the platform.</p><p>A Real-World Example: Healthcare Patient Portal</p><p>Instead of using a simple retail analogy, consider a modern healthcare provider offering a digital patient portal.</p><p>Patients use the portal to:</p><ul><li>Schedule appointments</li><li>Review laboratory results</li><li>Download prescriptions</li><li>Access medical records</li><li>Participate in telehealth consultations</li></ul><p>On an average day, system utilization remains relatively predictable. A small number of application containers can comfortably handle the incoming traffic.</p><p>Now imagine flu season or a public health emergency.</p><p>Thousands of patients attempt to access the portal simultaneously.</p><p>Without elastic infrastructure, users experience slow response times or failed requests.</p><p>CloudHub 2.0 continuously monitors application demand. As traffic increases, additional Mule runtime containers are automatically provisioned across the Kubernetes cluster. Incoming requests are distributed across these containers, allowing the application to maintain consistent performance without manual intervention.</p><p>Once demand returns to normal levels, the additional containers are automatically removed, optimizing infrastructure utilization without affecting application availability.</p><p>The development team never provisions servers, configures load balancers, or manually scales infrastructure. CloudHub manages the entire lifecycle.</p><p>Understanding Containers in CloudHub 2.0</p><p>One of the most significant architectural improvements in CloudHub 2.0 is its container-based runtime.</p><p>Rather than installing applications directly on shared servers, every Mule application executes inside its own isolated container.</p><p>Each container includes:</p><ul><li>Mule Runtime</li><li>Application package</li><li>Required libraries</li><li>Configuration files</li><li>Secure properties</li><li>Runtime dependencies</li></ul><p>Because containers are self-contained, applications remain portable, consistent, and isolated from one another. A problem affecting one application cannot interfere with another application’s runtime environment.</p><p>This isolation significantly improves operational stability across enterprise integration platforms.</p><p>Intelligent Auto Scaling</p><p>CloudHub continuously evaluates runtime metrics instead of relying on fixed infrastructure capacity.</p><p>The scaling process follows a simple operational model:</p><ol><li>Client applications begin sending requests.</li><li>CloudHub monitors runtime utilization and traffic patterns.</li><li>When predefined thresholds are exceeded, additional containers are automatically provisioned.</li><li>Traffic is distributed across available containers.</li><li>Response times remain consistent even during periods of heavy demand.</li><li>When utilization decreases, unnecessary containers are gracefully removed.</li></ol><p>This dynamic allocation of compute resources ensures organizations only consume the infrastructure required at any given moment.</p><p>High Availability Without Operational Complexity</p><p>Enterprise applications cannot afford extended downtime.</p><p>CloudHub 2.0 addresses this through container orchestration provided by Kubernetes.</p><p>If a runtime container unexpectedly becomes unavailable:</p><ul><li>Health checks immediately detect the issue.</li><li>Traffic is redirected to healthy containers.</li><li>Replacement containers are automatically provisioned.</li><li>End users experience little or no disruption.</li></ul><p>This self-healing capability eliminates many of the operational tasks traditionally handled by infrastructure administrators.</p><p>Security Built Into the Platform</p><p>Security is integrated into every layer of CloudHub 2.0 rather than being treated as an afterthought.</p><p>The platform provides:</p><ul><li>Container isolation</li><li>TLS encryption</li><li>Secure property management</li><li>Secret storage</li><li>Identity and access management</li><li>Network segmentation</li><li>Certificate management</li></ul><p>Because these capabilities are managed centrally through the platform, development teams spend less time maintaining infrastructure-level security configurations.</p><p>Simplified Enterprise Architecture</p><p>A typical CloudHub 2.0 deployment follows a streamlined architecture.</p><p>Developers build Mule applications using Anypoint Studio and deploy them through Anypoint Platform.</p><p>The CloudHub control plane manages deployment, monitoring, logging, scaling, and operational governance.</p><p>The runtime plane executes containerized Mule applications within Kubernetes clusters.</p><p>Those applications securely integrate with enterprise systems such as:</p><ul><li>Salesforce</li><li>SAP</li><li>Workday</li><li>Oracle</li><li>Snowflake</li><li>Databases</li><li>REST APIs</li><li>Event-driven platforms</li></ul><p>This separation between management services and runtime execution improves scalability while simplifying operational governance.</p><p>Global Deployment Made Simple</p><p>Organizations increasingly serve customers across multiple geographic regions.</p><p>CloudHub 2.0 allows applications to be deployed close to end users through regional cloud environments.</p><p>Whether customers are located in North America, Europe, Canada, India, or other supported regions, applications can be deployed with region-specific endpoints while maintaining centralized operational management.</p><p>This approach reduces latency and improves overall application responsiveness.</p><p>Why CloudHub 2.0 Represents a Modern Runtime Platform</p><p>CloudHub 2.0 is more than a deployment destination.</p><p>It combines several cloud-native capabilities into a single managed platform:</p><ul><li>Kubernetes orchestration</li><li>Automatic scaling</li><li>Containerized runtime</li><li>Built-in resilience</li><li>Enterprise-grade security</li><li>Centralized monitoring</li><li>Global deployment capabilities</li><li>Managed infrastructure operations</li></ul><p>Instead of investing engineering effort into operating servers and runtime environments, organizations can focus on delivering business value through APIs and integrations.</p><p>Key Takeaways</p><p>CloudHub 2.0 fundamentally changes how Mule applications are deployed and operated.</p><p>By leveraging Kubernetes and container technology, it removes much of the infrastructure complexity traditionally associated with enterprise integration platforms. Developers deploy applications, while the platform automatically manages scaling, availability, security, monitoring, and infrastructure lifecycle.</p><p>For organizations building mission-critical integrations across systems such as Salesforce, SAP, Workday, Oracle, healthcare platforms, banking systems, or manufacturing applications, CloudHub 2.0 provides a cloud-native runtime that is resilient, scalable, and operationally efficient.</p><p>Rather than asking teams to become infrastructure experts, CloudHub allows them to focus on what matters most — building reliable APIs that solve real business problems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=339719896840" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Oracle EPM Cloud Implementation: A Practical End-to-End Guide for Successful Deployment]]></title>
            <link>https://medium.com/@ram.changalva/oracle-epm-cloud-implementation-a-practical-end-to-end-guide-for-successful-deployment-8661739d9012?source=rss-7352be1e457d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8661739d9012</guid>
            <dc:creator><![CDATA[Ram Changalva]]></dc:creator>
            <pubDate>Tue, 10 Mar 2026 02:57:47 GMT</pubDate>
            <atom:updated>2026-03-10T02:57:47.912Z</atom:updated>
            <content:encoded><![CDATA[<p>Implementing <strong>Oracle EPM Cloud</strong> is not simply a system installation — it is a structured transformation that aligns financial processes, governance, and technology. A successful implementation follows a clear lifecycle that ensures business requirements are translated into scalable system configurations while minimizing risk during deployment.</p><p>This guide walks through the <strong>end-to-end Oracle EPM Cloud implementation lifecycle</strong>, covering every major phase — from discovery to post-production support — using real-world project terminology used by implementation teams.</p><h3>1. Discovery Phase</h3><p>The <strong>Discovery Phase</strong> is the foundation of the entire implementation. During this stage, consultants collaborate with business stakeholders to understand existing processes, reporting structures, pain points, and future expectations.</p><p>Key activities include:</p><ul><li>Conducting stakeholder interviews and workshops</li><li>Reviewing current financial processes and reporting structures</li><li>Understanding planning, consolidation, and forecasting requirements</li><li>Identifying integration points with ERP systems</li><li>Documenting key risks and assumptions</li></ul><p>The output of this phase is a clear understanding of the organization’s operational landscape and transformation goals.</p><h3>2. Business Requirement Document (BRD)</h3><p>After discovery, the next step is to document the findings in the <strong>Business Requirement Document (BRD)</strong>.</p><p>The BRD captures:</p><ul><li>Business objectives</li><li>Current vs future processes</li><li>Functional requirements</li><li>Reporting expectations</li><li>Data sources and dependencies</li></ul><p>The BRD is reviewed and approved by business stakeholders to ensure alignment before moving into design.</p><p>A well-defined BRD prevents scope misunderstandings later in the project.</p><h3>3. Solution Design: FDD and TDD</h3><p>Once requirements are finalized, the design phase begins.</p><h3>Functional Design Document (FDD)</h3><p>The <strong>Functional Design Document (FDD)</strong> explains how the business requirements will be implemented in Oracle EPM Cloud from a functional perspective.</p><p>It typically includes:</p><ul><li>Planning and forecasting models</li><li>Metadata structure</li><li>Workflow processes</li><li>Approval hierarchies</li><li>Calculation logic</li><li>Security model</li></ul><h3>Technical Design Document (TDD)</h3><p>The <strong>Technical Design Document (TDD)</strong> focuses on the technical architecture required to support the solution.</p><p>It covers:</p><ul><li>Integration architecture</li><li>Data flow diagrams</li><li>Data migration strategy</li><li>Data conversion logic</li><li>Automation and scheduling</li><li>System dependencies</li></ul><p>Together, the FDD and TDD act as the blueprint for the build phase.</p><h3>4. Application Build: Configuration and Setups</h3><p>During this phase, the system is configured according to the approved designs.</p><p>Major activities include:</p><h3>Chart of Accounts (COA)</h3><p>The <strong>Chart of Accounts (COA)</strong> structure is established in Oracle EPM Cloud to align with financial reporting needs. It defines account hierarchies, dimensions, and reporting rollups.</p><h3>Business Units</h3><p>Organizational structures such as <strong>Business Units</strong>, cost centers, entities, and departments are configured to reflect the company’s operational hierarchy.</p><h3>Security Roles</h3><p>A role-based access model is implemented using <strong>Security Roles</strong> to control user access to data, forms, and workflows.</p><p>Examples include:</p><ul><li>Administrator roles</li><li>Power users</li><li>Finance planners</li><li>Read-only stakeholders</li></ul><p>Proper security configuration ensures governance and compliance.</p><h3>5. Data Migration and Data Conversion</h3><p>A key milestone in the project is bringing historical and operational data into the new system.</p><p>Two important activities take place here:</p><h3>Data Migration</h3><p><strong>Data Migration</strong> involves moving historical financial data from legacy systems into Oracle EPM Cloud.</p><p>This may include:</p><ul><li>Historical actuals</li><li>Budget data</li><li>Forecast data</li><li>Metadata structures</li></ul><h3>Data Conversion</h3><p><strong>Data Conversion</strong> ensures that legacy data is transformed into formats compatible with the new application.</p><p>Activities include:</p><ul><li>Data mapping</li><li>Cleansing and validation</li><li>Dimensional alignment</li></ul><p>Successful migration ensures continuity of reporting and analysis.</p><h3>6. Integration with Source Systems</h3><p>Modern finance systems rarely operate in isolation. Oracle EPM Cloud must integrate with upstream and downstream systems such as ERP platforms.</p><p>Key integration activities include:</p><ul><li>ERP to EPM data loads</li><li>Automated data extracts</li><li>Scheduled data refresh processes</li><li>Validation and reconciliation</li></ul><p>Reliable <strong>integration</strong> pipelines are essential to ensure accurate planning and reporting.</p><h3>7. Testing Phase</h3><p>Testing validates that the configured solution meets both functional and technical requirements.</p><h3>System Integration Testing (SIT)</h3><p>During <strong>System Integration Testing (SIT)</strong>, the implementation team verifies:</p><ul><li>End-to-end data flows</li><li>Calculation logic</li><li>Integration processes</li><li>Workflow functionality</li></ul><p>This phase ensures the system works as designed.</p><h3>User Acceptance Testing (UAT)</h3><p><strong>User Acceptance Testing (UAT)</strong> is conducted by business users.</p><p>They validate:</p><ul><li>Planning forms</li><li>Reports and dashboards</li><li>Forecast processes</li><li>Data accuracy</li></ul><p>UAT sign-off confirms that the solution is ready for production.</p><h3>8. Cutover Plan and Go-Live Preparation</h3><p>Before launching the system, the team prepares a <strong>Cutover Plan</strong>.</p><p>This document outlines all activities required to transition from legacy systems to Oracle EPM Cloud, including:</p><ul><li>Final data loads</li><li>Security activation</li><li>User provisioning</li><li>Integration activation</li><li>Production validation</li></ul><p>Once all steps are completed, the system officially moves to <strong>Go-Live</strong>.</p><p>Go-Live marks the beginning of live operational usage by business teams.</p><h3>9. Hypercare Support</h3><p>Immediately after Go-Live, the project enters the <strong>Hypercare</strong> phase.</p><p>Hypercare typically lasts between two to four weeks and focuses on:</p><ul><li>Resolving user issues quickly</li><li>Monitoring system performance</li><li>Validating integrations</li><li>Ensuring reporting accuracy</li></ul><p>This phase provides a safety net during the early adoption period.</p><h3>10. Gold Tenant Strategy</h3><p>Many organizations maintain a <strong>Gold Tenant</strong> environment.</p><p>A Gold Tenant acts as a controlled template environment used to:</p><ul><li>Test enhancements</li><li>Validate configuration changes</li><li>Perform upgrades before production deployment</li></ul><p>This helps maintain stability in the production system.</p><h3>11. Managing Change Requests (CR)</h3><p>As business needs evolve, enhancements are requested through <strong>Change Requests (CR)</strong>.</p><p>Typical CR examples include:</p><ul><li>New planning scenarios</li><li>Additional reports</li><li>Security adjustments</li><li>New integrations</li></ul><p>Each CR follows a structured lifecycle involving impact assessment, design, development, testing, and deployment.</p><h3>12. Post-Production Support</h3><p>After stabilization, the project transitions into <strong>Post-Production Support</strong>.</p><p>This includes:</p><ul><li>Monitoring system health</li><li>Handling user tickets</li><li>Managing security updates</li><li>Supporting new reporting requirements</li><li>Implementing enhancements</li></ul><p>Strong support governance ensures the system continues delivering long-term value.</p><h3>13. Implementing Financials, Capex, and Projects Modules with EDMCS and EPM Agent Integration</h3><p>In many Oracle EPM Cloud programs, organizations extend the core implementation by deploying additional planning modules such as <strong>Financials, Capital Expenditure (Capex), and Projects</strong>. When these modules are implemented, additional architecture components like <strong>Enterprise Data Management Cloud Service (EDMCS)</strong> and the <strong>EPM Agent</strong> are commonly used to support governance and integration with on-premise or external systems.</p><p>This section explains how these components fit into the implementation lifecycle.</p><h3>Financials Module Implementation</h3><p>The <strong>Financials module</strong> in Oracle EPM Cloud supports operational expense planning and income statement forecasting.</p><p>During implementation, consultants configure:</p><ul><li>Revenue planning models</li><li>Operating expense planning</li><li>Workforce-driven expense allocations</li><li>Driver-based forecasting models</li><li>Financial reporting structures aligned with the <strong>Chart of Accounts (COA)</strong></li></ul><p>Key configuration tasks include:</p><ul><li>Mapping accounts to financial statements</li><li>Configuring planning forms for departments and <strong>Business Units</strong></li><li>Building calculation rules for allocations and forecasts</li><li>Applying <strong>Security Roles</strong> for planners and approvers</li></ul><p>Financials often becomes the central planning model that integrates inputs from workforce, projects, and capital planning.</p><h3>Capex (Capital Expenditure) Module Implementation</h3><p>The <strong>Capex module</strong> manages planning and tracking of capital investments such as infrastructure, equipment, or technology assets.</p><p>Typical configuration activities include:</p><ul><li>Capital project request forms</li><li>Asset lifecycle planning</li><li>Depreciation calculations</li><li>Capital approval workflows</li><li>Asset-to-financial statement mapping</li></ul><p>Capex integrates with the Financials module by automatically generating:</p><ul><li>Depreciation expense</li><li>Asset additions</li><li>Balance sheet impacts</li></ul><p>This ensures capital investments flow directly into financial forecasts.</p><h3>Projects Module Implementation</h3><p>The <strong>Projects module</strong> enables organizations to plan and monitor project-level financials.</p><p>Key implementation components include:</p><ul><li>Project hierarchies</li><li>Project expense categories</li><li>Resource and cost planning</li><li>Project lifecycle tracking</li><li>Integration with Financials and Capex</li></ul><p>Projects planning often includes:</p><ul><li>Project start and end dates</li><li>Budget allocation across periods</li><li>Resource cost allocations</li><li>Expense tracking by project phase</li></ul><p>When implemented properly, the Projects module provides visibility into long-term initiatives and their financial impact.</p><h3>EDMCS for Master Data Governance</h3><p>When multiple EPM modules are deployed, maintaining consistent metadata becomes critical. This is where <strong>Enterprise Data Management Cloud Service (EDMCS)</strong> plays a key role.</p><p>EDMCS provides centralized governance for enterprise dimensions such as:</p><ul><li>Chart of Accounts</li><li>Entities</li><li>Cost centers</li><li>Departments</li><li>Business Units</li><li>Product hierarchies</li></ul><p>Key benefits of EDMCS include:</p><ul><li>Master data version control</li><li>Approval workflows for hierarchy changes</li><li>Automated metadata synchronization across systems</li><li>Audit tracking of structural changes</li></ul><p>For example, when a new department is created in the ERP system, EDMCS can govern the change and push the update to Oracle EPM applications.</p><h3>Integration Using the EPM Agent</h3><p>Many organizations still run <strong>on-premise ERP systems</strong> or maintain data inside internal networks. In such cases, <strong>EPM Agent</strong> is used to securely connect on-premise systems with Oracle EPM Cloud.</p><p>The <strong>EPM Agent</strong> enables:</p><ul><li>Secure data transfer from on-premise databases</li><li>Automated integration jobs</li><li>File-based and direct database integrations</li><li>Scheduled data loads into planning applications</li></ul><p>Common integration scenarios include:</p><ul><li>ERP actuals loaded into Financials planning</li><li>Project data imported from project management systems</li><li>Capital asset information integrated into Capex planning</li><li>Metadata synchronization between ERP and EDMCS</li></ul><p>The EPM Agent acts as a bridge between internal systems and the Oracle EPM Cloud environment without exposing internal infrastructure to the internet.</p><h3>Testing for Multi-Module Implementations</h3><p>When Financials, Capex, Projects, EDMCS, and integrations are implemented together, testing becomes more complex.</p><p>Testing typically includes:</p><p><strong>System Integration Testing (SIT)</strong><br>Validates:</p><ul><li>Data flow between ERP, EDMCS, and EPM</li><li>Capital depreciation calculations</li><li>Project expense rollups</li><li>Financial statement consolidation</li></ul><p><strong>User Acceptance Testing (UAT)</strong><br>Business users validate:</p><ul><li>Planning forms</li><li>Capital approval workflows</li><li>Project budgeting</li><li>Financial reporting outputs</li></ul><p>Cross-module validation is critical to ensure the entire planning ecosystem works seamlessly.</p><h3>Go-Live Considerations for Multi-Module Deployments</h3><p>When deploying multiple planning modules, the <strong>Cutover Plan</strong> must include additional steps such as:</p><ul><li>Synchronizing metadata via EDMCS</li><li>Validating EPM Agent connectivity</li><li>Finalizing integration schedules</li><li>Confirming depreciation and project calculations</li><li>Validating financial statement outputs</li></ul><p>Once validated, the system proceeds to <strong>Go-Live</strong>, followed by the <strong>Hypercare</strong> support phase to stabilize the environment.</p><h3>Long-Term Governance</h3><p>After implementation, governance processes should include:</p><ul><li>Managing hierarchy updates through EDMCS</li><li>Monitoring integrations via EPM Agent</li><li>Reviewing <strong>Change Requests (CR)</strong> for new planning requirements</li><li>Supporting enhancements during <strong>Post-Production Support</strong></li></ul><p>This ensures the EPM ecosystem remains scalable as the organization evolves.</p><h3>Final Thoughts</h3><p>An Oracle EPM Cloud implementation is not just a technical deployment — it is a transformation of financial planning and performance management processes.</p><p>A structured approach that includes <strong>Discovery, BRD, Design (FDD/TDD), Configuration, Data Migration, Integration, Testing, Go-Live, and Hypercare</strong> ensures that the platform delivers reliable insights and scalable planning capabilities.</p><p>Organizations that combine strong governance, clear documentation, and disciplined testing practices are far more likely to achieve a smooth implementation and sustained success with Oracle EPM Cloud.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8661739d9012" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Data Loads to Data Architecture: Growing as an Oracle EPM Cloud Integration Professional]]></title>
            <link>https://medium.com/@ram.changalva/from-data-loads-to-data-architecture-growing-as-an-oracle-epm-cloud-integration-professional-9a710f0abf85?source=rss-7352be1e457d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a710f0abf85</guid>
            <dc:creator><![CDATA[Ram Changalva]]></dc:creator>
            <pubDate>Fri, 27 Feb 2026 15:44:30 GMT</pubDate>
            <atom:updated>2026-02-27T15:44:30.733Z</atom:updated>
            <content:encoded><![CDATA[<p>When I first started working with Oracle EPM Cloud, my focus was simple: get the data loaded correctly.</p><p>If the file imported without errors, it felt like success.</p><p>But over time, I realized something important — loading data is the smallest part of the job. The real value comes from how well the integration is designed, automated, secured, and maintained.</p><p>If you’re aiming to grow as an Oracle EPM Data Integration professional, here are a few lessons that genuinely changed how I approach implementations.</p><h3>1. Data Integration Is Not About Files — It’s About Frameworks</h3><p>Anyone can configure an import format and run a data load rule.</p><p>The difference comes when you start asking:</p><ul><li>Can this run without manual intervention?</li><li>Can it scale next year?</li><li>What happens if the source structure changes?</li><li>How quickly can I troubleshoot failures?</li></ul><p>Strong professionals design reusable integration structures. They parameterize rules. They standardize mappings. They document logic. They think ahead.</p><p>The goal isn’t just a successful load today — it’s a sustainable process for the next five years.</p><h3>2. The Integration Agent Changes the Game</h3><p>The first time I implemented the EPM Integration Agent in a hybrid environment, I understood how powerful EPM Cloud could be.</p><p>Instead of waiting for flat files, we connected directly to the on-prem database. Securely. Cleanly. Without opening inbound firewall rules.</p><p>That shift moves you from “file handler” to “pipeline designer.”</p><p>You begin optimizing SQL queries, managing secure credentials, monitoring agent logs, and building true data pipelines between systems.</p><p>That’s a completely different level of ownership.</p><h3>3. Learning REST APIs Is a Career Accelerator</h3><p>There’s a clear before-and-after moment when you start using REST APIs with EPM Cloud.</p><p>Before REST:<br> You log in. You click. You wait. You monitor manually.</p><p>After REST:<br> You trigger jobs programmatically.<br> You monitor job status automatically.<br> You chain processes.<br> You build alerts.</p><p>Once you understand how to execute data rules, business rules, metadata exports, and slice updates through APIs, you stop depending on manual execution. You start designing automation strategies.</p><p>That’s when stakeholders begin to see you differently.</p><h3>4. EPM Should Not Live in Isolation</h3><p>One mistake I see often is treating EPM as a standalone tool.</p><p>In reality, enterprise environments require orchestration — ERP extracts, transformation logic, validation layers, notifications, approvals.</p><p>This is where integration platforms like Oracle Integration Cloud come in. When EPM becomes part of a larger automated flow, finance processes become smoother and more reliable.</p><p>Month-end close becomes predictable.<br> Data movement becomes traceable.<br> Failures become manageable.</p><p>That’s not just technical improvement — that’s operational maturity.</p><h3>5. Automation Is No Longer Optional</h3><p>If you’re still running month-end processes manually, you’re creating risk.</p><p>EPM Automate, Groovy scripting, Python-based REST orchestration, and pipelines allow you to:</p><ul><li>Remove repetitive manual steps</li><li>Standardize deployments across environments</li><li>Implement Dev → Test → Prod promotion flows</li><li>Add validation before calculations</li><li>Reduce human error</li></ul><p>The most valuable consultants I’ve worked with automate everything they can.</p><p>Not because it’s impressive.<br> Because it’s responsible.</p><h3>6. The Biggest Shift Is Mindset</h3><p>The real transformation from beginner to professional isn’t technical — it’s conceptual.</p><p>Beginners focus on:<br> “How do I make this work?”</p><p>Professionals focus on:<br> “How do I make this reliable, secure, scalable, and supportable?”</p><p>They think about:</p><ul><li>Error handling</li><li>Logging</li><li>Performance</li><li>Governance</li><li>Audit requirements</li><li>Documentation</li><li>Future enhancements</li></ul><p>That’s the difference between someone who configures tools and someone who designs solutions.</p><h3>7. What Actually Makes You Market-Ready?</h3><p>In my experience, you know you’re growing when:</p><ul><li>You can design an automated ERP → EPM flow end-to-end</li><li>You understand REST payloads without copying examples blindly</li><li>You can read logs and pinpoint issues quickly</li><li>You build integration processes that survive audits</li><li>You think about deployment strategy, not just configuration</li></ul><p>At that point, you’re not just implementing features.</p><p>You’re contributing to finance transformation.</p><h3>Final Thought</h3><p>Oracle EPM Cloud is powerful. But the real impact doesn’t come from forms or reports — it comes from how intelligently data flows into and through the system.</p><p>If you’re serious about growing in this space:</p><p>Learn APIs deeply.<br> Automate relentlessly.<br> Think architecturally.<br> Stay hands-on.</p><p>And most importantly — build solutions you’d be comfortable supporting yourself.</p><p>That’s what separates a user from a professional.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a710f0abf85" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Export Your Salesforce Data Model to Lucidchart: A Complete Guide]]></title>
            <link>https://medium.com/@ram.changalva/export-your-salesforce-data-model-to-lucidchart-a-complete-guide-d196ebbfafa5?source=rss-7352be1e457d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d196ebbfafa5</guid>
            <dc:creator><![CDATA[Ram Changalva]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 21:45:02 GMT</pubDate>
            <atom:updated>2026-01-06T21:34:57.918Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How to visualize your Salesforce org’s data model with an open-source FastAPI application</em></p><h3>Introduction</h3><p>As Salesforce administrators and developers, we often need to understand the data model of our orgs — especially when working with complex customizations, multiple apps, or when onboarding new team members. Creating Entity Relationship Diagrams (ERDs) manually is time-consuming and error-prone.</p><p>What if you could automatically extract your entire Salesforce data model and import it directly into Lucidchart for beautiful, interactive visualizations?</p><p>In this article, I’ll introduce you to the <strong>Salesforce Data Model Exporter</strong> — a lightweight, open-source FastAPI application that does exactly that. Whether you’re working with Org62, OrgSF, Finance Force, or any custom Salesforce org, this tool can help you generate comprehensive ERD diagrams in minutes.</p><h3>What is the Salesforce Data Model Exporter?</h3><p>The Salesforce Data Model Exporter is a web-based application built with FastAPI and Python that:</p><ul><li>✅ Extracts metadata from any Salesforce org</li><li>✅ Generates CSV files compatible with Lucidchart’s ERD import</li><li>✅ Supports app-specific filtering (extract only objects from a specific app)</li><li>✅ Works with both Password Flow and OAuth2 (MFA support)</li><li>✅ Provides real-time progress tracking</li><li>✅ Integrates with Google Drive for file sharing</li></ul><p>The best part? It’s completely open-source and can be deployed to Heroku in minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*FSZwi2wwH1TfXP2WpeEibA.png" /></figure><h3>Key Features</h3><h3>1. Dual Authentication Methods</h3><p>The application supports two authentication flows:</p><p><strong>Password Flow (No MFA)</strong></p><ul><li>Fast and straightforward</li><li>Perfect for development environments</li><li>Requires appending security token to password</li></ul><p><strong>OAuth2 Flow (MFA Support)</strong></p><ul><li>Full OAuth2 Authorization Code Flow</li><li>Supports Multi-Factor Authentication</li><li>More secure for production use</li><li>Redirects to Salesforce login page for authentication</li></ul><h3>2. Environment Management</h3><p>Switch between environments effortlessly with a dropdown menu:</p><ul><li><strong>DEV</strong>: Development orgs</li><li><strong>STG</strong>: Staging/Sandbox orgs</li><li><strong>PROD</strong>: Production orgs</li></ul><p>The instance URL automatically updates based on your selection.</p><h3>3. App-Specific Extraction</h3><p>One of the most powerful features is the ability to filter by Salesforce app:</p><ul><li>Automatically loads all apps from your Salesforce App Launcher</li><li>Filter metadata extraction by app namespace</li><li>Generated filenames include the app name for easy identification</li><li>Perfect for documenting specific applications or packages</li></ul><h3>4. Real-Time Processing</h3><ul><li>Background task processing (non-blocking)</li><li>Real-time log updates in the web interface</li><li>Progress tracking with object counts</li><li>Ability to terminate long-running processes</li></ul><h3>5. Lucidchart Integration</h3><ul><li>Generates Lucidchart-compatible CSV format</li><li>Direct links to Lucidchart login and document viewing</li><li>Import from desktop or Google Drive</li><li>Beautiful, interactive ERD diagrams</li></ul><h3>Getting Started</h3><h3>Prerequisites</h3><ul><li>Python 3.11 or higher</li><li>A Salesforce org (any edition)</li><li>A Salesforce External Client App (we’ll set this up)</li><li>(Optional) Google Drive account for file sharing</li><li>(Optional) Lucidchart account for ERD visualization</li></ul><h3>Installation</h3><ol><li><strong>Clone the repository:</strong></li></ol><pre>git clone &lt;repository-url&gt;<br>cd sfdc-data-model-exporter</pre><ol><li><strong>Install dependencies:</strong></li></ol><pre>pip install -r requirements.txt</pre><ol><li><strong>Start the application:</strong></li></ol><pre>python main.py</pre><ol><li><strong>Open your browser:</strong> Navigate to <a href="http://localhost:8000/">http://localhost:8000</a></li></ol><h3>Setting Up Salesforce External Client App</h3><p>Before you can use the application, you need to create an External Client App in Salesforce. Here’s how:</p><h3>Step 1: Navigate to Setup</h3><ol><li>Log in to your Salesforce org</li><li>Click the gear icon (⚙️) → <strong>Setup</strong></li></ol><h3>Step 2: Create External Client App</h3><ol><li>In Quick Find, type “External Client Apps”</li><li>Click <strong>External Client Apps</strong> under <strong>Apps</strong></li><li>Click <strong>New External Client App</strong></li></ol><h3>Step 3: Configure OAuth Settings</h3><p><strong>Basic Information:</strong></p><ul><li><strong>External Client App Name</strong>: Salesforce Data Model Exporter</li><li><strong>Contact Email</strong>: Your email</li><li><strong>Description</strong>: (Optional)</li></ul><p><strong>OAuth Settings:</strong></p><ul><li>✅ Check <strong>Enable OAuth Settings</strong></li><li><strong>Callback URL</strong>:</li><li>For local: <a href="http://localhost:8000/salesforce-callback">http://localhost:8000/salesforce-callback</a></li><li>For Heroku: <a href="https://your-app.herokuapp.com/salesforce-callback">https://your-app.herokuapp.com/salesforce-callback</a></li><li><strong>Selected OAuth Scopes</strong>:</li><li>✅ Access and manage your data (api)</li><li>✅ Perform requests on your behalf at any time (refresh_token, offline_access)</li><li>✅ Access your basic information (id, profile, email, address, phone)</li></ul><p><strong>Important Settings:</strong></p><ul><li>✅ <strong>Require Secret for Web Server Flow</strong>: Checked</li><li>❌ <strong>Require PKCE for Authorization Code Flow</strong>: <strong>Unchecked</strong> (critical!)</li></ul><h3>Step 4: Get Your Credentials</h3><p>After saving:</p><ol><li>Go to <strong>Manager</strong> → <strong>OAuth Settings</strong></li><li>Copy the <strong>Consumer Key</strong> (Client ID)</li><li>Click <strong>Reveal</strong> and copy the <strong>Consumer Secret</strong> (Client Secret)</li></ol><h3>Using the Application</h3><h3>Step 1: Choose Your Authentication Method</h3><p><strong>For Password Flow:</strong></p><ul><li>Select “Password Flow (No MFA)”</li><li>Enter your username and password + security token</li><li>Click “Login &amp; Load Apps”</li></ul><p><strong>For OAuth2 Flow (Recommended for MFA):</strong></p><ul><li>Select “OAuth2 Flow (Supports MFA)”</li><li>Enter Client ID and Client Secret</li><li>Click “Login &amp; Load Apps”</li><li>You’ll be redirected to Salesforce for authentication</li><li>Enter MFA code if prompted</li><li>You’ll be redirected back automatically</li></ul><h3>Step 2: Select Environment</h3><p>Choose your environment from the dropdown:</p><ul><li><strong>DEV</strong>: Development org</li><li><strong>STG</strong>: Staging/Sandbox</li><li><strong>PROD</strong>: Production</li></ul><p>The instance URL updates automatically.</p><h3>Step 3: Select an App (Optional)</h3><p>After authentication, all apps from your App Launcher are loaded:</p><ul><li>Select a specific app to filter objects by that app’s namespace</li><li>Or select “All Objects (No Filter)” to extract everything</li></ul><p><strong>Pro Tip</strong>: App-specific extraction is perfect for documenting individual applications or packages. The generated filename will include the app name.</p><h3>Step 4: Start Extraction</h3><ol><li>Click <strong>“Retrieve Selected App Data Model”</strong></li><li>Monitor progress in the log output</li><li>Wait for completion (this may take several minutes for large orgs)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/1*k156l8x59vEDcmrQFUVRcw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mTmXC0ZcFTaQUB3IlOsPBw.png" /></figure><h3>Step 5: Download or Share</h3><p>After extraction:</p><ul><li><strong>Download Metadata CSV</strong>: Raw metadata file</li><li><strong>Download Lucidchart CSV</strong>: Ready for Lucidchart import</li><li><strong>Upload to Google Drive</strong>: Share with your team</li></ul><h3>Step 6: Import to Lucidchart</h3><ol><li>Download the Lucidchart CSV file</li><li>Go to Lucidchart</li><li>Click <strong>Import</strong> → <strong>ERD</strong> → <strong>Import from CSV</strong></li><li>Upload the file</li><li>Your ERD diagram is ready! 🎉</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/434/1*svyh9zIOsMw1x7jBp82clA.png" /></figure><h3>Real-World Use Cases</h3><h3>1. Documenting Custom Applications</h3><p>When building or maintaining custom Salesforce applications, you need to document the data model. With app-specific extraction:</p><ul><li>Extract only objects related to your app</li><li>Generate ERD diagrams for documentation</li><li>Include app name in filenames for easy organization</li></ul><h3>2. Onboarding New Team Members</h3><p>New developers or administrators can quickly understand the org structure:</p><ul><li>Generate comprehensive ERD diagrams</li><li>Visualize relationships between objects</li><li>Understand customizations at a glance</li></ul><h3>3. Auditing and Compliance</h3><p>For compliance and auditing purposes:</p><ul><li>Document current data model state</li><li>Track changes over time (by generating ERDs periodically)</li><li>Share visualizations with stakeholders</li></ul><h3>4. Package Development</h3><p>When developing managed packages:</p><ul><li>Extract only package objects</li><li>Document package data model</li><li>Include in package documentation</li></ul><h3>Advanced Features</h3><h3>Environment-Specific Configuration</h3><p>The application supports environment-specific instance URLs:</p><pre># Automatically set based on DEPLOYMENT_ENV<br>DEV:  https://your-dev-org.my.salesforce.com<br>STG:  https://test.salesforce.com<br>PROD: https://login.salesforce.com</pre><p>Set the environment variable:</p><pre>export DEPLOYMENT_ENV=&quot;PROD&quot;</pre><h3>Pre-filling Credentials</h3><p>For convenience, you can pre-fill Client ID and Client Secret:</p><pre>export SALESFORCE_CLIENT_ID=&quot;your-consumer-key&quot;<br>export SALESFORCE_CLIENT_SECRET=&quot;your-consumer-secret&quot;</pre><p>These will appear in the form automatically (but can still be overridden).</p><h3>Sign Out Functionality</h3><p>After authentication, a “Sign Out” button appears:</p><ul><li>Clears all session data</li><li>Resets the form</li><li>Perfect for switching between orgs or users</li></ul><h3>Deployment to Heroku</h3><p>Deploying to Heroku is straightforward:</p><h3>1. Create Heroku App</h3><pre>heroku create your-app-name</pre><h3>2. Set Environment Variables</h3><pre>heroku config:set SALESFORCE_CLIENT_ID=&quot;your-key&quot;<br>heroku config:set SALESFORCE_CLIENT_SECRET=&quot;your-secret&quot;<br>heroku config:set DEPLOYMENT_ENV=&quot;PROD&quot;</pre><h3>3. Deploy</h3><pre>git push heroku main</pre><h3>4. Update Salesforce Callback URL</h3><p>Don’t forget to add your Heroku callback URL to Salesforce:</p><ul><li><a href="https://your-app-name.herokuapp.com/salesforce-callback">https://your-app-name.herokuapp.com/salesforce-callback</a></li></ul><h3>Architecture Overview</h3><p>The application is built with a clean, modular architecture:</p><pre>sfdc-data-model-exporter/<br>├── main.py                    # FastAPI application<br>├── config.py                  # Configuration management<br>├── models.py                  # Data models<br>├── exceptions.py              # Custom exceptions<br>├── services/<br>│   ├── salesforce_service.py  # Salesforce API integration<br>│   ├── file_service.py        # CSV generation<br>│   ├── google_drive_service.py<br>│   └── lucidchart_service.py<br>└── templates/                 # Jinja2 templates</pre><p><strong>Key Design Decisions:</strong></p><ul><li><strong>Service Layer</strong>: Separates business logic from API routes</li><li><strong>Background Tasks</strong>: Long-running extractions don’t block the web server</li><li><strong>Real-time Logging</strong>: Process logs stored in memory for instant updates</li><li><strong>Type Hints</strong>: Full type annotation for better code quality</li></ul><h3>Technical Highlights</h3><h3>1. Salesforce UI API Integration</h3><p>The application uses Salesforce’s User Interface API to fetch all apps from the App Launcher:</p><pre>ui_api_url = f&quot;{instance_url}/services/data/v{version}/ui-api/apps?formFactor=Large&quot;</pre><p>This ensures you see all apps exactly as they appear in Salesforce.</p><h3>2. Namespace Filtering</h3><p>For app-specific extraction, objects are filtered by namespace prefix:</p><pre>if namespace_prefix:<br>    filtered_objects = [<br>        obj for obj in objects <br>        if obj.get(&#39;name&#39;, &#39;&#39;).startswith(f&quot;{namespace_prefix}__&quot;)<br>    ]</pre><h3>3. Lucidchart CSV Format</h3><p>The application generates CSV files in Lucidchart’s ERD import format:</p><ul><li>Table definitions</li><li>Column details</li><li>Relationships</li><li>Data types</li></ul><h3>Troubleshooting</h3><h3>Common Issues and Solutions</h3><p><strong>“redirect_uri_mismatch” Error:</strong></p><ul><li>Ensure callback URL is configured in Salesforce External Client App</li><li>URL must match exactly (including protocol and port)</li><li>Wait 2–10 minutes after updating</li></ul><p><strong>“missing required code challenge” Error:</strong></p><ul><li>Disable “Require PKCE for Authorization Code Flow” in Salesforce settings</li><li>This application doesn’t use PKCE</li></ul><p><strong>No Apps in Dropdown:</strong></p><ul><li>Verify authentication was successful</li><li>Check user permissions</li><li>Try refreshing and re-authenticating</li></ul><p><strong>No Objects for Selected App:</strong></p><ul><li>Apps without namespace extract all objects (standard Salesforce apps)</li><li>Apps with namespace only extract objects with that namespace prefix</li><li>Verify the app has custom objects</li></ul><h3>Best Practices</h3><p><strong>Use OAuth2 Flow for Production</strong></p><ul><li>More secure</li><li>Supports MFA</li><li>Better for enterprise environments</li></ul><p><strong>App-Specific Extraction</strong></p><ul><li>Use when documenting specific applications</li><li>Reduces file size and processing time</li><li>Makes ERD diagrams more focused</li></ul><p><strong>Regular Documentation</strong></p><ul><li>Generate ERDs periodically</li><li>Track changes over time</li><li>Version control your ERD files</li></ul><p><strong>Environment Variables</strong></p><ul><li>Use environment variables for credentials</li><li>Never commit credentials to version control</li><li>Use different credentials for different environments</li></ul><h3>Conclusion</h3><p>The Salesforce Data Model Exporter is a powerful tool for anyone working with Salesforce orgs. Whether you’re documenting custom applications, onboarding team members, or auditing your data model, this application makes the process fast and efficient.</p><p><strong>Key Takeaways:</strong></p><ul><li>✅ Extract data models from any Salesforce org</li><li>✅ Generate Lucidchart-compatible ERD diagrams</li><li>✅ Filter by app for focused documentation</li><li>✅ Support for both Password Flow and OAuth2</li><li>✅ Easy deployment to Heroku</li><li>✅ Open-source and customizable</li></ul><p><strong>Next Steps:</strong></p><ol><li>Clone the repository</li><li>Set up your Salesforce External Client App</li><li>Start extracting and visualizing your data models!</li></ol><h3>Resources</h3><ul><li><strong>GitHub Repository</strong>: <a href="https://github.com/ramchangalva-salesforce/sfdc-data-model-exporter">sfdc-data-model-exporter</a></li><li><strong>Salesforce API Documentation</strong>: <a href="https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/">https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/</a></li><li><strong>Lucidchart ERD Import</strong>: <a href="https://www.lucidchart.com/pages/erd">https://www.lucidchart.com/pages/erd</a></li><li><strong>FastAPI Documentation</strong>: <a href="https://fastapi.tiangolo.com/">https://fastapi.tiangolo.com/</a></li></ul><p><em>Have questions or suggestions? Leave a comment below or contribute to the project on GitHub!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d196ebbfafa5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Deploy MuleSoft RPA Builder, Recorder & Bot on AWS Windows Server using Terraform]]></title>
            <link>https://medium.com/@ram.changalva/deploy-mulesoft-rpa-builder-recorder-bot-on-aws-windows-server-using-terraform-b72f3e6fa0bd?source=rss-7352be1e457d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b72f3e6fa0bd</guid>
            <category><![CDATA[aws-ec2-windows-instance]]></category>
            <category><![CDATA[mulesoft-rpa]]></category>
            <dc:creator><![CDATA[Ram Changalva]]></dc:creator>
            <pubDate>Thu, 09 Oct 2025 18:45:51 GMT</pubDate>
            <atom:updated>2025-10-09T19:05:37.861Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uOTkAUi9WU8rAqdsSgnMLg.png" /></figure><h3>🧩 Introduction</h3><p>As MuleSoft developers, we often need an isolated, always-available Windows environment to run <strong>MuleSoft RPA Builder</strong>, <strong>Recorder</strong>, and <strong>Bot</strong> components — — especially for enterprise-scale automation projects.</p><p>In this article, we’ll walk through <strong>step-by-step instructions</strong> to:</p><ol><li>Provision a Windows EC2 instance on AWS using <strong>Terraform</strong>\</li><li>Connect to it via RDP\</li><li>Install and configure <strong>MuleSoft RPA Builder</strong>, <strong>Recorder</strong>, and <strong>Bot</strong>\</li><li>Optionally automate the full setup</li></ol><p>By the end, you’ll have a working RPA workstation or bot environment ready to integrate with your <strong>MuleSoft RPA Manager</strong> instance.</p><h3>🧰 Prerequisites</h3><p>Before you start, make sure you have:</p><p><strong>Requirement</strong></p><ol><li>AWS Account</li><li>Terraform CLI</li><li>AWS Credentials</li><li>Windows AMI ID</li><li>RPA Manager Access.RPA Builder, Recorder, and Bot installers</li><li>RDP Client</li></ol><p>👉 <strong>Note:</strong> MuleSoft RPA requires .NET Framework 4.5+, administrative rights, and specific write-access paths (Documents, AppData, ProgramData).</p><h3>🔑 AWS Account Setup</h3><p>Before running the Terraform scripts, you <strong>must have an active AWS account</strong>. Terraform uses your AWS credentials to create and manage resources like VPCs, subnets, and EC2 instances.</p><h3>🧾 Why You Need It</h3><p>Terraform communicates directly with AWS APIs to provision infrastructure. Without an AWS account, it cannot authenticate or deploy any resources.</p><h3>🧰 Setup Checklist</h3><p><strong>Steps:</strong></p><p>1️⃣<strong>Create an AWS Account</strong> at <a href="https://aws.amazon.com/">https://aws.amazon.com</a> Required to use AWS services</p><p>2️⃣<strong>Sign in to the AWS Console</strong> and create an <strong>IAM User</strong> (e.g., terraform-user)Used by Terraform to deploy resources</p><p>3️⃣<strong>Attach IAM Policies</strong> such as AmazonEC2FullAccess, AmazonVPCFullAccess, and IAMFullAccess <em>(for testing — restrict later)</em>Grants Terraform permission to create AWS resources</p><p>4️⃣<strong>Generate Access Keys</strong> (Access Key ID &amp; Secret Access Key)Credentials Terraform uses to authenticate</p><p>✅ Once your account and credentials are configured, you’re ready to run Terraform to deploy your Windows EC2 instance.</p><h3>Install Terraform on Windows</h3><ol><li><strong>Download Terraform</strong></li></ol><ul><li>Visit: <a href="https://developer.hashicorp.com/terraform/downloads">Terraform Downloads</a></li><li>Download the Windows 64-bit ZIP file.</li></ul><p><strong>2. Extract the ZIP</strong></p><ul><li>Extract the contents to a folder, e.g., C:\Terraform.</li></ul><p><strong>3. Add Terraform to System PATH</strong></p><h3>☁️ Step 1: Create the AWS Windows Server with Terraform</h3><h3>1.1 Folder Structure</h3><p>Create folder rpa-aws-windows and create the list of terraform files in the folder. Use visual studio code</p><pre>rpa-aws-windows/<br>├── providers.tf<br>├── variables.tf<br>├── network.tf<br>├── security.tf<br>├── instance.tf<br>└── outputs.tf</pre><h3>1.2 providers.tf</h3><pre>terraform {<br>  required_providers {<br>    aws = {<br>      source  = &quot;hashicorp/aws&quot;<br>      version = &quot;~&gt; 4.16&quot;<br>    }<br>  }<br>}<br><br>provider &quot;aws&quot; {<br>  region     = &quot;us-east-2&quot;<br>  access_key = &quot;&quot;  # Add your AWS access key<br>  secret_key = &quot;&quot;  # Add your AWS secret key<br>}<br><br>resource &quot;tls_private_key&quot; &quot;rsa_4096&quot; {<br>  algorithm = &quot;RSA&quot;<br>  rsa_bits  = 4096<br>}<br><br>resource &quot;aws_key_pair&quot; &quot;key_pair&quot; {<br>  key_name   = var.key_name<br>  public_key = tls_private_key.rsa_4096.public_key_openssh<br>}<br><br>resource &quot;local_file&quot; &quot;private_key&quot; {<br>  content  = tls_private_key.rsa_4096.private_key_pem<br>  filename = &quot;${var.key_name}.pem&quot;<br>}</pre><h3>1.3 variables.tf</h3><pre>variable &quot;aws_region&quot; {<br>  default = &quot;us-east-2&quot;<br>}<br><br>variable &quot;vpc_cidr&quot; {<br>  default = &quot;10.0.0.0/16&quot;<br>}<br><br>variable &quot;public_subnet_cidr&quot; {<br>  default = &quot;10.0.1.0/24&quot;<br>}<br><br>variable &quot;instance_type&quot; {<br>  default = &quot;t3.micro&quot;<br>}<br><br>variable &quot;windows_ami_id&quot; {<br>  description = &quot;Windows AMI ID (leave empty to auto-select latest)&quot;<br>  default     = &quot;ami-0684b1bd72f4b0d55&quot;<br>}<br><br>variable &quot;rdp_source_cidr&quot; {<br>  description = &quot;CIDR to allow RDP (restrict to your IP)&quot;<br>  default     = &quot;0.0.0.0/0&quot;<br>}<br><br>variable &quot;key_name&quot; {<br>  description = &quot;Name of the SSH key pair&quot;<br>  type        = string<br>}</pre><h3>1.4 network.tf</h3><pre>resource &quot;aws_vpc&quot; &quot;main&quot; {<br>  cidr_block           = var.vpc_cidr<br>  enable_dns_hostnames = true<br>}<br><br>resource &quot;aws_internet_gateway&quot; &quot;igw&quot; {<br>  vpc_id = aws_vpc.main.id<br>}<br><br>resource &quot;aws_subnet&quot; &quot;public&quot; {<br>  vpc_id                  = aws_vpc.main.id<br>  cidr_block              = var.public_subnet_cidr<br>  map_public_ip_on_launch = true<br>}<br><br>resource &quot;aws_route_table&quot; &quot;public&quot; {<br>  vpc_id = aws_vpc.main.id<br>}<br><br>resource &quot;aws_route&quot; &quot;default&quot; {<br>  route_table_id         = aws_route_table.public.id<br>  destination_cidr_block = &quot;0.0.0.0/0&quot;<br>  gateway_id             = aws_internet_gateway.igw.id<br>}<br><br>resource &quot;aws_route_table_association&quot; &quot;assoc&quot; {<br>  subnet_id      = aws_subnet.public.id<br>  route_table_id = aws_route_table.public.id<br>}</pre><h3>1.5 security.tf</h3><pre>resource &quot;aws_security_group&quot; &quot;rpa_sg&quot; {<br>  name        = &quot;rpa-windows-sg&quot;<br>  description = &quot;Allow RDP&quot;<br>  vpc_id      = aws_vpc.main.id<br><br>  ingress {<br>    from_port   = 3389<br>    to_port     = 3389<br>    protocol    = &quot;tcp&quot;<br>    cidr_blocks = [var.rdp_source_cidr]<br>  }<br><br>  egress {<br>    from_port   = 0<br>    to_port     = 0<br>    protocol    = &quot;-1&quot;<br>    cidr_blocks = [&quot;0.0.0.0/0&quot;]<br>  }<br>}</pre><h3>1.6 instance.tf</h3><pre>data &quot;aws_ami&quot; &quot;windows&quot; {<br>  most_recent = true<br>  filter {<br>    name   = &quot;name&quot;<br>    values = [&quot;Windows_Server-2022-English-Full-Base-*&quot;]<br>  }<br>  owners = [&quot;amazon&quot;]<br>}<br><br>resource &quot;aws_instance&quot; &quot;rpa_win&quot; {<br>  ami                         = var.windows_ami_id != &quot;&quot; ? var.windows_ami_id : data.aws_ami.windows.id<br>  instance_type               = var.instance_type<br>  subnet_id                   = aws_subnet.public.id<br>  vpc_security_group_ids      = [aws_security_group.rpa_sg.id]<br>  associate_public_ip_address = true<br>  key_name                    = aws_key_pair.key_pair.key_name<br>  tags = {<br>    Name = &quot;mulesoft-rpa-server&quot;<br>  }<br>}</pre><h3>1.7 outputs.tf</h3><pre>output &quot;public_ip&quot; {<br>  value = aws_instance.rpa_win.public_ip<br>}</pre><h3>1.8 Deploy Infrastructure</h3><p>Run the below terraform commands one after other.</p><pre>terraform init<br>terraform plan<br>terraform apply -auto-approve</pre><p>After completion, Terraform outputs the public IP address for RDP access.</p><h3>🖥️ Step 2: Connect to Your Windows Server</h3><h3>1. Get the Public IP or DNS</h3><ul><li>Go to the AWS Console.</li><li>Select your EC2 instance.</li><li>Find the Public IP or Public DNS in the instance details.</li></ul><h3>2. Get the Administrator Password</h3><ul><li>In the AWS Console, select your instance.</li><li>Click <strong>Connect</strong> &gt; <strong>RDP client</strong>.</li><li>Click <strong>Get Password</strong>.</li><li>Upload your private key file (e.g., rpamuley.pem).</li><li>Click <strong>Decrypt Password</strong> to reveal the Administrator password.</li></ul><h3>3. Connect Using Remote Desktop (RDP)</h3><ul><li>Open the Remote Desktop app on your computer.</li><li>Enter the Public IP or DNS.</li><li>Username: Administrator</li><li>Password: (the decrypted password from step 2)</li></ul><h3>🤖 Step 3: Install MuleSoft RPA Components</h3><h3>RPA Builder</h3><ol><li>Download from RPA Manager\</li><li>Run installer as Administrator\</li><li>Configure repository: <strong>RPA Manager URL</strong>, username, password\</li><li>Test connection</li></ol><h3>RPA Recorder</h3><ol><li>Download and install from RPA Manager\</li><li>Launch Recorder and test sample recording</li></ol><h3>RPA Bot</h3><ol><li>Download installer from RPA Manager\</li><li>During setup, provide RPA Manager URL, Bot Name, and API Key\</li><li>Verify registration in RPA Manager → <em>Bots</em></li></ol><h3>🧠 Step 4: Validation Checklist</h3><p>✅ Confirm RDP access works\ ✅ RPA Builder connects to RPA Manager\ ✅ Recorder captures UI actions\ ✅ Bot executes assigned processes</p><h3>🔐 Best Practices</h3><ul><li>Restrict RDP to corporate IP ranges\</li><li>Store secrets securely in AWS Secrets Manager\</li><li>Keep Terraform state in S3 with locking\</li><li>Regularly patch Windows\</li><li>Validate RPA installers’ checksum before automation</li></ul><h3>🏁 Conclusion</h3><p>You’ve now successfully automated the creation of a Windows environment and installed MuleSoft RPA components using Terraform! 🎉</p><p>This repeatable IaC-driven approach ensures consistent, secure RPA infrastructure across development and production environments.</p><h3>References</h3><ul><li><a href="https://docs.mulesoft.com/rpa-builder/latest/install-and-configure">MuleSoft RPA Builder Docs</a></li><li><a href="https://docs.mulesoft.com/rpa-bot/latest/installation">MuleSoft RPA Bot Installation</a></li><li><a href="https://registry.terraform.io/providers/hashicorp/aws/latest/docs">Terraform AWS Provider</a></li><li><a href="https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/">AWS EC2 Windows Guide</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b72f3e6fa0bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Apache Airflow and Its Architecture]]></title>
            <link>https://medium.com/@ram.changalva/introduction-to-apache-airflow-and-its-architecture-579626853827?source=rss-7352be1e457d------2</link>
            <guid isPermaLink="false">https://medium.com/p/579626853827</guid>
            <category><![CDATA[apache-airflow]]></category>
            <dc:creator><![CDATA[Ram Changalva]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 22:14:06 GMT</pubDate>
            <atom:updated>2025-01-27T22:52:09.225Z</atom:updated>
            <content:encoded><![CDATA[<p>Apache Airflow is an open-source platform for orchestrating workflows through code. Its powerful architecture ensures reliability, scalability, and flexibility in managing complex workflows. To fully understand its functionality, let’s first explore its architectural components.</p><h3>Key Architectural Components of Airflow</h3><ol><li><strong>Scheduler</strong><br>The Scheduler is responsible for orchestrating the execution of tasks within a DAG. It reads the DAGs, identifies their task dependencies, and determines when tasks are ready to run based on their schedule and state. The Scheduler continuously monitors the state of the workflows and ensures tasks are queued for execution.</li><li><strong>Executor</strong><br>The Executor is the component that manages task execution. It works in conjunction with the Scheduler to run tasks either locally or on distributed systems, depending on the configured execution backend. Common executors include SequentialExecutor,LocalExecutor,CeleryExecutor,KubernetesExecutor</li><li><strong>Metadata Database</strong><br>The metadata database stores all essential information about DAGs, task instances, and their states. It acts as the central repository for Airflow, ensuring persistence and allowing the platform to track workflow execution history. Popular databases like MySQL, PostgreSQL, and SQLite can be used for this purpose.</li><li><strong>Web Server</strong><br>The Web Server provides an intuitive user interface for managing workflows. Through the UI, users can:</li></ol><ul><li>View DAGs and their statuses.</li><li>Monitor task execution in real-time.</li><li>Trigger DAGs manually or adjust their schedules.</li><li>Access logs for debugging and performance tuning.</li></ul><p>The Web Server is built using Flask and serves as the central point for user interaction with Airflow.</p><ol><li><strong>Worker Nodes</strong><br>In distributed setups, Worker Nodes handle the execution of tasks. They receive instructions from the Executor and perform the actual work, such as running Python functions, executing scripts, or transferring data. Workers ensure scalability by distributing tasks across multiple nodes.</li><li><strong>DAGs (Directed Acyclic Graphs)</strong><br>DAGs are the backbone of Airflow workflows. They define the tasks and their execution order, expressed as Python code. Each DAG represents a complete workflow, and its tasks are executed in a topological order, respecting dependencies.</li><li><strong>Task Instances</strong><br>A Task Instance is a specific run of a task within a DAG. It has a unique state (e.g., running, failed, or succeeded) and metadata that allows Airflow to monitor and manage its execution. Task instances are tied to DAG runs and ensure workflows can recover from failures or rerun specific tasks.</li></ol><h3>How These Components Work Together</h3><ul><li><strong>Workflow Definition</strong>: Users define workflows as code (DAGs) and save them in a specified directory.</li><li><strong>Scheduling</strong>: The Scheduler scans the DAG directory and decides when tasks should run based on the defined schedules.</li><li><strong>Execution</strong>: The Executor distributes tasks to workers, which perform the actual work.</li><li><strong>Tracking</strong>: Task states and metadata are stored in the database, providing visibility into workflow execution.</li><li><strong>Monitoring</strong>: The Web Server offers a graphical interface for monitoring DAGs and managing workflows interactively.</li></ul><p>By combining these components, Apache Airflow delivers a robust, modular system for orchestrating workflows in diverse environments, from small projects to enterprise-scale data pipelines.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=579626853827" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mule Standalone Runtime Setup and Deployment]]></title>
            <link>https://medium.com/@ram.changalva/mule-standalone-runtime-setup-and-deployment-2f44d996bd45?source=rss-7352be1e457d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f44d996bd45</guid>
            <dc:creator><![CDATA[Ram Changalva]]></dc:creator>
            <pubDate>Wed, 29 May 2024 20:34:27 GMT</pubDate>
            <atom:updated>2024-05-29T21:52:23.036Z</atom:updated>
            <content:encoded><![CDATA[<h3>Steps to Configure Mule Runtime Instance on Standalone Server</h3><ol><li>Download Mule 4 standalone from <a href="https://www.mulesoft.com/lp/dl/anypoint-mule-studio">https://www.mulesoft.com/lp/dl/anypoint-mule-studio</a></li><li>Extract download ZIP file on the location where you want to configure the Mule instance.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fh3E4p41s_d6HjsSTNAPJw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*KQ8C7crVM1V_S8umXIX1OA.png" /></figure><h3>Add Mule Server to Runtime Manager</h3><p>From Anypoint Platform, select <strong>Runtime Manager</strong>.</p><ol><li>Click <strong>Servers</strong> in the left menu.</li><li>Click the <strong>Add Server</strong> button.</li><li>Enter a name for your server.</li><li>Click the <strong>Copy command</strong> to copy the amc_setup command.</li></ol><p>Open a command window, change to the $MULE_HOME/bin directory for the Mule instance that you’re registering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*l60hPAOpkw21zDDcNjafkQ.png" /></figure><p>Run the command copied from the runtime manager and execute</p><p>C:\mule-enterprise-standalone-4.6.3\bin&gt;amc_setup -H 6481b76c-eaaa-430b-bf52–2786fed2b928 — -1018678 ramch-standalone-server</p><h3>Installation Started</h3><pre>--<br><br>Mule Agent Installer<br> - - - - - - - - - - - - - - -<br>For help please run the script with - help option<br>INFO: MULE_HOME is set as C:\mule-enterprise-standalone-4.6.3<br>-&gt; Unpacking Mule Agent …<br>Creating: lib/ len 0 added 04/16/24<br> Creating: META-INF/ len 0 added 04/16/24<br> Creating: META-INF/maven/ len 0 added 04/16/24<br> Creating: META-INF/maven/com.mulesoft.agent/ len 0 added 04/16/24<br> Creating: META-INF/maven/com.mulesoft.agent/mule-agent-plugin/ len 0 added 04/16/24<br> Creating: META-INF/mule-artifact/ len 0 added 04/16/24<br> Creating: META-INF/sisu/ len 0 added 04/16/24<br> Creating: META-INF/services/ len 0 added 04/16/24<br> Creating: com/ len 0 added 04/16/24<br> Creating: com/mulesoft/ len 0 added 04/16/24<br> Creating: com/mulesoft/agent/ len 0 added 04/16/24<br> Creating: com/mulesoft/agent/configuration/ len 0 added 04/16/24<br> Creating: com/mulesoft/agent/configuration/guice/ len 0 added 04/16/24<br> Creating: lib/kotlin-stdlib-jdk8–1.6.20.jar len -1 added 04/16/24<br> Creating: lib/hk2-locator-2.6.1.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-log-gw-http-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jersey-container-servlet-core-2.39.1.jar len -1 added 04/16/24<br> Creating: lib/jjwt-api-0.11.5.jar len -1 added 04/16/24<br> Creating: lib/netty-transport-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-analytics-event-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/grizzly-websockets-2.3.34.jar len -1 added 04/16/24<br> Creating: lib/jackson-databind-2.16.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-plugin-file-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-artifact-validation-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-utils-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/netty-handler-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/jersey-client-2.39.1.jar len -1 added 04/16/24<br> Creating: lib/jetty-io-9.4.53.v20231009.jar len -1 added 04/16/24<br> Creating: lib/joda-time-2.9.1.jar len -1 added 04/16/24<br> Creating: lib/splunk-1.6.4.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-ingest-publisher-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/minlog-1.3.1.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-messagehistory-event-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-logging-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/javax.inject-1.jar len -1 added 04/16/24<br> Creating: lib/netty-resolver-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-value-provider-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-installer-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/javax.servlet-api-3.1.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-db-gw-http-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-scheduling-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/checker-qual-3.33.0.jar len -1 added 04/16/24<br> Creating: lib/annotations-13.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-websocket-jersey2–2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-domain-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/commons-cli-1.4.jar len -1 added 04/16/24<br> Creating: lib/mule-module-logging-4.6.2.jar len -1 added 04/16/24<br> Creating: lib/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar len -1 added 04/16/24<br> Creating: lib/log4j-slf4j2-impl-2.20.0.jar len -1 added 04/16/24<br> Creating: lib/commons-lang-2.4.jar len -1 added 04/16/24<br> Creating: lib/reactive-streams-1.0.3.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-signature-validator-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jjwt-impl-0.11.5.jar len -1 added 04/16/24<br> Creating: lib/jul-to-slf4j-2.0.7.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-properties-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jersey-server-2.39.1.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-web-interface-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-configurable-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/slf4j-api-1.7.30.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-graphite-publisher-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-http-event-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jcl-over-slf4j-2.0.7.jar len -1 added 04/16/24<br> Creating: lib/jackson-annotations-2.16.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-application-properties-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/aws-java-sdk-cloudwatch-1.12.674.jar len -1 added 04/16/24<br> Creating: lib/jsr305–3.0.2.jar len -1 added 04/16/24<br> Creating: lib/guava-32.0.1-jre.jar len -1 added 04/16/24<br> Creating: lib/mule-module-log4j-boot-configurator-4.6.2.jar len -1 added 04/16/24<br> Creating: lib/aws-java-sdk-core-1.12.674.jar len -1 added 04/16/24<br> Creating: lib/j2objc-annotations-2.8.jar len -1 added 04/16/24<br> Creating: lib/kotlin-stdlib-jdk7–1.6.20.jar len -1 added 04/16/24<br> Creating: lib/plexus-utils-3.3.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-metadata-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/commons-collections-3.2.2.jar len -1 added 04/16/24<br> Creating: lib/jersey-entity-filtering-2.39.1.jar len -1 added 04/16/24<br> Creating: lib/jetty-client-9.4.53.v20231009.jar len -1 added 04/16/24<br> Creating: lib/jackson-module-jaxb-annotations-2.14.1.jar len -1 added 04/16/24<br> Creating: lib/netty-common-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/jackson-dataformat-cbor-2.12.6.jar len -1 added 04/16/24<br> Creating: lib/okio-jvm-3.4.0.jar len -1 added 04/16/24<br> Creating: lib/mule-module-boot-ee-4.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-modules-common-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jackson-core-2.16.0.jar len -1 added 04/16/24<br> Creating: META-INF/maven/com.mulesoft.agent/mule-agent-plugin/pom.xml len -1 added 04/16/24<br> Creating: META-INF/mule-artifact/mule-artifact.json len -1 added 04/16/24<br> Creating: META-INF/sisu/javax.inject.Named len -1 added 04/16/24<br> Creating: META-INF/services/com.mulesoft.agent.configuration.guice.ModuleProvider len -1 added 04/16/24<br> Creating: com/mulesoft/agent/AgentServiceLifecycleManager$Callback.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/AgentPlugin$2.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/AgentServiceLifecycleManager.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/AgentServiceLifecycleManager$LifecycleStage.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/AgentPlugin$3.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/AgentPlugin.class len -1 added 04/16/24<br> Creating: lib/netty-transport-native-unix-common-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/netty-codec-socks-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/aopalliance-1.0.jar len -1 added 04/16/24<br> Creating: lib/hk2-utils-2.6.1.jar len -1 added 04/16/24<br> Creating: lib/kotlin-stdlib-1.6.20.jar len -1 added 04/16/24<br> Creating: lib/okhttp-4.11.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-plugin-websocket-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/spring-jcl-5.3.33.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-runtime-configuration-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/commons-logging-1.2.jar len -1 added 04/16/24<br> Creating: lib/netty-transport-native-epoll-4.1.104.Final-linux-x86_64.jar len -1 added 04/16/24<br> Creating: lib/netty-buffer-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/jakarta.xml.bind-api-2.3.3.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-splunk-gw-http-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/bcutil-jdk15to18–1.74.jar len -1 added 04/16/24<br> Creating: lib/jersey-media-multipart-2.39.1.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-tooling-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-extensions-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/snakeyaml-2.0.jar len -1 added 04/16/24<br> Creating: lib/java-uuid-generator-3.1.3.jar len -1 added 04/16/24<br> Creating: lib/org.eclipse.sisu.inject-0.3.5.jar len -1 added 04/16/24<br> Creating: lib/reflectasm-1.11.9.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-messagehistory-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-action-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jetty-http-9.4.53.v20231009.jar len -1 added 04/16/24<br> Creating: lib/jetty-security-9.4.53.v20231009.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-monitoring-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-api-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-health-check-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/error_prone_annotations-2.18.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-client-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-tracking-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jetty-servlet-9.4.53.v20231009.jar len -1 added 04/16/24<br> Creating: lib/mule-runtime-event-model-1.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-configuration-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/log4j-api-2.22.1.jar len -1 added 04/16/24<br> Creating: lib/hk2-api-2.6.1.jar len -1 added 04/16/24<br> Creating: lib/mule-module-jpms-utils-4.6.2.jar len -1 added 04/16/24<br> Creating: lib/kotlin-stdlib-common-1.6.20.jar len -1 added 04/16/24<br> Creating: lib/osgi-resource-locator-1.0.3.jar len -1 added 04/16/24<br> Creating: lib/jersey-media-json-jackson-2.39.1.jar len -1 added 04/16/24<br> Creating: lib/servo-core-0.12.22.jar len -1 added 04/16/24<br> Creating: lib/bigqueue-0.7.0.jar len -1 added 04/16/24<br> Creating: lib/grizzly-framework-2.3.34.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-db-event-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/netty-codec-http-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/jjwt-gson-0.11.5.jar len -1 added 04/16/24<br> Creating: lib/commons-codec-1.14.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-splunk-event-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jetty-util-9.4.53.v20231009.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-cloudwatch-publisher-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/async-http-client-netty-utils-2.12.3.jar len -1 added 04/16/24<br> Creating: lib/netty-transport-classes-epoll-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/javax.ws.rs-api-2.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-log-event-tracker-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/logging-interceptor-4.11.0.jar len -1 added 04/16/24<br> Creating: lib/tape-1.2.2.jar len -1 added 04/16/24<br> Creating: lib/bcprov-jdk15to18–1.74.jar len -1 added 04/16/24<br> Creating: lib/commons-lang3–3.4.jar len -1 added 04/16/24<br> Creating: lib/mule-module-boot-api-4.6.2.jar len -1 added 04/16/24<br> Creating: lib/kryo-5.5.0.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-administration-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/grizzly-http-2.3.34.jar len -1 added 04/16/24<br> Creating: lib/keystore-generator.jar len -1 added 04/16/24<br> Creating: lib/jersey-container-servlet-2.39.1.jar len -1 added 04/16/24<br> Creating: lib/jakarta.inject-2.6.1.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-gw-analytics-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jersey-common-2.39.1.jar len -1 added 04/16/24<br> Creating: lib/httpcore-4.4.5.jar len -1 added 04/16/24<br> Creating: lib/spectator-api-0.67.0.jar len -1 added 04/16/24<br> Creating: lib/jakarta.ws.rs-api-2.1.6.jar len -1 added 04/16/24<br> Creating: lib/aopalliance-repackaged-2.6.1.jar len -1 added 04/16/24<br> Creating: lib/disruptor-3.4.3.jar len -1 added 04/16/24<br> Creating: lib/commons-io-2.8.0.jar len -1 added 04/16/24<br> Creating: lib/jsendnsca-2.1.1.jar len -1 added 04/16/24<br> Creating: lib/jetty-server-9.4.53.v20231009.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-rest-common-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/bcpkix-jdk15to18–1.74.jar len -1 added 04/16/24<br> Creating: lib/jetty-util-ajax-9.4.53.v20231009.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-internal-handlers-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mimepull-1.9.15.jar len -1 added 04/16/24<br> Creating: lib/httpclient-4.5.13.jar len -1 added 04/16/24<br> Creating: lib/validation-api-1.0.0.GA.jar len -1 added 04/16/24<br> Creating: lib/jakarta.validation-api-2.0.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-last-run-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jmespath-java-1.12.674.jar len -1 added 04/16/24<br> Creating: lib/netty-handler-proxy-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-dataweave-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/javassist-3.28.0-GA.jar len -1 added 04/16/24<br> Creating: lib/jakarta.annotation-api-1.3.5.jar len -1 added 04/16/24<br> Creating: lib/netty-reactive-streams-2.0.4.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-plugin-rest-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/okio-3.4.0.jar len -1 added 04/16/24<br> Creating: lib/jersey-hk2–2.39.1.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-zabbix-publisher-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/jasypt-1.9.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-application-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/failureaccess-1.0.1.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-clustering-service-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-nagios-publisher-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/guice-5.0.1.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-websocket-common-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/maven-artifact-3.8.5.jar len -1 added 04/16/24<br> Creating: lib/log4j-1.2-api-2.22.1.jar len -1 added 04/16/24<br> Creating: lib/jakarta.activation-1.2.2.jar len -1 added 04/16/24<br> Creating: lib/async-http-client-2.12.3.jar len -1 added 04/16/24<br> Creating: lib/mule-agent-details-2.6.2.jar len -1 added 04/16/24<br> Creating: lib/aws-java-sdk-pinpoint-1.12.674.jar len -1 added 04/16/24<br> Creating: lib/netty-codec-4.1.104.Final.jar len -1 added 04/16/24<br> Creating: lib/gson-2.8.9.jar len -1 added 04/16/24<br> Creating: lib/log4j-core-2.22.1.jar len -1 added 04/16/24<br> Creating: lib/spring-core-5.3.33.jar len -1 added 04/16/24<br> Creating: com/mulesoft/agent/configuration/guice/HierarchyModule$1.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/configuration/guice/HierarchyModule$3.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/configuration/guice/HierarchyModule.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/configuration/guice/PluginModuleProvider.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/configuration/guice/HierarchyModule$2.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/AgentTransportManager.class len -1 added 04/16/24<br> Creating: com/mulesoft/agent/AgentPlugin$1.class len -1 added 04/16/24<br>-&gt; Mule Agent Unpacked<br>INFO: Fips enabled: false<br>Communication between Anypoint Management Center and the Mule Agent is authorized by using two way SSL verification. In the following step we are<br>going to create a keystore and request Anypoint Management Center to sign it. Your private key will never leave your machine.<br>INFO: Configuring HTTP Client with no Proxy<br>Sending Sign request to Anypoint Management Center<br>Mule Agent configured successfully<br>Mule Agent configuration saved successfully<br>Successfully server is added in the Mulesoft anypoint platform<br><br>---<br><br>Run Server and Deploy Application<br>To run the server, execute the mule from bin folder of<br>C:\mule-enterprise-standalone-4.6.3\bin&gt;mule<br>***************************************************************************<br>MULE_HOME is set to C:\mule-enterprise-standalone-4.6.3<br>MULE_BASE is set to C:\mule-enterprise-standalone-4.6.3<br>Running in console/foreground mode by default, use Ctrl-C to exit…<br>Found JAVA_HOME = C:\Program Files\Java\jdk1.8.0_202<br> → Wrapper Started as Console<br>Java Service Wrapper Standard Edition 64-bit 3.5.51<br> Copyright © 1999–2022 Tanuki Software, Ltd. All Rights Reserved.<br> http://wrapper.tanukisoftware.com<br> Licensed to MuleSoft Inc. for Mule Runtime Enterprise Edition<br>Launching a JVM…<br>Starting the Mule Container…<br>WrapperManager: Initializing…<br>Valid license key → Evaluation = true, Expiration Date = Fri Jun 28 00:00:00 EDT 2024, Contact Name = MuleSoft Support, Contact Email Address = support@mulesoft.com, Contact Telephone = support@mulesoft.com, Contact Company = MuleSoft, Contact Country = US, Entitlements =<br>**********************************************************************<br>* *<br>* ((((((((((((((((((( *<br>* ((((( ((((# *<br>* &amp;((( *((( *<br>* &amp;((( ((( *<br>* ((( (((% (((# ((( *<br>* (( ((((((( ((((((( ((( *<br>* (( ((((((((( ((((((((( (( *<br>* (( #((((((((((( #((((((((((( ((( *<br>* #(( (((((((((((((( (((((((((((((( (( *<br>* (( (((((( /((((((( ((((((( /(((((( (( *<br>* (( (((((( (((((((&amp;((((((( (((((( (( *<br>* (( ((((( ((((((((((((* (((((( (( *<br>* (( (((((( *((((((((( (((((( (( *<br>* (( (((((( ((((((( (((((( ((( *<br>* (( (((((( (((((( (( *<br>* ((# ((((((# ((((((( (( *<br>* ((# (((((((( (((((((( ((( *<br>* ((( ((((((( ((((( ((. *<br>* (( ((( ((( #(( *<br>* /(( ((( *<br>* ((( &amp;((( *<br>* *((((&amp; &amp;(((( *<br>* ((((((((((((((/ *<br>* *<br>* ___ ___ _ ______ _ _ *<br>* | \/ | | | | ___ \ | | (_) *<br>* | . . |_ _| | ___ | |_/ / _ _ __ | |_ _ _ __ ___ ___ *<br>* | |\/| | | | | |/ _ \ | / | | | &#39;_ \| __| | &#39;_ ` _ \ / _ \ *<br>* | | | | |_| | | __/ | |\ \ |_| | | | | |_| | | | | | | __/ *<br>* \_| |_/\__,_|_|\___| \_| \_\__,_|_| |_|\__|_|_| |_| |_|\___| *<br>* *<br>* *<br>* Mule Runtime and Integration Platform *<br>* Version: 4.6.3 Build: e886d5ed *<br>* MuleSoft, Inc. *<br>* For more information go to *<br>* https://www.mulesoft.com/platform/soa/mule-esb-enterprise *<br>* *<br>* Server started: 5/29/24 3:27 PM *<br>* JDK: 1.8.0_202 (mixed mode) *<br>* JDK properties: *<br>* - java.vendor = Oracle Corporation *<br>* - java.vm.name = Java HotSpot(TM) 64-Bit Server VM *<br>* - java.home = C:\Program Files\Java\jdk1.8.0_202\jre *<br>* OS: Windows 10 - (10.0, amd64) *<br>* Wrapper PID: 1064 *<br>* Java PID: 13668 *<br>* Host: DESKTOP-AIID4LQ (172.24.144.1) *<br>* Mule services: *<br>* - api-gateway-contract-service-1.4.0 *<br>* - api-gateway-events-collector-service-1.4.0 *<br>* - mule-service-http-ee-1.9.3 *<br>* - mule-service-oauth-ee-1.3.3 *<br>* - mule-service-scheduler-1.6.3 *<br>* - mule-service-soap-1.6.3 *<br>* - mule-service-weave-ee-2.6.3 *<br>* Mule server plugins: *<br>* - mule-agent-plugin *<br>* Applied artifact patches: *<br>* - AGW-4162–1.1.1–1.0.jar *<br>* - AGW-4162–1.1.2–1.0.jar *<br>* - APIKIT-2576–1.3.7–1.3.9–2.0.jar *<br>* - APIKIT-2612–1.0.0–1.0.2–1.1.0–1.0.jar *<br>* - APIKIT-2612–1.1.1–1.0.jar *<br>* - APIKIT-2612–1.1.11–1.0.jar *<br>* - APIKIT-2612–1.1.12–1.2.0–1.2.2–1.0.jar *<br>* - APIKIT-2612–1.1.13–1.1.14–1.2.3–1.2.4–1.0.jar *<br>* - APIKIT-2612–1.1.15–1.1.16–1.0.jar *<br>* - APIKIT-2612–1.1.2–1.0.jar *<br>* - APIKIT-2612–1.1.3–1.0.jar *<br>* - APIKIT-2612–1.1.4–1.0.jar *<br>* - APIKIT-2612–1.1.5–1.1.6–1.0.jar *<br>* - APIKIT-2612–1.1.7–1.0.jar *<br>* - APIKIT-2612–1.1.8–1.1.10–1.0.jar *<br>* - APIKIT-2612–1.2.5–1.3.1–1.3.4–1.0.jar *<br>* - APIKIT-2612–1.3.0–1.0.jar *<br>* - APIKIT-2612–1.3.5–1.3.9–1.0.jar *<br>* - APIKIT-2613–1.2.0–1.2.1–1.0.jar *<br>* - APIKIT-2613–1.2.2–1.0.jar *<br>* - APIKIT-2613–1.2.3–1.2.4–1.3.0–1.0.jar *<br>* - APIKIT-2613–1.2.5–1.3.1–1.3.4-1.0.jar *<br>* - APIKIT-2613–1.3.5–1.3.6–1.0.jar *<br>* - APIKIT-2613–1.3.7–1.3.8–1.0.jar *<br>* - APIKIT-2613–1.3.9–1.0.jar *<br>* - APIKIT-2989–1.1.16–1.0.jar *<br>* - APIKIT-2989–1.2.5–1.0.jar *<br>* - APIKIT-2989–1.3.16–1.3.19–1.0.jar *<br>* - APIKIT-2989–1.4.0–1.4.2–1.0.jar *<br>* - APIKIT-2989–1.5.1–1.5.3–1.0.jar *<br>* - EE-7996–1.1.1–1.1.jar *<br>* - EE-7996–1.1.2–1.2.jar *<br>* - EE-7996–1.2.2–1.2.1–1.2.0–1.1.jar *<br>* - MULE-17706–1.1.1–1.1.2–1.0.jar *<br>* - MULE-17706–1.2.0–1.0.jar *<br>* - MULE-17706–1.2.1–1.2.2–1.0.jar *<br>* - MULE-17706–1.2.3–1.0.jar *<br>* - MULE-17706–1.3.0–1.3.1–1.0.jar *<br>* - MULE-17706–1.3.2–1.3.3–1.0.jar *<br>* - MULE-17706–1.3.4–1.0.jar *<br>* - MULE-17706–1.4.0–1.0.jar *<br>* - MULE-17706–1.4.1–1.4.3–1.0.jar *<br>* - MULE-17706–1.5.0–1.5.6–1.0.jar *<br>* - MULE-17706–1.5.10–1.5.11–1.0.jar *<br>* - MULE-17706–1.5.7–1.5.9–1.0.jar *<br>* - MULE-18457-MULE-19564–1.1.1–1.0.jar *<br>* - MULE-18457-MULE-19564–1.2.0–1.2.1–1.0.jar *<br>* - MULE-18457-MULE-19564–1.3.0–1.0.jar *<br>* - MULE-18457-MULE-19564–1.3.1–1.0.jar *<br>* - MULE-18457-MULE-19564–1.3.2–1.0.jar *<br>* - MULE-18457-MULE-19564–1.3.3–1.0.jar *<br>* - MULE-18900–19139–1.4.0–1.4.1–1.4.2–1.0.jar *<br>* - MULE-19564–1.3.4–1.0.jar *<br>* - MULE-19564–1.3.5–1.0.jar *<br>* - MULE-19564–1.3.6–1.0.jar *<br>* - SE-12551–1.0.0–1.0.1–1.0.jar *<br>* - SE-12551–1.1.0–1.1.15–2.0.jar *<br>* - SE-12551–1.2.0–1.3.0–1.0.jar *<br>* - SE-12551–1.3.1–1.3.4–1.0.jar *<br>* - SE-12562–1.0.0–1.5.5–1.0.jar *<br>* - SE-17198–1.0.jar *<br>* Mule system properties: *<br>* - mule.metadata.cache.expirationInterval.millis = 5000 *<br>* - mule.base = C:\mule-enterprise-standalone-4.6.3 *<br>* - mule.bootstrap.container.wrapper.class = *<br>* org.mule.runtime.module.boot.tanuki.internal.MuleContainerTanukiWr *<br>* apper *<br>* - mule.home = C:\mule-enterprise-standalone-4.6.3 *<br>* - mule.metadata.cache.entryTtl.minutes = 10 *<br>**********************************************************************<br>*********************************************************************<br>* Cluster configuration *<br>* *<br>* Cluster mode disabled *<br>**********************************************************************</pre><p>Once the server is running &amp; deploy the application</p><ol><li>Create an application in Anypoint Studio and deploy.</li><li>Click on Applications.</li><li>Click on Deploy application.</li><li>Provide a <em>logical name</em> for the application select target as “*-<em>standalone-server</em>”, <em>choose application</em> file and click on deploy application.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QEncbljBSjAf6WR2YNw0Ow.png" /></figure><p>***********************************************************************</p><pre>INFO 2024–05–29 15:28:07,586 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.AgentPlugin: Starting Mule Agent Version: 2.6.2 ; build-20240416<br>INFO 2024–05–29 15:28:07,587 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.AgentPlugin: Agent Security Manager initialized successfully: fips mode (disabled)<br>INFO 2024–05–29 15:28:08,215 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.AgentPlugin: The /C:/mule-enterprise-standalone-4.6.3/server-plugins/mule-agent-plugin/\lib\modules folder doesn&#39;t exists, skipping appending of jars.<br>INFO 2024–05–29 15:28:08,891 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.gw.http.handler.database Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,891 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.gw.http.handler.log Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,892 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.gw.http.handler.splunk Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,896 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.tracking.handler.analytics Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,897 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.tracking.handler.database Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,897 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.tracking.handler.http Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,897 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the tracking.notification.internal.message.handler Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,897 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.tracking.handler.log Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,898 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.tracking.handler.messageHistory Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,898 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.tracking.handler.splunk Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:08,901 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the mule.agent.ingest.application.metrics.internal.handler …<br>WARN 2024–05–29 15:28:09,175 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.util.client.DefaultAuthenticationProxyUtil: You have a proxy configured for the Authentication Proxy but it doesn&#39;t have the host and port configured.<br>WARN 2024–05–29 15:28:09,175 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.util.client.DefaultAuthenticationProxyUtil: Proxy configuration for the Authentication Proxy with basic auth client is either null or missing host/port fields. Resorting to default, non-proxied client<br>WARN 2024–05–29 15:28:09,175 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.util.client.DefaultAuthenticationProxyUtil: Could not resolve proxy configuration for the Authentication Proxy. Falling back to default client instance<br>INFO 2024–05–29 15:28:09,317 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: mule.agent.ingest.application.metrics.internal.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,321 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the cloudwatch.agent.monitor.publisher Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:09,321 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the mule.agent.ingest.target.metrics.internal.handler …<br>WARN 2024–05–29 15:28:09,323 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.util.client.DefaultAuthenticationProxyUtil: You have a proxy configured for the Authentication Proxy but it doesn&#39;t have the host and port configured.<br>WARN 2024–05–29 15:28:09,323 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.util.client.DefaultAuthenticationProxyUtil: Proxy configuration for the Authentication Proxy with basic auth client is either null or missing host/port fields. Resorting to default, non-proxied client<br>WARN 2024–05–29 15:28:09,323 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.util.client.DefaultAuthenticationProxyUtil: Could not resolve proxy configuration for the Authentication Proxy. Falling back to default client instance<br>INFO 2024–05–29 15:28:09,328 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: mule.agent.ingest.target.metrics.internal.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,328 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.nagios.jmx.internal.handler Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:09,328 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.zabbix.jmx.internal.handler Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:09,334 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.graphite.jmx.internal.handler Internal Handler because it&#39;s disabled.<br>INFO 2024–05–29 15:28:09,335 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the action.status.internal.message.handler …<br>INFO 2024–05–29 15:28:09,335 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: action.status.internal.message.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,335 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the application.deployment.notification.internal.message.handler …<br>INFO 2024–05–29 15:28:09,335 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: application.deployment.notification.internal.message.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,335 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the configuration.notification.internal.message.handler …<br>INFO 2024–05–29 15:28:09,335 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: configuration.notification.internal.message.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,336 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the domain.deployment.notification.internal.message.handler …<br>INFO 2024–05–29 15:28:09,336 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: domain.deployment.notification.internal.message.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,336 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the flow.status.notification.internal.message.handler …<br>INFO 2024–05–29 15:28:09,336 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: flow.status.notification.internal.message.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,337 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the membership.change.notification.internal.message.handler …<br>INFO 2024–05–29 15:28:09,337 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: membership.change.notification.internal.message.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,337 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the primary.node.notification.internal.message.handler …<br>INFO 2024–05–29 15:28:09,337 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: primary.node.notification.internal.message.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,337 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Initializing the scheduling.notification.internal.message.handler …<br>INFO 2024–05–29 15:28:09,337 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: scheduling.notification.internal.message.handler initialized successfully.<br>INFO 2024–05–29 15:28:09,375 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.util.DefaultLicenseService: Mule EE evaluation version. Enabling Mule Agent usage.<br>INFO 2024–05–29 15:28:09,378 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.AgentTransportManager: Skipping initialization of transport FileAgentTransport<br>INFO 2024–05–29 15:28:09,378 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.AgentTransportManager: Skipping initialization of transport RestAgentTransport<br>INFO 2024–05–29 15:28:09,378 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.AgentTransportManager: Initializing transport: WebSocketAgentTransport<br>WARN 2024–05–29 15:28:10,029 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.tooling.ToolingRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,029 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.administration.ComponentRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.administration.ComponentRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,029 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.deployment.DomainsRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.deployment.DomainsRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,029 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.extensions.ExtensionRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.extensions.ExtensionRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,029 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.tracking.TrackingExternalHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.tracking.TrackingExternalHandler will be ignored.<br>WARN 2024–05–29 15:28:10,029 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.logging.LoggingRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.logging.LoggingRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,029 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.deployment.ApplicationsRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.deployment.ApplicationsRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.metadata.MetadataRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.valueprovider.ValueProviderRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.valueprovider.ValueProviderRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.clustering.ClusteringRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.clustering.ClusteringRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.dataweave.DataWeaveRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.dataweave.DataWeaveRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.monitoring.MonitoringRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.monitoring.MonitoringRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.properties.PropertiesRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.properties.PropertiesRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.installer.InstallerRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.installer.InstallerRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.flows.FlowsRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.flows.FlowsRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.healthcheck.HealthCheckRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.healthcheck.HealthCheckRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.action.ActionRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.action.ActionRequestHandler will be ignored.<br>WARN 2024–05–29 15:28:10,030 [WrapperListener_start_runner] [processor: ; event: ] org.glassfish.jersey.internal.inject.Providers: A provider com.mulesoft.agent.external.handlers.runtime.RuntimeConfigurationRequestHandler registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider com.mulesoft.agent.external.handlers.runtime.RuntimeConfigurationRequestHandler will be ignored. <br>INFO 2024–05–29 15:28:10,211 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.AgentTransportManager: WebSocketAgentTransport initialised<br>INFO 2024–05–29 15:28:11,091 [pool-13-thread-1] [processor: ; event: ] com.mulesoft.agent.transport.connections.AsyncHttpWSConnectionThread: Initializing Mule Agent WebSocket connection<br>INFO 2024–05–29 15:28:11,091 [pool-13-thread-1] [processor: ; event: ] com.mulesoft.agent.transport.connections.AsyncHttpWSConnectionThread: Mule Agent WebSocket connecting to host: runtime-manager.anypoint.mulesoft.com<br>INFO 2024–05–29 15:28:11,092 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.AgentTransportManager: WebSocketAgentTransport started<br>INFO 2024–05–29 15:28:11,098 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.services.artifactvalidator.AgentApplicationValidatorService: Initializing Artifact Validator service<br>INFO 2024–05–29 15:28:11,100 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.services.artifactvalidator.AgentApplicationValidatorService: Total validators loaded: 1<br>INFO 2024–05–29 15:28:11,100 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.services.artifactvalidator.AgentApplicationValidatorService: Validators listed by type:<br>INFO 2024–05–29 15:28:11,102 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.services.artifactvalidator.AgentApplicationValidatorService: Type: jarSignatureValidator Names: [defaultJarSignatureValidator]<br>INFO 2024–05–29 15:28:11,102 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.services.healthcheck.AgentHealthCheckService: Initializing HealthCheck service<br>**********************************************************************<br>* Started DefaultSchedulerService *<br>* *<br>* Resolved configuration values: *<br>* *<br>* Pooling strategy: UBER *<br>* gracefulShutdownTimeout: 15000 ms *<br>* uber.threadPool.maxSize: 148 *<br>* uber.threadPool.threadKeepAlive: 30000 ms *<br>* *<br>* These can be modified by editing &#39;conf/scheduler-pools.conf&#39; *<br>**********************************************************************<br>INFO 2024–05–29 15:28:11,825 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.transport.handlers.GenericWebSocketHandler: Opening Mule Agent WebSocket<br>WARN 2024–05–29 15:28:12,028 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.handlers.internal.InternalDomainDeploymentNotificationHandler: Could not send message to external system via WebSocketAgentTransport: the channel is insecure InsecureTransportException: The Web socket channel is not authorized yet<br>WARN 2024–05–29 15:28:12,029 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.handlers.internal.InternalDomainDeploymentNotificationHandler: Could not send message to external system via WebSocketAgentTransport: the channel is insecure InsecureTransportException: The Web socket channel is not authorized yet<br>WARN 2024–05–29 15:28:12,030 [WrapperListener_start_runner] [processor: ; event: ] com.mulesoft.agent.handlers.internal.InternalDomainDeploymentNotificationHandler: Could not send message to external system via WebSocketAgentTransport: the channel is insecure InsecureTransportException: The Web socket channel is not authorized yet<br>INFO 2024–05–29 15:28:12,040 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.transport.handlers.GenericWebSocketHandler: Mule Agent WebSocket opened<br>INFO 2024–05–29 15:28:12,040 [pool-13-thread-1] [processor: ; event: ] com.mulesoft.agent.transport.connections.AsyncHttpWSConnectionThread: Mule Agent WebSocket connection was initialized after: 1 attempts<br>INFO 2024–05–29 15:28:12,146 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.services.security.HandshakeAuthorizationService: WebSocket Client connection authorized<br>**********************************************************************<br>* Started domain &#39;default&#39; *<br>**********************************************************************<br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>+ Mule is up and kicking (every 5000ms) +<br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>**********************************************************************<br>* - - + DOMAIN + - - * - - + STATUS + - - *<br>**********************************************************************<br>* default * DEPLOYED *<br>**********************************************************************<br>WARN 2024–05–29 15:28:13,618 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.external.handlers.administration.ComponentRequestHandler: Ignored reference in configuration: &#39;&#39; does not exist in component &#39;mule.agent.tracking.handler.analytics&#39;<br>WARN 2024–05–29 15:28:13,619 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.external.handlers.administration.ComponentRequestHandler: Ignored reference in configuration: &#39;enabled&#39; does not allow dynamic configuration for component &#39;mule.agent.tracking.handler.analytics&#39;<br>INFO 2024–05–29 15:28:13,628 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.configuration.postconfigure.DefaultPostConfigureRunner: Skipping the initialization of the mule.agent.tracking.handler.analytics Internal Handler because it&#39;s disabled.<br>WARN 2024–05–29 15:33:04,107 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.external.handlers.administration.ComponentRequestHandler: Ignored reference in configuration: &#39;schedulerConfigurations&#39; does not exist in component &#39;mule.agent.logging.service&#39;<br>WARN 2024–05–29 15:33:04,107 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.external.handlers.administration.ComponentRequestHandler: Ignored reference in configuration: &#39;enabled&#39; does not allow dynamic configuration for component &#39;mule.agent.logging.service&#39;<br>WARN 2024–05–29 15:33:04,110 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.configuration.descriptor.YamlMuleAgentDescriptor: Descriptor file C:\mule-enterprise-standalone-4.6.3\conf\sapi-patient-record-standalone-api.yml not found.<br>INFO 2024–05–29 15:33:04,129 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.services.administration.components.ComponentManager: Re-enabling component: mule.agent.logging.service<br>INFO 2024–05–29 15:33:04,179 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.services.administration.components.ComponentManager: Re-enabling component: mule.agent.tracking.service<br>INFO 2024–05–29 15:33:24,370 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.services.application.AgentApplicationService: Deploying the sapi-patient-record-standalone-api application from jar file.<br>INFO 2024–05–29 15:33:24,965 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.agent.services.artifactvalidator.AgentApplicationValidatorService: Application &#39;sapi-patient-record-standalone-api&#39; was not validated. No validators enabled found<br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>+ New app &#39;sapi-patient-record-standalone-api&#39; +<br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>+ Initializing app &#39;sapi-patient-record-standalone-api&#39; +<br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>INFO 2024–05–29 15:33:52,619 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.mule.runtime.gw.deployment.ApiDeploymentCoreExtension: Starting API Gateway Extension in STANDALONE mode<br>INFO 2024–05–29 15:33:52,771 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.mule.runtime.gw.policies.lifecyle.GateKeeper: GateKeeper started in FLEXIBLE mode<br>INFO 2024–05–29 15:33:54,005 [WebSocketInboundExecutor] [processor: ; event: ] com.mulesoft.mule.runtime.gw.client.provider.ApiPlatformClientProvider: Client ID and Client Secret successfully validated against API Manager.<br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>+ Starting app &#39;sapi-patient-record-standalone-api&#39; +<br>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>*********************************************************************<br>* Started app &#39;sapi-patient-record-standalone-api&#39; *<br>* Application plugins: *<br>* - Database : 1.14.8 *<br>* - Sockets : 1.2.4 *<br>* - HTTP : 1.9.1 *<br>* - APIKit : 1.10.3 *<br>* Application libraries: *<br>* - mysql-connector-java-8.0.30.jar *<br>* - protobuf-java-3.19.4.jar *<br>* - postgresql-42.7.3.jar *<br>* - checker-qual-3.42.0.jar *<br>* - postgresql-42.7.3–0.1.jar *<br>* - sapi-patient-record-api-1.0.3-raml.zip *<br>* - patient-1.0.1-raml-fragment.zip *<br>* - patient-example-1.0.1-raml-fragment.zip *<br>* - error-code-library-1.0.0-raml-fragment.zip *<br>**********************************************************************</pre><p><strong>Now Server is running &amp; Application is deployed successfully!!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nZR83H1-hOiw4PtUWMTE1A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*976vXoKKSXFDU_S4JQUSEw.png" /></figure><p><em>Happy Learning!!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f44d996bd45" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS setup — Jenkins, SonarQube, and Nexus]]></title>
            <link>https://medium.com/@ram.changalva/aws-setup-jenkins-sonarqube-and-nexus-69f0083c754f?source=rss-7352be1e457d------2</link>
            <guid isPermaLink="false">https://medium.com/p/69f0083c754f</guid>
            <dc:creator><![CDATA[Ram Changalva]]></dc:creator>
            <pubDate>Sat, 18 May 2024 14:17:38 GMT</pubDate>
            <atom:updated>2024-05-18T18:14:54.652Z</atom:updated>
            <content:encoded><![CDATA[<h3>AWS setup for CICD — Jenkins, SonarQube, and Nexus</h3><p>AWS setup using Terraform that deploys Jenkins, SonarQube, and Nexus on separate EC2 instances with Docker.</p><p>To create an AWS setup using Terraform that deploys Jenkins, SonarQube, and Nexus on separate EC2 instances with Docker, we need to extend the provided configuration to include Docker installation and running the respective Docker containers on each instance. Below is the modified Terraform configuration that includes setting up security groups, user data scripts for Docker installation, and running the necessary containers for Jenkins, SonarQube, and Nexus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4--C2_MTpYd8JHkVr_6jA.png" /><figcaption><strong>AWS Setup</strong></figcaption></figure><h3>Prerequisites:</h3><ul><li>AWS Account</li><li>GitHub account</li><li>Jenkins</li><li>Nexus</li><li>SonarQube</li><li>MuleSoft Anypoint Platform</li><li>MuleSoft Runtime</li><li>Slack</li><li>Splunk</li></ul><h3>Step 1: Define Variables</h3><p>variables.tf: This file will contain all the variable declarations.</p><pre>variable &quot;key_name&quot; {<br>  description = &quot;Name of the SSH key pair&quot;<br>  type        = string<br>}<br><br>variable &quot;instance_type&quot; {<br>  description = &quot;Instance type for the EC2 instances&quot;<br>  default     = &quot;t2.medium&quot;<br>}<br><br>variable &quot;ami&quot; {<br>  description = &quot;AMI ID for Ubuntu 24.04 LTS&quot;<br>  default     = &quot;ami-09040d770ffe2224f&quot;<br>}</pre><h3>Step 2: Define Providers</h3><p>provider.tf: This file will contain the provider configuration and any global settings.</p><pre>terraform {<br>  required_providers {<br>    aws = {<br>      source  = &quot;hashicorp/aws&quot;<br>      version = &quot;~&gt; 4.16&quot;<br>    }<br>  }<br>}<br><br>provider &quot;aws&quot; {<br>  region     = &quot;us-east-2&quot;<br>  access_key = &quot;&quot;  # Add your AWS access key<br>  secret_key = &quot;&quot;  # Add your AWS secret key<br>}<br><br>resource &quot;tls_private_key&quot; &quot;rsa_4096&quot; {<br>  algorithm = &quot;RSA&quot;<br>  rsa_bits  = 4096<br>}<br><br>resource &quot;aws_key_pair&quot; &quot;key_pair&quot; {<br>  key_name   = var.key_name<br>  public_key = tls_private_key.rsa_4096.public_key_openssh<br>}<br><br>resource &quot;local_file&quot; &quot;private_key&quot; {<br>  content  = tls_private_key.rsa_4096.private_key_pem<br>  filename = &quot;${var.key_name}.pem&quot;<br>}</pre><h3>Step 3: Create EC2 Instances with User Data</h3><p>main.tf: This file will contain the main resources and logic of your infrastructure.</p><pre>resource &quot;aws_instance&quot; &quot;jenkins_instance&quot; {<br>  ami                    = var.ami<br>  instance_type          = var.instance_type<br>  key_name               = aws_key_pair.key_pair.key_name<br>  security_groups        = [aws_security_group.jenkins_sg.name]<br><br>  user_data = &lt;&lt;-EOF<br>              #!/bin/bash<br>              apt-get update -y<br>              apt-get install -y docker.io<br>              systemctl start docker<br>              systemctl enable docker<br>              docker run -d -p 8080:8080 -p 50000:50000 --name jenkins jenkins/jenkins:lts<br>              EOF<br><br>  tags = {<br>    Name = &quot;Jenkins-instance&quot;<br>  }<br>}<br><br>resource &quot;aws_instance&quot; &quot;sonarqube_instance&quot; {<br>  ami                    = var.ami<br>  instance_type          = var.instance_type<br>  key_name               = aws_key_pair.key_pair.key_name<br>  security_groups        = [aws_security_group.sonarqube_sg.name]<br><br>  user_data = &lt;&lt;-EOF<br>              #!/bin/bash<br>              apt-get update -y<br>              apt-get install -y docker.io<br>              systemctl start docker<br>              systemctl enable docker<br>              docker run -d -p 9000:9000 --name sonarqube sonarqube<br>              EOF<br><br>  tags = {<br>    Name = &quot;SonarQube-instance&quot;<br>  }<br>}<br><br>resource &quot;aws_instance&quot; &quot;nexus_instance&quot; {<br>  ami                    = var.ami<br>  instance_type          = var.instance_type<br>  key_name               = aws_key_pair.key_pair.key_name<br>  security_groups        = [aws_security_group.nexus_sg.name]<br><br>  user_data = &lt;&lt;-EOF<br>              #!/bin/bash<br>              apt-get update -y<br>              apt-get install -y docker.io<br>              systemctl start docker<br>              systemctl enable docker<br>              docker run -d -p 8081:8081 --name nexus sonatype/nexus3<br>              EOF<br><br>  tags = {<br>    Name = &quot;Nexus-instance&quot;<br>  }<br>}</pre><h3>Step 4: Initialize and Apply Terraform Configuration</h3><pre>terraform init<br>terraform apply</pre><h3>CI/CD Pipeline</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*AXnVCca6dWh9LEWlcbUHTw.png" /></figure><h3>Steps to Set Up CI/CD Pipeline</h3><h4>1. Set Up Jenkins</h4><ol><li>Install Necessary Plugins:</li></ol><ul><li>GitHub Plugin</li><li>Maven Integration</li><li>Pipeline</li><li>SonarQube Scanner</li><li>Nexus Artifact Uploader</li></ul><p>2. Configure Jenkins:</p><p>Jenkins Global Tool Configuration:</p><ul><li>Add JDK.</li><li>Add Maven.</li><li>Add SonarQube servers.</li></ul><h4>2. Set Up GitHub</h4><ol><li>Create a Repository:</li></ol><ul><li>Push your MuleSoft project to the GitHub repository.</li></ul><p>2. Generate Personal Access Token:</p><ul><li>Generate a token in GitHub settings for Jenkins to access the repository.</li></ul><h4>3. Set Up SonarQube</h4><ol><li>Create a Project:</li></ol><ul><li>Define a project key and name in SonarQube.</li></ul><p>2. Configure Jenkins for SonarQube:</p><ul><li>Add SonarQube server details in Jenkins under Manage Jenkins -&gt; Configure System.</li></ul><h4>4. Set Up Nexus Repository</h4><ol><li>Create a Repository:</li></ol><ul><li>Create a Maven hosted repository in Nexus for storing your MuleSoft artifacts.</li></ul><p>2. Configure Jenkins for Nexus:</p><ul><li>Add Nexus credentials in Jenkins under Manage Jenkins -&gt; Manage Credentials.</li></ul><h4>5. Create Jenkins Pipeline</h4><ol><li>Pipeline Script: Create a Jenkinsfile in your GitHub repository. Below is a sample Jenkinsfile that handles different environments:</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69f0083c754f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>