Sending mail in mule
•
0 likes•800 views
The document discusses how to send emails with attachments in Mule. It shows a Mule flow that uses a Groovy component to design the email body in HTML format. An Attachment component then attaches a file to the message payload. Finally, an SMTP component sends the email with the attached file. The flow is triggered by hitting a URL, which is demonstrated in the logs and by checking the recipient's mailbox, where the email with attachment is received.
Report
Share
Report
Share
Recommended
Input and output flow using file to string and logger component
The document discusses using File, File to String, and Logger components in Mulesoft Anypoint Studio to read a text file and log its contents. The steps are: 1) Create a Mule project in Anypoint Studio, 2) Drag File, File to String, and Logger components onto the message flow, 3) Configure the File component to point to a local folder, 4) Configure the Logger to print the file contents to the console, 5) Run the Mule application and drop a text file in the folder to see it logged.
Mule esb lesson 3
This document provides instructions for creating a simple Mule ESB flow that reads a text file, converts it to a string, and logs the string to the console. The steps are:
1. Create a new Mule project in Anypoint Studio and add a HTTP component, Java component, File component, File-to-String transformer, and Logger component to the message flow.
2. Configure the File component to point to a local folder and text file.
3. Configure the Logger to print the flow message to the console.
4. Run the Mule application and view the console log, which prints the content of the text file after it is dropped in the configured folder.
Example esb file-to-string flow
This document provides instructions for creating a simple Mule HTTP flow that uses a File to String transformer and Logger component to read a text file and log its contents to the console. The steps are to create a Mule project, drag the necessary components into the flow, configure the File component to point to a local folder, add a Logger to print the message, and run the Mule application to see the file contents logged.
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.
Simple interact between http and java components
This document provides instructions for creating a simple Mule ESB application that exposes an HTTP endpoint to trigger a Java component that writes data to a file.
The steps are:
1. Create a new Mule project in Anypoint Studio and add an HTTP listener on port 8081 and path /filetransfer configured for GET requests.
2. Add a Java component and create a class to write data to a text file located in a specific folder.
3. Configure the Java component to reference the class.
4. Start the Mule server and test the application by making a GET request to http://localhost:8081/filetransfer which will trigger the Java class to write to the file
Mule esb - How to use Idempotent Filters in 5 minutes
This document discusses how to use an idempotent filter in Mule ESB to ensure unique messages are received by a service. It explains setting up an HTTP inbound endpoint to trigger a flow, then using an expression filter configured to allow messages to pass only if the expression evaluates to true once, such as a unique name parameter. The document tests sending a message with the same name parameter twice to demonstrate the filter will only allow the first unique message to pass through successfully.
Mule esb How to convert from CSV to Json in 5 minutes
This document provides a tutorial for converting a CSV file to JSON format using Mule ESB in 5 minutes. It describes creating a simple Mule flow with a file reader component to read a sample CSV file, using a DataWeave transformer to convert the CSV data to JSON format, and adding an object-to-string transformer and logger to output the results.
Mule esb file to-string flow
This document provides instructions for creating a simple Mule ESB flow that uses a File to String transformer and Logger component. The flow reads a text file from a local folder using the File component, transforms it to a string using File to String, and logs the message to the console using the Logger. The steps include creating a Mule project in Anypoint Studio, dragging the necessary components into the flow, configuring the File component path, saving and deploying the project, and observing the logged output in the console to confirm it is working.
Recommended
Input and output flow using file to string and logger component
The document discusses using File, File to String, and Logger components in Mulesoft Anypoint Studio to read a text file and log its contents. The steps are: 1) Create a Mule project in Anypoint Studio, 2) Drag File, File to String, and Logger components onto the message flow, 3) Configure the File component to point to a local folder, 4) Configure the Logger to print the file contents to the console, 5) Run the Mule application and drop a text file in the folder to see it logged.
Mule esb lesson 3
This document provides instructions for creating a simple Mule ESB flow that reads a text file, converts it to a string, and logs the string to the console. The steps are:
1. Create a new Mule project in Anypoint Studio and add a HTTP component, Java component, File component, File-to-String transformer, and Logger component to the message flow.
2. Configure the File component to point to a local folder and text file.
3. Configure the Logger to print the flow message to the console.
4. Run the Mule application and view the console log, which prints the content of the text file after it is dropped in the configured folder.
Example esb file-to-string flow
This document provides instructions for creating a simple Mule HTTP flow that uses a File to String transformer and Logger component to read a text file and log its contents to the console. The steps are to create a Mule project, drag the necessary components into the flow, configure the File component to point to a local folder, add a Logger to print the message, and run the Mule application to see the file contents logged.
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.
Simple interact between http and java components
This document provides instructions for creating a simple Mule ESB application that exposes an HTTP endpoint to trigger a Java component that writes data to a file.
The steps are:
1. Create a new Mule project in Anypoint Studio and add an HTTP listener on port 8081 and path /filetransfer configured for GET requests.
2. Add a Java component and create a class to write data to a text file located in a specific folder.
3. Configure the Java component to reference the class.
4. Start the Mule server and test the application by making a GET request to http://localhost:8081/filetransfer which will trigger the Java class to write to the file
Mule esb - How to use Idempotent Filters in 5 minutes
This document discusses how to use an idempotent filter in Mule ESB to ensure unique messages are received by a service. It explains setting up an HTTP inbound endpoint to trigger a flow, then using an expression filter configured to allow messages to pass only if the expression evaluates to true once, such as a unique name parameter. The document tests sending a message with the same name parameter twice to demonstrate the filter will only allow the first unique message to pass through successfully.
Mule esb How to convert from CSV to Json in 5 minutes
This document provides a tutorial for converting a CSV file to JSON format using Mule ESB in 5 minutes. It describes creating a simple Mule flow with a file reader component to read a sample CSV file, using a DataWeave transformer to convert the CSV data to JSON format, and adding an object-to-string transformer and logger to output the results.
Mule esb file to-string flow
This document provides instructions for creating a simple Mule ESB flow that uses a File to String transformer and Logger component. The flow reads a text file from a local folder using the File component, transforms it to a string using File to String, and logs the message to the console using the Logger. The steps include creating a Mule project in Anypoint Studio, dragging the necessary components into the flow, configuring the File component path, saving and deploying the project, and observing the logged output in the console to confirm it is working.
2310 b 17
This document provides an overview and content review of 17 modules covering topics related to developing web applications using the Microsoft .NET framework and ASP.NET. The modules cover using Visual Studio .NET, .NET languages, creating ASP.NET web forms, adding code and tracing, validating user input, creating user controls, accessing data, working with XML and web services, managing state, configuring and optimizing ASP.NET applications, securing ASP.NET applications, and a review game and course evaluation.
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.
Email server system1.ppt
Microsoft Outlook is used to manage email in organizations using different domains. It sends emails from employees or clients to the main server using SMTP. For Linux/Unix systems, a lightweight command line tool called Email Server System is used to perform similar email functions. The Email Server System has a simple interface and can send emails and attachments to multiple users. An email server receives emails from users and forwards them to recipients. It consists of storage to hold emails for local users and components to transfer messages between mail servers and email clients. An email client-server system involves multiple clients connecting to a central server, which provides services to clients upon request.
Processing files sequentially in mule
This easy-to-follow tutorial will get your files processed in the order you want them. All it takes is Mule ESB and a bit of Java.
Email server configuration on cisco packet tracer
Mail server configuration on cisco packet tracer. We configured the mail server on the cisco packet tracer.
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.
Packet Tracer WEB & Email
This document describes a Packet Tracer activity to configure and test web and email services on simulated servers. The activity involves two parts: 1) configuring HTTP web services on CentralServer and BranchServer and verifying access from a client, and 2) configuring SMTP and POP3 email services on the servers, creating users, and sending emails between clients to test the services. DNS is used to translate domain names like centralserver.pt.pka to IP addresses.
Mule esb How to convert from Json to Xml in 5 minutes
This document discusses how to create a JSON to XML converter using Mule ESB in 5 minutes. It describes creating an HTTP listener flow to receive JSON data from an external source. A XML transformer is used to transform the JSON to XML. A logger is added to output the transformed XML to the console. The application is tested using Postman to send a request and see the XML response.
Node mailer example how to send email using nodemailer with gmail & mailtrap
This document discusses how to send emails from a Node.js application using Nodemailer. It explains that Nodemailer is a popular module for sending emails and describes how to set up Nodemailer with either a Mailtrap or Gmail account. The document provides step-by-step instructions for sending basic text emails, HTML emails, and emails with attachments from a Nodemailer application.
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.
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.
Python component in mule
The document discusses using Python in Mule applications. It describes how Python allows interceptors to alter message properties and be used for tasks like logging. Python scripts can trigger database transactions or modify web interfaces. It then provides examples of Python features like accessing substrings, integer arithmetic, input/output, and using range functions. It concludes by demonstrating a simple Hello World Python script configured in a Mule flow.
Mail server
A mail server is a computer that handles email delivery. It implements the client and server portions of SMTP to reliably transfer messages between servers using TCP on port 25. A mail server stores users' incoming emails in their mailboxes and queues outgoing messages to be sent. IMAP and POP3 are additional protocols that allow users to access their mailboxes to read and manage messages.
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
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.
Email using mule
Mule ESB is an integration platform that allows applications to connect and exchange data regardless of technology. This document discusses using Mule ESB to send an email with an attachment. It describes using a file inbound endpoint to read a file from a source directory, an attachment transformer to add the file content as an attachment, and an SMTP outbound endpoint to send the email. Running the Mule application results in the file content being sent as an attachment in an email.
Javascript HTTP Requests
A basic introduction to how XMLHttpRequests work in Javascript. Written as a supplement to Eloquent Javascript Ch. 17 by Marijn Haverbeke.
Ftp server configuration on cisco packet tracer
This document provides instructions for configuring an FTP server on Cisco Packet Tracer, including building a network topology with a PC and server, assigning IP addresses, using an FTP client on the PC to upload a file to the FTP server, and verifying the file was received on the server. The tutorial explains how to set up the network infrastructure, transfer a file from the laptop to the server using FTP, and check the server's FTP directory to confirm the file was successfully received.
Mail server
A mail server is a computer application that receives emails from local users and remote senders, forwards outgoing emails for delivery, and stores emails in mailboxes. Key components of a mail server include the Mail Transfer Agent (MTA) that transports emails between hosts, the Mail Delivery Agent (MDA) that delivers emails to user mailboxes, and the Mail User Agent (MUA) email client software used by people to send and receive emails. Popular mail servers include Exim, Sendmail, Postfix, and Qmail.
Basic example using file connector in anypoint studio
The document discusses using the File connector in Anypoint Studio to exchange files between a Mule application and file system. The File connector can be used as an inbound or outbound endpoint and implements a one-way exchange pattern. An example configuration is provided to poll a directory for files, read the file contents, and write the contents to the logs.
Stored procedure in mule
The document discusses how to call stored procedures from a Mule application. It explains that Mule's database component allows connecting to JDBC databases and performing SQL operations including stored procedures. It provides steps to create a stored procedure in MS SQL, call it from a Mule flow, and test the application. The Mule database component makes it simple to invoke stored procedures on the database.
Input and output flow with logger component
The document discusses using File, File to String, and Logger components in Mulesoft Anypoint Studio to read a text file and log its contents. The steps are: 1) Create a Mule project in Anypoint Studio, 2) Drag File, File to String, and Logger components onto the message flow, 3) Configure the File component to point to a local folder, 4) Configure the Logger to print the file contents to the console, 5) Run the Mule application and drop a text file in the folder to see it logged.
More Related Content
What's hot
2310 b 17
This document provides an overview and content review of 17 modules covering topics related to developing web applications using the Microsoft .NET framework and ASP.NET. The modules cover using Visual Studio .NET, .NET languages, creating ASP.NET web forms, adding code and tracing, validating user input, creating user controls, accessing data, working with XML and web services, managing state, configuring and optimizing ASP.NET applications, securing ASP.NET applications, and a review game and course evaluation.
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.
Email server system1.ppt
Microsoft Outlook is used to manage email in organizations using different domains. It sends emails from employees or clients to the main server using SMTP. For Linux/Unix systems, a lightweight command line tool called Email Server System is used to perform similar email functions. The Email Server System has a simple interface and can send emails and attachments to multiple users. An email server receives emails from users and forwards them to recipients. It consists of storage to hold emails for local users and components to transfer messages between mail servers and email clients. An email client-server system involves multiple clients connecting to a central server, which provides services to clients upon request.
Processing files sequentially in mule
This easy-to-follow tutorial will get your files processed in the order you want them. All it takes is Mule ESB and a bit of Java.
Email server configuration on cisco packet tracer
Mail server configuration on cisco packet tracer. We configured the mail server on the cisco packet tracer.
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.
Packet Tracer WEB & Email
This document describes a Packet Tracer activity to configure and test web and email services on simulated servers. The activity involves two parts: 1) configuring HTTP web services on CentralServer and BranchServer and verifying access from a client, and 2) configuring SMTP and POP3 email services on the servers, creating users, and sending emails between clients to test the services. DNS is used to translate domain names like centralserver.pt.pka to IP addresses.
Mule esb How to convert from Json to Xml in 5 minutes
This document discusses how to create a JSON to XML converter using Mule ESB in 5 minutes. It describes creating an HTTP listener flow to receive JSON data from an external source. A XML transformer is used to transform the JSON to XML. A logger is added to output the transformed XML to the console. The application is tested using Postman to send a request and see the XML response.
Node mailer example how to send email using nodemailer with gmail & mailtrap
This document discusses how to send emails from a Node.js application using Nodemailer. It explains that Nodemailer is a popular module for sending emails and describes how to set up Nodemailer with either a Mailtrap or Gmail account. The document provides step-by-step instructions for sending basic text emails, HTML emails, and emails with attachments from a Nodemailer application.
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.
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.
Python component in mule
The document discusses using Python in Mule applications. It describes how Python allows interceptors to alter message properties and be used for tasks like logging. Python scripts can trigger database transactions or modify web interfaces. It then provides examples of Python features like accessing substrings, integer arithmetic, input/output, and using range functions. It concludes by demonstrating a simple Hello World Python script configured in a Mule flow.
Mail server
A mail server is a computer that handles email delivery. It implements the client and server portions of SMTP to reliably transfer messages between servers using TCP on port 25. A mail server stores users' incoming emails in their mailboxes and queues outgoing messages to be sent. IMAP and POP3 are additional protocols that allow users to access their mailboxes to read and manage messages.
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
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.
Email using mule
Mule ESB is an integration platform that allows applications to connect and exchange data regardless of technology. This document discusses using Mule ESB to send an email with an attachment. It describes using a file inbound endpoint to read a file from a source directory, an attachment transformer to add the file content as an attachment, and an SMTP outbound endpoint to send the email. Running the Mule application results in the file content being sent as an attachment in an email.
Javascript HTTP Requests
A basic introduction to how XMLHttpRequests work in Javascript. Written as a supplement to Eloquent Javascript Ch. 17 by Marijn Haverbeke.
Ftp server configuration on cisco packet tracer
This document provides instructions for configuring an FTP server on Cisco Packet Tracer, including building a network topology with a PC and server, assigning IP addresses, using an FTP client on the PC to upload a file to the FTP server, and verifying the file was received on the server. The tutorial explains how to set up the network infrastructure, transfer a file from the laptop to the server using FTP, and check the server's FTP directory to confirm the file was successfully received.
Mail server
A mail server is a computer application that receives emails from local users and remote senders, forwards outgoing emails for delivery, and stores emails in mailboxes. Key components of a mail server include the Mail Transfer Agent (MTA) that transports emails between hosts, the Mail Delivery Agent (MDA) that delivers emails to user mailboxes, and the Mail User Agent (MUA) email client software used by people to send and receive emails. Popular mail servers include Exim, Sendmail, Postfix, and Qmail.
What's hot (19)
Mule esb How to convert from Json to Xml in 5 minutes
Mule esb How to convert from Json to Xml in 5 minutes
Node mailer example how to send email using nodemailer with gmail & mailtrap
Node mailer example how to send email using nodemailer with gmail & mailtrap
Viewers also liked
Basic example using file connector in anypoint studio
The document discusses using the File connector in Anypoint Studio to exchange files between a Mule application and file system. The File connector can be used as an inbound or outbound endpoint and implements a one-way exchange pattern. An example configuration is provided to poll a directory for files, read the file contents, and write the contents to the logs.
Stored procedure in mule
The document discusses how to call stored procedures from a Mule application. It explains that Mule's database component allows connecting to JDBC databases and performing SQL operations including stored procedures. It provides steps to create a stored procedure in MS SQL, call it from a Mule flow, and test the application. The Mule database component makes it simple to invoke stored procedures on the database.
Input and output flow with logger component
The document discusses using File, File to String, and Logger components in Mulesoft Anypoint Studio to read a text file and log its contents. The steps are: 1) Create a Mule project in Anypoint Studio, 2) Drag File, File to String, and Logger components onto the message flow, 3) Configure the File component to point to a local folder, 4) Configure the Logger to print the file contents to the console, 5) Run the Mule application and drop a text file in the folder to see it logged.
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.
Database integrate with mule
The document discusses Mule's new JDBC component that allows connecting to relational databases using a single interface. It provides examples of how to perform SQL operations like select, insert, update, delete using parameterized, dynamic and template queries. It also demonstrates how to call stored procedures. Configuration of the database connector and different query types like parameterized, dynamic and from template are explained.
Input and output flow using http and java component
The document describes how to create an HTTP input and Java component flow in Mule to create a text file. It involves creating a Mule project in Anypoint Studio, dragging an HTTP listener and Java component into the flow, configuring the HTTP listener endpoint and Java transformer class, running the Mule server, and making an HTTP request to trigger the flow and generate a text file.
Viewers also liked (6)
Basic example using file connector in anypoint studio
Basic example using file connector in anypoint studio
Input and output flow using http and java component
Input and output flow using http and java component
Similar to Sending mail in mule
Protocols and standards (http , html, xhtml, cgi, xml, wml, c html, etc)
in this presentation i will describe about the standards and protocols of the following languages such as:
1. HTTP
2. HTML.
3. X-HTML
4. CGI
5. XML
6. WML
7. C-HTML
Mule with velocity
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.
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.
Mule with velocity
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.
Mule with velocity
Mule can be used to send emails with dynamically generated content from a Velocity template. A Velocity transformer class maps external properties to the email template. The template uses HTML tags to design the email with colors, images, and logos. Dynamic values like names are populated from a properties file. When a file is processed, its content is appended to the email sent using the Velocity template.
Mule with velocity
Mule can be used to send emails with a predefined Velocity template that allows designing the email body with HTML tags, images, and logos. Dynamic values can be picked up from a properties file and inserted into the template. A Velocity transformer Java class is used to set the email payload and map external dynamic values. The template contains HTML tags to design the email content and references dynamic values from the properties file. When tested, the application successfully sends an email with the customized body defined in the Velocity template.
Mule with velocity
Mule can be used to send emails with dynamically generated content from a Velocity template. A Velocity transformer class maps external properties to the email template. The template uses HTML tags to design the email with colors, images, and logos. Dynamic values like names are populated from a properties file. When a file is processed, its content is appended to the email sent using the Velocity template.
Mule with velocity
Mule can be used to send emails with dynamically generated content from a Velocity template. A Velocity transformer class maps external properties to the email template. The template uses HTML tags to design the email with colors, images, and logos. Dynamic values like names are populated from a properties file. When a file is processed, its content is appended to the email sent using the Velocity template.
Mule with velocity
Mule can be used to send emails with dynamically generated content from a Velocity template. A Velocity transformer class maps external properties to the email template. The template uses HTML tags to design the email with colors, images, and logos. Dynamic values like names are populated from a properties file. When a file is processed, its content is appended to the email sent using the Velocity template.
Mule velocity
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.
02 wireshark http-sept_15_2009
This document provides instructions for using Wireshark to analyze HTTP traffic. It describes capturing and examining HTTP GET requests and responses for simple HTML files, conditional GET requests, retrieving long documents, documents with embedded objects, and HTTP authentication. Key things to look for include the HTTP version, accepted languages, IP addresses, status codes, headers, file sizes, and number of packets. Capturing live traffic or using provided packet traces allows analyzing the HTTP messages and interactions.
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.
Composite source in bound and out-bound
The document discusses using a composite source in Mule to accommodate multiple inbound endpoints to trigger a flow. A composite source listens in parallel on different channels for incoming messages, and passes any received message to the first message processor to trigger the flow. This allows a single flow to be triggered by messages from different inbound endpoints like HTTP, file, FTP, etc. The document provides an example where a flow is triggered either by a Quartz scheduled task or by an HTTP request using a composite source with both endpoints.
Handle File on mule
The document discusses two ways to stop a Mule flow after processing a file: 1) stopping the flow at the end using a Groovy component, or 2) stopping the connector at the end. It focuses on the first option, showing how a Groovy script can call muleContext.registry.lookupFlowConstruct('Flow name').stop() to end the flow after a file has been read. This prevents any additional files from being processed by the inbound endpoint.
Send email attachment using smtp in mule esb
This document describes how to send an email attachment using Mule ESB's SMTP connector. It involves configuring a file inbound endpoint to read a file from a source directory, transforming it to a string, setting it as an attachment using the attachment transformer, and sending it via SMTP using properties like the host, username, password, to and from addresses. When run, it will read the file, send an email with it as an attachment, and output logs showing the file was read and email sent successfully.
Wireshark Lab HTTP v7.0 Supplement to Computer Network.docx
Wireshark Lab: HTTP v7.0
Supplement to Computer Networking: A Top-Down
Approach, 7th ed., J.F. Kurose and K.W. Ross
“Tell me and I forget. Show me and I remember. Involve me and I
understand.” Chinese proverb
© 2005-2016, J.F Kurose and K.W. Ross, All Rights Reserved
Having gotten our feet wet with the Wireshark packet sniffer in the introductory lab,
we’re now ready to use Wireshark to investigate protocols in operation. In this lab, we’ll
explore several aspects of the HTTP protocol: the basic GET/response interaction, HTTP
message formats, retrieving large HTML files, retrieving HTML files with embedded
objects, and HTTP authentication and security. Before beginning these labs, you might
want to review Section 2.2 of the text.1
1. The Basic HTTP GET/response interaction
Let’s begin our exploration of HTTP by downloading a very simple HTML file - one that
is very short, and contains no embedded objects. Do the following:
1. Start up your web browser.
2. Start up the Wireshark packet sniffer, as described in the Introductory lab (but
don’t yet begin packet capture). Enter “http” (just the letters, not the quotation
marks) in the display-filter-specification window, so that only captured HTTP
messages will be displayed later in the packet-listing window. (We’re only
interested in the HTTP protocol here, and don’t want to see the clutter of all
captured packets).
3. Wait a bit more than one minute (we’ll see why shortly), and then begin
Wireshark packet capture.
4. Enter the following to your browser
http://gaia.cs.umass.edu/wireshark-labs/HTTP-wireshark-file1.html
Your browser should display the very simple, one-line HTML file.
5. Stop Wireshark packet capture.
1 References to figures and sections are for the 7th edition of our text, Computer Networks, A Top-down
Approach, 7th ed., J.F. Kurose and K.W. Ross, Addison-Wesley/Pearson, 2016.
Your Wireshark window should look similar to the window shown in Figure 1. If you
are unable to run Wireshark on a live network connection, you can download a packet
trace that was created when the steps above were followed.2
Figure 1: Wireshark Display after http://gaia.cs.umass.edu/wireshark-labs/ HTTP-
wireshark-file1.html has been retrieved by your browser
The example in Figure 1 shows in the packet-listing window that two HTTP messages
were captured: the GET message (from your browser to the gaia.cs.umass.edu web
server) and the response message from the server to your browser. The packet-contents
window shows details of the selected message (in this case the HTTP OK message,
which is highlighted in the packet-listing window). Recall that since the HTTP message
was carried inside a TCP segment, which was carried inside an IP datagram, which was
carried within an Ethernet frame, Wireshark displays the Frame, Ethernet, IP, and TCP
packet information as well. We want to .
File server(h.m merajul hasan)
This document outlines steps to configure an FTP server and client on a laptop and server:
1) Configure static IP addresses on the laptop and server.
2) Connect from the laptop to the FTP server using the server's IP address and login credentials.
3) Create a file on the laptop, upload it to the server using FTP, and verify it has been received on the server.
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.
Send email attachment using smtp in mule esb
This document discusses how to send an email attachment using Mule ESB's SMTP connector. It describes how to configure a Mule flow to read a file from a source directory, attach it to an email message, and send the email using SMTP. The key components used are the file inbound endpoint to read the file, attachment transformer to attach it to the email, and SMTP outbound endpoint to send the email. Running the example flow results in the attached file being sent as an email attachment to the specified recipient address.
COZA HOST HELP
This document provides instructions for publishing a website using FTP. It discusses using an FTP client like FileZilla to connect to an FTP server and upload files. The steps include creating an FTP account, downloading and installing FileZilla, configuring FileZilla with FTP login credentials, connecting to the FTP server, copying files from the local computer to the server, and allowing the FTP client access through the firewall. The goal is to upload files to the server's /wwwroot folder so that other users can view the website when browsing to it.
Similar to Sending mail in mule (20)
Protocols and standards (http , html, xhtml, cgi, xml, wml, c html, etc)
Protocols and standards (http , html, xhtml, cgi, xml, wml, c html, etc)
Wireshark Lab HTTP v7.0 Supplement to Computer Network.docx
Wireshark Lab HTTP v7.0 Supplement to Computer Network.docx
More from Son Nguyen
Wsdl connector introduction
A WSDL endpoint in Mule allows invoking web services without generating a client. At runtime, it reads the WSDL to determine how to call the remote service and constructs SOAP messages using the payload and WSDL. CXF and Axis provide WSDL connectors that create a dynamic proxy for the service. The WSDL URL and operation must be specified. CXF is generally recommended, but Axis may be needed if CXF has issues. Multiple arguments can be passed from the console to invoke a service and output the response.
Android intergrate with mule
This document provides steps for integrating an Android application with a Mule API. It outlines how to build an Android app that can make requests to a backend service API, connect from the Android app to the service API using Retrofit, and test and publish the application. The steps include creating a new Android project, setting up permissions, applying Retrofit to connect to the API, accessing MuleSoft's Anypoint Platform to update and test the API, and then publishing the final application.
Mule flow overview
This document provides an overview of a Mule Flow that includes a custom filter. It shows how to configure an XML flow definition that receives an HTTP request, logs the payload, converts the XML payload to JSON, and passes it through a custom Java class filter. The flow demonstrates how to build a custom filter that can manipulate the payload as needed within a Mule application.
Mule flow and filter
This document describes a Mule Flow that uses a custom Java filter class to filter XML payload data converted to JSON. The flow contains an HTTP listener, XML to JSON transformer, and custom filter that can manipulate the JSON data as needed before it is logged. The full XML configuration for the flow is provided.
Handle exceptions in mule
Mule provides default exception handling but also allows custom exception strategies to implement more precise error management. Exception strategies include choice, catch, and rollback strategies. A rollback strategy reverts a message flow to an earlier state if an exception occurs during a transactional flow.
Spring security integrate with mule
This document discusses how to integrate Spring Security as a security manager in Mule. It provides an example configuration that uses an in-memory database of users for authentication. Key aspects covered include configuring Spring Security providers, adding the necessary XML schema references, using security filters on connectors to handle authentication and attaching credentials to requests, and defining a proxy bean to apply security interceptors.
Message processor in mule
The document summarizes various message processors in Mule, including their purpose and example usage. Key message processors described include:
- All - Sends the same message to multiple targets.
- Async - Runs a chain of processors in a separate thread.
- Choice - Sends a message to the first matching processor.
- Collection Aggregator - Groups messages by correlation ID before forwarding.
- Collection Splitter - Splits messages whose payload is a collection.
- Custom processors - Allow custom message processing logic.
- Filtering processors - Filter messages based on properties.
- Routing processors - Route messages in various ways like first successful, round robin, etc.
Expression language in mule
The document provides an overview of Mule Expression Language (MEL), including its main uses and syntax. MEL allows accessing and manipulating message properties and context through expressions. Key points include:
- MEL expressions can make decisions, select values, replace tokens, and act as scripts using message properties and context.
- Syntax is Java-like with property expressions to access message fields. Operators include arithmetic, comparison, logical, and control flow statements.
- Context objects model the message, server, Mule instance, and application to access environment properties in expressions.
- Variables store expression values globally or across flows. Functions extract data through XPath and regex expressions.
Mule with data weave
The document discusses various ways to transform data and integrate systems using Mule and DataWeave including: calling global MEL functions from DataWeave; using the read, write, and log functions; and calling external flows. It provides code examples for defining global functions, reading and writing different data formats, logging output, and triggering other flows.
Using spring scheduler mule
Using Spring Scheduler Mule allows scheduling tasks in Mule applications using a Java class and Spring task scheduler. This provides an alternative to using Quartz scheduler or Poll components. The document demonstrates creating a Java class that prints a message every 10 seconds, and configuring the Spring task scheduler in Mule to trigger that class repeatedly to continuously monitor an application.
Batch job processing
The document discusses batch job processing in Mule. It describes a use case where a batch job queries a database to retrieve approved users and generates a CSV file with the user account attributes. Batch processing in Mule allows splitting messages into records, performing actions on each record, and reporting results. It is useful for integrating or synchronizing data sets, ETL processes, and handling large amounts of incoming data.
Using message enricher
The document discusses using a message enricher in Mulesoft to enrich messages by adding additional data from external sources. It provides an example of using an enricher to lookup the two-letter state based on the zip code contained in the original message. The enricher calls an external resource, retrieves the state, and adds it to the message as a new variable before sending it to the target system. This allows target systems to receive messages with more information than what the source system originally provided.
Finance connectors with mule
- Financial institutions need a new way to connect traditional delivery channels with emerging digital business models as they struggle with operational inefficiencies, disparate systems, legacy technology, and security concerns.
- Mulesoft provides connectors that allow for syncing of data and automation of processes between applications like QuickBooks, Avalara, FreshBooks, PayPal, and Zuora to help address these issues.
- The connectors enable seamless integration and consumption of APIs to help reduce double data entry and automate common business processes.
Google drive connection
The document discusses various Google connectors provided by MuleSoft that allow integration between Google services like Prediction, Tasks, Contacts, Calendar, and Spreadsheets with third party applications. It provides descriptions of each connector and explains how they enable access and synchronization of data between the Google services and applications like Salesforce, Outlook, and Excel through APIs.
Using properties in mule
Properties files allow configuration values to be externalized and reused throughout a Mule application. Property placeholders can be used to reference values from properties files, enabling environment-specific configurations. Values for placeholders can come from global properties, property files, environment variables, or runtime arguments, with earlier sources taking priority.
Mule integrate with microsoft
MuleSoft provides solutions for integrating Microsoft applications and platforms like .NET, Microsoft SharePoint, Microsoft Dynamics CRM, and MSMQ. This allows organizations to leverage existing Microsoft investments by connecting applications across diverse codebases on-premises and in the cloud on a modern integration platform. MuleSoft's solutions for Microsoft give IT organizations using .NET the ability to connect different applications and services wherever needed.
Jms queue
This document discusses JMS queues and provides an example of using a JMS queue with ActiveMQ. It describes JMS and the queue model, then provides steps to set up a Mule application that enqueues messages to an ActiveMQ queue using HTTP and receives messages from the queue using JMS. The example shows importing ActiveMQ libraries, creating an ActiveMQ connector, adding messages to the queue from HTTP and receiving them from the queue using JMS.
Anypoint connectors
Anypoint Connectors provide integration solutions for connecting applications, data, and devices across cloud and on-premises systems using a variety of pre-built connectors available on Anypoint Exchange. Connectors include those for ActiveMQ, Cassandra DB, generic databases, Amazon S3, Amazon SQS, Oracle Siebel, and more. They allow for CRUD operations and data synchronization between the target systems and MuleSoft's Anypoint Platform.
Mule esb basic introduction
Mule ESB is an open source enterprise service bus (ESB) that allows for lightweight and flexible integration. It uses a loosely coupled architecture and supports major protocols and technologies. Mule ESB uses a staged event-driven (SEDA) architecture that decomposes services into stages for modularity and code reuse. It processes messages using universal message objects (UMOs) and endpoints, with transports handling specific protocols and connectors sending/receiving messages. Transformation and routing are done through transformers, routers, and an exception strategy handles errors.
Runing batch job in mule
Mule ESB allows processing of messages in batches. A batch job splits large messages into individual records, processes each record through batch steps, and generates a report with results. Batch jobs are useful for processing large datasets from APIs, databases, or between applications. The key parts of a batch job are the input phase, loading phase, processing phase, and completion phase.
More from Son Nguyen (20)
Recently uploaded
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Things to Consider When Choosing a Website Developer for your Website | FODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
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.
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
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
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
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf
In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
Recently uploaded (20)
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Things to Consider When Choosing a Website Developer for your Website | FODUU
Things to Consider When Choosing a Website Developer for your Website | FODUU
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdf
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Sending mail in mule
- 1. Sending Mail in Mule
- 2. Have you ever wondered you can send mail from Mule application with attachment
- 3. We need attachment component in Mule to attach any files with current payload
- 4. Let us we have following Mule flow:- Here you can see we are using Groovy component to design the email body content in HTML format and that is followed by the Attachment component which will attach a file with the current message payload and will be send as a mail by the SMTP component
- 5. The corresponding Mule flow will be as follows:- You can see here Groovy component has designed the payload in HTML content and Attachment component has picked the file1.txt from it’s location and finally both the content and the attachmen is send as mail by SMTP component
- 6. Now we will be hitting our url http://localhost:8081/attachment on the browser to start the flow and we will get the following on log :- You can see in the log that email has been dispatched
- 7. We will be checking our mail box and will find the following :- You can see the mail has arrived
- 8. If you open the mail, you will find the content of the mail is designed in HTML format and the mail contains the attachment
- 9. 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