New SOA Gadgetry from WSO2
New SOA Gadgetry from WSO2
Join the DZone community and get the full member experience.Join For Free
Learn how API management supports better integration in Achieving Enterprise Agility with Microservices and API Management, brought to you in partnership with 3scale
WSO2 Gadget Server
For the Gadget Server, WSO2 used Apache Shindig, which is like a reference implementation for Google's Gadget spec. Shindig is tied together with WSO2's core enterprise middleware framework, registry, and repository, giving users the ability to personalize the Gadget Server. Users can pull a Gadget from its URL or from the Gadget Server repository. A Gadgets can also come from a server in a different department. "Suppose someone in the core IT team created a new gadget that shows you whether the servers you rely on are up or not," said Fremantle. Instead of having to go through a portal server department, he says, they can just create a URL for the Gadget and other departments can paste it into their dashboards. Administrators then have the ability to filter which Gadgets the employees put into their dashboards through the Enterprise Gadget Repository. For identity management, the Gadget Server can plug into an existing internal LDAP directory or use InfoCard or OpenID.
WSO2 Business Activity Monitor
Gadgets are used in WSO2's other new tool, the Business Activity Monitor (BAM), to provide SOA visualization and analytics. Here is the BAM dashboard:
Fremantle says the funnel shows how many requests are going into placing orders, order approval, billing, and finally payment at the bottom. The circular graph is a pie chart showing the percentage of different service requests. You can click on the pieces of the pie chart and get details about response time, response count, fault count, and request count (see below). Since the BAM is made of gadgets, an enterprise can also build gadgets based on the BAM's analytics. Like a mini-SOA, Fremantle says, the gadgets talk to the data through a data service. These graphs, Fremantle says, can help people spot problems instantly.
The BAM can go to existing servers and pull data out, or it can receive events that the ESB or app server publish into it. If a customer has a WebSphere, Oracle, or TIBCO system, Fremantle says there's a standard service interface that can be used by the BAM to receive data from those systems as well. "It's fully heterogeneous in the sense that there's open interfaces and it all uses SOAP and web services so that we can take any part of a customer's SOA and feed data into it," said Fremantle.
Even though more customers are turning to WSO2 for a complete SOA platform, Fremantle says they are still focused on providing interoperability with a wide range of third party solutions. "50% of our business is on a single-product basis," said Fremantle. He says that's still pretty good for a relatively new company.
Opinions expressed by DZone contributors are their own.