Q060601 ODMA FAQtip Confirming ODMA-Aware Connection

ODMA>faq> 2006>06> Q060601> 0.10 2007-07-28 -11:14 -0700

Every ODMA-aware application is expected to operate as an ordinary application when ODMA is not installed.  When the ODMA Connection Manager is installed, ODMA-aware applications are expected to dynamically register with it.  If  registration is unsuccessful, the application must also behave as if ODMA is not present at all.  Successful end-to-end discovery of ODMA availability by an ODMA-aware application is the first confirmation that an application is properly connecting with ODMA.

This confirmation procedure is useful for troubleshooting an application's integration with ODMA.  It serves as the first end-to-end test case for progressive development of software for an ODMA-aware application.  The basic approach is summarized below.  Technical details are on the procedure page.

1. Summary
2. Further Information

1. Summary

1.1 This FAQtip provides a procedure for verifying that an ODMA-Aware application is successfully detecting and connecting with the ODMA Connection Manager.

1.2 The procedure confirms the following scenario:

• 1.2.1 ODMA-aware applications on the desktop are expected to automatically detect the presence of the ODMA Connection Manager. 
     
• 1.2.2 When the Connection Manager is present, the ODMA-aware application is expected register itself with ODMA prior to its first need to determine the location of a document, whether to open an existing one or to store a new one.
    
• 1.2.3 If the Connection Manager refuses to accept the registration of the ODMA-aware application, it typically means that there is no Document Management System (DMS) that is available as the default ODMA DMS for this application.  The application is expected to silently ignore the presence of the ODMA Connection Manager and to operate on the local system as if there is no ODMA presence.
    
• 1.2.4 The procedure described here confirms that a registration is requested, that it is denied by ODMA, and that the application proceeds as it would were ODMA not present at all.

1.3 Once this much is accomplished, other confirmations of ODMA operation can be undertaken using a default DMS and ODMA Connection Manager logs.  {tbd: Add links to those FAQs here or in the extended text.  Link to the appropriate place from here.}

{tbd: There will be a link to documentation on how a default ODMA DMS is determined for each application, either a global default or a specific default for the particular application.  There is an administration procedure for controlling the use of default DMS integrations on an application-by-application basis.   

For DMS Developers there will be a link to procedures for detecting that there is an ODMA Connection Manager and when there is, linking to it in a safe way.  This will be developed as part of the ODMrun10 tool project under ODMdev.}

2. Further Information

• Q061001b: Confirming ODMA-Aware Connection (latest)
• Q051001c: Confirming ODMA-Aware Connection - Procedure 0.10
• Q051001a: Confirming ODMA-Aware Connection - Diary & Job Jar

Revision History:
0.10 2006-06-18-15:39 Provide Summary for Initial Review

The summary sets the stage for the progressive refinement of the detailed procedure from its initial-review version 0.10.

0.00 2006-06-14-12:09 Establish Placeholder for Pending Material

Also start a job jar page for recording work items for building more content.  This page is a customization of the TROST InfoNote Bootstrap Template 0.20 template.  A version from TROST Develop InfoNote Bootstrap Template 0.20 Material was used.