AcuConnect Configuration Files

AcuConnect uses three separate configuration files to differentiate client and server processes:

1. Client configuration file (e.g., "client.cfg ")

2. Server configuration file (e.g., "server.cfg ")

3. Runtime configuration file for the remote application component (e.g., "cblconfig ")

NOTE: Throughout this book, the names, "client.cfg", "server.cfg", and "cblconfig" are used to distinguish the configuration file types; however, these names are arbitrary. In reality, you can name the AcuConnect configuration files anything you like.

Client configuration file

The client configuration file, called "client.cfg" for illustrative purposes, is where you specify the remote server path and runtime flags for the server program. It is also where you specify the name of a runtime configuration file to be used when AcuConnect launches the remote application. The following configuration file variables are typically included in the file: CODEPREFIX , ACUCONNECT-RUNTIME-FLAGS , ACUCONNECT-CONFIGURATION-FILE , and ACUCONNECT-CLOSE-AFTER-CANCEL , along with any other ACUCOBOL-GT configuration file variables you choose.

Server configuration file

The server configuration file, called "server.cfg" in this book, is a configuration file for the AcuConnect daemon on the server. In this file, you specify the location of the "AcuAccess " security file, define the default user, and supply information about passwords and password attempts.

Runtime configuration file for remote application

The last configuration file, referred to as "cblconfig" in this book, is the runtime configuration file for the application started on the server--the remote application. This is like any other ACUCOBOL-GT runtime configuration file. It runs along with the remote application and defines how the application should behave. It is totally optional.