The flow of typical CGI implementation is as follows:
Note that this diagram shows the CGI program and ACUCOBOL-GT application as separate components. In many instances, you may choose to add CGI functions directly to your COBOL application, making them one in the same thing.
In addition, any and all connectivity options available to extend customers can be applied in the third step if desired. For instance, the CGI program can CALL a remote program using the AcuConnect® application server for connectivity. Likewise, the CGI program or CALLed program can access any file system or database that we support to perform a lookup. If the file system resides on another machine, the program can use the AcuServer® remote file server to achieve access. If a relational database access is desired, the Acu4GL® interface or AcuSQL® precompiler can be used to translate the request into SQL.
The CGI method is best suited for programs that do not use a user interface (UI) based on COBOL DISPLAY/ACCEPT statements–for instance, programs with a Web interface, batch processes, processes that use socket routines to communicate with an external UI, component adapter technology processes, and BEA Tuxedo processes.