This is second in series of how to DevOps articles, and is a follow-up to the MUnit blog – HowTo(DevOps) – Leveraging MUnit For Test Automation.
A core component of the continuous integration process, that includes the previously discussed test automation framework, is the build process. As soon as the developer commits the code to version control repository, the build tool compiles the source code runs unit and integration tests and generates feedback for the developers.
New year, new tips! But, before sharing this week’s Training Talks question, here’s a fun fact about one of our technical instructors, Poornima Sundararaman.
In grad school, Poornima worked on a software project for NASA to engineer a plant gardening robot that monitors and gardens hydrophobic plants (tomatoes and strawberries to start with) in outer space for astronauts to consume. How cool is that?
Mule ESB allows you to connect to anything and anywhere using a wide range of connectors and endpoints. File connector is one of the commonly used connectors that allows you to read/write files with file systems. There are two ways to use file connector –
- Inbound Endpoint – When file connector is used at the beginning of the flow, it acts as an inbound endpoint where you can receive files for processing.
This post was originally written by Filip Vavera from profiq.
I would like to share my first experience with developing a connector. I decided to develop a Gitlab connector because it is a great system and I did not find a connector that would be developed for it.
First, I’m going to focus on describing the options you have when you decide to develop a connector. Next, I will describe, how to structure the connector and what are the specifics that you need to care of in comparison to the development of a standard Java program.
Studio’s Visual Debugger allows you to run your application in Debug mode, stopping execution to check the contents of a message at previously-specified building blocks.
To do this, you set a breakpoint at any building block in your flow that you wish to check or test. When you run your application in Debug mode, the application stops immediately after executing the building block with the breakpoint. Using the Mule Debugger View, you can browse through the contents of the message as it exists at that point in the flow, and evaluate Mule Expressions against the message.
CloudHub is the platform as a service (PaaS) component of Anypoint Platform. It is a fully-managed, multi-tenanted, globally available, secure and highly available cloud platform for integration and APIs.
If you’re new to CloudHub and are learning how to deploy an application from Anypoint Platform, here are some things you need to know:
- Only a CloudHub Administrator can move applications between environments.
Traditional integration platforms could get away with providing some command line tools to automate the build and deployment of applications built on their platform. But in the modern world, integration platforms need to encompass the critical API management & cloud components as well, so the scope of continuous integration and continuous delivery tools are no longer just limited to integration applications only.
Interested in learning more about how to use Anypoint Platform? It’s time to get that dust off your running shoes because we’re going to get you in top MuleSoft shape. There’s nothing like having something extra to add to your learning routine, whether it’s helpful tips from our forum or challenges from the Champions Program, we’re growing the number of resources for you to become an Anypoint Platform expert.
As organizations embrace APIs for exchanging information with internal or external customers and partners, it’s critical not to sacrifice visibility or governance. That’s where API management comes in. API management policies can be layered on top of the implementation of the APIs to provide the governance, security and visibility required.
Out-of-the-box the Anypoint platform provides a full number of policies. Policies are grouped into categories of:
Welcome to this series of “HowTos” covering exceptions in MuleSoft Anypoint Platform. We will be covering many topics specifically with exceptions and exception/error handling in Mule integration flows.
The exception handling is demonstrated using a simple use-case. The example Mule project is available in exchange here.
Integration projects are complex, and exceptions are bound to happen. It is important that we have the ability to catch, categorize and handle exceptions so that we do not leave the system/application/data in an inconsistent state.