We’re happy to announce the release of MuleSoft’s Ideas Portal – where any user with a support login for Anypoint Platform can post new product enhancement ideas or upvote any existing ideas submitted by others in the community. We are excited to hear from you!
As part of the official release, we’ve reviewed over 300 enhancement requests and are moving them into the Ideas Portal. Customers who created these enhancement requests will receive emails from our support team so that you can start to follow your post!
If you share your code on GitHub with other developers, you may want to be notified about commits. GitHub has a built in feature to provide notifications or send an e-mail about these commits. I wanted to see, if I could leverage MuleSoft to introduce notifications through alternative channels, particularly through Twitter.
I implemented two solutions. Each has some pros and cons. You need to decide, which one works better for you. The description of the first one comes in this post.
How do you transition your organization from mainframe to microservices?
According to our recent survey of IT decision makers, 91% say that they are either undertaking digital transformation initiatives or planning to do so in the next three years. But nearly half say also say that legacy systems are the single biggest obstacle to achieving their digital transformation goals. Clearly, legacy modernization is on the minds of IT decision makers and is a key issue to resolve.
When it comes to choosing the right training it’s helpful to know all your options before making a final decision. Whether you’re a developer—with prior MuleSoft experience or not— a business manager, operations professional or architect, MuleSoft Training & Certification has a broad catalog that fits different roles and levels.
But it’s not only about your role and expertise level, it’s also about the investment you can make, of both time and money. Which is why you should consider MuleSoft.U when evaluating our recommended learning paths.
In this week’s Training Talks we’re going to talk about domains. But first, we have another fun fact from our next instructor, Ethan Port. Back in the 80’s (not that long ago), Ethan played the guitar and drums in a rock band that is still very popular today in Greece. Did I mention the drums were flaming?
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.