eSciDoc is an eResearch environment developed specifically for use by scientific and scholarly communities to collaborate globally and interdisciplinary. It comprises a set of services and solutions that enable innovative eScience scenarios: Scientists, librarians, and software developers can work with research data, create novel forms of publications, and establish new ways of scientific and scholarly communication. more...
Teaser for an interesting book...
EAI - The Broader Perspective
No one should have (or will) ever dared to build a 'Single System' which will take care of the entire business requirements of an enterprise. Instead, we build few (or many) systems,and each of them takes care of a set of functionalities in a single Line of Business (LOB). There is absolutely nothing wrong here, but the need of the hour is that these systems have to exchange information and interoperate in many new ways which have not been foreseen earlier. Business grows, enterprise boundaries expands and mergers and acquisition are all norms of the day. If IT cannot scale up with these volatile environments, the failure is not far.
Willkommen in der iteraplan Community. iteraplan ist das erste Open Source Enterprise Architecture Management (EAM) Werkzeug für das strategische Management Ihrer Applikationslandschaft. Das Software- und Beratungshaus iteratec hat das Werkzeug iteraplan erstellt und übernimmt auch zukünftig die Führung in der Weiterentwicklung von iteraplan im Rahmen der Open Source Community.
The XAware project provides real time data integration with a service-oriented flavor. XAware makes other tools and frameworks much more productive by hiding data complexity behind "XML views". XML views span any number of data sources, and can read data, write data, or transfer data between sets of sources, all within a distributed transaction.
ChainBuilder ESB is Java Business Integration (JBI) compliant open source solution for use in Service Oriented Architecture (SOA) environments. ChainBuilder ESB's graphical integration enables new and older applications to easily enter into SOA.
Apache Camel is a powerful rule based routing and mediation engine which provides a POJO based implementation of the Enterprise Integration Patterns using an extremely powerful fluent API (or declarative Java Domain Specific Language) to configure routing and mediation rules. The Domain Specific Language means that Apache Camel can support type-safe smart completion of routing rules in your IDE using regular Java code without huge amounts of XML configuration files; though Xml Configuration inside Spring is also supported.
* is language-neutral: it will allow the writing of software libraries for communicating with JMS providers in any language that has libraries for communicating over HTTP.
* is RESTful: it provides a RESTful equivalent to all of the non-optional portions of the JMS API including
o registration of resources administered by the messaging provider
o connection and session management
o sending and receipt of all types of JMS message
Implementation overview
HJB
*
is deployed as a servlet (HJBServlet), that can run on any compliant Servlet specification 2.4 container.
*
will work with any messaging vendor that provides a JMS interface.
*
aims to do one thing well. Its role is to act as an HTTP gateway server for JMS resources. Other potentially useful features are deliberately excluded, e.g,
o HTTP session management
o authentication and authorization
The Synapse project is a robust, lightweight implementation of a highly scalable and distributed service mediation framework based on Web services and XML specifications.
PEtALS is the highly distributed Open Source ESB hosted by OW2. PEtALS delivers OW2 JavaTM Business Integration (JBI) platform.
PEtALS provides lightweight and packaged integration solutions, based on JSR-208 specifications, with a strong focus on distribution and clustering.
One of the biggest promises of Business Process Management was that the business people can model and execute their business processes without involvement from IT folks. This promise was kept in a simple workflow sceanarios by utilizing limited number of 'built-in' activity types of BPMS packages but once you face little more complex business process sceanarios providing transactional integration with existing software and complex interactions with human beings, this limited expression power make it hard to drag and drop process modeling, and finally it brings a huge help from software vendors or system integrators and write a lot of code that is making processes utterly inflexible downstream. That means, concurrent BPMS is extremely lack in something like 'Technical Abstraction' and 'Expression Extensibility'.
The intention for this project is a very simple API to call different kinds of services (provider/technology). Crispy's aims is to provide a single point of entry for remote invocation for a wide number of transports: eg. RMI, EJB, JAX-RPC or XML-RPC. It works by using properties to configure a service manager, which is then used to invoke the remote API. Crispy is a simple Java codebase with an API that sits between your client code and the services your code must access. It provides a layer of abstraction to decouple client code from access to a service, as well as its location and underlying implementation. The special on this idea is, that these calls are simple Java object calls (remote or local calls are transparent).