New Developments in Practice II: Enterprise Application Integration
Bibliographic record
Abstract
The term enterprise application integration (EAI) refers to the plans, methods, and tools aimed at modernizing, consolidating, integrating and coordinating the computer applications within an enterprise. The need to integrate across applications is being driven by customer demand for access to information and the desire of the business for a single point of contact with their customer base. The challenges are significant because of the variety of technologies in need of integration and because integration cuts across lines of business. This paper distinguishes among four different (but related) targets of EAI: Data-level integration Application-level integration Process-level integration Inter-organizational-level integration The paper then discusses the technologies that assist with this integration (the "EAI toolkit") under the following categories: Asynchronous Event/Message Transport Transformation Engines Integration Brokers Business Process Management Frameworks The paper concludes by outlining six key strategies for managing EAI suggested by a group of senior IT managers from leading-edge firms.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.010 | 0.013 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.004 |
| Science and technology studies | 0.003 | 0.009 |
| Scholarly communication | 0.017 | 0.022 |
| Open science | 0.002 | 0.010 |
| Research integrity | 0.005 | 0.007 |
| Insufficient payload (model declined to judge) | 0.016 | 0.008 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".