Fwd: [Carbon-dev] [ANN] WSO2 ESB 2.0 beta3 released!

2 views
Skip to first unread message

Senaka Fernando

unread,
Jan 13, 2009, 12:51:15 PM1/13/09
to sci-fl...@googlegroups.com
Folks, I have tried out SCI-Flex with the latest ESB beta. Works fine as it seems. However, please do try this out and let me know if I've made any wrong assumptions.

Thanks,
Senaka

---------- Forwarded message ----------
From: Ruwan Linton <ru...@wso2.com>
Date: Mon, Jan 12, 2009 at 9:18 PM
Subject: [Carbon-dev] [ANN] WSO2 ESB 2.0 beta3 released!
To: WSO2 ESB User Mailing list <esb-ja...@wso2.org>, esb <esb-ja...@wso2.org>, carbo...@wso2.org


The WSO2 ESB team is pleased to announce the release of version
2.0-beta3 of the Open Source Enterprise Service Bus (ESB).

WSO2 ESB is a lightweight and easy-to-use Open Source Enterprise Service
Bus (ESB) available under the Apache Software License v2.0. WSO2 ESB
allows administrators to simply and easily configure message routing,
intermediation, transformation, logging, task scheduling, etc.. The
runtime has been designed to be completely asynchronous, non-blocking
and streaming based on the Apache Synapse core.

WSO2 ESB 2.0-beta3 is developed on top of the revolutionary Carbon
platform (Middleware a la carte'), and is based on the OSGi framework to
achieve the better modularity for your SOA architecture. This also
contains a lots of new features and many other optional components to
customize the behavior of the server. Further, if you do not want any of
the built in features, you can uninstall those
features without any trouble. In other words, this ESB can be customized
and hardened to your SOA needs.

You can download this distribution from [1] and give it a try.

_How to Run_

  1. Extract the downloaded zip
  2. Go to the bin directory in the extracted folder
  3. Run the wso2server.sh or wso2server.bat as appropriate
  4. Point you browser to the URL https://localhost:9443/carbon
  5. Use "admin", "admin" as the username and password to login as an
     admin and create a user account.
  6. Assign the required permissions to the user through a role
  7. If you need to start the OSGi console with the server use the
     property -DosgiConsole when starting the server
  8. Samples configurations can be specified by passing the property
     -Desb.sample=${SAMPLE_NUMBER}

_*New Features of this release includes;*_

  1. Based on the OSGi based WSO2 Carbon platform. This is a
     unification of all Java based products from WSO2.
  2. Enhanced fully internationalized User Interface
  3. Separable frontend & backend - a single frontend server can be
     used to administer several cluster of backend servers
  4. EDA support with WS-Eventing
  5. Graphical user management, role management and user permissions
  6. Graphical keystore management support
  7. Graphical data sources editor for the DB mediators
  8. Graphical event sources editor
  9. Transport management
 10. Enhanced integrated registry
 11. Enhanced statistics, tracing and logging support
 12. Server management integrated to the user interface (Graceful
     Shutdown/Restart)
 13. Enhanced task, proxy service sequence and endpoint editors
 14. Try-It tool integrated to the user interface
 15. Now you can optionally have features from the web service
     application server WSO2 WSAS and BPEL running on your ESB instance
     seamlessly integrated onto ESB.

All the known issues has been reported to [2] and please note that the
samples documentation is not available in the beta3, and you are more
than welcome to report any issues to shape up the final release.

[1] - http://wso2.org/downloads/esb
[2] - https://wso2.org/jira/browse/CARBON

Thanks,
The WSO2 ESB Team.

_______________________________________________
Carbon-dev mailing list
Carbo...@wso2.org
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Senaka Fernando

unread,
Jan 14, 2009, 9:59:36 AM1/14/09
to sci-fl...@googlegroups.com
Hi again,

I forgot to mention. Due to a minor fix that was lately introduced, SCI-Flex might not work with ESB 2.0 versions below ESB 2.0 beta3 (the latest), there was a small change done to the services.xml in the admin service. This is totally a WSO2 Carbon change, beyond our control.

Regards,
Senaka
Reply all
Reply to author
Forward
0 new messages