Understanding The Three Levels Of Integration - Novell GROUPWISE 8 - LIBRARIES AND DOCUMENTS Manual

In that location, the GroupWise client user has sufficient rights to edit the file. The GroupWise
Windows client always checks the user-editable location first.
You might want to print the
integrations have been set up for your users during GroupWise client installation.
Section 24.2.1, "Understanding the Three Levels of Integration," on page 381
Section 24.2.2, "Understanding the gwappint.inf File," on page 382
Section 24.2.3, "Editing the gwappint.inf File," on page 385

24.2.1 Understanding the Three Levels of Integration

The file provides for three different levels of integration, to meet the needs of
gwappint.inf
different types of document-producing applications:
"ODMA Integration" on page 381
"Point-to-Point Integration" on page 381
"No Integration" on page 381
ODMA Integration
The Open Document Management API (ODMA) is an industry standard for applications and
document management programs to use in achieving seamless integration. ODMA is platform-
independent. GroupWise DMS is 32-bit ODMA-compliant, and can automatically integrate with all
32-bit ODMA-compliant applications. Applications that are not 32-bit ODMA-compliant must have
integrations created for them to be used with GroupWise DMS.
Point-to-Point Integration
This integration involves applications that are not 32-bit ODMA-compliant. Novell
macros for various applications, such as Microsoft Word, which allow them to be integrated with
GroupWise. This provides the same functionality as for 32-bit ODMA-integrated applications.
These applications can be selected for integration when the GroupWise client is installed.
Integration macros are written in the macro language of the application being integrated with
GroupWise. Macro calls are made to GroupWise dialog boxes to replace access of the application's
own dialog boxes (for example, Open and Save).
No Integration
Non-integrated applications rely on Windows associations. When a reference icon is selected in
GroupWise, the file's extension is examined to determine which application to use. The application
is launched and the file is opened.
Functions performed in a non-integrated application are not managed by GroupWise. So, if the file
is renamed or saved to a different location, the file is not part of a GroupWise library. When the file
is opened later, a message is displayed reminding the user that the file is not under management of
GroupWise. However, if you simply edit the file and re-save it without changing the name or
location, GroupWise continues to provide management of the file.
file from a user workstation to help you understand how
gwappint.inf
®
has written
Integrations 381