ContentsIndexPreviousNext

4.3 Creating a Client Configuration File

Once you have installed your client applications on the client(s), you must create a special configuration file that tells AcuConnect the location of the remote application component, the runtime flags to use when running the remote application (if any), and the runtime configuration file to use. This file can be named anything, but for clarity, it is called "client.cfg" throughout this book. The client configuration file should be placed in the /etc or \etc directory on the client or specified using the "-c" command line option.

When AcuConnect is shipped, it includes a sample "client.cfg" file. If you want to install this sample file on your client machine(s), you may do so. This may be a good starting point for creating and modifying your own file.

The "client.cfg" file can contain any standard configuration file variable defined in the ACUCOBOL-GT User's Guide (for instance, CODE-SUFFIX, ACUCOBOL, SERVER-PORT and TEXT). In addition, it can contain any of several AcuConnect-specific variables discussed in this section.


Note: Many of these variables are used to specify the location of remote programs and files. You can use either IP addresses or server names in the "client.cfg" file.
More:

4.3.1 Defining Remote Application Path

4.3.1.1 CODE-PREFIX

4.3.1.2 Code Name Aliases

4.3.2 Other Variables

4.3.2.1 ACUCONNECT-RUNTIME-FLAGS

4.3.2.2 ACUCONNECT-CONFIGURATION-FILE

4.3.2.3 ACUCONNECT-CLOSE-AFTER-CANCEL

4.3.2.4 DEFAULT-MAP-FILE

4.3.2.5 server-MAP-FILE

4.3.2.6 SERVER-PORT

4.3.2.7 TEXT

4.3.3 Sample "client.cfg" file