New Ways to Connect with 3 New Connectors – XBRL, Atlassian Stash, and Atlassian JIRA REST

Reading Time: 4 minutes

We are thrilled to introduce 3 new MuleSoft Certified Connectors developed by our partners through our connector certification program. These connectors have been thoroughly reviewed and certified by MuleSoft for their use case and compatibility with MuleSoft’s products. More connectors will come in a month or two. If you are interested in purchasing the connector or have questions, please contact the partners directly.

XBRL Connector by GLOMIDCO

icon-XBRL-big-w-badge

GLOMIDCO’s XBRL Connector tackles recognizable problems that many companies face when it comes to financial reporting, namely: the lack of transparency, efficiency, and accuracy. The XBRL Connector adds functionality to existing Mule environments that allows the organization to extract, aggregate, sort and render financial information from disparate enterprise systems throughout the company. The connector allows organizations to gain an increased transparency in the company’s business information supply chain, optimized compliance-related processes, increased business agility through continuous auditing and an improved governance landscape.

Atlassian Stash Connector by Hotovo

The Stash connector functions within a Mule application as a secure opening through which you can access and act upon your information in Stash. Using the connector, your application can perform several operations which Stash exposes via their REST API. When building an application that connects with Stash, for example, an application to display all your Stash repositories, you don’t have to go through the effort of custom-coding and securing a connection. Rather, you can just drop a connector into your flow, configure a few connection details, then begin transferring data. Atlassian Stash is now called Bitbucket Server.

Atlassian JIRA REST Connector by Hotovo

The Atlassian JIRA REST Connector from Hotovo integrates JIRA with existing SaaS and on-premises applications quickly and easily. The connector allows businesses to synchronize data and automate processes between JIRA and third-party collaboration, mobile, social applications such as GitHub, Clarizen, Salesforce or Desk.com. Connectivity with the latest, up-to-date JIRA REST API, gives users the ability to perform various operations, like tracking of issues and issue statistics, working with issues, comments, work logs, attachments, projects, user groups and other information, across third-party applications.

To see a complete listing of all connectors, take a look at Anypoint Exchange.


types of apis

How Visa is using APIs to digitally transform

Reading Time: 4 minutes

How we pay for things is fundamentally changing. You may have noticed this if you go into a store and pay for an item using an app on your phone, or by waving your smartwatch at a console.  Suddenly, handing over cash or a credit card seems a bit old-fashioned – people want to be able to pay for things whenever, wherever, without a great deal of fuss.

Visa has announced it will be opening its payment processing platform to third-party developers. This makes life easier for app developers to incorporate Visa seamlessly into any payment system they’d want to develop, and because nearly everyone in the western world has a Visa card, it opens up payment processing to a larger customer base, which is attractive to app developers.

And it also means that developers are going to come up with increasingly interesting and innovative ways to incorporate payment into various connected devices and systems. Payments are only the beginning. Visa is opening up APIs into its localization, foreign exchange, and tokenization systems, offering a variety of options to create services.

Visa’s exposing its services as APIs exemplifies our vision of a composable enterprise – a company that is creating opportunities for innovation and additional revenue streams by making its services available to anyone who might like to use them in new and interesting ways. Not only have they recognized the transformative changes happening within the financial industry, they are actually responding to those changes in a dynamic and agile way.

On Saturday, March 12, 2016 Visa will be holding its 2nd Developer Challenge at SXSW in Austin, TX, where startups will pitch solutions leveraging Visa’s APIs. It’ll be interesting to see where Visa’s developer program takes them and the experiences that will emerge.   For more about Visa’s approach to APIs, take a look at this video on “What is an API” that we created together.

Using Anypoint Data Gateway for Lightning Connect, all within Anypoint Platform

Reading Time: 5 minutes
Anypoint Data Gateway Download

Anypoint Data Gateway for Lightning Connect is a packaged cloud service that allows you to quickly and easily integrate data stored in legacy back-office systems with Salesforce. Using a simple point-and-click visual interface, you can access data from SAP, Oracle DB, Microsoft SQL, MySQL and others instantaneously from Salesforce. This ability to quickly connect diverse back-office systems eliminates the need to create separate design environments or to implement extensive training for Salesforce users, making it a perfect tool for application owners and business users.

What is new?

Screen Shot 2016-03-04 at 3.08.51 PM

Data Gateway is now an Anypoint Platform application, accessible through the main Anypoint Platform management center, and available for use within your environments and business groups. For Anypoint Platform users, you now have full visibility into the deployment and management of all your applications all within one console. For those who prefer to access it from Salesforce, the product is still available there as well. For more information about Data Gateway and using it within Salesforce, please visit my previous blog post.

Creating a new Data Gateway in Anypoint Platform

Once you’ve logged into Anypoint Platform, you’ll see Data Gateway listed on the top navigation bar. Clicking on it will take you to the Data Gateway landing page, allowing you to manage your data gateways, your connections and VPC settings.

Creating a new Data Gateway requires three simple steps (which are the same as what you would do within Salesforce):

Creating a DataGateway

  1. Connection creation: Select any of the available datasources and enter the connection settings. This datasource can be either publicly accessible or behind a firewall. For the latter, a VPC or Cloud Extender agent are required to access the resource.
  2. Data Gateway creation: Enter the name, description and security credentials for the OData API that will be created. You can also set a throttling policy for this API.
  3. Object selection: Once the Data Gateway is created, select the entities (or “objects”) to be exposed and their fields. For databases, this matches the concept of tables and columns.

Once these steps are complete, the OData API is exposed through a single HTTP endpoint, accessible from within the Salesforce menu item on the left.

Publishing objects to Salesforce

Clicking on “Salesforce” on the top left menu allows you to log into Salesforce with your own set of credentials. Once logged in, select the Data Gateways to be published and voila, those objects are now available in your Salesforce organization as external objects.

Screen Shot 2016-03-04 at 3.31.09 PM

Furthermore, if you need help understanding what OData is and how to use it, take a look here, or register for our upcoming webinar, When Out-of-the-Box Isn’t Enough: Extend Anypoint Data Gateway for Your Needs, live March 17 @ 10:00am PT.

Anypoint Data Gateway Download

Why healthcare systems are failing doctors and patients: they’re in the dark

Reading Time: 4 minutes

Imagine you’re a skier with a history of injuries. You fall one winter but the only consequence is a sore head and a warning to avoid concussion; the next winter you fall and lose consciousness, and your doctors have no idea about your medical history nor the doctor’s report from just a year ago. Plus, the medical equipment they’re using isn’t connected to any system, so they have to keep entering your information in their computers, increasing the chance of human error. Healthcare professionals being in the dark about your medical history could jeopardize your life.

This is the scenario Ross Mason presents when making the case for digitized, centralized, connected health records. “[Healthcare] IT systems, claimed to be patient-centric, are trapped within the four walls of a hospital, incapable of connecting critical information locally and externally, Ross writes. “This prevents care providers from sharing clinical data, such as patient records, across systems within the hospital and with external healthcare IT systems across the nation and globe. Healthcare IT is failing doctors, medical staff and patients.”

There are a number of reasons that hospitals haven’t made a wholesale move to digitized, connected healthcare records yet. The first one, Ross points out, is cost: “Many hospitals shy away from digital transformation because it’s feared to be a massive investment. For instance, a common electronic medical record (EMR) system, EPIC, can have implementation costs upwards of $500 million. However, using incremental approaches and partnering with leading companies that have an expertise where hospitals don’t, hospitals can keep digital transformation costs within budget.”

Secondly, Ross acknowledges that information security is a worry, but points out that “The big irony here is by not making data available to other medical providers, it puts a patient in much greater risk of being misdiagnosed or given the wrong medication.”

The starting point to make changes in connected healthcare systems is through APIs. We’ve seen that APIs are the “invisible warriors of healthcare;” and they can help make the digital transformation of the healthcare system a less onerous task.

“Given medical errors are the third leading cause of death behind heart disease and cancer, it’s imperative these systems connect and talk,” writes Ross. Take a look at more of his thoughts about why healthcare records need to be connected, and check out more resources about how digital transformation is providing positive patient outcomes.

MuleSoft customer success: “This isn’t just about software – we’re here to help you solve your problems”

Reading Time: 10 minutes

One of the awesome things about working for MuleSoft is seeing all the innovations our customers produce using Anypoint Platform. And one of the people responsible for helping customers make that happen is Customer Success Director Cat Huegler.

Cat has been working with MuleSoft for two years, and her job is to help global Fortune 500 companies deploy and manage MuleSoft’s products to do extraordinary things. I sat down with Cat recently to talk about the role of customer success at MuleSoft and some of the outcomes that Anypoint Platform is creating.

It seems like customer success is a crucial part of the MuleSoft experience.

Absolutely, we’re attached to real outcomes. We are about the real business use cases and tangible results. When you get started with Anypoint Platform, you’ll find that you haven’t just bought some software – you’ve got a team of people who are going to help you transform your business.

In a really big company, there are always lots of stakeholders for technology projects. How do you get the right people’s buy-in?

You do internal evangelism. You have to navigate each customer’s unique situation. You have to change not only the way companies view integration, but how they manage their business processes.

Here’s an example. A global retailer recently bought our full solution set, so we not only have services working on a specific task – API Manager – we went in with our Center for Enablement team and interviewed lines of business and IT owners and see where there are gaps and opportunities.

What we discovered was that the IT group that engaged us never talked to the business owners; they were sitting there designing all this stuff, thinking if they design it the business owners will come and want to use what was built.

We went back to the IT group and said you have to introduce us to the rest of the business for us to be successful. There was pushback, but they agreed.

We’re not just a technology solution, we are about business transformation. We get to go back to the entire business and because the doors are open, we’ll be able to achieve what everyone wants.

So we push for getting the business to articulate the value of what our software can do. We can help the whole business realize value, and we want to make sure the business cares about it. We’re helping connect the dots for them.

How do you overcome the silos that seem to spring up?

We often find champions to introduce us. The key is to find the executive that cares about both the business results and technical execution.

Successful executives can see the big picture. They  can understand the technical difficulties of their asks but also how they map to the business objectives.

Someone who would not be a great champion for us would only see the technical point of view. We aren’t that crazy about engaging with people who are focused on quick wins and don’t care about technical debt.

There are so many great opportunities to use Anypoint Platform for truly transformative business initiatives; we’re excited to work with companies who want to reinvent themselves and experiences for their customers.

What are some examples?

A restaurant group really wants to be a place where people go to hang out; they want to appeal to people who want to study or work or just spend time there as their third place between home and the office. So one of the cool things they’re figuring out how to do is geonotifications on your phone so you can request what song will be played next.  

One of the things we help companies with is running mobile apps that provide all sorts of interesting experiences for their customers.  A retailer uses Mule to run their mobile app for customer engagement, a non-profit uses Mule to run a mobile app that helps their customers try to break unhealthy habits, a mobile company uses Mule to run their content streaming app…the list goes on and on.  One interesting use case is a healthcare provider uses Mule to run their on-call notification process, using APIs rather than pagers.

It’s exciting to be able to help our customers really engage with their customers. Our customers use our software to make their customer interactions better, faster, more innovative and more fun – and that helps their brand loyalty.

What are some of the most interesting things you’ve heard from MuleSoft’s customers?

A customer once told me, “not only are you guys a company with a strong product that we know will help transform our business, but also every single person is a good human I like to work with.” You don’t often hear that about technology companies. It’s nice that our customers notice that.

We have so many potential customers and employees looking into us who ask about our company culture. They know about the product, but what they really want to know is what it’s like working here? How’s the executive team? You guys always seem full steam ahead and super happy, what’s the secret sauce? The customers want to feel like they’re in on something special.  And they want to know how we get the MuleSoft t-shirt so soft!

Developers always want to use the next coolest thing. They look to MuleSoft to solve their problems. We have to keep showing them how MuleSoft remains cutting edge. So far, nothing has replaced us at the cutting edge!

Thank you, Cat! Take a look at more exciting things our customers are doing with Anypoint Platform.  

Stop making spaghetti code

Reading Time: 4 minutes

Spaghetti is delicious when it’s on your dinner plate, but it can give you indigestion when it’s an enterprise integration pattern. When developers and IT teams are tasked with building integrations, creating too many point-to-point integrations can create an ugly mess that’s brittle, expensive to maintain, and difficult to modify or adapt. This has negative effects on enterprise agility and efficiency.

MuleSoft_SOTW_new_2-02 (1)

James Donelan, our VP of engineering, has an article in Techbeacon this week in which he outlines the risks of messy point-to-point enterprise integrations. He says, “what starts out as a simple integration quickly expands into a series of hacks and one-offs, accompanied by growing endpoints and increasingly more complex data transformation and integration logic. The problem, then, becomes the massive investment in developers, time, and money that’s needed to maintain these custom code solutions.”

He gives the example of a system developed for the U.S. Air Force that was estimated to cost $88.5 million to develop. Dubbed the Expeditionary Combat Support System (ECSS), the project racked up $1.03 billion in costs in seven short years and did not yield “significant military capability,” according to an Air Force spokesperson. The ECSS was supposed to integrate and replace more than 200 legacy systems but was eventually disbanded after the team realized they were creating an overwhelming amount of additional custom coding and integration work.

A better option, says James, is a connectivity layer that allows the business to simply plug in legacy and new applications to the integrated systems as required, and removes developers’ time and resources from maintaining complex enterprise integrations to creating new products and services for the business. The API-led approach to connectivity leads to faster delivery of new services and greater business agility.

“At the end of the day,” James says, “businesses shouldn’t waste valuable developer hours on grunt work that’s difficult to maintain and often someone else’s mess to untangle. The real crème de la crème for developers lies in building innovative products and services that bring overall value to a business and occasionally transform an industry.”

Take a look at Anypoint Platform, our enterprise integration solution, and find out how it could get your development team producing new products and services more quickly than ever before.

Why open a brick and mortar store? It’s all about the data.

Reading Time: 3 minutes

Last month, Amazon announced it would open its second bricks-and-mortar bookstore in San Diego. Its first physical bookstore opened last year in Seattle, setting off a flurry about what that meant for the online retail giant and the future of retail itself.

According to UK tech news site IDGConnect, the physical store is part of ” a general shift towards data driven omni-channel customer experiences…the extensive customer data now available via online channels means companies can now provide a range of targeted customer experiences to suit every purpose. Advanced analytics also means that companies can better stock stores based on up-to-date sales information.”

Ross Mason is quoted in the article; he points out that “an API approach is emerging where retailers can connect their front end systems with their back end systems…this creates a seamless experience for their shops, no matter if they are online shoppers, in-store-customers or both.”

Amazon’s physical shops provide not only a retail channel that customers want, but the free exchange of data in omnichannel retail also provides ever more personalized product recommendations, reviews, and services based on browsing and purchasing patterns. One of our customers, a Top 4 UK food retailer, used CloudHub to integrate data across their online and brick-and-mortar stores to get a single view of their customer as well as create more effective and more personalized marketing.

Forrester released a study in January of this year which forecast that the store of the future will be powered by real-time analytics technologies that understand shopper behavior across the entire shopping journey. Acquiring and using data will be the key to success in retail in the 21st century, and that’s made easier through an API-led approach to data integration.

Take a look at more information about how API-led connectivity could help your retail business.

Announcing solutions that will transform healthcare

Reading Time: 4 minutes

We are excited to announce healthcare initiatives that will have a profound effect on the way patients and medical professionals interact. The first of the vertical initiatives is being launched at HIMSS this year with MuleSoft’s new Solution for Epic EMR Integration and its inaugural Healthcare Product Advisory Board.

MuleSoft’s Solution for Epic EMR Integration allows healthcare organizations to accelerate development of applications that are external to Epic, such as patient CRM, web and mobile patient portals and document management systems, with a set of pre-built integration templates. The templates save manual development work and leverage integration best practices. Key features include:

  • Pre-built integration flows that read/write data from Epic, transform that data into HL7 FHIR and then expose that data via a well-defined RESTful API

  • End-to-end reference implementation of the FHIR standard, including the following FHIR objects: Patient Demographics, Condition, Observation, Allergy, Medication and Scheduling

  • Support for both Epic Bridges (HL7 v2) and Epic Interconnect (SOAP) interfaces

“Data integration and interoperability across healthcare IT and external systems have become exponentially more complex,” said Ross Mason, founder and vice president of product strategy, MuleSoft. “We’ve built a full end-to-end reference implementation of the FHIR standard to allow our customers to seamlessly bring data from the EMR to mobile and web applications and back, while enabling secure and governed data access. MuleSoft’s API-led approach is designed to enable the secure reuse of health data across the organization to accelerate development and reduce operational cost.”

In addition, MuleSoft will be launching a new healthcare product advisory board comprised of its core healthcare and life sciences customers intended to drive digital innovation and provide a forum for knowledge exchange and product feedback. Its founding members include leading healthcare providers like UCSF and Johns Hopkins Medicine.

MuleSoft will be at HIMSS16 from February 29 to March 4, 2016. Attend the “The Connected Hospital: Unlocking your EHR” session featuring MuleSoft on Wednesday, March 2 at 11:30 a.m. PST at the Salesforce lounge in the SLS Hotel. Attendees will learn how healthcare customers are lowering costs and improving patient care by taking an API-led approach to connectivity.

Take a look at more resources on how API-led connectivity is transforming healthcare.