Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Eric Schabell, JBoss Technology Evangelist for Red Hat and guest lecturer.
With the release of the JBoss BPM Suite we have something fun to preview some of the components found in the product itself. Together with the project team, Maciej and Tihomir that work on this fantastic component, we have set up a repeatable standalone demo installation of the BPMN2 process designer.
This a new future coming in wso2 IS 4.7.0 where we can define application specific permissions. The included tutorial should walk you through the creation process and later implementation.
The demo is really cool and shows how to go from scratch (nothing) to a fully deployed project on Fuse with fault-tolerant/highly-available messaging, scalability, flexibility, and logging/debugging/tracing. It’s really pretty fantastic technology and I highly recommend you take a look at the video.
Apache Kafka has been used for some time now by organizations to consume not only all of the data within its infrastructure from an application perspective but also the server statistics of the running applications and infrastructure. Apache Kafka is great for this.
The new JBoss BRMS & JBoss BPM Suite was released yesterday bringing a lot of new improvements, fixes, and features. One of the most exciting is the availability of a public facing maven repository based on these two products.
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.
Java EE 7 (JSR 342) is in itself an ‘umbrella’ specification which encompasses 33 individual specifications. I will provide a brief peek into few of these specifications with a special focus on the ‘new’ specifications and the ones which have undergone ‘significant’ overhaul and changes.
The first step to managing your APIs is to catalog them. I've written before about the importance of the API Catalog, both for consumers (in an API Developer Portal) and also for administrators to keep track of the APIs which they are managing.
Software as a Service Customer Relationship Management (Saas CRM) is a software usage model where a vendor licenses a certain software system to be utilized as a service on demand through time subscription or pay as you go.
It is always recommended to use Spring properties with Mule, to externalize any configuration parameters. For example, the Acme APIfrom my previous post connects to an external database. So instead of hard-coding connectivity options inside my application code, I would create a properties file.
The number of APIs is clearly growing rapidly – but it is increasingly difficult for directories to keep up, and many of these APIs are private or semi-private. Some clear use-cases for APIs have emerged and many companies are combining them to suit their business.
Circuit Breaker is a pattern that wraps the resource and monitors for errors. Initially it is in closed state and passes all calls to the wrapped resource. When the failures reaches a certain threshold, the circuit moves to open state where it returns error to the caller without actually calling the wrapped resource.
Here is WildFly application server System V Initial Script that I quickly put together for a Centos 6 virtual machine. Use it at your own risk, don’t call me if something goes wrong, because I assume that you are an experienced Web Ops or Sys Admin and you definitely know what you are doing.
This article includes a lengthy mapping on how the SharePoint 2010 server-side customization can be mapped to SP 2013 App Model. The full list is included in the article.
A common integration scenario is a single message needs to be sent through multiple routes.
It needs to be routed through the CRM to create the client, to marketing for leads, and finally passed to provisioning and stock systems so they can work their magic as well.
We've just released the v2.2.0 of the UltraESB. The release fixes some defects related to classloading from deployment units, and also introduces a few changes to the public API to make the ESB API more user friendly and intuitive.
The Spring framework 3 provides an annotation @ExceptionHandler that can be used to intercept uncaught/unhandled exceptions in request mapped functions in controllers. This approach is ideal as it helps us reuse and centralize exception/error handling in Spring MVC/REST controllers.
APItools provides a proxy layer that enables tracking, control and analysis of traffic going to and from the APIs used by your Apps. The system means you can transform inbound and outbound calls to an API without having to rewrite your app.
For a long time I thought that was impossible to query the SOA composite instance audit trail directly from database. Several references on internet said that only SOA Management APIs could understand the format in which this information is stored into SOA Dehydration Store.
Make sure you didn't miss anything with this list of the Best of the Week in the Enterprise Integration Zone (Apr. 4 to Apr. 10). Here they are, in order
of popularity:1. Services, Microservices, Nanoservices... oh my!
So microservices as they appear...
With Mule’s December release we introduced the new batch module. We received feedback about it and we even have some CloudHub users happily using it in production! However, we know that the journey of Batch has just begun and for the Early Access release of Mule 3.5 we added a bunch of improvements.
This article will outline the the basic control flow patterns as defined by vdAtHKB03. We will then analyze what patterns have limited support due to restrictions imposed by the BPMN2 process specification as detailed in BPM-06-22.
While developing flows with a recent Mule ESB there is a big chance you will make use of MEL in your configuration. Although this feature has added great benefits while developing Mule flows it sometimes drives me crazy.
This article covers a WSDL for a web service in which the target namespace and the service address were identical, and put a Mule web service proxy in front of the web service exposing the WSDL, not only the port address of the web service endpoint were rewritten, but also the target namespace.