Re: What is Tuscany?
On 12/17/07, Mike Edwards <[EMAIL PROTECTED]> wrote: > Joshua, > > Let me see if I can help explain some: > > Joshua Jackson wrote: > > > Thanks for the article. I kind of get idea now. This is what I get from it: > > SCA is a kind of glue code for glueing pool of apps to be used by > > another apps. So our new apps will connect to SCA and SCA will connect > > to these pool of apps. CMIIW. > > Yes, SCA is at one level a way of connecting together sets of components > to build up your overall application. One of the great things is that > you don't have to code any information about what is connected to what > into your code. This is applied as configuration data - and so it > allows the data to be changed without changing the code - and it allows > the code to be reused in different configurations. > > > > > > I don't quite understand. People out there compares SCA with JBI, > > which is an ESB. :( And that's an insight that I get from those > > articles you gave me too. > > > > JBI is largely a way of putting a runtime together - where the runtime > involves components written using different technologies (eg BPEL and > Java). SCA is a way of putting applications together - where there are > potentially components written in different technologies and connected > by different technologies. > > It happens that you could envisage running SCA applications on a JBI > runtime - ie JBI can provide the sort of runtime that SCA applications > can use. > > HOWEVER, SCA does not depend on JBI at all - Tuscany, for example, does > not use JBI at all. Further - SCA can describe applications that aren't > written in Java and don't use a Java based runtime either (eg there is a > C++ runtime in Tuscany that can run components written in C++, Ruby and > other scripting languages). > > One way to look at SCA is that it CAN be used as a programming model for > ESBs. SCA describes the components that run on the ESB and their > connectivity. You can have components that are message transformations > or the selection of a target service based on some rule, for example. > These are the sorts of things that ESBs do. > > That doesn't mean that SCA is an ESB - just that it can be used to build > applications that run on an ESB. > > Is Tuscany an ESB? Well, it could be ;-) - a funny half-answer. > I can do some of the things that an ESB does. But ESBs usually have > specialized component types that do things like message mapping - > Tuscany only has some of these today. On the other hand, anyone can > write new component types for SCA, so that anything needed could be > added to SCA. > > One other point about SCA is that it is about distributed systems - most > ESBs are not like that. In other words, for SCA, different components > can run on different nodes in a network. Wow. Very nice. Thank you so much Mike. A very insightful explanation that I didn't get after reading several articles. :) > > Is there anything I need to know in order for Tuscany to connect to AS400 ? > > > > You need to know which communication protocol(s) you can use to talk > with the AS/400 - plus the appropriate addresses of endpoints relating > to the AS/400. So, maybe you're using JMS over MQSeries, or Web > services, or . Yes. I'm doing a research on that now. I am going to use the Data Queue protocol. I might as well ask IBM for support regarding this. Thank you so much. -- I'm a coder not a drag-n-dropper Blog: http://joshuajava.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is Tuscany?
Joshua, Let me see if I can help explain some: Joshua Jackson wrote: Thanks for the article. I kind of get idea now. This is what I get from it: SCA is a kind of glue code for glueing pool of apps to be used by another apps. So our new apps will connect to SCA and SCA will connect to these pool of apps. CMIIW. Yes, SCA is at one level a way of connecting together sets of components to build up your overall application. One of the great things is that you don't have to code any information about what is connected to what into your code. This is applied as configuration data - and so it allows the data to be changed without changing the code - and it allows the code to be reused in different configurations. I don't quite understand. People out there compares SCA with JBI, which is an ESB. :( And that's an insight that I get from those articles you gave me too. JBI is largely a way of putting a runtime together - where the runtime involves components written using different technologies (eg BPEL and Java). SCA is a way of putting applications together - where there are potentially components written in different technologies and connected by different technologies. It happens that you could envisage running SCA applications on a JBI runtime - ie JBI can provide the sort of runtime that SCA applications can use. HOWEVER, SCA does not depend on JBI at all - Tuscany, for example, does not use JBI at all. Further - SCA can describe applications that aren't written in Java and don't use a Java based runtime either (eg there is a C++ runtime in Tuscany that can run components written in C++, Ruby and other scripting languages). One way to look at SCA is that it CAN be used as a programming model for ESBs. SCA describes the components that run on the ESB and their connectivity. You can have components that are message transformations or the selection of a target service based on some rule, for example. These are the sorts of things that ESBs do. That doesn't mean that SCA is an ESB - just that it can be used to build applications that run on an ESB. Is Tuscany an ESB? Well, it could be ;-) - a funny half-answer. I can do some of the things that an ESB does. But ESBs usually have specialized component types that do things like message mapping - Tuscany only has some of these today. On the other hand, anyone can write new component types for SCA, so that anything needed could be added to SCA. One other point about SCA is that it is about distributed systems - most ESBs are not like that. In other words, for SCA, different components can run on different nodes in a network. Is there anything I need to know in order for Tuscany to connect to AS400 ? You need to know which communication protocol(s) you can use to talk with the AS/400 - plus the appropriate addresses of endpoints relating to the AS/400. So, maybe you're using JMS over MQSeries, or Web services, or . Thanks in advance Yours, Mike Edwards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is Tuscany?
Joshua Jackson wrote: On 12/8/07, Raymond Feng <[EMAIL PROTECTED]> wrote: Hi, Joshua. Thank you for your interests in Tuscany. Let me try to dump some information to you :-). Tuscany provides open-source software for distribution at no charge to the public, that simplifies the development, deployment and management of distributed applications built as compositions of service components, where the components may be written using any of a wide range of programming languages and where the components can be connected using any of a wide range of communication technologies. This software will implement relevant open standards including, but not limited to, the SCA and SDO standards defined by the OASIS OpenCSA member section. There are a few articles/slides: http://webservices.sys-con.com/read/325183.htm http://java.sys-con.com/read/458183.htm http://cwiki.apache.org/confluence/download/attachments/70211/Tuscany-SOAWorld.ppt?version=1 http://apache-tuscany.blogspot.com/ Thanks for the article. I kind of get idea now. This is what I get from it: SCA is a kind of glue code for glueing pool of apps to be used by another apps. So our new apps will connect to SCA and SCA will connect to these pool of apps. CMIIW. You can find more information at: http://incubator.apache.org/tuscany/. Tuscany is not an ESB offering. My understanding is that it's closer to the business application developers by providing a service assembly model and programming model. The ESB will provide the flexible IT infrastructure that composite applications can be deployed. I don't quite understand. People out there compares SCA with JBI, which is an ESB. :( And that's an insight that I get from those articles you gave me too. This may help: http://www.osoa.org/display/Main/Relationship+of+SCA+and+JBI -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is Tuscany?
On 12/8/07, Raymond Feng <[EMAIL PROTECTED]> wrote: > Hi, Joshua. > > Thank you for your interests in Tuscany. Let me try to dump some information > to you :-). > > Tuscany provides open-source software for distribution at no charge to the > public, that simplifies the development, deployment and management of > distributed applications built as compositions of service components, where > the components may be written using any of a wide range of programming > languages and where the components can be connected using any of a wide > range of communication technologies. This software will implement relevant > open standards including, but not limited to, the SCA and SDO standards > defined by the OASIS OpenCSA member section. > > There are a few articles/slides: > > http://webservices.sys-con.com/read/325183.htm > http://java.sys-con.com/read/458183.htm > http://cwiki.apache.org/confluence/download/attachments/70211/Tuscany-SOAWorld.ppt?version=1 > http://apache-tuscany.blogspot.com/ Thanks for the article. I kind of get idea now. This is what I get from it: SCA is a kind of glue code for glueing pool of apps to be used by another apps. So our new apps will connect to SCA and SCA will connect to these pool of apps. CMIIW. > You can find more information at: http://incubator.apache.org/tuscany/. > > Tuscany is not an ESB offering. My understanding is that it's closer to the > business application developers by providing a service assembly model and > programming model. The ESB will provide the flexible IT infrastructure that > composite applications can be deployed. I don't quite understand. People out there compares SCA with JBI, which is an ESB. :( And that's an insight that I get from those articles you gave me too. > For AS400, what protocols do you have in mind to provide the connectivity? > They are captured as bindings in Tuscany/SCA. There is a bunch of bindings > available in Tuscany > (http://incubator.apache.org/tuscany/sca-java-user-guide.html#SCAJavaUserGuide-AvailableExtensions). > Tuscany runtime is extensible to plug in new bindings. Thanks. I will confirm these to my I.T team what protocol do Ineed in order to connect to AS400. Is there anything I need to know in order for Tuscany to connect to AS400 ? Thanks in advance -- I'm a coder not a drag-n-dropper Blog: http://joshuajava.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What is Tuscany?
Hi, Joshua. Thank you for your interests in Tuscany. Let me try to dump some information to you :-). Tuscany provides open-source software for distribution at no charge to the public, that simplifies the development, deployment and management of distributed applications built as compositions of service components, where the components may be written using any of a wide range of programming languages and where the components can be connected using any of a wide range of communication technologies. This software will implement relevant open standards including, but not limited to, the SCA and SDO standards defined by the OASIS OpenCSA member section. There are a few articles/slides: http://webservices.sys-con.com/read/325183.htm http://java.sys-con.com/read/458183.htm http://cwiki.apache.org/confluence/download/attachments/70211/Tuscany-SOAWorld.ppt?version=1 http://apache-tuscany.blogspot.com/ You can find more information at: http://incubator.apache.org/tuscany/. Tuscany is not an ESB offering. My understanding is that it's closer to the business application developers by providing a service assembly model and programming model. The ESB will provide the flexible IT infrastructure that composite applications can be deployed. For AS400, what protocols do you have in mind to provide the connectivity? They are captured as bindings in Tuscany/SCA. There is a bunch of bindings available in Tuscany (http://incubator.apache.org/tuscany/sca-java-user-guide.html#SCAJavaUserGuide-AvailableExtensions). Tuscany runtime is extensible to plug in new bindings. Thanks, Raymond - Original Message - From: "Joshua Jackson" <[EMAIL PROTECTED]> To: Sent: Thursday, December 06, 2007 9:03 PM Subject: What is Tuscany? Dear all, Can anyone explain to me what tuscany is? Can we call tuscany as an ESB to legacy apps? Does tuscany provide an interface to connect to AS400? Thanks in advance, -- What you want today, may not exist tommorrow Blog: http://joshuajava.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
What is Tuscany?
Dear all, Can anyone explain to me what tuscany is? Can we call tuscany as an ESB to legacy apps? Does tuscany provide an interface to connect to AS400? Thanks in advance, -- What you want today, may not exist tommorrow Blog: http://joshuajava.wordpress.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
