|
|
0.02 2008-04-23 21:12 -0700 |
The ODMA32 2.5 Development is a set of ODMA32 2.0 Supplementary integrations that support additional integration scenarios. ODMA32 2.5 provides a model by which the current ODMA Connection Manager implementation can be surrounded by supporting layers and then enriched to become the basis for migration to the 64-bit world with an ODMA64 3.0 release.
ODMJNI 1.0 development demonstrates the feasibility of embracing the ODMA 2.0 Connection Manager, ODMA32, with a series of wrappers that completely hide the original ODMA API and deliver a component library instead. The component libraries enable ODMA-aware Java-based, .NET-based, and ActiveX/COM-based software to be developed without any awareness of or concern for the C Language Win32 API of ODMA.
The object-oriented friendly component interfaces operate entirely with Unicode strings and improved abstractions for interactions with ODMA-aware DMS integrations.
An additional shared feature of the component libraries, also demonstrated with ODMJNI, is having a common bridge layer, the OdmNative library, that encapsulates access to the native ODMA 1.0-2.0 APIs beneath an in-process, statically-linked COM wrapper. OdmNative works as a single, consistent foundation for object-oriented wrappers in Java, the .NET languages, and ActiveX scripting. Initially developed to support ODMJNI, the OdmNative100 library will be refactored as a general ODMA-access library with the 0.80 deployment of ODMJNI 1.0. At that point, development of additional wrappers can begin.
OdmNative, the wrappers that are built above it, and accompanying utilities, cover over the native ODMA Connection Manager to provide a modern component-oriented integration into ODMA-aware software on the desktop.
It is also desirable to improve the integration model, allowing Unicode-oriented Document Management System (DMS) integrations to avoid translation to single-byte character encodings when the ODMA-connection desktop software is Unicode friendly.
Extended interfaces from DMS integrations will be usable directly from the OdmNative layer when it is present. This provides an opportunity to eliminate intermediate conversions and operate with Unicode data all the way through from desktop program to the DMS and back. The extended interfaces also provide for streamlined object models, including delivery of container models, document streams, and other improvements when it is valuable to avoid copying documents to and from the desktop file system in order to exchange content with the DMS.
Just as important for engulfing of ODMA32 is the provision of special DMS integration-level fixtures and adapters. Adapters that substitute for DMS integrations can allow fully-automated tests that confirm correct operation of ODMA-aware desktop software and the ODMA Connection Manager. This completes the engulfment of ODMA32, allowing it to be completely tested and also safely replaced by improved implementations.
Ideally, the engulfment of ODMA32 on the Win32 platform will allow enrichment of the ODMA 2.0 Connection Manager and support of transition of ODMA fixtures to a level (termed ODMA 2.5) that poises them for migration to Win64 and operation with an ODMA64 connection (termed the ODMA 3.0 level).
The purpose of this folio is to envision the road map, risk mitigation, and important milestones for engulfing and extending ODMA32 that simplifies the ultimate migration to ODMA64.
Although it is also desirable to have adapters to DMS integrations developed in Java, .NET languages, and as ActiveX/COM components, it is not clear what the feasible cases are and how they might be demonstrated. This is not a condition on the successful engulfment of ODMA32. Any success in this area is a bonus.
- see also:
- d080101: ODMA Roadmap
d080102: ODMA Effectiveness- d071002: ODMA64 3.0 Interoperability
d071004: ODMA Core
d061003: OdmNative100 ODMA-Access Implementation- ODMA q070701: ODMJNI Java-ODMA Integration Kit
NuovoDoc Analysis: ODMA -- Where's It Going?
- Hamilton, Dennis E.
- ODMA32 Engulfed. AIIM ODMA Interoperability Exchange, ODMdev Development Note d071003 0.02, February 15, 2008. Available at <http://ODMA.info/dev/devNotes/2007/10/d071003.htm>.
|
|
created 2007-10-25-19:20 -0700 (pdt) by
orcmid |
