Questions on the SOPERA Architecture

[bensehmuz]

Hi all,

I have some very basic questions concerning the SOPERA tooling. I read through the documentations, the forum, and elsewhere on the internet.. So I'd be pleased not to only get a hint to some docs.

I couldn't find a proper and clear explanation to the following:

a) ToolSuite 3.3 = ESB 3.3?
Is there a difference between "ToolSuite 3.3" and "ESB 3.3"? On the download page (http://www.sopera.de/downloads/sopera-asf-33/), there is one download for Windows, and another one for Linux/ Solaris.

b) Since there is one for Linux/ Solaris, is there also an ESB for Windows? How are Toolsuite and ESB related?

c) In the case the ESB is not integrated into the Toolsuite: is there an option to use the ESB separately (standalone)? If so, where can I find it?

d) Toolsuite 3.3 = ASF 3.3?
Are "ToolSuite 3.3" and "ASF 3.3" the same? On the download page of ASF (http://www.sopera.de/downloads/sopera-asf-33/toolsuite-33-allinone-binaries-fuer-windows/) both seem to be equal, whereas on the "SOPERA ASF Community Edition" page (and many more documents) it looks more like ASF is a composition of Toolsuite and ESB.

e) Swordfish = SOPERA ESB Runtime Framework? (First Webinar (http://www.sopera.de/community/sopera-webinare/webinar-archiv/videoarchiv/))
SOPERA Runtime is actually described as being part of the Development Box (Documentation).

f) Swordfish = Distributed Service Bus?
Is the current version of Swordfish already included in Toolsuite or whatsoever?

g) SOPERA Runtime Framework = Distributed Service Bus?
In different illustrations both are used adequately. Are they the same?

e) It is said that JMS is supported. Can I find an example how this is done?


Sorry for so many questions, but I find the naming (conventions) all over SOPERA very confusing. I wish the distinction would have been a little more obvious.

bensehmuz

[zubairov]

Helo bensehmuz,


a) ToolSuite 3.3 = ESB 3.3?
Is there a difference between "ToolSuite 3.3" and "ESB 3.3"? On the download page, there is one download for Windows, and another one for Linux/ Solaris.

It's a bit complicated due to the many names, but in short - SOPERA ASF 3.3 is a distributed ESB product. ESB installers are available for Linux, Solaris, etc. For Windows we have a ESB tooling called ToolSuite. The ToolSuite contains also a simplified mini-version of ESB and all servers that it needs (ActiveMQ, OpenDS, etc). This mini developer ESB is called DevBox. We also have an AdminTool that could be installed on Windows separately from ESB Tooling, or together with it.


b) Since there is one for Linux/ Solaris, is there also an ESB for Windows? How are Toolsuite and ESB related?


Technically they are the same, Toolsuite contains a ESB the same that is installed on Linux/Solaris.


c) In the case the ESB is not integrated into the Toolsuite: is there an option to use the ESB separately (standalone)? If so, where can I find it?


It's integrated. You could also use Toolsuite to develop/administer remote ESB installed on Linux. Also Linux installers are working on Mac OS X (after little adjustments, see here (http://code.google.com/p/sopera-examples/downloads/detail?name=sopera_mac_patch.tar.bz2&can=2&q=#makechanges))


d) Toolsuite 3.3 = ASF 3.3?


Toolsuite is a part of ASF.


e) Swordfish = SOPERA ESB Runtime Framework?


Yes, for OSGi participants, next week we are going to have a Helios release, just download the Eclipse SOA Package and there you will find a tutorial on how to integrate Swordfish OSGi participants with the SOPERA ASF.


f) Swordfish = Distributed Service Bus?


Yes, Swordfish is a next generation of SOPERA ASF connection layer (similar to what ServiceBackbone is for existing ASF), it has a little ESB instances inside, which is however could scale e.g. by using ASF Service Registry - hence allow Swordfish instances to work as parts of distributed ESB.


g) SOPERA Runtime Framework = Distributed Service Bus?


Yes, SOPERA Runtime Framework (aka. Service Backbone) is also a small ESB deployed on each SOPERA ASF Participant that allow them to communicate and work as part of distributed ESB.


It is said that JMS is supported. Can I find an example how this is done?


JMS, or any other communication protocol is seen in SOPERA terms is a part of non-functional service contract. Functional service contract is expressed in WSDL (SDX + SPDX) where non-functional service contract is expressed in terms of Service Provider capabilities and/or Service Consumer requirements - hence as Service Provider policies and Service Consumer Policies.
Service Registry getting request from Service Consumers along with the consumer policies, then compare them to the registered service providers and their policies.
For more information about policies you can check here (http://www.sopera.de/SOP-Library/ASF_33/Service_Design_and_Development/Developer_Tools_User_Guide/wwhelp/wwhimpl/common/html/wwhelp.htm#context=Developer_Tools_User_Guide&file=dt_developer_tools_userguide.2.132.html) and here (http://www.sopera.de/SOP-Library/ASF_33/Technical_Reference/Policies_Reference_Guide/wwhelp/wwhimpl/common/html/wwhelp.htm#context=Policies_Reference_Guide&file=qos_policies_guide.2.7.html)
In the Toolsuite installation you can find a Library tutorial (http://www.sopera.de/SOP-Library/ASF_33/Service_Design_and_Development/Developer_Guide/wwhelp/wwhimpl/common/html/wwhelp.htm#context=Developer_Guide&file=dv_developers_guide.2.50.html) which is using JMS for pub-sub communication example.

It's is long answer :) however I hope it would help to clarify things.

Renat

[bensehmuz]

Hi zubairov,

first of all thank you for the reply!

I think I'm getting closer to understanding SOPERA :) May be a glossary would be very helpful. In my opinion, the word ESB is quite overloaded:


"SOPERA ASF 3.3 is a distributed ESB"
"SOPERA Runtime Framework (aka. Service Backbone) is also a small ESB"
"Toolsuite contains an ESB"
"Swordfish [...] has a little ESB instances inside"

This would lead to a construct like:
An ESB (ASF) consists of an ESB (Runtime Framework) and an(other) ESB (Toolsuite), the last of which contains an ESB (DevBox) :)

Anyhow, I'll try to keep on working. I may get back with more questions..

Thanks again!

bensehmuz

[Michael]

Perhaps this makes it easier:

The ESB Runtime 3.3 bundle provides two different installations for Linux/Solaris:

A infrastructure with the technical service participants (TSP) like ServiceRegistry, Security TSP and Configuration TSP.
SOPERA participant installation (ServiceBackbone/SBB) which prepares a server to run business service participants.


ToolSuite 3.3 is a bundle which contains

ESB Runtime 3.3 for Windows

SOPERA infrastructure
SOPERA participant installation (which can be selected seperatly for business service participants on Windows)

ASF Design Tools
ASF Administration Tools
Development Tools

Generic Service Provider
Simple Service Consumer
...



What you should download:

You want to evaluate SOPERA ASF
Take the ToolSuite bundle. It contains everything you need: Infrastructure, participant installation, design tools, development and adminstration tools.

You want to develop service participants
Take the ToolSuite and install at least ServiceStudio, SBB Library and DevBox.

You want to to run an ASF infrastructure
Take ESB Runtime and install with the SOPERA Infrastructure Server option. This is prepared to run on Linux and Solaris. Windows is not supported so far, sorry.
For administration of this infrastructure you need either ToolSuite for Administrators or ToolSuite with at least SBB Library and AdminTool installed.

You want to to run a service participant
For Linux/Solaris take ESB Runtime and install with the SOPERA Participant Server option.
For Windows take the ToolSuite and install SBB Library.
Note: An ASF infrastucture must be available in your network.

Cheers
Michael