Articles

Send PDF Files as Binary Strings

,

Introduction

In this article, I am going to explain to you how we can use the power of MuleSoft to send PDF files from Experience API to Process/System API, using the multipart/form-data type, and to covert it back to PDF file in the second API.

Use Case

We are going to read the PDF file from the local disk using Mule’s out-of-the-box (OOTB) File connector to read in Experience API. Then we will be sending this PDF as binary with some other fields to another API (this can be named as Process API) which accepts data as multipart/form-data. Next, we will extract this PDF binary from the received payload and convert it back to PDF and save the file to the local disk using Mule’s OOTB File connector to write.

Source de l’article sur DZONE

/par

MuleSoft Integration With RabbitMQ

,

This article will explain in detail, how to integrate with RabbitMQ in MuleSoft and read messages from a queue.

Install and Setup RabbitMQ on Mac

In this section, I will explain how to install RabbitMQ on Mac, create a new queue and publish messages to the queue using the RabbitMQ portal.

Source de l’article sur DZONE

/par

How to Use Mulesoft VM Connector

,

VM Connector is used for intra-app (within the app) and inter-app communication through either transient or persistent asynchronous queues.               

  • Transient queues: This type of queue is volatile means data would be lost in case of system crashes or restart. Transient queues are faster than persistent queues.
  • Persistent queues: This type of queues are more reliable, data would be persisted in case of a system crash or failure, or restart. These queues are slower than Transient Queues.

VM Connector is mainly used for the following: 

Source de l’article sur DZONE

/par

MuleSoft for Beginners – Mule 4 Development (Complete Series )

,

Hey Guys

These are below 10 videos that help you to learn MuleSoft Development Hands-on!

Source de l’article sur DZONE

/par

Working With Custom Policy in Mule 4

,

MuleSoft Custom Policies can be layered on top of the implementation of the APIs to provide the governance, security, and visibility required. While the out-of-the-box API management policies cover the majority of use cases, an organization may need to create a custom policy to meet specific business needs.

There is a lot of documentation that shows how to work with MuleSoft custom policies through API manager, however, developing the custom policy and debugging them locally has been always challenging. In this article, I will demonstrate how to develop and test Mule custom policy on your local standalone Mule runtime instances before uploading to the API manager or Exchange for live running APIs.

Source de l’article sur DZONE

/par