Novell GROUPWISE 7 - LIBRARIES AND DOCUMENTS Manual page 76

Libraries and documents
Table of Contents

Advertisement

[executable_name] Sections
The gwappint.inf file contains one [executable_name] section for each integrated application. It
supplies the name of the executable for the program being integrated.
Integration= Line
Each [executable_name] section must have an Integration= line, where digits identify the type of
integration employed for the executable:
Integration = 0
Integration = 1
Integration = 2
DualExe= Line
Some programs, such as Lotus Word Pro, use a small startup executable that, in turn, calls the main
program. Use the DualExe= line to specify the name of the main executable. You can specify the full
path to the main executable, or you can specify the path relative to the startup executable.
AppName= Line
The AppName= line assigns the application an arbitrary name for use in the
Extensions]
AppKey= Line
The AppKey= line is used only with point-to-point integrations (Integration=1). It specifies a value
used by GroupWise to pass information to and from the integrated application. The value must be
unique among the point-to-point integrations defined in the gwappint.inf file.
Examples Based on Standard Integrations
The table below shows how the standard integrations are implemented in the gwappint.inf file:
366 GroupWise 7 Administration Guide
-
AppKey= line
[ODMA Application Extensions] section
[Integration State] section
[Non-Integrated Defaults] section
-
WaitInterval= line
-
ShowMessage= line
(No
Integration)
(Point-to-Point
(ODMA
Integration)
and
[Integration State]
Integration)
sections.
[ODMA Application

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the GROUPWISE 7 - LIBRARIES AND DOCUMENTS and is the answer not in the manual?

This manual is also suitable for:

Groupwise 7 dms

Table of Contents