[Fwd: [ebxml-iic-comment] Public Comment]

[Sacha Schlegel <sschlegel@cyclonecommerce.com>]

Email to ebxml-iic-comment. Sacha

--- Begin Message ---

• From: comment-form@oasis-open.org
• To: ebxml-iic-comment@lists.oasis-open.org
• Date: 9 Sep 2005 14:09:15 -0000

Comment from: ladislav.urban@webswell.com

Name: Ladislav Urban
Title: CEO
Organization: Webswell Inc.
Regarding Specification:
 Hello Sacha and all IIC group members,
I would like to introduce what we do. We develop open source implementation of ebXML and WS-I web services standards. It is based on open source components. Webswell Connect http://sourceforge.net/project/showfiles.php?group_id=79859&package_id=93615
 
One of the components that can be used even independently is Webswell Broker. http://sourceforge.net/docman/display_doc.php?docid=26987&group_id=79859

The most recent version is on CVS. 
Webswell Broker (WB) is an integration module between business application and local message service handler. It can be used as a module of Webswell Connect or as an additional module to MSH Hermes and ebXMLRR. WB can be used for integration of legacy applications that are able to export and import data to and from file systems.
 
 

When WB is started it reads the list of applicable CPA's. The next step is to select and download CPAs from Reg/Rep and register application contexts for receiving and sending ebXML messages on local instance of message service handler. The basic behavior is that it scans configured directories for payloads and control files. 
 
Payloads are documents that have to be securely and reliably transferred to the remote business applications. Control files have the same purpose as in classical EDI integration but include just ebXML application context, (the address in ebXML world). After WB reads control file and corresponding payload it asks Registry / Repository through REST interface for specific CPA that is suitable for given type of transaction. 

The next step of WB is to select specific parameters for given type of action and create appropriate ebXML message and pass the message through SOAP interface to local message service handler. The advantage of this separation is that WB can be behind a firewall and local message service handler could be outside. Webswell Broker package includes set of supporting utilities for testing and monitoring. 
 
Please if you have any questions let me know. We will certainly have questions regarding interoperability. We are currently in process of
 integration Webswell Connect with other ebxml implementation for our customer.

---------------------------------------------------------------------
To unsubscribe, e-mail: ebxml-iic-comment-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ebxml-iic-comment-help@lists.oasis-open.org

--- End Message ---

This is a digitally signed message part