5.4 Preparing Your ACUCOBOL-GT Application for the Plug-in

Web Plug-ins are significantly different from standard ACUCOBOL-GT runtimes in the following way:

Web Plug-ins are invoked to process a single file.

In the case of the ACUCOBOL-GT Web Plug-in, that file can be

• a library file that "packages" all of the objects and bitmap resources of your application into a single file. The library file can contain a configuration file if desired. It can also contain extended file descriptors (".xfd" files) for use with Acu4GL.

• the initial object of your COBOL application, with the remaining objects residing on a server. (This approach requires the use of AcuServer or AcuConnect technologies.)

The procedure for preparing your application for use with the plug-in runtime depends on whether you will be deploying your application in a distributed or non-distributed environment.

More:

To prepare your application for use in a non-distributed environment

To prepare your application for use in a distributed environment

5.4.1 Coding for the Plug-in

5.4.1.1 W$BROWSERINFO library routine

5.4.1.2 W$STATUS library routine

5.4.1.3 IS-PLUGIN field in ACUCOBOL.DEF

5.4.1.4 W$GETURL library routine

5.4.1.5 Other coding considerations

5.4.2 Configuring the Plug-in Runtime

5.4.2.1 Using runtime options

5.4.3 Linking C Routines Into the Plug-in Runtime

5.4.4 Packaging Your Application and Resources

5.4.4.1 Using cblutil

5.4.4.2 Using COPY RESOURCE