Slides are also available now, click here to view them.
The combination of legislative, technological, and market pressures has created a digital transformation imperative in healthcare.
For healthcare IT teams, addressing this imperative requires the the ability to expose and orchestrate data between clinical and non-clinical systems, while doing so in a way that promotes reuse and accelerates project delivery.
With MUnit 1.2.0, we launched Domain Support, and since then, we have been collecting feedback on the release. We take quality very seriously here – after all, we are a testing framework aimed at ensuring the quality of your code. With that in mind, we looked very carefully at what our users were saying and fixed every bug we could find.
About three months ago, we released Studio 6.0, which was a significant step towards covering all API-related use cases in one single design environment. Since then, almost half of our active users have embraced Studio 6.x, to define, create, consume and test APIs. Now, we are excited to release Studio 6.1 as another step to make Studio the most powerful and productive API development and integration tool.
In this blog post, I’d like to show you a step-by-step guide on how to set up an OAuth2 configuration using the HTTP Connector in Studio 6.0. I will use the GitHub RAML using the OAuth2 configuration to get a list of emojis supported by GitHub. You can also follow this example to set your OAuth2 configuration using the HTTP Connector for different RAMLs or APIs.
I previously published a blog post in DZone that demonstrated how to design a RAML in API Designer, which is an online cloud editor that uses an in-browser filesystem in HTML5 Local storage. But then I thought of exploring some more options for a tool/editor that can help us to design and code our RAML locally as an IDE (such as Eclipse or Netbean for Java).
MuleSoft has launched a beta release of API Workbench. This is an integrated development environment (IDE) allows developers to build RESTful APIs based on a design-first approach. API Workbench supports both RAML 0.8 and the newly launched RAML 1.0. RAML (RESTful API Modeling Language) is one of several API description specifications than can be used to design and document APIs.
This post is the second in a three-part series covering the IoT projects that came out our first internal hackathon of the year and that we had on display at our first Integration of Things Zone at CONNECT 2015. Missed us there? No worries, not only will you get a sense of the cool installations we built below, you’ll also get a front row seat as to how we built them,
Today, the Mule 3.7 runtime and Anypoint Studio June 2015 are now GA. This release brings to a close over two months of product announcements impacting nearly every aspect of Anypoint Platform. It also marks the beginning of a new way for our user community to experience our products — less as a collection of rich independent capabilities and more a unified platform with unified tooling and unified management to help users deliver value with speed,
Ever wanted to get certified on our Anypoint Platform, but discovered that you didn’t have the training?
We’d like to introduce MuleSoft.U: self-study, public, FREE certification courses that will enable developers to learn core MuleSoft skills. At a significant cost per seat for a public class, instructor-led training is unattainable for most independent developers. With MuleSoft.U, independent developers can get up and running in no time.
MuleSoft provides the most widely used integration platform for connecting any application, data source or API, whether in the cloud or on-premises. With Anypoint Platform®, MuleSoft delivers a complete integration experience built on proven open source technology, eliminating the pain and cost of point-to-point integration. Anypoint Platform includes CloudHub™ iPaaS, Mule ESB™, and a unified solution for API management™, design and publishing.