I am trying to find information on what the Sonic Connect service type can be used for.
According to the "Sonic ESB Configuration and Management Guide", it looks as if its for Actional and web services.
Is this correct, or can this service type be used for other types of connections (for instance Camel connections)?
Sonic Connect Service is just like any other ESB Service, this would enable you to build Web Services and RESTful Web Services. You can expose ESB Processes as Web Services or RESTful Services and you can consume external Web Services and RESTful Web Services. For doing this you do not need Actional.
Actional is required when you want to cover your Web Services with some security aspects.
Thanks Kiran.
So, it is only for web services and not for "connections" in general (in some way)?
Yes. Right now it is useful for Web Services and RESTful Web Services.
Kiran,
please, and is this Actional Intermediary licensed with Sonic ESB, or it should be bought separately?
(If separately, then this seems to me like a step back - in V7, WS-Security was available with Sonic ESB, and in V8, it should be paid for?)
Thank you,
Pavol Mederly
Hello,
WS-Security is still available as it was in 7.6/7.5.
You can still expose WS-Security via the SonicMQ broker.
But the recommended approach is to use Actional Intermediary (a separate license) as it provides a much richer functionallity.
Let us knwo what you try to achieve rather than starting a featuers discussion here.
Then it is easier for us to help you :-)
Thanks
Stefan
Thank you, Stefan. Actually, we are OK with https for now, but our system landscape is dynamically changing, so it is possible that we would need WS-Security some day. (I was just curious, to be informed before that day comes.)
I will ask you for more details if (when) the need really comes. We are a public university in Central Europe (Slovakia), so the IT budget is very low; that's why I asked about separate licensing.
Best regards,
Pavol