ODMA FAQtip

Q000706: ODMA Version-Interoperability Configuration

Version 0.14  Last updated 2000-11-01-16:38 -0800 (pst)
The latest version of this information is available at the AIIM DMware ODMA site.

This document addresses questions about installation of ODMA in a way that provides for development, trouble-shooting, and interoperability testing of components with multiple versions of ODMA.  A specific, tested configuration is described.  This can be varied to provide similar capabilities on other configurations.

In the ODMA Version-Interoperability Configuration, three releases of ODMA are installed in a non-conflicting way so that operation across different levels of ODMA-aware applications, ODMA Connection Managers, and ODMA-compliant DMS integrations can be confirmed.

The testing uses Windows 98 and the original ODMA software supplied in the ODMA 1.0, ODMA 1.5, and ODMA 2.0 SDK packages.  It exercises interoperability across Win16 and Win32 applications as well as across levels of ODMA.

The basic ODMA-compliant fixtures used are the ODMA 2.0 ODMASAMP DMS Integration, the ODMA 2.0 ODMATest document application, and the ODMA 1.0 MultODMA document application.  These provide an experimental baseline using components that are simple, freely obtained, and accompanied by complete source code for inspection, instrumentation, and further experimentation. 


Content

1. Platform Configuration

1.1 Hardware

1.2 Platform Software

2. ODMA 2.0 SDK

2.1 Installation

2.2 Usage

2.2.1 ODMA 2.0 Connection Managers
2.2.2 ODMA 2.0 ODMATest Application

2.3 File Version Identifications

3. ODMA 1.5 SDK

3.1 Installation

3.2 Usage

3.3 File Version Identifications

4. ODMA 1.0 SDK

4.1 Installation

4.2 Usage

4.2.1 ODMA 1.0 Connection Managers
4.2.2 ODMA 1.0 MultODMA Application

4.3 File Version Identifications


1. Platform Configuration

1.1 Hardware

Dell Inspiron 7000 Notebook Computer

300MHz Intel Pentium II Processor with MMX Technology

Phoenix Technology 9/19/98 BIOS

192 MB RAM

6.05GB (FAT32) Hard Disk (430MB Available)

1.2 Platform Software

MS-DOS 7.10
4DOS 6.01a installed in place of COMMAND.COM.
The MS-DOS OEM code page number is 473.
 
Microsoft Windows 98 4.10.1998 
All critical updates installed as of 2000-07-24.
All customer service packs installed as of 2000-07-24.
Configuration is for English (United States) with International time and date formats. (yyyy-mm-dd and local time in 24-hour format).
The default code page is Windows ANSI 1252, ISO Character Set ISO 8859-1 Latin 1.
Please noteWindows View/Folder Options/View options are set to allow all uppercase names.  The filenames shown in this document are the accurate names as shown in the directories and in the Zip files.
 
Internet Explorer 5.00.2314.1003 (128-bit encryption)

Windows 98 Internet Services Personal Web Server Running with FrontPage Extensions 4.0.2.2717

Norton Antivirus v5.0 Auto-Protect Enabled.

Norton CrashGuard 3.03 Enabled.

Microsoft Office 2000 Developer Edition 6.00.8433 installed.
This impacts the level of standard libraries (e.g., MFC42.DLL) that are installed.
Service Release SR-1 is not installed.
 
Nico Mak WinZip 7.0 SR-1 (1285) Registered Version used for all archive extractions.
Options | Configuration ... | View tab General option for allowing all-upper case filenames is selected so that consistency between names in archives and extracted files can be confirmed.

2. ODMA 2.0 SDK

The original packaging of the ODMA 2.0 SDK is as a self-installing utility inside of a Zip archive.  Earlier ODMA SDK versions are distributed as Zip archives of individual components to be installed by the user.  

ODMA 2.0 is installed first, allowing its installation of registry information and ODMA .dll files to operate.  The ODMA 2.0 versions of ODMATest, ODMATest32, and ODMASAMP (16-bit and 32-bit) are installed and then available for use in all experiments.

2.1 Installation

Open the ODMA 2.0 SDK package, 5_11_98Odma20.zip, and execute the program Odma20.exe.  

Specify a working directory, ODMA200-SDK, as the destination of all material.  The name is chosen to keep the different versions segregated.  

Install both 16-bit and 32-bit versions of ODMA.

After installation is complete, manually add a new subdirectory:

ODMA200-SDK\ConMan

Copy the ODMA .dll files from c:\Windows\System to the new ConMan subdirectory.  This is the safe parking place for backups of the ODMA 2.0 odma.dll (16-bit) and ODMA 2.0 ODMA32.dll files.  A separate subdirectory is employed so that there is no chance of these .dll files still being used by Odmatest.exe and ODMATest32.exe when different versions of the Connection Manager are installed in Windows\System.

The ODMA Sample DMS, ODMASAMP, is automatically installed by the ODMA 2.0 SDK.  It is retained for usage, since ODMA 2.0 DMS integrations operate correctly with all versions of the ODMA Connection Manager and of ODMA-aware applications.

2.2 Usage

2.2.1 ODMA 2.0 Connection Managers

To Restore the ODMA 2.0 Connection Managers for testing or production operation, copy the desired files from ODMA200-SDK\ConMan to Window\System.  Generally, it is best to always operate with the latest Win32 ODMA32.dll version.  It is sometimes desirable to operating with an older Win16 Odma.dll version.  (See the Recommended Approach section of FAQtip Q000703.)

Add or change registry settings to have the desired DMS integrations as the defaults for ODMA. 

 Adjust the ODMA 2.0 Connection Manager logging instructions as needed.  Since earlier versions of the Connection Manager do not provide logging, the logging instructions can be left unchanged between uses of the ODMA 2.0 Connection Manager implementations (Win16 or Win32).

2.2.2 ODMA 2.0 ODMATest Application

For Win16 ODMATest operation, run

ODMA200-SDK\Odmatest.exe.

For Win32 ODMATest operation, run

ODMA200-SDK\ODMATest32.exe.

Make sure that an appropriate ODMA DMS Integration is selected as the overall default (Win16 and Win32) or have an application-default DMS registered for ODMATest.

2.3 File Version Identifications

Table 1.  ODMA 2.0 SDK Components Used in Interoperability Testing
Name Size (bytes) Time Stamp
(
local time)
Edition Description
Odma20.exe

437229

1998-05-11-08:54

2.0.0-1 Edition 2.0.0-1 of the ODMA SDK Self-Installer, as packaged in 5_11_98Odma20.zip
ODMA200-SDK\
Odmasamp.dll

23344

1998-04-09-15:21

2.0.0-1 Win16 edition of ODMA 2.0 ODMASAMP DMS integration sample.
ODMA200-SDK\
ODMASamp32.dll

68096

1998-04-09-15:31

2.0.0-1 Win32 edition of ODMA 2.0 ODMASAMP DMS integration sample.
ODMA200-SDK\
Odmatest.exe

127072

1998-04-09-15:22

2.0.0-1 Win16 edition of ODMA 2.0-aware ODMATest application.
ODMA200-SDK\
ODMATest32.exe

 39936

1998-04-09-15:31

2.0.0-1 Win32 edition of the ODMA 2.0-aware ODMATest application:
File Version: 1, 0, 0, 1
Description:  ODMATEST MFC
Application
Copyright: Copyright 1997
Internal Name: ODMATEST
Language: English
(United States)
Original Filename: ODMATEST.EXE
Product Name: ODMATEST
Application
Product Version: 1, 0, 0, 1
ODMA200-SDK\
ConMan\
Odma.dll

28672

1998-04-09-15:21

2.0.0-1 Win16 edition of ODMA 2.0 Connection Manager
ODMA200-SDK\
ConMan\
ODMA32.dll

69632

1998-05-07-13:10

2.0.0-1 Win32 edition of ODMA 2.0 Connection Manager.
ODMA200-SDK\
Specification\
Subdirectory with copy of the original ODMA 2.0 Specification
ODMA200-SDK\
Source\
Subdirectory with source code and library files used to build ODMA components, including everything for the ODMATest and ODMASample components.

Not all ODMA 2.0 SDK components are identified in this table.  Some components not required for interoperability testing are omitted.

3. ODMA 1.5 SDK

The original packaging of the ODMA 1.5 SDK is in Zip archive 15devkit.zip.  It is designed for extraction into a specified subdirectory of your choice.  The SDK provides the ODMA 1.5 Connection Manager .dll files.  It also provides all library files necessary for creating ODMA-compliant products and all files for constructing an ODMA 1.5 ODMASAMP DMS Integration (Win16 and Win32).  

For interoperability testing, the ODMA 1.5 components can remain in the separate directory.  The ODMA 1.5 .dll files are moved to Windows\System whenever it is desired to operate with that level of Connection Manager.  So long as the ODMA 2.0 SDK installation has already been done, this simply substitutes the ODMA 1.5 Connection Manager in that testing configuration.

3.1 Installation

Create working directory ODMA150-SDK as the location for all ODMA 1.5 material.

Open the ODMA 1.5 SDK package, 15devkit.zipIMPORTANT: Select the Extract All action.  This preserves the date-time stamps from the packaged files. Select the Use Folder Names option.  Specify the ODMA150-SDK subdirectory as the destination.

3.2 Usage

To test with the ODMA 1.5  Connection Manager for Win16, copy 

ODMA150-SDK\CONMAN\OUT16\ODMA.DLL

to Windows\System.

To test with the ODMA 1.5 Connection Manager for Win32, copy

ODMA150-SDK\CONMAN\OUT32\ODMA32.DLL

to Windows\System.

Add or change registry settings to have the desired DMS integrations as the defaults for ODMA. 

3.3 File Version Identifications

Table 2.  ODMA 1.5 SDK Components Used in Interoperability Testing
Name Size (bytes) Time Stamp
(
local time)
Edition Description
ODMA150-SDK\
ODMASAMP\

Source code and construction components for an ODMA 1.5 Sample DMS, ODMASAMP.
ODMA150-SDK\
CONMAN\

Subdirectory for all materials needed to install ODMA 1.5 or build ODMA-1.5-compliant components.
ODMA150-SDK\
CONMAN\OUT16\
ODMA.DLL

14816

1996-10-31-13:05

1.5.0-1 Win16 edition of ODMA 1.5 Connection Manager
ODMA150-SDK\
CONMAN\OUT32\
ODMA32.DLL

12168

1996-10-31-13:03 1.5.0-1 Win32 edition of ODMA 1.5 Connection Manager.

Not all ODMA 1.5 SDK components are identified in this table.  Some components not required for interoperability testing are omitted.

4. ODMA 1.0 SDK

The final packaging of the ODMA 1.0 SDK is in Zip archive oddev.zip.  It is designed for extraction into a specified subdirectory of your choice.  The SDK provides ODMA 1.0 Connection Manager .dll files.  It also provides all library files necessary for creating ODMA-1.0-compliant products.  There are implementations of an ODMA 1.0 ODMASAMP DMS Integration (Win16 and Win32) and an ODMA 1.0 MultODMA application.  

For interoperability testing, the ODMA 1.0 components can remain in the separate directory.  The ODMA 1.0 .dll files are moved to Windows\System whenever it is desired to operate with that level of Connection Manager.  So long as the ODMA 2.0 SDK installation has already been done, this simply substitutes the ODMA 1.0 Connection Manager in that testing configuration.

4.1 Installation

Create working directory ODMA100-SDK as the location for all ODMA 1.0 material.

Open the ODMA 1.0 SDK package, oddev.zipIMPORTANT: Select action "Extract All".  This preserves the date-time stamps from the packaged files. Select the Use Folder Names option.  Specify the ODMA100-SDK subdirectory as the destination.

4.2 Usage

4.2.1 ODMA 1.0 Connection Managers

To test with the ODMA 1.0  Connection Manager for Win16, copy 

ODMA100-SDK\CONMAN\OUT16\ODMA.DLL

to Windows\System.

To test with the ODMA 1.0 Connection Manager for Win32, copy

ODMA100-SDK\CONMAN\OUT32\ODMA32.DLL

to Windows\System.

Add or change registry settings to have the desired DMS integrations as the defaults for ODMA. 

4.2.2 ODMA 1.0 MultODMA 

To use the Win16 ODMA 1.0 MultODMA application, run

ODMA100-SDK\MULTODMA\OUT16\MULTODMA.EXE.

To use the Win32 ODMA 1.0 MultODMA application, run

ODMA100-SDK\MULTODMA\OUT32\MULTODMA.EXE.

4.3 File Version Identifications

Table 3.  ODMA 1.0 SDK Components Used in Interoperability Testing
Name Size (bytes) Time Stamp
(
local time)
Edition Description
ODMA100-SDK\
CONMAN\

Subdirectory for all materials needed to install ODMA 1.0 or build ODMA-1.0-compliant components.
ODMA100-SDK\
CONMAN\OUT16\
ODMA.DLL

47616

1995-06-26-12:59

1.0.0-2 Win16 edition of ODMA 1.0 Connection Manager
ODMA100-SDK\
CONMAN\OUT32\
ODMA32.DLL

34304

1995-06-26-12:34

1.0.0-2 Win32 edition of ODMA 1.0 Connection Manager.
ODMA100-SDK\
DOC\
ODMA 1.0 Document Files, including README.TXT.
ODMA100-SDK\
MULTODMA
ODMA 1.0 MultODMA sample application with source code and executables
ODMA100-SDK\
MULTODMA\
OUT16\
MULTODMA.EXE

114516

1995-06-26-13:00

1.0.0-2 Win16 edition of MultODMA sample application
ODMA100-SDK\
MULTODMA\
OUT32\
MULTODMA.EXE

48640

1995-06-26-12:57

1.0.0-2 Win32 edition of MultODMA sample application
ODMA100-SDK\
ODMASAMP\
ODMA 1.0 ODMASAMP sample DMS integration with source code and .dll files.

Not all ODMA 1.0 SDK components are identified in this table.  Components not required for interoperability testing are omitted.

Dennis E. Hamilton
AIIM DMware Technical Coordinator
Renton, Washington, July 25, 2000


Version 0.14: 2000-09-11 (orcmid)
Separated from Q000703 as a free-standing FAQtip in its own right.  Something I should have figured out right away when I wanted to refer to it independently. 
Version 0.13: 2000-07-29 (orcmid)
Moved to odma/downloads area for ease in packaging with library materials and cross-referencing with that material via simple shortcuts.  Exploit location with downloads and libraries to have more shortcuts available to users.  Arrange for the file to work properly when downloaded as part of ODMA 2.0 Library materials.
Version 0.12: 2000-07-27 (orcmid)
Clean up shortcuts.  Make alignments in tables more consistent.
Version 0.11: 2000-07-26 (orcmid)
Clean up fonts in some of the table entries so they don't display too small.  Added more information about file names and the WinZip program used.
Version 0.10: 2000-07-25 (orcmid)
The initial setup was done to obtain crude confirmation of down-level interoperability.  This was verified as part of documenting the  ODMA 2.0 libraries.

created 2000-07-24-21:46 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 00-11-01 16:39 $
$$Revision: 10 $