[Users] [SCA-JBI] Replacing SMX EIP SE in SMX ESB with Petals SCA SE

vzurczak vincent.zurczak at petalslink.com
Wed Mar 16 11:00:29 CET 2011


ObjectOrange wrote:
> Are the 'Components' in the SCA composite model the same as the JBI Components (Binding Components/Service Engines)?


No, they are no the same.
SCA components are configured code (i.e. an implementation, with SCA services and SCA references).

Call to external services (bus services here) are managed by the references.
These references can be used in the implementation.

I invite you to take a look at one of the tutorials that was written on the SCA Tools wiki (http://wiki.eclipse.org/STP/SCA_Component/SCA_First_Steps_With_Composite_Designer). :) 


ObjectOrange wrote:
> The service orchestration basically looks like this (using the JBI components, each with needed services registered):
> 
> HTTP BC -> EIP Pipeline Route -> Saxon SE -> EIP Pipeline Route -> JSR181 SE -> EIP Pipeline Route -> Saxon SE -> File BC


With SCA, that would give:
1. HTTP BC -> SCA SE
2. The SCA application, deplolyed on the SCA SE, calls:
2.1 The Saxon SE
2.2 The Jsr181 SE
2.3 The Saxon SE
2.4 The File BC

And if the Saxon end-points bother you, you could directly merge them in the SCA application.
That would reduce the number of intermediate end-points. But it is a matter of granularity.




-------------------- m2f --------------------

Subscribe/Unsubscribe emails notifications.

Response to this email will be posted on the Petals forum.
Please delete the existing text before responding :)

Read the topic online:
http://forum.petalslink.com/viewtopic.php?p=31148#31148

-------------------- m2f --------------------






More information about the Users mailing list