Box is one of the leading content and collaboration providers for enterprise, giving users the ability to store and share files from both personal computers and mobile devices like smartphones and tablets. With over 200,000 business clients and enterprise grade security and architecture, Box is a great example of how rising Silicon Valley stars use MuleSoft’s Anypoint Platform for internal and external integration needs.
As Box is onboarding an ever increasing number of Global Fortune 500 companies, the need for MS SharePoint integration is growing rapidly. These large companies have traditionally made large investments in SharePoint, but are now looking to Box to meet the needs of a more mobile, collaborative workforce. For most organizations with both SharePoint and Box, integration is difficult or non-existent.
It’s a pleasure for me to introduce the Mule Dropbox Connector. I’m sure you have heard of Dropbox and many of you have been delighted by its simple features, and now you can take advantage of them in your Mule applications.
Getting the Dropbox Connector
It’s really easy to start using this connector thanks to Mule Studio update site. To install it:
- Go to the menu Help -> Install new software
The DevKit is a tool for accelerating the development of Mule extensions. A popular Mule extension is what we call a Cloud Connector. A Cloud Connector provides Mule with the ability to receive and send messages to/from a cloud service provider. We do not make assumptions about whether that service provider is a REST-based service, a SOAP endpoint or a custom protocol on top of TCP. Having said that, we do offer certain services for some types of service providers. In this post I’m going to be talking about connection management, a feature in the DevKit that provides management and sharing of connections for those service providers that have stateful protocols.
Less than a month ago we released the DevKit 3.0 and we are on a roll here. Just in case you are jumping onto the bandwagon a little late, the DevKit is a tool for authoring Mule extensions. The model is quite easy. First you write a POJO, then you annotate your POJO with Mule concepts and then when you run DevKit on the code you authored it will generate all the needed boiler plate code including a Mule-compatible schema. Sounds exciting, isn’t it? Unfortunately this blog post is all about whats change since the last release, but if you want to learn more you can do so at our website here.
We added several features in this release but to keep this blog post short I will cover just a few of them.
As cliché as it is to say, it’s hard to believe that an entire year has passed since I last took stock of Mule. When I look back on 2011, it’s absolutely incredible to me how far MuleSoft and the Mule community have come.
Of all the professional networks available LinkedIn has clearly taken the lead with more than 120 million members. Do you use LinkedIn? Most likely you do! That’s why we thought it’s important to have a Cloud Connector to interact with LinkedIn and take advantage of its social power.
This section of our blog is about showcasing current and upcoming cloud connectors. Cloud Connectors are Mule modules that allow easy connectivity to cloud APIs such as Twiiter, Facebook, and the thousands of Software as a Service platform out there on the net.
This week we are presenting a new Cloud Connector for Attlasian Jira, one of the most popular issue tracker. JIRA is widely used in many different companies reaching the amazing amount of 14,500 organisations in 122 countries around the globe — across Fortune 1000, public enterprise, science and technology sectors.
More and more companies are using geocoding at some point in their business processes. Geocoding can help companies take smarter decisions by offering customers location-specific services and more. The fact is, geocoding is becoming a go-to resource for those with high hopes of increasing revenue, reducing expenses, and driving up customer loyalty and satisfaction. This is where an API like GeoNames comes into play.
Geocoding & Geotagging
Geocoding is the process of finding associated geographic coordinates (often expressed as latitude and longitude) from other geographic data, such as street addresses, or zip codes (postal codes). With geographic coordinates the features can be mapped and entered into Geographic Information Systems, or the coordinates can be embedded into media such as digital photographs via geotagging.
Working with web APIs, local APIs and different data formats and structures is too damn hard. You have to write painful verbose code to:
- Query Web APIs and work with the data
- Enrich and join data from external services with local services
- Compose RESTful services from existing services
- Version services and data formats
- Merge data from different sources into a common data format
- Sort through sets of data