Author: ruwan Date: Mon Jul 6 13:23:59 2009 New Revision: 40883 URL: http://wso2.org/svn/browse/wso2?view=rev&revision=40883
Log: Applyig the documentation patches to the trunk Added: trunk/esb/java/docs/resources/images/esb-architecture.png (contents, props changed) Modified: trunk/esb/java/docs/site.xml trunk/esb/java/docs/xdoc/index.xml Added: trunk/esb/java/docs/resources/images/esb-architecture.png URL: http://wso2.org/svn/browse/wso2/trunk/esb/java/docs/resources/images/esb-architecture.png?pathrev=40883 ============================================================================== Binary file. No diff available. Modified: trunk/esb/java/docs/site.xml URL: http://wso2.org/svn/browse/wso2/trunk/esb/java/docs/site.xml?rev=40883&r1=40882&r2=40883&view=diff ============================================================================== --- trunk/esb/java/docs/site.xml (original) +++ trunk/esb/java/docs/site.xml Mon Jul 6 13:23:59 2009 @@ -66,6 +66,7 @@ <item name="User Guide" href="user_guide.html"/> <item name="Installation Guide" href="installation_guide.html"/> <item name="Quick Start" href="quickstart_guide.html"/> + <item name="Administrator Guide" href="admin_guide.html"/> <item name="Deployment Guide" href="deployment_guide.html"/> <item name="Extending ESB" href="extensions_guide.html"/> <item name="Configuration" href="configuration_language.html"/> @@ -86,13 +87,14 @@ </menu> <menu name="Catalogs"> <item name="Transports" href="transports/transports-catalog.html"/> - <item name="Mediators" href="mediator_guide.html"/> - <item name="Endpoints" href="endpoint-catalog.html"/> + <item name="Mediators" href="mediator_guide.html"/> + <item name="Endpoints" href="endpoint_guide.html"/> </menu> <menu name="Resources"> <item name="FAQ's" href="faq.html"/> <item name="Java Docs" href="http://ws.apache.org/synapse/apidocs/index.html"/> <item name="Library" href="http://wso2.org/library/esb"/> + <item name="Features" href="http://wso2.org/projects/esb/java/features"/> <item name="Source Code" href="source-repository.html"/> <item name="Wiki" href="http://wso2.org/wiki/display/esbjava"/> </menu> Modified: trunk/esb/java/docs/xdoc/index.xml URL: http://wso2.org/svn/browse/wso2/trunk/esb/java/docs/xdoc/index.xml?rev=40883&r1=40882&r2=40883&view=diff ============================================================================== --- trunk/esb/java/docs/xdoc/index.xml (original) +++ trunk/esb/java/docs/xdoc/index.xml Mon Jul 6 13:23:59 2009 @@ -24,258 +24,108 @@ <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"/> <title> - Welcome to WSO2 Enterprise Service Bus (ESB) v1.7 + Welcome to WSO2 Enterprise Service Bus (ESB) v2.1.0 </title> <link href="css/esb-docs.css" rel="stylesheet"/> <link href="styles/dist-docs.css" rel="stylesheet" type="text/css" media="all"/> </head> <body xml:lang="en"> <h1> - Welcome to WSO2 Enterprise Service Bus (ESB) v1.7 + Welcome to WSO2 Enterprise Service Bus (ESB) v2.1.0 </h1> - <h3> - June, 2008 - WSO2 ESB, v1.7 Released! - </h3> - <p> - [<a href="http://dist.wso2.org/products/esb/java/1.7">Download</a>] | [<a - href="docs_index.html">Documentation Index</a>] | [<a - href="http://wso2.org/projects/esb/java#resources">Project Resources</a>] - | [<a href="http://wso2.org/projects/esb/java">Official Web site</a>]</p> - <p/> - <p> - The WSO2 ESB is an ultra fast, light-weight and versatile Enterprise Service Bus - based on the <a href="http://synapse.apache.org">Apache Synapse ESB</a>. It allows you - to Connect, Manage and Transform service interactions between Web services, - REST/POX services and Legacy systems - </p> - <p> - WSO2 ESB is released under the <a - href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache License v2.0</a> - </p> - <h2> - New Features - </h2> - <h3> - WSO2 ESB 1.7 Features - </h3> - <ul> - <li>Support for Hessian binary messages</li> - <li>FIX (Financial Information eXchange) protocol transport</li> - <li>WS-Reliable Messaging support with WSO2 Mercury</li> - <li>Ability to stop, re-start and gracefully shutdown the ESB through JMX</li> - <li>Integrated WSO2 Registry shipped, with ability to connect to a remote WSO2 Registry</li> - <li>Support for re-usable database connection pools for DB report/lookup mediators</li> - <li>Support for GZip encoding and HTTP 100 continue</li> - <li>Natural support for dual channel messaging with WS-Addressing</li> - <li>Cluster aware sticky load balancing support</li> - <li>Non-blocking streaming of large messages at high concurreny with constant memory usage</li> - <li>Support for an ELSE clause for the Filter mediator</li> - <li>Ability to specify XPath expressions relative to the envelope or body</li> - <li>Support for separate policies for incoming/outgoing messages</li> - <li>Support for a mandatory sequence before mediation</li> - <li>New Router mediator</li> - <li>Ability to re-deploy proxy services</li> - </ul> - <h3> - WSO2 ESB 1.6 Features - </h3> - <ul> - <li> - Ability to pin a proxy or a task to server instances - </li> - <li> - Improved error handling in JMS transport - </li> - <li> - New Mail transport that supports POP3/IMAP/SMTP - </li> - <li> - Clustering support for the Cache/Throttle mediators - </li> - <li> - Maintainance mode support for the HTTP transport - </li> - <li> - JMX statistics monitoring and management support - </li> - <li> - New mediator - Callout - </li> - <li> - Improved REST/POX support - </li> - <li> - Annotations support for POJOCommand mediator - </li> - <li> - Ability to edit UI-less mediators in raw XML - </li> - </ul> - <h3> - WSO2 ESB 1.5 Features - </h3> - <ul> - <li> - Apache VFS based file transport - </li> - <li> - Scheduled Task support - </li> - <li> - New mediators - XQuery, POJO Command, DB Report and DB Lookup - </li> - <li> - New EIP mediators - Split/Clone and aggregator mediators - </li> - <li> - Cache, Throttle and Class mediator enhancements - </li> - <li> - Improved logging and tracing support, and reconfiguration of Log4J - instance at runtime - </li> - <li> - Ability to save/edit sequences and endpoints directly to/from the - integrated registry - </li> - <li> - Ability define more than one administration account - </li> - <li> - General UI usability enhancements and fixes - </li> - </ul> - <h3> - WSO2 ESB 1.0 Features - </h3> - <ul> - <li> - Proxy services - facilitating transport, interface (WSDL/Schema/Policy), - message format (SOAP/POX), QoS (WS-Security/RM), and optimization - switching (MTOM/SwA) - </li> - <li> - Non-blocking HTTP/HTTPS transport for ultrafast execution and support - for many connections. - </li> - <li> - Integrated Registry/Repository, facilitating dynamic updating and - reloading of the configuration and resources. - </li> - <li> - Easily extended via custom Java class/Spring mediators, or BSF Scripting - languages (JavaScript, Ruby, etc) - </li> - <li> - Load-balancing/Fail-over and Throttling support - </li> - <li> - WS-Security, WS-Reliable Messaging, and Throttling configurable via - WS-Policies. - </li> - <li> - JMS message support for binary, plain text, and XML payloads. - </li> - <li> - Facilitates easy management and monitoring of the service - infrastructure. - </li> - <li> - Lightweight, XML, Web services centric message model. - </li> - <li> - Configurations serialized into a file system for versioning/backup and - restoration. - </li> - </ul> - <h3> - Known Issues and Limitations - </h3> - - <ol><li>WSO2 ESB known issues and limitations - - <ul> - <li>ESBJAVA-509 Unwanted Java Script alert displayed when updating the Cache Mediator</li> - <li>ESBJAVA-444 Problem when creating an endpoint from a WSDL and the address of the WSDL is a https address</li> - <li>ESBJAVA-452 Once a Proxy Service is removed the relevant statistics of that particular Proxy service should be removed as well</li> - <li>ESBJAVA-484 ESB fails to start when WSDL URI is not found</li> - <li>ESBJAVA-497 VFSTransportListener Error closing stream</li> - <li>ESBJAVA-346 Cursor not available in some of the popup windows</li> - <li>ESBJAVA-372 [IE] When the wso2-esb.log is about 2MB .. the browser hangs</li> - <li>ESBJAVA-505 Problems with web console in Firefox 3.0 RC1</li> - </ul> - </li> - - - <li>As the WSO2 ESB 1.7 depends on the Apache Synapse 1.2, it inherits the list of known issues of - the Apache Synapse 1.2 release listed below - - <ul> - <li>SYNAPSE-180 Does not support throttling by concurrency within a cluster</li> - <li>SYNAPSE-186 Does not support HTTP some of the REST operations (such as put/delete etc)</li> - <li>SYNAPSE-181 Does not yet support JTA transactions</li> - <li>SYNAPSE-330 Does not yet support load balancing with session affinity using SOAP sessions</li> - <li>SYNAPSE-280 Does not preserve CDATA sections within payloads</li> - <li>SYNAPSE-307 The XSLT mediator will not report errors encountered in a provided stylesheet</li> - <li>SYNAPSE-348 MTOM serialization of attachment fails</li> - <li>The Synapse JMS implementation supports JMS 1.0.2b, however due to licensing issues we include - the JMS 1.1 spec JAR from Apache Geronimo (geronimo-jms_1.1_spec-1.1.jar) instead. If you have - any issues with JMS 1.0.x, please download the Sun JMS 1.0.2b JAR and replace supplied JAR from - Geronimo.</li></ul></li> - -<li>Dependencies are currently allowed to be removed from the admin console, while live references - remains - - <ul><li>The ESB UI currently does not perform a check on references before the elements are allowed to - be removed. Thus there is a possibility of defining references to non-existent endpoints, - sequences etc. as well as removing them while live references still exist.</li></ul></li> - </ol> - <p/> - <h2> - How You Can Contribute - </h2> - <h3> - Mailing Lists - </h3> - <p> - Join our mailing list and correspond with the developers directly. - </p> - <ul> - <li> - Developer List : <a href="mailto:[email protected]">[email protected]</a> + <p>The WSO2 ESB is a lightweight and easy-to-use Open Source Enterprise Service Bus (ESB) + available under the <a href="http://www.apache.org/licenses/LICENSE-2.0.html">Apache + Software License v2.0</a>. WSO2 ESB allows administrators to + simply and easily configure message routing, virtualization, intermediation, + transformation, logging, task scheduling, load balancing, failover routing, event + brokering, etc.. The runtime has been designed to be completely asynchronous, non-blocking + and streaming based on the <a href="http://synapse.apache.org">Apache Synapse</a> core.</p> + + <p>WSO2 ESB 2.1.0 is developed on top of the revolutionary + <a href="http://wso2.org/projects/carbon">Carbon platform</a> (Middleware a' la carte), + and is based on the OSGi framework to achieve the better + modularity for your Service Oriented Architecture (SOA). 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 to + your SOA needs.</p> + + <p>You can download this distribution from <a href="http://wso2.org/downloads/esb">Project + Download Page</a> and give it a try.</p> + + <h2>Getting Started</h2> + <p>Getting your integration project off the ground with the WSO2 ESB is fairly simple.</p> + <ol> + <li><a href="http://wso2.org/downloads/esb">Download</a> the WSO2 ESB 2.1.0</li> + <li>Read through the <a href="docs_index.html">Documentation Index</a></li> + <li>Visit our <a href="http://wso2.org/projects/esb/java">Official Web site</a></li> + <li>Look at the <a href="release-notes.html">Release Notes</a> for the high level + features, or the <a href="http://wso2.org/projects/esb/java/features">WSO2 ESB Data + Sheet</a></li> + <li> + Developer Mailing List : <a href="mailto:[email protected]">[email protected]</a> | <a href="mailto:[email protected]?subject=subscribe">Subscribe</a> | <a href="mailto:[email protected]?subject=unsubscribe">Unsubscribe</a> | <a href="http://wso2.org/mailarchive/esb-java-dev/">Mail Archive</a> </li> <li> - User List : <a href="mailto:[email protected]">[email protected]</a> + User Mailing List : <a href="mailto:[email protected]">[email protected]</a> | <a href="mailto:[email protected]?subject=subscribe">Subscribe</a> | <a href="mailto:[email protected]?subject=unsubscribe">Unsubscribe</a> | <a href="http://wso2.org/mailarchive/esb-java-user/">Mail Archive</a> </li> - </ul> - <h3> - Reporting Issues - </h3> - <p> - WSO2 encourages you to report issues and your enhancement requests for the - WSO2 ESB using the public <a - href="http://www.wso2.org/jira/browse/ESBJAVA">JIRA</a>. - </p> - <p> - You can also watch how they are resolved, and comment on the progress.. - </p> - <h3> - Discussion Forums - </h3> - <p> - Alternatively, questions could be raised using the forums available. - </p> - <p> - <a href="http://wso2.org/forum/187">WSO2 ESB Forum</a> : - Discussion forum for WSO2 ESB developers/users - </p> + <li><a href="http://wso2.org/forum/187">Discussion forum</a> for + WSO2 ESB developers/users</li> + <li>Report issues on the <a + href="http://www.wso2.org/jira/browse/ESBJAVA">ESB Public JIRA</a></li> + </ol> + <h2>WSO2 ESB Component Architecture</h2> + + <p><img src="images/esb-architecture.png" alt="ESB Architecture"/></p> + + <p>WSO2 ESB supports all the widely used transports including HTTP/s, JMS, VFS and domain + specific transports like FIX, HL7 and so on.. A new transport can be added easily using + the Axis2 transport framework and plug-in to the ESB. Variety of transports brings variety + of message content/payload to the ESB. To identify the message by using the content type + and make it to common XML infoset done by the message builders. So there are message + builders associate with each content type. WSO2 ESB contains message builders for text + based content as well as binary content. Message formatters are the opposite partners of + the builders, formatter convert back the message to the original format by referring the + content type just before the message handover to the transports. Similar to the transports + user can implement new message builders and formatters by using the Axis2 framework.</p> + <p>Endpoints stay as a logical component with the transports. There are three sets of first + level endpoints Address and WSDL & Default. An endpoint can use any available + transport to dispatch the messages. Proxy services the virtual services in the WSO2 ESB + that implemented using message receivers and open up to accept the messages. A proxy + service can access using a URL similar to a normal web service address. Proxy service + allow to publish a WSDL to suite for advance usage. Any available transport can be use to + recive and send messages through the proxy services.</p> + <p>Event-sources are another implementation of message recover to handle messages on eventing, + including both subscriptions and events. The power of the WSO2 ESB remains with the + comprehensive mediator library that serves for different aspects. Using the mediator + library we can implement widely used Message Exchange Patterns (MEP) and Enterprise + Integration Patterns (EIP). Writing a mediator is a simple task for a developer because + WSO2 ESB provides a healthy framework for that, though it is not required to write a + mediator by your own to get most of the mediations implemented on ESB. Mediators can be + implemented using various technologies including Java, scripting and Spring, all of whihc + are considered as extension points to the WSO2 ESB. Sequences is a speciall mediator that + act as the configuration component for the mediators. Sequences allow to organize the + mediators to implement an ordered pipes and filters pattern to achieve the mediation.</p> + <p>Tasks provide facility to configure scheduled jobs in the WSO2 ESB and it allows to execute + internal and external commands for mediation. QoS components that implements reliable + messaging and security for the proxy services and for mediation comes with the Apache + implementations of those two modules for axis2, which are Rampart and Sandesha.</p> + <p>WSO2 ESB has an inbuilt registry/repository to store the configuration and configuration + metadata and it provides the facility to use a remote repository as well. Components that + helps to run WSO2 ESB on production environment are clustering, high availability and + load balancing capabilities. Finally the GUI components that make the comprehensive + management, configuration and monitoring capabilities to the ESB. GUI has done on a layered + architecture by separating the backend and frontend concerns. This allow the user to + connect to multiple backends using a single GUI console. The component based architecture + of the WSO2 ESB has enhanced the loosely coupling nature with the usage of OSGi. All the + components are built as OSGi bundles.</p> + </body> </html> \ No newline at end of file _______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
