GroupWise Can’t
Monitor a Non-Integrated Application
Problem:
The user edits a document and the GroupWise Windows client
indicates the application cannot be monitored. Therefore, the user
must return the document to the GroupWise library manually.
Explanation:
The manner in which the GroupWise client monitors applications
can be modified using settings in the gwappint.inf file, located
in the \windows\system directory.
This file contains information about integrating applications and
monitoring non-integrated applications that are started from the
GroupWise client.
Possible Cause:
Some applications, such as WordPerfect* 7.0 and Lotus* Word
Pro 96, are integrated through ODMA. Other applications, such as
Microsoft* Word 7.0 and Excel 7.0, are integrated through
application macros. If an integrated application is not set up correctly,
it is handled as a non-integrated application.
Normally, Setup detects if an application is installed and
then allows the user to choose whether or not to have integrations
installed for that application. If the application setup didn’t
run correctly, the GroupWise client might not detect that the integration
installed. If necessary, integrations can be installed manually.
Action:
For ODMA applications, the gwappint.inf file needs to contain
an Integrations=2 entry for the application.
In addition, the following DLL programs are copied to the \windows\system directory
when Setup is run: odma32.dll, gwodm132.dll,
and gwodm1xx.dll.
The name of the gwodm1xx.dll depends
on which language was selected when Setup was run.
Action:
For applications that use an integration macro, the gwappint.inf file
needs to contains an Integrations=1 entry
for the application. There should also be an integration macro installed
in the application’s macro startup directory.
Possible Cause:
For non-integrated applications, the GroupWise client attempts
to monitor when an application terminates so open documents can
be returned to the GroupWise library automatically. If the GroupWise
client wasn’t able to determine the information needed
to monitor the application termination, the user is instructed to
return documents manually.
Action:
Return documents manually. Save and exit each document. In
the GroupWise client, right-click each document reference, then
click .
Possible Cause:
Some applications do not start quickly enough for the GroupWise
client to detect that they have started.
Action:
You can change the amount of time the GroupWise client allows
for the application to start using the WaitInterval setting.
Action:
If problems persists, you can turn off the message for the
application. Use ShowMessage=0 in the gwappint.inf file
to turn off the message.
Action:
See the gwappint.inf file in the \windows\system directory
for more information.