Mule velocity
•Download as PPTX, PDF•
0 likes•530 views
Mule can be used to send emails with dynamically generated content using Velocity templates. Velocity templates allow using HTML tags to design colorful email bodies with images, logos, and dynamic text values pulled from property files. The example shows how to create a Velocity transformer class to set the email payload and map external values, use a properties file to define dynamic values, and write a Velocity template integrating the HTML tags, dynamic values, and file content into the email body. Testing confirms Mule successfully sends the email with the customized Velocity template design.
Report
Share
Report
Share
Recommended
Mule with velocity
This document discusses how to use Mule and Velocity templates to send dynamic emails with formatted content like images, logos, and text styles. It provides an example of using a Velocity transformer class to map external properties values to the email template. The template is an HTML file that can include dynamic values from a properties file to customize the email content. When a file is placed in an inbound folder, Mule will send an email with the file content appended to the template-generated body.
Getting anypoint studios all versions
Anypoint Studio is a graphical design environment for Anypoint Platform that allows developers to create SOA, SaaS, and API integrations with a single click deployment to Mule runtime on-premises or in the cloud. To use Anypoint Studio, Java SE JDK 7 or 8 must be installed. Previous versions of Anypoint Studio, formerly known as Mule Studio, can be downloaded from a URL listing all releases by appending the version key to the download URL.
Demo on Mule ESB Facebook Connector
This presentation demonstrates a simple example on how to configure Facebook and use Mule ESB Facebook connector to perform basic operations like authorize, get user details and publish a message on Facebook
Velocity in Mule
This document discusses how to use Velocity templates in Mule to send dynamic emails with pre-defined formatting and content. Specifically:
- Velocity templates allow designing email bodies with HTML tags to include text formatting, images, logos, and dynamic values from properties files.
- A Velocity transformer Java class is used to set the email payload and map external dynamic values to the email body.
- An example template picks values like names from a properties file and appends the content of an inbound file to the email body.
- Testing the application involves placing a file in an inbound folder, which triggers an email with the Velocity-generated body to be sent successfully.
Deploying and Running in Mule
Mule Standalone Server is a proprietary application server that can host Java code, web services, and Mule applications. To deploy a Mule application, it must be exported from Anypoint Studio as a zip file and copied to the Mule Standalone app folder. Starting the mule.bat file launches the Mule Standalone server, deploying any applications in the app folder. The document then walks through creating a simple Mule application in Anypoint Studio, exporting and deploying it to the Mule Standalone server, and invoking it to confirm it is running successfully.
Mule esb - How to connect to a MySql Database in 5 minutes
This document provides instructions for connecting Mule ESB to a MySQL database in 5 steps: 1) Create a database called "mule_test" and a table called "User" with sample data using phpMyAdmin; 2) Populate the "User" table with sample data; 3) Create a new Mule project with an empty flow called "db_testFlow" and an HTTP inbound endpoint; 4) Add the MySQL JAR client to the project build path; 5) Configure the database connector and create a query to retrieve the "User" table data and print it to the console using a logger component.
Running mule standalone
This document discusses deploying and running a simple Mule application on a Mule Standalone server. It explains that Mule Standalone server is a proprietary application server that can host Mule applications as well as other Java code and web services. It demonstrates creating a sample Mule application, exporting it to a deployable zip file, copying this file to the Mule Standalone server's app folder, and starting the server to successfully deploy and run the application.
Mule
Anypoint Studio has a feature to automatically generate documentation for Mule projects. It allows users to generate an HTML-based documentation file with a single click. The documentation generator plugin extracts information from doc:name attributes added to components in the Mule configuration file. It produces documentation containing graphical and code views of all flows in the project.
Recommended
Mule with velocity
This document discusses how to use Mule and Velocity templates to send dynamic emails with formatted content like images, logos, and text styles. It provides an example of using a Velocity transformer class to map external properties values to the email template. The template is an HTML file that can include dynamic values from a properties file to customize the email content. When a file is placed in an inbound folder, Mule will send an email with the file content appended to the template-generated body.
Getting anypoint studios all versions
Anypoint Studio is a graphical design environment for Anypoint Platform that allows developers to create SOA, SaaS, and API integrations with a single click deployment to Mule runtime on-premises or in the cloud. To use Anypoint Studio, Java SE JDK 7 or 8 must be installed. Previous versions of Anypoint Studio, formerly known as Mule Studio, can be downloaded from a URL listing all releases by appending the version key to the download URL.
Demo on Mule ESB Facebook Connector
This presentation demonstrates a simple example on how to configure Facebook and use Mule ESB Facebook connector to perform basic operations like authorize, get user details and publish a message on Facebook
Velocity in Mule
This document discusses how to use Velocity templates in Mule to send dynamic emails with pre-defined formatting and content. Specifically:
- Velocity templates allow designing email bodies with HTML tags to include text formatting, images, logos, and dynamic values from properties files.
- A Velocity transformer Java class is used to set the email payload and map external dynamic values to the email body.
- An example template picks values like names from a properties file and appends the content of an inbound file to the email body.
- Testing the application involves placing a file in an inbound folder, which triggers an email with the Velocity-generated body to be sent successfully.
Deploying and Running in Mule
Mule Standalone Server is a proprietary application server that can host Java code, web services, and Mule applications. To deploy a Mule application, it must be exported from Anypoint Studio as a zip file and copied to the Mule Standalone app folder. Starting the mule.bat file launches the Mule Standalone server, deploying any applications in the app folder. The document then walks through creating a simple Mule application in Anypoint Studio, exporting and deploying it to the Mule Standalone server, and invoking it to confirm it is running successfully.
Mule esb - How to connect to a MySql Database in 5 minutes
This document provides instructions for connecting Mule ESB to a MySQL database in 5 steps: 1) Create a database called "mule_test" and a table called "User" with sample data using phpMyAdmin; 2) Populate the "User" table with sample data; 3) Create a new Mule project with an empty flow called "db_testFlow" and an HTTP inbound endpoint; 4) Add the MySQL JAR client to the project build path; 5) Configure the database connector and create a query to retrieve the "User" table data and print it to the console using a logger component.
Running mule standalone
This document discusses deploying and running a simple Mule application on a Mule Standalone server. It explains that Mule Standalone server is a proprietary application server that can host Mule applications as well as other Java code and web services. It demonstrates creating a sample Mule application, exporting it to a deployable zip file, copying this file to the Mule Standalone server's app folder, and starting the server to successfully deploy and run the application.
Mule
Anypoint Studio has a feature to automatically generate documentation for Mule projects. It allows users to generate an HTML-based documentation file with a single click. The documentation generator plugin extracts information from doc:name attributes added to components in the Mule configuration file. It produces documentation containing graphical and code views of all flows in the project.
Deploying and running mule standalone
This document provides instructions for deploying and running a simple Mule application on a Mule Standalone server. It explains that a Mule application needs to be exported from Anypoint Studio as a deployable ZIP file and copied to the Mule Standalone server's app folder. It then describes starting the Mule Standalone server from the bin folder and viewing the application running at a URL to confirm successful deployment and operation.
Sending mail with attachment
This document discusses how to send an email with an attachment from a Mule application. It shows a Mule flow that uses a Groovy component to design the email body in HTML format, an Attachment component to attach a file to the message payload, and an SMTP component to send the email. When the flow is triggered, it successfully sends an email with the HTML body and file attachment. The document demonstrates how to add attachments to emails from Mule applications.
Idempotent filter in Mule
The document discusses how to use an Idempotent Filter in Mule to avoid duplicate messages by checking message IDs. It provides an example of configuring an Idempotent Filter to use a simple-text-file-store to store message IDs in files and check for duplicates. When the example flow is run, it generates a text file to store message IDs and will return "passed" for new messages but "EXCEPTION" for duplicate messages.
Idempotent filter in mule
The document discusses how the Idempotent Filter in Mule ensures only unique messages are received by checking message IDs. It demonstrates configuring the Idempotent Filter with a simple-text-file-store to avoid duplicate messages. When messages are received, the filter will check the file store for duplicates and only allow unique messages to pass through the flow.
Deploying and running in mule standalone
The document discusses deploying and running a simple Mule application on a Mule Standalone server. It describes creating a deployable ZIP file of a Hello World Mule application in Anypoint Studio, copying it to the Mule Standalone server's app folder, and starting the server to deploy and run the application. The application is then accessible at http://localhost:8081/test.
Example mule
This document provides steps to create a simple "Hello World" Mule application using Eclipse. It describes generating a Mule project, configuring a service that listens on port 8080 and redirects requests to a Groovy component, and running the application to display "Hello World" when accessing the URL.
Mule management console installation with Tomcat
This document provides instructions for installing and configuring Tomcat and Mule ESB, deploying services on Mule, and configuring alerts. It discusses:
1. Installing Tomcat by downloading the installer, accepting licenses, choosing an installation directory, and installing Java.
2. Deploying Mule services on Tomcat by packaging the Mule application as a WAR file and copying it to Tomcat's webapps directory.
3. Configuring Mule services by creating servers and adding deployable files to the Mule repository, deploying services from the repository to servers, and creating and modifying alerts in the Mule management console.
My journey and learnings using mule esb part 1
This document outlines lessons learned from using Mule ESB for integration projects. It recommends mavenizing all Mule projects to easily manage dependencies rather than using JAR files. It also suggests tools like Postman and SoapUI for testing APIs during integration work. Resources are provided for validating payloads and learning more about Mule.
Cloud hub with mule
CloudHub is the platform as a service component of Anypoint Platform that provides a fully-managed, secure cloud platform for integration and APIs. It requires no hardware maintenance and continuous software updates. Developers can build Mule applications in Anypoint Studio and deploy them to CloudHub directly from Studio or by exporting the application to a deployable ZIP file and uploading it through the CloudHub management console. Once deployed, applications run on CloudHub's global infrastructure and developers can monitor logs and test applications through the console.
Using ajax in mule
The document discusses how to use AJAX in Mule applications. It explains that AJAX allows updating parts of a web page without reloading the entire page. It then demonstrates creating a Mule flow with a web service that can insert and retrieve data from a database in response to requests from an HTML page hosted using Mule's AJAX component, without reloading the page. The HTML page is hosted at a URL and uses the web service to handle data input and output without changing the page. This allows asynchronous data exchange between the HTML page and backend database via a web service in Mule.
Expose web service
To expose a SOAP web service, an interface is typically created and implemented by a Java class containing the business logic. However, this document shows that a SOAP service can be exposed without implementing an interface by deleting the "method" invocation property in Mule, allowing the Java class to function without directly implementing the interface. Testing in SOAPUI confirms the service runs successfully.
Anypoint lessons
This document provides 8 steps for creating a simple "Hello, World!" application using Anypoint Platform: create a new project, name the project, drag a HTTP connector onto the empty canvas along with its configurations, insert a SET Payload connector to write the message, add a logger to monitor the application, run the project, execute it in a browser using the HTTP connector address, and see the result displayed on the console. The steps guide building a basic application that displays "Hello, world!" when accessed via HTTP.
Using maven with mule
Maven can be used to develop and manage Mule projects. Mule provides built-in Maven functionality in Anypoint Studio and for Mule ESB. In Studio, new projects can be built with Maven or existing projects can have Maven support enabled. Maven plugins for Mule ESB allow controlling Mule instances from Maven and provide archetypes for regular Mule applications. Projects developed outside Studio using Maven can also be imported.
Mule ESB - How to convert from Xml to Json in 5 minutes
This document discusses how to create an XML to JSON converter using Mule ESB in 5 minutes. It describes creating a simple HTTP listener flow to receive XML data, adding an XML to JSON transformer to convert the data, and logging the transformed JSON output to the console. The tutorial is tested by sending sample XML to the flow using Postman and verifying the JSON response.
Integrate to retrieve data microsoft azure
MuleSoft's integration platform connects applications and APIs across cloud and on-premise systems. The Microsoft Azure connector allows accessing and storing data in Microsoft Azure from MuleSoft. It requires setting up a Microsoft Azure account and namespace, and configuring the Microsoft Service Bus connector in MuleSoft with the Azure connection information. A Mule flow can then use the connector to retrieve data from Azure by calling APIs through HTTP endpoints.
Mule with drools
This document discusses using Drools, a business rules management system, with Mule to execute business rules in applications. It provides an example of creating a simple Mule application that uses a .drl file to define rules to determine a warehouse destination based on a randomly generated weight variable. The application is deployed to a Mule standalone server and the rules are executed by the Drools component to set the destination variable according to the rules.
Mule with salesforce push topic notification copy
The easiest way to do this is to either use the workbench at developerforce.com or the developer console. I'm going to use the developer console. In the console head to Debug Execute Anonymous Apex Code. We are essentially creating a SOQL query with a few extra parameters that watch for changes in a specified object.
If the Push Topic is executed successfully then Salesforce is ready to post notification to MULE ESB if any changes made in the Account object in Salesforce, because the below Push Topic has been created for Salesforce’s Account object.
Introduction to mule esb
Mule is an open-source enterprise service backbone (ESB) that allows users to move data between different endpoints and applications in a flexible way. It uses a universal message object and XML configuration to define routing, transformations, and processing of data through components. Mule handles exception handling by associating exception strategies with connectors, components, or for all components in a configuration to redirect errors to a specified endpoint.
Creating dynamic json in mule
This document discusses how to dynamically generate JSON payloads in Mule ESB flows. It shows how to use an expression transformer to generate a sample JSON payload with values from flow variables. The generated JSON is then posted to an external service, which returns a response. Testing the flow by hitting a URL generates the JSON request and logs the request and response, demonstrating how to dynamically create and use JSON in Mule.
How to use expression filter
This document provides an example of how to use an expression filter in Mule applications. It shows XML configuration with two flows, one that sets a session property and logs it, and another that is called by the first flow via VM connector if the session property value is not equal to "mule". The output logs from both flows are displayed, demonstrating the expression filter functionality.
Mapping and listing with mule
Mule ESB allows defining variables to store data, including flow and session variables. Lists and maps can be defined as Mule variables similarly to Java by using square brackets. Values can then be retrieved from the list or map using indexes or keys, and the list values can be reassigned. For example, a list variable can be set as #[{1000,100,14,1}] and values retrieved using flowVars['test'][0]. Similarly, a map can be set as # [{'k2':'new', 'k3':'v3'}] and values retrieved using flowVars['customMap']['k2'].
xslt in mule
XSLT is used to transform XML payloads between different forms. In Mule, the XSLT transformer component allows transforming XML payloads using XSLT stylesheets. For example, a flow uses an HTTP inbound endpoint, sets an XML payload, and applies an XSLT stylesheet using the XSLT transformer to output a new transformed XML payload. The XSLT stylesheet matches elements in the input XML and outputs a new structure defined in the stylesheet.
More Related Content
What's hot
Deploying and running mule standalone
This document provides instructions for deploying and running a simple Mule application on a Mule Standalone server. It explains that a Mule application needs to be exported from Anypoint Studio as a deployable ZIP file and copied to the Mule Standalone server's app folder. It then describes starting the Mule Standalone server from the bin folder and viewing the application running at a URL to confirm successful deployment and operation.
Sending mail with attachment
This document discusses how to send an email with an attachment from a Mule application. It shows a Mule flow that uses a Groovy component to design the email body in HTML format, an Attachment component to attach a file to the message payload, and an SMTP component to send the email. When the flow is triggered, it successfully sends an email with the HTML body and file attachment. The document demonstrates how to add attachments to emails from Mule applications.
Idempotent filter in Mule
The document discusses how to use an Idempotent Filter in Mule to avoid duplicate messages by checking message IDs. It provides an example of configuring an Idempotent Filter to use a simple-text-file-store to store message IDs in files and check for duplicates. When the example flow is run, it generates a text file to store message IDs and will return "passed" for new messages but "EXCEPTION" for duplicate messages.
Idempotent filter in mule
The document discusses how the Idempotent Filter in Mule ensures only unique messages are received by checking message IDs. It demonstrates configuring the Idempotent Filter with a simple-text-file-store to avoid duplicate messages. When messages are received, the filter will check the file store for duplicates and only allow unique messages to pass through the flow.
Deploying and running in mule standalone
The document discusses deploying and running a simple Mule application on a Mule Standalone server. It describes creating a deployable ZIP file of a Hello World Mule application in Anypoint Studio, copying it to the Mule Standalone server's app folder, and starting the server to deploy and run the application. The application is then accessible at http://localhost:8081/test.
Example mule
This document provides steps to create a simple "Hello World" Mule application using Eclipse. It describes generating a Mule project, configuring a service that listens on port 8080 and redirects requests to a Groovy component, and running the application to display "Hello World" when accessing the URL.
Mule management console installation with Tomcat
This document provides instructions for installing and configuring Tomcat and Mule ESB, deploying services on Mule, and configuring alerts. It discusses:
1. Installing Tomcat by downloading the installer, accepting licenses, choosing an installation directory, and installing Java.
2. Deploying Mule services on Tomcat by packaging the Mule application as a WAR file and copying it to Tomcat's webapps directory.
3. Configuring Mule services by creating servers and adding deployable files to the Mule repository, deploying services from the repository to servers, and creating and modifying alerts in the Mule management console.
My journey and learnings using mule esb part 1
This document outlines lessons learned from using Mule ESB for integration projects. It recommends mavenizing all Mule projects to easily manage dependencies rather than using JAR files. It also suggests tools like Postman and SoapUI for testing APIs during integration work. Resources are provided for validating payloads and learning more about Mule.
Cloud hub with mule
CloudHub is the platform as a service component of Anypoint Platform that provides a fully-managed, secure cloud platform for integration and APIs. It requires no hardware maintenance and continuous software updates. Developers can build Mule applications in Anypoint Studio and deploy them to CloudHub directly from Studio or by exporting the application to a deployable ZIP file and uploading it through the CloudHub management console. Once deployed, applications run on CloudHub's global infrastructure and developers can monitor logs and test applications through the console.
Using ajax in mule
The document discusses how to use AJAX in Mule applications. It explains that AJAX allows updating parts of a web page without reloading the entire page. It then demonstrates creating a Mule flow with a web service that can insert and retrieve data from a database in response to requests from an HTML page hosted using Mule's AJAX component, without reloading the page. The HTML page is hosted at a URL and uses the web service to handle data input and output without changing the page. This allows asynchronous data exchange between the HTML page and backend database via a web service in Mule.
Expose web service
To expose a SOAP web service, an interface is typically created and implemented by a Java class containing the business logic. However, this document shows that a SOAP service can be exposed without implementing an interface by deleting the "method" invocation property in Mule, allowing the Java class to function without directly implementing the interface. Testing in SOAPUI confirms the service runs successfully.
Anypoint lessons
This document provides 8 steps for creating a simple "Hello, World!" application using Anypoint Platform: create a new project, name the project, drag a HTTP connector onto the empty canvas along with its configurations, insert a SET Payload connector to write the message, add a logger to monitor the application, run the project, execute it in a browser using the HTTP connector address, and see the result displayed on the console. The steps guide building a basic application that displays "Hello, world!" when accessed via HTTP.
Using maven with mule
Maven can be used to develop and manage Mule projects. Mule provides built-in Maven functionality in Anypoint Studio and for Mule ESB. In Studio, new projects can be built with Maven or existing projects can have Maven support enabled. Maven plugins for Mule ESB allow controlling Mule instances from Maven and provide archetypes for regular Mule applications. Projects developed outside Studio using Maven can also be imported.
Mule ESB - How to convert from Xml to Json in 5 minutes
This document discusses how to create an XML to JSON converter using Mule ESB in 5 minutes. It describes creating a simple HTTP listener flow to receive XML data, adding an XML to JSON transformer to convert the data, and logging the transformed JSON output to the console. The tutorial is tested by sending sample XML to the flow using Postman and verifying the JSON response.
Integrate to retrieve data microsoft azure
MuleSoft's integration platform connects applications and APIs across cloud and on-premise systems. The Microsoft Azure connector allows accessing and storing data in Microsoft Azure from MuleSoft. It requires setting up a Microsoft Azure account and namespace, and configuring the Microsoft Service Bus connector in MuleSoft with the Azure connection information. A Mule flow can then use the connector to retrieve data from Azure by calling APIs through HTTP endpoints.
Mule with drools
This document discusses using Drools, a business rules management system, with Mule to execute business rules in applications. It provides an example of creating a simple Mule application that uses a .drl file to define rules to determine a warehouse destination based on a randomly generated weight variable. The application is deployed to a Mule standalone server and the rules are executed by the Drools component to set the destination variable according to the rules.
Mule with salesforce push topic notification copy
The easiest way to do this is to either use the workbench at developerforce.com or the developer console. I'm going to use the developer console. In the console head to Debug Execute Anonymous Apex Code. We are essentially creating a SOQL query with a few extra parameters that watch for changes in a specified object.
If the Push Topic is executed successfully then Salesforce is ready to post notification to MULE ESB if any changes made in the Account object in Salesforce, because the below Push Topic has been created for Salesforce’s Account object.
What's hot (17)
Mule ESB - How to convert from Xml to Json in 5 minutes
Mule ESB - How to convert from Xml to Json in 5 minutes
Viewers also liked
Introduction to mule esb
Mule is an open-source enterprise service backbone (ESB) that allows users to move data between different endpoints and applications in a flexible way. It uses a universal message object and XML configuration to define routing, transformations, and processing of data through components. Mule handles exception handling by associating exception strategies with connectors, components, or for all components in a configuration to redirect errors to a specified endpoint.
Creating dynamic json in mule
This document discusses how to dynamically generate JSON payloads in Mule ESB flows. It shows how to use an expression transformer to generate a sample JSON payload with values from flow variables. The generated JSON is then posted to an external service, which returns a response. Testing the flow by hitting a URL generates the JSON request and logs the request and response, demonstrating how to dynamically create and use JSON in Mule.
How to use expression filter
This document provides an example of how to use an expression filter in Mule applications. It shows XML configuration with two flows, one that sets a session property and logs it, and another that is called by the first flow via VM connector if the session property value is not equal to "mule". The output logs from both flows are displayed, demonstrating the expression filter functionality.
Mapping and listing with mule
Mule ESB allows defining variables to store data, including flow and session variables. Lists and maps can be defined as Mule variables similarly to Java by using square brackets. Values can then be retrieved from the list or map using indexes or keys, and the list values can be reassigned. For example, a list variable can be set as #[{1000,100,14,1}] and values retrieved using flowVars['test'][0]. Similarly, a map can be set as # [{'k2':'new', 'k3':'v3'}] and values retrieved using flowVars['customMap']['k2'].
xslt in mule
XSLT is used to transform XML payloads between different forms. In Mule, the XSLT transformer component allows transforming XML payloads using XSLT stylesheets. For example, a flow uses an HTTP inbound endpoint, sets an XML payload, and applies an XSLT stylesheet using the XSLT transformer to output a new transformed XML payload. The XSLT stylesheet matches elements in the input XML and outputs a new structure defined in the stylesheet.
Groovy in Mule
This document discusses using a Groovy scripting component in Mule to add a delay to a flow. The Groovy component uses the sleep method to pause message processing for a specified time period. This allows holding the payload for a set interval before writing the file to the outbound location. The example flow reads a file from one directory, uses a Groovy script to sleep for 3000ms, then writes the file to another directory.
Mule technology
Mule is a lightweight Java-based messaging framework that allows for integration of applications regardless of technology. It uses an Enterprise Service Bus architecture to act as a transit system to carry data between applications. Mule wraps application functionality as services with components for business logic, routers to specify message destinations, and transports to carry messages while transforming data as needed between services. This enables exchange of data among applications to integrate systems with little code.
Mule anypoint exchange
Anypoint Exchange is a platform that allows for the exchange of data between systems using different patterns like aggregation, bi-directional, and broadcast. It supports the exchange of various object types like accounts, contacts, leads, and products at different difficulty levels from easy to difficult. Anypoint Exchange aims to facilitate data migration between systems and applications.
Mule real-world-old
Mule is used to implement an ESB that aggregates loan quotes from multiple banks. It uses Mule transports like JMS, HTTP, VM, and SOAP to connect various components. These include a LoanBroker service, CreditAgency, LenderService, and multiple Bank components. Messages are routed between components, transforming data and aggregating responses to return the best loan quote to the client.
Documantation with mule
Anypoint Studio has a built-in feature to automatically generate documentation for Mule projects. The documentation plugin allows users to generate an HTML-based documentation with a single click that describes each flow, element, and attribute in the project. Developers can add descriptive text to components using the "doc:name" attribute, which will then appear in the generated documentation. The documentation is saved as an index.html file in a selected folder, displaying both graphical and XML representations of the project's configuration.
Anypoint data gateway
Anypoint Data Gateway allows users to integrate data from legacy back-office systems like SAP, Oracle, and SQL into Salesforce using a simple visual interface. It supports connecting to various data sources instantly and eliminates the need for separate integration environments or extensive training. The Data Gateway is installed via the Salesforce AppExchange and provides a designer to create and publish gateways to external data sources and view existing source objects.
Send email attachment using smtp in mule esb
This document discusses sending email attachments using Mule ESB's SMTP connector. It describes how to configure a Mule flow to read a file from a source directory using the file inbound endpoint, transform it to a string using the file-to-string transformer, attach it to the message using the attachment transformer, and send it in an email using the SMTP outbound endpoint. The email will be sent to the specified recipient address with the file attached.
Mule google connectors
This document describes several Google connectors that are provided by Anypoint Platform from MuleSoft. It lists connectors for Google Prediction, Tasks, Contacts, Calendar, and Spreadsheets. Each connector allows integration between the respective Google service and third party applications by providing access to the Google APIs. The connectors allow applications to import, export, sync and modify data in Google services. This enables automation and extension of processes across different enterprise systems and departments.
Mule security-jaas
The document discusses how to configure the JaasSimpleAuthenticationProvider security provider in Mule to use the Jaas Authentication Service. It describes two configuration methods - passing a Jaas configuration file that defines login modules and credentials, or configuring attributes directly on the provider. The Jaas configuration file example shows a file defining a login module, required flag, and authorized users mapped to passwords.
Soap request in mule
The document discusses validating SOAP requests in Mule by using a schema validation filter. The filter allows validating a SOAP request against an XSD schema file. If invalid, a custom error message can be returned. The code example shows adding the filter to the flow before the SOAP service. This validates requests and routes invalid ones to a subflow to return the error.
Mule batch processing
Batch processing in Mule allows splitting messages into individual records, performing actions on each record in parallel, and reporting results. It is useful for integrating or synchronizing large datasets between systems, extracting/transforming/loading data into a target system, and handling large volumes of incoming API data. Mule's batch jobs simplify processing massive amounts of data with record-based reporting, error handling, and parallel processing.
Mule oracle connectors
This document describes several Oracle connectors that can be used with MuleSoft's Anypoint Platform to integrate Oracle applications and data with other systems. It lists connectors for Oracle Service Cloud (RightNow), PeopleSoft, Database, E-Business Suite (EBS), Siebel, and a Siebel to Salesforce contact synchronization connector. The connectors allow automated processes and data synchronization between the Oracle applications and other enterprise applications both on-premise and in the cloud.
Mmc rest api user groups
This document outlines the REST API operations for user groups in MMC, including creating, getting, updating, deleting user groups, and getting permissions. It provides the URL, HTTP method, and sample curl commands for each operation: to create a user group a POST request is used, GET is used to get user groups or a specific one, PUT updates a group, DELETE removes a group, and GET also retrieves all permissions.
Mule soap
This document discusses how to validate SOAP requests against an XSD schema file using a schema validation filter in Mule. The schema validation filter refers to XSD files to validate the SOAP request. If invalid, a custom error message is thrown. The code example shows adding the schema validation filter to the flow and configuring it with the XSD schema location.
Viewers also liked (20)
Similar to Mule velocity
Dynamic file attribute
The document discusses how to dynamically set file connector attributes in Mule at runtime by reading values from a JSON file. It presents a Mule flow that uses a file inbound endpoint to read a JSON file containing folder path, file pattern, and work directory. These values are then parsed and set as variables to configure a file outbound endpoint, which writes the file to the specified location. This allows file connector attributes like path and name to be dynamically determined based on external configuration.
Email configuration in mule esb
This document discusses how to send an email attachment using Mule ESB's SMTP connector. It explains that Mule ESB allows connecting applications together quickly through its lightweight Java-based integration platform. The example demonstrates configuring a flow that reads a file from a source directory, attaches it to an email, and sends it using SMTP. It provides the XML configuration and console output showing the file being read and email sent with attachment.
What is html xml and xhtml
This document is a group assignment submitted by 6 students from Assosa University in Ethiopia on May 26, 2013. It provides information on HTML, XHTML, XML, and summarizes key differences between these markup languages. HTML is for creating web pages, XHTML is a stricter version of HTML, and XML is a generic markup language that allows users to define their own tags for transporting and storing data.
Automatic documentation with mule
Anypoint Studio has a feature to automatically generate documentation for Mule projects. The documentation plugin allows users to generate an HTML-based documentation with a single click. It documents each flow, element, and attribute in the project. Developers can add descriptions to components using the doc:name attribute, and these will appear in the generated documentation. The documentation is saved as an index.html file in a selected folder, displaying both graphical and XML representations of the project's flows and configurations.
Automatic documantation with mule
Anypoint Studio has a feature to automatically generate documentation for Mule projects. The documentation plugin allows users to generate an HTML report of all flows, elements, and code including attributes and descriptions provided in doc:name tags. Users select a folder location and the documentation is generated, containing both graphical and XML representations of all flows and components in the project. This simplifies the process of documenting Mule applications within the IDE.
Automatic documantation with mule
Anypoint Studio has a built-in feature to automatically generate documentation for Mule projects. The documentation plugin allows users to generate an HTML-based documentation with a single click that describes each flow, element, and attribute in the project. Developers can add descriptive text to components using the "doc:name" attribute, which will then appear in the generated documentation. The documentation is saved as an index.html file in a selected folder, displaying both graphical and XML representations of the project's configuration.
Automatic documantation with mule
Anypoint Studio has a feature to automatically generate documentation for Mule projects. The documentation plugin allows users to generate an HTML-based documentation with a single click. It documents each flow, element, and attribute in the project. Developers can add descriptions to components using the doc:name attribute, and these will appear in the generated documentation. The documentation is saved as an index.html file in a selected folder, displaying both graphical and XML representations of the project's flows and configurations.
Automatic documentation with mule
Anypoint Studio has a built-in feature to automatically generate documentation for Mule projects. The documentation plugin allows users to generate an HTML report of all flows, elements, and code including attributes and descriptions provided in doc:name tags. To generate documentation, users simply select the documentation plugin in Anypoint Studio and choose an output folder. The plugin then builds an index.html file containing graphical and code views of each flow and component in the project.
Automatic documentation with mule
Anypoint Studio has a feature to automatically generate documentation for Mule projects. The documentation plugin allows users to generate an HTML report of all flows, elements, and code including attributes and descriptions provided in doc:name tags. Users select an output folder, click the documentation plugin, and a fully navigable documentation site is generated with graphical and code views of all project components. The automated documentation simplifies explaining how a Mule application operates and makes project knowledge sharing easier.
Joomla tempates talk
The document provides information about creating custom Joomla templates including discussing various tools used for template development, the anatomy of a Joomla template including key files and elements, and how to package and install a custom template. It outlines the responsibilities of the index.php file as the entry point and discusses including modules, components, and other elements. The document appears to be from a talk or presentation on how to build custom Joomla templates from start to finish.
Automatic documantation with mule
Anypoint Studio has a feature to automatically generate documentation for Mule projects. It allows users to generate an HTML-based documentation file with a single click. The documentation generator plugin extracts information from code comments and attributes to document each flow, element, and component in the project. Developers can add descriptive text in doc:name attributes to include explanations of components that will appear in the generated documentation.
Automatic documentation with mule
Anypoint Studio has a feature to automatically generate documentation for Mule projects. It allows users to generate an HTML-based documentation file with a single click. The documentation generator plugin extracts information from code comments and attributes to document each flow, element, and component in the project. Developers can add descriptive text in doc:name attributes to include explanations of components that will appear in the generated documentation.
Presentation 1 [autosaved]
- In this course you will learn how to create a responsive web design that adapts to different screen sizes by changing the layout and rearranging content, and also optimizes the design for printing. You will start by building the HTML structure and then use CSS to style the content and create different layouts based on screen size and media queries. The course provides step-by-step instructions to teach techniques for responsive design, CSS styling, and combining HTML elements with CSS properties.
Mule connectors-session1
The File and Database connectors in Mule allow applications to exchange files and connect to databases. The File connector can read and write files as an inbound or outbound endpoint. The Database connector performs SQL operations like select, insert, update and delete. Mule also supports web services through connectors that consume or expose SOAP/REST APIs.
Trigger Emails BigD17
It’s a simple concept, a new user is added and an email is triggered to let them know what to do to get started with the application. But is it that simple? There is so much to consider before creating that email. What does the email look like? How do you code the html? Why does it look different in every email client? How do we keep track of all the different emails going out? What is the tone of voice in the copy? What are the other triggers that call for an email to be sent to the user? What about translating the emails? How can we structure templates to make them translated easily?
Automatic documentation with mule
The document discusses how Anypoint Studio can automatically generate documentation for Mule projects. It has a built-in documentation generator plugin that allows users to export project documentation as HTML files with details about each flow, element, and code attributes. The document provides an example of adding descriptions to components using doc:name attributes, then generating documentation that includes both graphical and XML representations of the flows and components.
Send email attachment using smtp in mule esb
Mule ESB is a lightweight Java-based integration platform that allows developers to connect applications together quickly and easily. It enables integration regardless of application technologies. The document provides an example of using Mule ESB to send an email attachment by reading a file from a source directory using the SMTP connector and attachment transformer. It describes the prerequisites and provides the full XML configuration for the flow.
Emberjs and ASP.NET
This document summarizes a presentation about Emberjs and its components. Emberjs is a framework for creating ambitious web applications that uses templates, components, controllers, models, routes and a router. Templates define the user interface using Handlebars, components organize the UI and define behaviors, controllers are similar to components, models represent persistent data, routes load controllers/templates/models, and the router maps URLs to routes. The presentation demonstrates creating an Emberjs app and some of its key concepts like objects, enumerables and the object model. It also discusses why one may choose Emberjs over Angular and the roadmap to move away from controllers to components.
Mule connectors-part 1
The document discusses various connectors in Mule ESB including the File, Database, and Web Service connectors.
The File connector allows exchanging files with the file system and can be configured as an inbound or outbound endpoint. The Database connector allows connecting to relational databases using JDBC to perform SQL operations. The Web Service connector allows consuming existing web services, building new services, and creating proxies. The REST component allows Mule to act as a RESTful service consumer or publisher.
Mulesoft - Documentation (Automation)
Anypoint Studio has a built-in documentation generator plugin that allows users to automatically generate HTML documentation for their Mule projects with a single click. The documentation generator extracts descriptions from doc:name attributes in the code and presents both graphical and XML representations of each flow and component. Users can specify an output location, then the documentation is generated, saving an index.html file that can be viewed in a web browser to see documentation on all flows and their configurations.
Similar to Mule velocity (20)
More from Praneethchampion
Mule execution
1) The document describes a real-world loan broker application that uses Mule to integrate various systems and services. It involves a loan broker service receiving requests and coordinating responses from a credit agency, lender service, and banks.
2) Key components include a loan broker endpoint, credit agency gateway, lender gateway, and banking gateway. Messaging is handled through JMS, with services exposed via transports like HTTP, JMS, EJB, and SOAP.
3) The implementation uses Mule components, transports, and message routing to handle the request flow, transforming data between formats and systems as needed.
Mule soa
1. The document discusses selecting Mule as an ESB over other open source options like Fuse after evaluating criteria like maintenance, support, licensing, performance, and integration capabilities.
2. Examples of Mule use cases are presented, including embedding Mule in a Java web application, controlling access to endpoints using Spring security, and routing requests to different data sources using Groovy.
3. Best practices discussed include using Mule testing components during development, combining SoapUI with mock services for testing, and taking a staged approach to migrating systems to the new ESB architecture.
Mule esb stripe
MuleSoft's Stripe connector allows developers to integrate their MuleSoft applications with the Stripe API to perform payment-related functions like accepting payments, creating invoices and customers. The document provides steps for setting up a Stripe developer account, configuring the Stripe API key, and using the Stripe connector in a Mule flow to create a customer and coupon in Stripe. Sample Mule flows are demonstrated to showcase how to trigger customer and coupon creation via HTTP requests.
Dataweave
DataWeave can be used in Mule to transform message payloads. The Transform Message element allows writing DataWeave code to transform incoming message elements into outgoing message elements. The editor provides input/output previews and autocomplete. DataWeave expressions can also be used directly in other Mule components using the dw() function.
Mule for each scope header collection
The document discusses using a foreach scope to process a list of values in the message header of a Mule flow. An HTTP listener converts query parameters to a map accessible by key. A Java component converts comma separated query parameter values to a list for foreach to iterate over. The flow uses the Java component after the HTTP listener to convert the query parameters to a list that a foreach scope then processes.
Mmc
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive functioning. Exercise boosts blood flow, releases endorphins, and promotes changes in the brain which help enhance one's emotional well-being and mental clarity.
Mule esb api layer
MULE ESB provides an API layer that offers a decoupled interface for interacting with applications in a common, language-agnostic way. Common uses of an API layer include connecting to legacy applications that lack REST APIs or publishing APIs for partners to communicate with systems through a well-defined interface. The Anypoint Platform enables API-led connectivity by helping users build, design, and manage APIs from a single platform to expose enterprise data and applications in a secure and controlled way.
Mule security
The document discusses Mule's support for SAML (Security Assertion Markup Language) for exchanging security information between federated systems. Mule version 2.2.3 introduced support for SAML 1.1 when using CXF web services. Future versions will support additional transports. The SAML module is only available in the Mule Enterprise edition. The document provides instructions on configuring the SAML module, including adding the JAR, configuring the security manager with keystores and realms, and configuring security filters on CXF endpoints. It also describes the sender vouches and holder of key SAML profiles.
Webservice vm in mule
The document discusses decomposing a complex Mule flow into smaller parts using VM components.
The VM transport allows breaking a large, complex flow into smaller pieces connected by queues for better control and performance. This helps control each event queue, reduces flow complexity, and prevents resources from being overcommitted.
The example shows exposing a CXF web service by breaking the flow into two parts connected by a VM queue. It stores the SOAP action in a property before sending to the VM queue to preserve it for the second flow.
Scatter gather flow in mule
The document discusses scatter-gather flow control in Mulesoft. Scatter-gather sends a request message concurrently to multiple targets and aggregates the responses. It replaces the deprecated all message processor by executing routes in parallel instead of sequentially, improving efficiency. Scatter-gather collects results into a message collection. If a route fails, it sets the exception payload and throws a composite exception mapping failures to routes.
Mule rabbitmq
RabbitMQ is an open-source message broker software written in Erlang. It uses exchanges to route messages from producers to queues based on routing keys or bindings. There are four main exchange types - direct, fanout, topic, and headers. Mule connects to RabbitMQ using the AMQP connector. It can send and receive messages to/from RabbitMQ queues using different exchange types like direct exchanges as demonstrated in the example config with two flows, one to send and one to receive a message.
Mule quartz
Quartz transport in Mule allows scheduling inbound and outbound events. Cron expressions are used to define schedules and jobs trigger actions when a time trigger occurs. A simple example application writes a file to an outbound folder at a specified interval using Quartz, demonstrating how it can schedule flows to run periodically.
Mule drools
This document discusses using Drools, a business rules management system, with Mule to execute business rules in applications. It provides an example of creating a simple Mule application that uses a .drl file to define rules to determine a warehouse destination based on a randomly generated weight variable. The application is deployed to a Mule standalone server and the rules are executed by the Drools component to set the destination variable according to the rules.
Mule esb DataWeave
This document describes using DataWeave in Mule ESB to transform XML input into a Java object. It includes an XML input file, Mule flow configuration with a DataWeave transform, and a User Java class. The DataWeave transform defines a 'user' object type and maps the XML elements to fields on the User class, setting the payload to a User instance.
Idempotent filter in mule
The document discusses how to use an Idempotent Filter in Mule to avoid duplicate messages by checking message IDs. It provides an example of configuring an Idempotent Filter to use a simple-text-file-store to store message IDs in files and check for duplicates. When the example flow is run, it generates a text file to store message IDs and will return "passed" for new messages but "EXCEPTION" for duplicate messages.
More from Praneethchampion (15)
Recently uploaded
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Securing your Kubernetes cluster_ a step-by-step guide to success !
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Recently uploaded (20)
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Large Language Model (LLM) and it’s Geospatial Applications
Large Language Model (LLM) and it’s Geospatial Applications
Monitoring Java Application Security with JDK Tools and JFR Events
Monitoring Java Application Security with JDK Tools and JFR Events
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Securing your Kubernetes cluster_ a step-by-step guide to success !
Securing your Kubernetes cluster_ a step-by-step guide to success !
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Mule velocity
- 2. Have you ever wondered how to send an email through Mule Esb with a well designed format and where you can pick up some dynamic values from properties file and designed your email from a pre defined template and design in a colourful format with colourful text and logos ?? Yes you can design that email for your customers, subscribers or anybody else you wish to. Mule can trigger mail with a pre defined template where you can design the body of your email with different HTML tags and put various texts, text colour, images, logos in your email body and also pic some dynamic values in it. To design the template you only need a minimum knowledge of HTML tags and can design the template easily. Yes .. I am talking about Mule with Velocity template for your mail ..
- 4. Before we start, we will see what is Velocity template. Velocity is an open source templating tool developed by an international volunteer community and hosted by the Apache Software Foundation's Jakarta Project. You can find more information on it here :- https://velocity.apache.org/engine/releases/velocity- 1.5/user-guide.html#what_is_velocity To integrate Velocity template with Mule you will find good examples over net. There is already example by great David Dossot of using Velocity transformer class here :- https://muleinaction.googlecode.com/svn-history/r490/branches/mule-3/chapter05/velocity- transformer/src/main/java/com/muleinaction/transformer/MarkingVelocityMessageTransformer.jav a I have just modified the code and reused it as per my requirement
- 5. So, we first need a Velocity transformer Java class as following :- This class will set the email payload, map the external dynamic values with the email
- 6. So, we will also have external values from properties files as following :- These values from properties file will make the Velocity template dynamic as it will pick the values form here and set to the mail body .. Values like customer or subscriber name can be defined here dynamically
- 7. So, we will also have external values from properties files as following :- Here you can see, file is picked up by the flow and the file content is set as message body of the email along with other dynamic values from external properties file
- 8. And finally our Velocity template is as following :- Here you can see the HTML codes like <p/>, <img/> <html> tags are used to design the email content .. Also, values like $FileName, $Subscriber are picked from properties file. Also $payload is the content from the inbound file and it is appended with this mail body. Isn’t these are dynamic !!!!
- 9. Let’s test our application now.. Let’s place a file in the inbound folder with a content say This message is from a file !!! And start our application … we will see the console as following :- You can see the email has been send successfully and the email body as a preview in the log .. Now let’s check our actual email
- 10. Here is the mail we received from Mule with Velocity template and here what we got :- You can see different text formats, bold texts , images , logos etc that was designed in Velocity template with HTML codes. Also, you can see the values are picked from properties file
- 11. So, here you can see how to set a email body colourful and dynamic using Mule and Velocity template !!!….
- 12. In my next slide I will bring some other techniques in Mule implementation . Hope you have enjoyed this simpler version. Keep sharing your knowledge and let our Mule community grow