At first it might seem baffling as to why you are unable to make a remote JMX connection to a Linux server but the resolution is really quite simple.
To understand how replication is implemented in Kafka, we need to first introduce some basic concepts. In Kafka, a message stream is defined by a topic, divided into one or more partitions. Replication happens at the partition level and each partition has one or more replicas.
A web service is proxied with Mule ESB and password protection is added to it by applying Spring Security. The code is quite straightforward. I'm going to use SoapUI to test this setup...
I've spent a good amount of time setting up message-based infrastructures, so I decided to make a tool that would allow me to set up localhost friendly, network available message queues much quicker so I could try out all the things I wanted.
The Axway Vordel API Server allows you to read in REST API parameters from an incoming request, and then use these parameters for a variety of purposes, for example to pass them into a SOAP message, or use them to call a method of a Java class via the Scripting Filter.
To use Twitter API we need to handle http requests. I’ve written several post about http request with PHP (example1, example2), but today we will use one amazing library to build clients: Guzzle. Guzzle is amazing. We can easily build a Twitter client with it.
When creating webservices a lot of people have objections against using JAXB for binding XML to objects. This may be because of performance reasons, allergy to generated code or simply a philosophical belief that you should not mix document centric services with an object oriented model.
This post is a follow on from my previous post OAuth with NancyFX and WorldDomination.Web.Authentication except this demonstrates how you can use WorldDomination.Web.Authentication with ASP.NET MVC, writing only minimal code in the process.
When I think about API Analytics, I like to think about the "Goldilocks Question". This question is "Who's been using my APIs?". One of the tests of an API Analytics solution is how easy it makes it to answer this question.
When using an external API for WebHooks or Callbacks as discussed in Chapters 3 and 5 of Getting Started with Mule Cloud Connect . . .
As I've shown it in my previous post JBoss Drools are a very useful rules engine. The only problem is that creating the rules in the Rule language might be pretty complicated for a non-technical person. That's why one can provide an easy way for creating business rules - decision tables created in a spreadsheet!
I just want to emphasize that the goal of this new camel-servletlistener component is to allow people to easily bootstrap their Camel applications in any web container, without the need to be tied to any particular 3rd party framework such as Spring.
As a provider of a service, one is obliged to maintain different versions of a service. One of the possible reasons could be the existing consumers of the service doesn’t want to upgrade to newer version.
API evolution is something absolutely non-trivial. Something that only few have to deal with. Most of us work on internal, proprietary APIs every day.
I needed to handle an http post that would carry not one but N > 1 uploaded files. And then came Mule into my life, and this task became as simple as navigating the properties of a MuleMessage interface. Let’s explain a little bit….
There are many ways to expose an HTTP endpoint in Camel: jetty, tomcat, servlet, cxfrs and restlet. Two of these components - cxfrs and restlet also support REST semantics just with few lines of code. This simple example demonstrates how to do CRUD operations with camel-restlet and camel-jdbc.
Don’t be lazy and try to make too generic repositories. It gives you no upsides compared to using the OR/M directly. If you want to use the repository pattern, make sure that you do it properly.
SOA is hard. Learn how Square is approaching this problem today with JRuby and where we hope to be in the future. We'll go from git init to cap deploy, covering Square's approach to testing and service isolation, dependency management, API documentation, code quality metrics, and more.
As promised I’m going to show a test case for which I have used Citrus to implement it. n a predefined folder on a machine a character-separated file is placed. This file is picked up by our Mule ESB application...
Recently, I ran into an open-source test framework called Citrus. Citrus supports you in testing message interfaces in enterprise applications. Manual testing effort as well as coding mocks and simulators are not necessary.
See how to log onto the server log file, log a message and log a specific property on the WSO2 ESB.
I'd really like to redo this with a micro-framework for routing and the PHP client libraries to handle emitting TwiML - but exactly what is going on might be less clear.
You want to get more done in 2013 so you’re going to need to switch from synchronous to asynchronous processing to do more with the same resources.
SAML 2.0 Bearer Assertion Profile which is built on top of OAuth 2.0 Assertion Profile defines the use of a SAML 2.0 Bearer Assertion as a means for requesting an OAuth 2.0 access token as well as for use as a means of client authentication.
Just some simple XML and you'll be creating custom dispatchers for WSO2 ESB. This example will create a Maven project