The document summarizes new features and enhancements in WSO2 ESB 4.5.1. Key points include: - WSO2 ESB is a lightweight, high performance and standards compliant ESB with support for routing, orchestration, filtering, transformation and other capabilities. - New features in 4.5.1 include an EJB mediator, improved XSLT and JSON support, an MSMQ transport, and built-in multi-tenant support. - The product now uses the WSO2 Carbon platform 4 for its core functionality, providing enhancements like management and worker node separation and improved deployment synchronization.

1. Better Enterprise Integration with
the WSO2 ESB 4.5.1
Miyuru Wanninayaka
Senior Software Engineer
miyuru@wso2.com

2. WSO2 ESB is…
• A lightweight, high performance ESB
• Feature rich and standards compliant
– SOAP and WS-* standards
– REST support
– Domain specific protocol support (eg: FIX)
• User friendly and highly extensible
• 100% free and open source with commercial
support

3. Runtime Architecture
API

4. Key Features

5. Routing

6. Service Orchestration

7. Traffic Filtering

8. Transformation

9. Protocol Switching

10. Load Balancing

11. QoS : Security, Throttling, Caching

12. New on WSO2 ESB 4.5.0
• Based on WSO2 Carbon Platform 4
• EJB mediator
• Better XSLT and XPATH
• Better JSON support
• MSMQ transport
• SNMP monitoring
• Mediation libraries
• SAP adaptor
• Built in Multi-tenant support
• Worker – Manager separated deployment model

13. WSO2 Carbon Core version 4
• Enhanced Deployment Synchronizer
• Deployment performance improvements
• Management & worker node separation
• JDK 1.7 support
• P2 Repository: Features grouped by product

14. EJB Mediator
• Can call an external Enterprise JavaBean
hosted in a app server
• Stores the result in the message payload or in
a message context property.
• Currently supports EJB3 Stateless Session
Beans and stateful session beans.

15. EJB Mediator…
WSO2 ESB
Proxy Service/API
Application Server
EJB
Client EJB
Mediator
<ejb beanstalk="string" class="string" [sessionId="string"] [remove="true | false"]
[method="string"] [target="string | {xpath}"] [jndiName="string"] />
<args>
<arg (value="string | {xpath}")/>*
</args>
</ejb>

16. Better XSLT and XPATH
• Supports XSLT 2.0
• Improved XSLT performance
– Almost doubled in most cases
• Support XPath 2.0
– Not enabled by default

17. JSON Improvements
• JSON streaming support
• Supports multi-rooted JSON
• JavaScript mediator support for JSON
{“name”:”miyuru”}
<script language="js">
var symbol = mc.getPayloadJSON().name.toString();
……..
</script>
<script language="js">
mc.setPayloadJSON({“name”:”miyuru”});
……..
</script>

18. MSMQ Transport
(Microsoft Message Queuing)
•http://docs.wso2.org/wiki/display/ESB450/MSMQ+Transport
•http://docs.wso2.org/wiki/display/ESB450/Sample+270%3A+Transport+switching+fr
om+HTTP+to+MSMQ+and++MSMQ+to+HTTP
• Sends/receives messages to/from MSMQ
queue
• Connects to MSMQ using native interface
– Only works in Windows
<endpoint>
<address uri="msmq:DIRECT=OS:localhostprivate$msmqTest"/>
</endpoint>
<proxy name="msmqTest" transports="msmq" startOnLoad="true">
……

19. SNMP monitoring
• Alternative to JMX
• Exposes all JMX MBeans via SNMP
• Can be easily integrate with monitoring
systems in data centers
– Transport statistics
– Service statistics
– Endpoint statistics/status

20. Mediation libraries
• New extension point of WSO2 ESB
• Mediation Library is a mechanism to group
Templates, Class mediatiors and Jar libraries
and expose it as a self contained set of
function modules.
• Once deployed, mediation library can be
import and use in mediation flow
Mediation Library
Sequence Class
SDK
Templates Mediatos

21. Mediation Libraries..
• Working on creating libraries for many cloud
APIs
• Library can import to runtime using
<import …/> configuration element
• After that call-template mediator can be used
to invoke mediation library functions

22. Multi-tenant support
• Standalone products supports multi-tenant
• Seamless migration from on-premise to cloud
• No need for a fully fledged cloud setup to get
the benefits of MT

23. Management & Worker Node Separation

24. Management & Worker Node Separation
• Proper separation of concerns - management nodes
specialize in management of the setup while worker
nodes specialize in serving requests to deployment
artifacts
• Only management nodes are authorized to add new
artifacts into the system or make configuration
changes
• Worker nodes can only deploy artifacts & read
configuration
• Lower memory foot in the worker nodes because the
management console related OSGi bundles are not
loaded

25. Management & Worker Node Separation …
• Worker Nodes can be added to cluster on-the-fly
and WSO2 ELB will automatically discover and
route traffic to new nodes.
– Using cluster messages to discover nodes
– Automatically detects node failures
• Improved security - management nodes can be
behind the internal firewall & be exposed to
clients running within the organization only, while
worker nodes can be exposed to external clients.

26. Improved Deployment Synchronization

27. Improved Deployment Synchronization
• DepSync allows you to synchronize
deployment artifacts across nodes in a cluster
– Management node(s) commits artifacts to repo
– Worker nodes checkout artifacts from repo
– Using SVN as the repository
• Also includes meta data synchronization
• New nodes can add to cluster on-the-fly and
artifacts will pull from repository

28. P2 Repository: Features grouped by
product
Latest P2 repository : http://dist.wso2.org/p2/carbon/releases/4.0.2/