 |
|
<<O>> Difference Topic
Abstract
(4 - 10 Apr 2007 - Main.bkroczak)
|
| |
| META TOPICPARENT | name="CommunityCorner" |
|---|
JBI is a specification for the integration, it provides a standard for building integration projects, just as EJB provides a standard for transactional projects. | | | To meet this need Imola provided two JBI compliant binding components: jbi4cics and jbi4corba. These components allow for reusing existing business logic, provided the business logic is available as service, without modifying it. So basically these components allow to seamlessly build a SOA architecture upon legacy applications. | |
<
< | Once a legacy service is available as an endpoint published inside a JBI Enterprise Service Bus such as the Sun OpenESB, it can be consumed in many ways and mixed with present and to-be technologies. | >
> | Once a legacy service is available as an endpoint published inside a JBI Enterprise Service Bus such as the Sun OpenESB, it can be consumed in many ways and mixed with present and to-be technologies. | | | -- Main.fredaabedi - 04 Apr 2007 |
|
<<O>> Difference Topic
Abstract
(3 - 09 Apr 2007 - Main.bkroczak)
|
| |
| META TOPICPARENT | name="CommunityCorner" |
|---|
| |
<
< | JBI is a specification for the integration, it provides a standard for building integration projects, just as EJB provides a standard for transactional projects. One of our open source partners who has contributed several JBI binding components is here to present their views about JBI and JBI components. We think that for JBI to have broad acceptance there must be a way first of all to build bridges with existing application and services. To meet this need Imola provided two JBI compliant binding components: jbi4cics and jbi4corba. These components allow for reusing existing business logic, provided the business logic is available as service, without modifying it. So basically these components allow to seamlessly build a SOA architecture upon legacy applications. Once a legacy service is available as an endpoint published inside a JBI Enterprise Service Bus such as the Sun OpenESB, it can be consumed in many ways and mixed with present and to-be technologies | >
> | JBI is a specification for the integration, it provides a standard for building integration projects, just as EJB provides a standard for transactional projects.
One of our open source partners who has contributed several JBI binding components is here to present their views about JBI and JBI components. We think that for JBI to have broad acceptance there must be a way first of all to build bridges with existing application and services.
To meet this need Imola provided two JBI compliant binding components: jbi4cics and jbi4corba. These components allow for reusing existing business logic, provided the business logic is available as service, without modifying it. So basically these components allow to seamlessly build a SOA architecture upon legacy applications.
Once a legacy service is available as an endpoint published inside a JBI Enterprise Service Bus such as the Sun OpenESB, it can be consumed in many ways and mixed with present and to-be technologies. | | | -- Main.fredaabedi - 04 Apr 2007 |
|
<<O>> Difference Topic
Abstract
(2 - 09 Apr 2007 - Main.bkroczak)
|
| |
| META TOPICPARENT | name="CommunityCorner" |
|---|
| |
<
< | JBI is a specification for the integration, it provides a standard for building integration projects, just as EJB provides a standard for transactional projects.
One of our open source partners who has contributed several JBI binding components is here to present their views about JBI and JBI components.
In Imola Informatica we think that for JBI to have broad acceptance there must be a way first of all to build bridges with existing application and services.
To meet this need we provide two JBI compliant binding component jbi4cics and jbi4corba.
These components allow for reusing existing business logic, provided the business logic is available as service, without modifying it.
So basically these components allow to seamlessly build a SOA architecture upon legacy applications.
Once a legacy service is available as an endpoint published inside a JBI Enterprise Service Bus it can be consumed in many ways and mixed with present and to-be technologies.
In Imola we are also designing a semantic service engine, a standard JBI service engine based on the semantic web technologies and able to link services semantically equivalent but syntactically different.
Imola has over 20 years of expertise in enterprise IT consulting and skill transfer.
Imola provides highly qualified enterprise strategists, architects and experts.
Imola has a reputation of “Innovation Company”: we contributed to evangelize market in: OO, RAD, Open Source Business Model, Corba, Java, UML, Open Distributed Architecture, SOA, SCA, EDA, Semantic Technologies. | >
> | JBI is a specification for the integration, it provides a standard for building integration projects, just as EJB provides a standard for transactional projects. One of our open source partners who has contributed several JBI binding components is here to present their views about JBI and JBI components. We think that for JBI to have broad acceptance there must be a way first of all to build bridges with existing application and services. To meet this need Imola provided two JBI compliant binding components: jbi4cics and jbi4corba. These components allow for reusing existing business logic, provided the business logic is available as service, without modifying it. So basically these components allow to seamlessly build a SOA architecture upon legacy applications. Once a legacy service is available as an endpoint published inside a JBI Enterprise Service Bus such as the Sun OpenESB, it can be consumed in many ways and mixed with present and to-be technologies | | | -- Main.fredaabedi - 04 Apr 2007 |
|
<<O>> Difference Topic
Abstract
(1 - 04 Apr 2007 - Main.fredaabedi)
|
|
>
> |
| META TOPICPARENT | name="CommunityCorner" |
|---|
JBI is a specification for the integration, it provides a standard for building integration projects, just as EJB provides a standard for transactional projects.
One of our open source partners who has contributed several JBI binding components is here to present their views about JBI and JBI components.
In Imola Informatica we think that for JBI to have broad acceptance there must be a way first of all to build bridges with existing application and services.
To meet this need we provide two JBI compliant binding component jbi4cics and jbi4corba.
These components allow for reusing existing business logic, provided the business logic is available as service, without modifying it.
So basically these components allow to seamlessly build a SOA architecture upon legacy applications.
Once a legacy service is available as an endpoint published inside a JBI Enterprise Service Bus it can be consumed in many ways and mixed with present and to-be technologies.
In Imola we are also designing a semantic service engine, a standard JBI service engine based on the semantic web technologies and able to link services semantically equivalent but syntactically different.
Imola has over 20 years of expertise in enterprise IT consulting and skill transfer.
Imola provides highly qualified enterprise strategists, architects and experts.
Imola has a reputation of “Innovation Company”: we contributed to evangelize market in: OO, RAD, Open Source Business Model, Corba, Java, UML, Open Distributed Architecture, SOA, SCA, EDA, Semantic Technologies.
-- Main.fredaabedi - 04 Apr 2007 |
|