http://www.andrewferrier.com/blog/2006/06/28/5-minute-soa-sca-in-websphere-esb/?utm_source=rss&utm_medium=rss&utm_campaign=5-minute-soa-sca-in-websphere-esb Economics; Travel; Film; and Technology. Tue, 07 Feb 2012 03:31:30 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.andrewferrier.com/blog/2006/06/28/5-minute-soa-sca-in-websphere-esb/comment-page-1/#comment-156 Andrew Ferrier’s Blog » Blog Archive » What is WebSphere Integration Developer? Tue, 25 Jul 2006 16:46:55 +0000 http://www.new-destiny.co.uk/andrew/blog/2006/06/28/5-minute-soa-sca-in-websphere-esb/#comment-156 [...] (see this posting for more information on SCA modules and components) [...] [...] (see this posting for more information on SCA modules and components) [...]

]]> http://www.andrewferrier.com/blog/2006/06/28/5-minute-soa-sca-in-websphere-esb/comment-page-1/#comment-135 Andrew Ferrier’s Blog » Blog Archive » Correction: SCA Default Binding Mon, 24 Jul 2006 12:37:44 +0000 http://www.new-destiny.co.uk/andrew/blog/2006/06/28/5-minute-soa-sca-in-websphere-esb/#comment-135 [...] In a previous post describing SCA in WebSphere ESB / Process Server, I wrote that SCA modules have to be running in the same address space. I’d like to correct this: the restriction actually imposed on these bindings is that they need to be between SCA modules running in the same WebSphere cell (see this post for more information on cells, nodes, and servers). This is because the SCA resources that are automatically created when an SCA module is deployed are cell-scoped. Different types of SCA resources are created depending on whether asynchronous or synchronous behaviour is required, which is normally decided automatically, but in both cases the scope is the same. For more information, see this Developerworks article. It’s worth adding that there also two other types of bindings that I didn’t cover before: [...] [...] In a previous post describing SCA in WebSphere ESB / Process Server, I wrote that SCA modules have to be running in the same address space. I’d like to correct this: the restriction actually imposed on these bindings is that they need to be between SCA modules running in the same WebSphere cell (see this post for more information on cells, nodes, and servers). This is because the SCA resources that are automatically created when an SCA module is deployed are cell-scoped. Different types of SCA resources are created depending on whether asynchronous or synchronous behaviour is required, which is normally decided automatically, but in both cases the scope is the same. For more information, see this Developerworks article. It’s worth adding that there also two other types of bindings that I didn’t cover before: [...]

]]>