2017 is off to a great start for MuleSoft’s community: new initiatives are coming up, new meetups groups get formed and many new events are in the plans.
In the next four weeks only, 7 Meetups are planned across the USA and in Europe. We have many organizer applications pending so more groups will pop up in other countries soon – stay tuned!
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.
Last year, I embarked on a new adventure with Mulesoft Engineering. It’s been over six months, and it’s been an incredible experience, and I’ve learned a lot. I wanted to share my six biggest insights into what it’s like working here.
What’s Mulesoft? We help businesses become more productive. We provide a platform that helps enterprises connect and orchestrate backend systems they build and/or use, which in turn saves time and money. I work on the Cloudhub Engineering team, and we are responsible for running the engine for deploying, running, and managing Mule applications in the cloud.
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.
With the rise of new technology trends, changing consumer behavior and disruption by new market entrants across industries, one thing has become clear: Speed is becoming the currency of success as organizations adapt to ever-changing market forces.
As such, the trends that are set to take hold over the next 12 months are ones that will not only help an organization evolve, but do it faster than the competition.
2016 has finally come to an end, and that means an opportunity for your IT teams to start fresh and do great things for the business in 2017. But where’s the best place to start? Here are our top 7 r resolutions for your teams to consider in the upcoming year.
Don’t take security for granted.
High profile security breaches this year highlighted just how important security practices are when doing business. Don’t wait until the last minute to implement security best practices when delivering projects; consider implementing security by design.
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.