Using MuleSoft’s AnyPoint Enterprise Security, we are able to easily utilize encryption and decryption modules using industry standard approaches such as PGP to ensure that messages are protected as it gets transmitted across systems.
Just as for any other critical connectivity or integration brick, you will want to control and monitor your API to ensure QoS and SLAs. And as for any new business line you would launch, you will want to and need to define, implement and operate a business model.
We are releasing the next set of Technical Breakout sessions on GlassFishVideos YouTube channel as well. In this series, we are releasing JSF 2.2, Interceptors 1.2, and JPA 2.1.
This article shows how to use jOOQ for the Liferay data model. Minuteproject generates jOOQ artifacts for Liferay.
Ready to get started with Apache Axis2? Check out these simple instructions so you can get set up on a Windows machine.
Here's a quick tip: If you download the Axway API Server and want to take a look at the OAuth samples, you can enable them simply by clicking on "Enable Interface" in Policy Studio, as shown below, then hitting "Deploy" (on the toolbar, in the top right).
The ubiquity of the "iceberg slide" shows that the API industry is agreed there are more Enterprise APIs than Open APIs. But, how *how much more*? To answer that question, we recently ran a survey...
As with everyone else in the industry, it’s natural that we’re often absorbed in the day to day if drilling down to individual technical challenges or choices. Sometimes however, it’s interesting to take a step back and when we do we’re continually surprised at how broad and deep the impact of APIs is likely to be.
In case you missed the previous post my reasons for choosing Blizzard’s World of WarCraft APIs was to create an understandable sample app to display Realm Status (these are the game servers for World of Warcraft).
Dataloader.io, MuleSoft’s data loading app for Salesforce, has now topped 1 billion records processed in under 9 months. There's also an interesting infographic below that was just released.
It is natural to get comfortable, perhaps too comfortable, with the state of your codebase. After all, it works and is probably meeting tangible business needs.
The first part of this is to create a configuration class for the web app.
These gems (not the Ruby kind) don’t get a lot of fanfare, nor do they often warrant much attention on their own, but put together, they make for a smoother, intuitive user experience. Nearly invisible, they have become nearly indispensable to me.
A SaaS API must (by definition) serve multiple consumers – tenant organizations that desire programmatic access to SaaS provider business capabilities. Building a SaaS API goes beyond simply adding a tenant key to your API message parser.
We will draw a Radar Chart .The Student input data is JSON in nature.The Servlet returns the JSON data when called by Jquery Ajax method.The Student Java class object is converted to JSON representation using GSON Library.
I have a number of Spring MVC based RESTful services that return JSON. In 90% of the cases, the state of objects these services return will not change within a 24 hour period. This makes them (the JSON objects) perfect candidates for simple caching enabled by memcached.
In March of this year, I traveled to Devoxx France and had a great time. One of the talks I delivered was Comparing JVM Web Frameworks, with a bit of a twist from prior versions.
You hear about them by the names of social, cloud, big data and mobility, but what those terms all represent at their core is a problem with the integration of it all.
Not being an expert in all these levels is fine. Be an expert in a couple. And be sure to know how the others below and above work in principle, so that you can become an expert when there’s a need for that.
I'm going to address the primary concerns that drive the need for security in a SOA, how the industry as a whole has addressed those concerns, the consequent emergence of popular technologies based on this Industrial best practice and finally, the implementation of these technologies in Mule.
Re-use is the main principle for us. We already have a tested and working infrastructure built for all the Truecaller customers. So we are using that in order to serve API requests as well.
The problem is that the wstx tokenizer/parser encountered unexpected (but not necessarily invalid per se) character.
REST is all about representations of resources. They might come in different formats, and they might appear at their own URI as well as in one or more collections, but essentially you just get a representation of a thing. This is great, apart from when it isn't.
I believe the organizers of Camel One will be publishing all of the presentations at some point, but if you’re interested in the slides from my talk ActiveMQ Internals, check them out below..
A very common question that we get on the Play mailing list is how do you write a REST API using Play Framework?