// The solutions architecture (WSO2 API-M v1.8.0 with WSO2 BAM v2.5.0)
// The deployment architecture (WSO2 API-M v1.8.0 with WSO2 BAM v2.5.0)
There seems to be a false alarm spreading over the online forums that WSO2 ESB cannot handle messages larger than 16K and results a corrupted response. This situation occurs only when a user enables one of the synapse properties which is disabled by default.
Streaming XPATH option is the aforesaid culprit, which is a newly introduced feature to optimize the performance in different message filtering / routing scenarios. However this does not effect the default workings of WSO2 ESB which does handle large messages successfully in thousands of enterprise deployments with the default XPATH implementation that ships out of the box.
As any new component achieve perfection with time, WSO2 ESB team have fixed all reported issues against streaming XPATH component (in ESB v4.8.0) and thrives to be the fastest ESB and the integration platform.
Following case study provide mode details on large message handling of WSO2 ESB in production.
UPDATE (02/17/2014) : WSO2 has released the latest performance stats, which details on the stream XPATH stabilization as well.
I’ve been doing release management and product engineering for almost three years in WSO2. By no means am an expert. Am still learning and trying to tame the beast. However I do have my fare share of experience and knowledge which I have gathered by screwing it all up and also sometimes, doing it right as well 🙂
Recently we have done a successful 1.0.0 release of WSO2 User Engagement Server and I felt writing this post as the release retrospect.
Team is the most important part of any product innovation. Without a strong, competent and hard working team you cannot achieve much (period !!). You feel it when it comes to agile release management. You cannot spoon feed your team. Each member will own a part towards success. You have to believe the quote “A Team Is Only As Strong As Its Weakest Link”, so your weakest got to be quite smart.
Milestones are short, quality of deliverables are high. The build *has* to pass always keeping the master stable. That’s a lot of work. A lot of smart work. So the team does matter and that’s the number one.
Well, WSO2 has the best from the Best and luckily UES had the dream team 🙂
Number two is the Vision. Its not about the person whose leading the effort need to know the product vision. The team got to have a shared understanding about the vision of the product that they develop. Everybody has to be on the same page. If a button was moved from left to right everybody must know the reason behind that decision.
Non should develop a component without knowing the bigger picture of where that component fits in. (s)He should know the future of that component, what are the improvements can be done, how can it aid to market the product and how does it contribute to achieve the product’s vision.
Reviews play a major role. They sync up the team. First you review the design, then review the architecture, the UI/UX and then the code. You get this right, you get a complete product feature.
During UES release, we did a lot of these. Our design review meetings were war zones. We talked about architecture and clean design patterns. Applied them appropriately and iteratively reviewed them. Our UI mockups were all over the whiteboard, we iterated until we achieve perfection. We reviewed our code, identified the improvements.
We started re-engineering WSO2 Gadget Server during 2012 Winter. We were brainstorming of how we can change it to be more flexible and accommodate wider enterprise data/information presentation use-cases. We wanted to give more power to the developer, not just the ability to drag and drop widgets and select a layout. We wanted these pages to be discovered around the organization. With such ideas in mind we created multiple mind maps to get a clear idea
We had plenty of email debates, F2F meetings of what we need to do ? Are we there yet ? Is this what developers/business users need ? etc. Continue reading WSO2 User Engagement Server: How it kicked off from the whiteboard
“A picture worth a thousand words” is a known fact which doesn’t need proof. At present we discuss about the value and the power of data. We use various tools to analyze them, we do business intelligence capturing trends or anomalies. However in the end you need to express the meaning in a sensible manner for the key decision makers. Would you go write thousand words or rather draw something, summarize the findings and let the stakeholder explore for more.
WSO2 Middleware stack has all the pieces you need to harvest, store & analyze (both real-time and periodical) vast amount of data sets, but when it comes to summarizing and presenting, the stack had somewhat a week tool set. We envisioned the idea of “SOA Last Mile” since latter part of 2009 with products such as WSO2 Gadget Server, WSO2 Mashup Server and frameworks such as viskit. We experimented, wrote code and delivered enterprise grade products to achieve this vision. For instance WSO2 Gadget Server was one of the most downloaded products during 2010 – 2011 time span, and even now people are using it for various data presentation purposes.
Is something I’ve been working on at wso2 for sometime, if you are following me I have tweeted the updates, releases etc. Jaggery went live with its fifth milestone, few weeks ago at jaggeryjs.org, its still young and has alot to improve.
A very simple page that prints out some request properties in jaggery looks like,
<html> <body> <p> <% print("Method : " + request.getMethod() + "<br/>"); print("Protocol : " + request.getProtocol() + "<br/>"); print("User-Agent : " + request.getHeader("User-Agent")); %> </p> </body> </html>
Jaggery docs site also provide a tool for you to try out some code and play around. So you can simply copy the above code and paste in jaggery try-it
I recently did a webinar on jaggery that explains the simple case, over looking its API and samples. Below is the recording hope it’ll help.
The post is about creating a dashboard to display event notifications using few of WSO2 Technologies.
Requirement : Capture events from an event sender and display it in a dashboard
Architecture : In brief, events are generated randomly, ESB will act as an event sink, and it will publish the events to the subscribed parties (to a service deployed in WSO2 AS). There is a gadget deployed in WSO2 Gadget Server where it will poll the received events from the service periodically.
At the ESB end we will have to set up the event sink as following,
Then you need to create a topic in the ESB and subscribe the created service. Steps in doing so is documented here
A very simple service to accumulate the events (this is not at all production grade, who whats to keep all the event in memory 😉 )
Its too long to post, you can check it at https://gist.github.com/1653062
You can run the client like “ant trafficevent -Dtrpurl=http://localhost:8280 -Devent=traffic.is.crazy”
Well, maybe I am too late to write this post; but hopefully I will be able to discard a misconception in some of you. As you all know by now WSO2Con starts tomorrow and goes on till Friday (16/09). Its a great tech feast, and there weren’t many such in recent history in Sri Lanka. Maybe am not the best person to write all the good stuff about it and asking you to take my word. But if I forget the fact that I am a member of wso2 team, and look at it as a Sri Lankan techie, the agenda still sounds pretty awesome.
Yesterday I meat a friend of mine (lets say Bob 🙂 ) at a dinner, and Bob was saying, “you guys are doing a software conference right; I saw in media, sounds great !!”. I was head over heels (didnt wona say I am doing a talk; wanted to be bit modest 😉 ) I asked excitedly, “So are you coming ?”. But his reply surprised me. He said “Well I dont think its for us you know. Its too hard core; you guys are doing open source, SOA and cloud stuff. I don’t think we are there yet”. If I add little bit of context, Bob is the senior IT manager in a well reputed insurance company in Sri Lanka. So as I felt he had all the reasons to attend to WSO2Con.
I see several misconceptions in his comment, maybe people in Sri Lankan IT services (not directly software, but software is a supporting system like for IT systems for banks) industry are bit behind the game. For one, some people say SOA and Web Services are dead 🙂 it’s no news neither a buzz, Yes cloud stuff is kinda new, but you have it every where now, I guess its high time to check that out too. But whats so hard core about Open Source ??? !@#$.
So yeah WSO2Con is NOT just for “Hard Core” Techies. It certainly feels awesome that people think like that, but the truth is its a week of discussions on software systems. Maybe little bit more about distributed and service oriented systems, But isn’t everything distributed and service oriented these days ? :).
If you checkout the agenda its mostly about enterprise systems, issues in enterprise systems, how to solve them, how open source software can help and most of all, its a week of discussions on experience. Why experience in bold; well if you read the abstracts of many talks, its all about how people solved their enterprise integration problems. It a talk show of first hand experiences. There are, IT consultants, Architects and Visionaries coming from around the world to share there knowledge and experience. What else can you ask for ?
So I guess, if you are a manger who has even a slight influence in IT matters, this is something you goto check out; maybe you do have the same problems as some of these speakers had some time back. It would be a great opportunity to talk to them in person and get some insight.
Well hope I did make some change of your attitude; and I do hope to see you :).
FYI you can still register at wso2con.com