I recently had a customer wanting to build a simple UI to maintain additional filtering data associated to a defined “Contract” contained within API Manager. This code would have to run outside of the MuleSoft eco-system, as a service, within a JAVA Data Layer container environment.
My goal was to develop a very simple JAVA API Manager Client Access Example, whose concept prototype could be used as a basis to construct a necessary Mashup of API Manager Resources and Custom Client oriented resources. A primary emphasis is to understand the OAUTH2 Authentication exchange requirements.
That’s a wrap everyone! CONNECT 2014, the integration conference of the year, has come to an end! With speakers from companies like Salesforce, Tesla, Box, Cisco, and Stripe, in addition to our very own MuleSoft experts, there were plenty of great sessions for everyone.
Over 1,200 registrants between CONNECT and its sister event APIcon
Attendees from 36 countries
Over 300 unique companies represented
It wasn’t all about being serious and talking business though – we made sure to have some fun along the way!
We’re very excited to announce the May 2014 release of Anypoint Platform. This new release, which includes the GA release of Mule 3.5.0, provides a faster, easier way to deliver data to business applications, whether they are event-driven, real-time data or batch data. The Anypoint Platform May 2014 release also includes templates to solve the most common Salesforce integration challenges and new security certifications for CloudHub, speeding time to market for SaaS integration initiatives.
At just over a year in the making, this release simplifies our core connectivity, increases performance, enhances the DataSense experience, and adds in new capabilities requested from our community and customers:
It’s been a while since we’ve had a Meet a Muley post, but we thought we’d bring it back this week and introduce you to a very special Muley – Max! Read on to hear more from the integration hero – from his favorite band to what exactly it is that he does here at MuleSoft.
First thought that came to mind when you looked into the mirror today?
Recently, I discussed how to build mule integrations using Gradle. This is a follow up post to discuss how to work with this plugin and mule studio, and to discuss some relevant enterprise features. This post assumes you already know how to do the basic setup of the gradle plugin (discussed on my previous post), so if you have not done it before, please go ahead and read it before continuing.
Creating a Mule Studio Project
From your gradle project, you can easily change it to a Mule Studio type just by applying the ‘mulestudio’ plugin and selecting the appropriate mule version, here is an example:
Now you can simply run ‘gradle studio’ from the command line and it will create the necessary files so you can import the project into your workspace.
“I believe that if we think first about people and then try, try, and try again to prototype our designs, we stand a good chance of creating innovative solutions that people will value and enjoy.” – Bill Moggridge, Designing Interactions
Prototyping is a key practice of design; it allows designers to visualize, evaluate, and communicate.
To explore design ideas, the prototype must be quick and inexpensive. It must suggest and explore these ideas, rather than confirm them. That’s why some HCI researchers like Bill Buxton, prefer the term sketch over prototype.
Paper prototypes have a unique feature: the return of investment, in terms of learning, is extremely high. It takes hours or even minutes to be created, and in exchange you can receive valuable feedback.
If you prefer digital means, tools like Balsamiq or Pencil, imitate the sketchy nature of a paper prototype. The term low-fi prototypes is used to refer to this kind of prototypes, regardless of them being on paper or not.
Tip: to quickly clean up scanned sketches, use the adjust levels option, included in most of the photo editing applications.
Last month the massive Heartbleed security vulnerability was exposed. Three weeks later a security flaw in Microsoft Internet Explorer was revealed. It seems as though every few months there is news of a security breach or vulnerability. As more and more business is done online, in the cloud and through SaaS providers, how can you be sure the applications you and your business use are safe? Using the Heartbleed vulnerability as a case study, this article will examine what went wrong, as well as what you should expect from a SaaS provider, before, during and after a security event.
What is Heartbleed?
Heartbleed is the commonly recognized name of an exposure identified in a critical Internet security software package called OpenSSL, the most common transmission encryption software package used by Internet servers worldwide. This vulnerability allows an attacker to craft keepalive messages in such a way as to force a server disclose its short-term memory space. Since a server’s memory often contains personal, confidential information, such as user passwords or credit card numbers, the attacker could obtain that information. More severely, the server may also inadvertently disclose to the attacker its own private encryption key, which then allows the attacker to subsequently listen to all communications with that server, even without using the Heartbleed vulnerability. The nature of this attack is such that it leaves no traces, and is practically invisible to common detection mechanisms (although now that it has been exposed, signatures for it are becoming available for popular intrusion detection software).
The idea of this blog post is to give you a short introduction on how to do Real time sync with Mule ESB. We’ll use several of the newest features that Mule has to offer – like the improved Poll component with watermarking and the Batch Module. Finally we’ll use one of our Anypoint Templates as an example application to illustrate the concepts.
What is it?
Near Real time sync is the term we’ll use along this blog post to refer to the following scenario:
“When you want to keep data flowing constantly from one system to another”
As you might imagine the keyword in the scenario definition here is constantly. That means, periodically the application will move whatever entity/data you care about from the source system to its destination system. The periodicity really depends on what the application is synchronizing. If you are moving purchase orders for a large retailer you could allow the application a few minutes between each synchronization. Now, if we are dealing with Banking transaction you’ll probably like to change that to something in the order of a few seconds or even a hundred milliseconds, unless you really like to deal with very angry people.
The battle between software giants Oracle and Google hit close to home again last week, when a Federal Court of Appeals overturned a 2-year-old ruling by a lower court and established that APIs are entitled to copyright protection. The first reaction from most people is: how strange! After all, APIs are just the specification of how a software system or service behaves – call it this way, send it this information, get back that information – so how is that possibly something copyrightable? It’s not like a book, or a painting, or even software… And the second reaction, from many in the API world, is: no!!!
Overcoming challenges with integration is no easy feat. Data driven by SaaS, Cloud Computing and Mobility results in an abundance of customer information. The challenge no longer lies in obtaining buyer information, but in integrating all of the data endpoints.
Integration across disparate systems is crucial to better understand customers, observe behavior, analyze data and create the optimal customer experience. However, not all marketing tools are designed to communicate with others. A whopping 500 billion dollars a year is spent trying to solve this problem.
Crimson Marketing, experts in marketing technology, sat down with MuleSoft’s Mahau Ma, VP of Marketing to chat about this problem and how it manifests itself:
MuleSoft for example, uses over 100 SaaS applications, a website on Drupal, a blog on WordPress, interactions though Marketo and Salesforce, a content engine on Insightera, and customer forums, to name just a few demand generation tools.
Retail “Omni Channel” operations: A company might have SAP at the core, legacy EDI systems, modern API technologies, social marketing channels, mobile channels, an E-commerce engine, a payments engine and interactions in a brick and mortar store as individual components of their product marketing machine.
The Healthcare industry: Having a 360° view of the buyer can literally be a matter of life and death. Ma details a case where his top five Pharma clients had to maintain product marketing data from over 8,000 websites, social channels, mobile apps and physician channels to ensure not only a great buyer experience and optimized demand generation, but also to avoid potentially fatal errors.