With DevKit 3.8.0, partners can manage their connector’s license natively within DevKit. This feature will allow partners to require license entitlement before users can deploy their connector in runtime. Now, similar to how our Premium Connectors work, users will see a form requiring the entitlement before the connector can be deployed.
Since I joined the company this summer, one of my main tasks has been to improve the connector certification program. To do this, I’ve engaged with partners, developers and MuleSoft employees; to further familiarize myself with our technology and processes, I decided to build my own Google Translate Connector. I’ve learned a lot by going through the process and wanted to share some resources I found most useful as I was building my connector.
I get the awesome opportunity to work with lots of MuleSoft developers. Today, many are venturing into the brave new world of connector development. I find a new connector developer’s first steps into this realm can be challenging. My hope, with this blog post, is to identify some of those common gotchas in connector development with Anypoint Connector DevKit. I won’t spend much time on implementation here. Let’s instead ensure the pieces are in place to make your implementing smooth.
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, scale, and control.
Can MuleSoft connect ________ (insert name of any system) to ________? Regardless of how you’ve filled in the blanks, anyone from MuleSoft will answer with an enthusiastic, ‘Yes, we can!’
To enable this universal connectivity, along with increasing the breadth and the quality of our out-of-the-box connectors, we are continuing to invest in expanding the usability and feature set of our connectivity tooling, including our: HTTP Connector, Web Service Consumer, and our SDK, Anypoint Connector DevKit.
Sometimes pre-built connectors can solve your integration challenges; other times you might need a connector with a specific functionality or you might want to connect to a system without an available pre-built connector. In these cases, building your own connector may be the better route to take.
While getting started on building a connector from scratch can seem daunting at first, the challenge often becomes much more manageable when you understand the tools and resources that are available.
Anyone that has used DevKit to write a Mule extension and then wanted to add it to Studio, may have notice that the extension will appear under the Cloud Connectors category in the palette. This is not a problem when the extension is actually a Cloud Connector, but is sort of a problem when it was something else (for example a component like the LDAP connector). This is not an issue anymore since DevKit 3.3.2, as you can now use the @Category annotation at class definition level (Connector or Module) to select under which category you want your extension to be listed in:
Google Apps offers a cloud alternative to many of the office products. If you have a Gmail account then you have Google Apps including Spreadsheets, Docs, Presentations, Contacts, Calendars and Tasks. Of course Google Apps have APIS and of course we have the connectors to make it easy to connect Google Apps and your applications together. Lets get the connectors and then take a look at what you can do.
Today I would like to talk a little bit about releasing a new version of your Mule extensions. As you may know Mule is a an extensible platform with well defined integration points for plugging in your own connectors transformations, components and even routers. Suppose you have used The Mule Devkit to create your very own extension or cloud connector, and your project is so cool that it was accepted on MuleForge.
What happens if you make changes to you project and it moves from version 1.0 to 1.1? We’ll take a very quick look at how to do that in this post.
First, modify your pom.xml to increase your version number. In this case, we’ll go from 1.0 to 1.1:
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.